SMB security hardening
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit 4c78bb4 · +1 −1 lines · also on GitHub
⋯ 102 unchanged lines
103103
104104
SMB over QUIC client access control enables you to limit which clients can access SMB over QUIC servers. The previous behavior allowed connection attempts from any client that trusted the QUIC server's certificate issuance chain. With client access control, an *allowlist* and *blocklist* are created for devices to connect to the file server.
105105
106
−A client must now have its own certificate and be on an **allowlist* to establish the QUIC connection before any SMB connection can occur. Client access control provides organizations with added protection without altering the authentication used during the SMB connection, and the user experience remains unaffected. Additionally, you can disable the SMB over QUIC client entirely or only allow connections to specific servers.
106
+A client must now have its own certificate and be on an *allowlist* to establish the QUIC connection before any SMB connection can occur. Client access control provides organizations with added protection without altering the authentication used during the SMB connection, and the user experience remains unaffected. Additionally, you can disable the SMB over QUIC client entirely or only allow connections to specific servers.
107107
108108
To learn more, see:
109109
⋯ 27 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/windowsserverdocs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 09:24 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.