SMBv1 = ANCIENT + BROKEN (1983): Security: No encryption, no integrity checks, no mutual authentication, Vulnerabilities: EternalBlue (NSA exploit, leaked 2017) โ WannaCry, NotPetya ransomware, Active exploitation: SMBv1 still targeted (easy attacks), Modern: SMBv2/v3 (encryption, signing, performance). Microsoft: 'SMBv1 should be disabled' (official guidance 2017+).
PowerShell Modules Vereist
Primary API: Microsoft Graph API Connection:Connect-MgGraph Required Modules: Microsoft.Graph.DeviceManagement
Implementatie
Disable SMBv1 client: Policy: SMB v1 client driver: Disabled, Effect: Windows CANNOT connect to SMBv1 shares (SMBv2/v3 only), Legacy devices: Upgrade to SMBv2+ OR isolate (risk acceptance), Compatibility: 99% of modern NAS/file servers support SMBv2/v3.
Microsoft Security Baseline, CIS Windows Benchmark L1, BIO 12.01, ISO 27001 A.13.1.3.
Monitoring
Gebruik PowerShell-script configure-smb-v1-client-driver-is-set-to-enabled-disable-driver-recommended.ps1 (functie Invoke-Monitoring) โ Controleren.
Remediatie
Gebruik PowerShell-script configure-smb-v1-client-driver-is-set-to-enabled-disable-driver-recommended.ps1 (functie Invoke-Remediation) โ Herstellen.
Compliance & Frameworks
CIS M365: Control Windows - SMBv1 (L1) -
BIO: 12.01.01 -
ISO 27001:2022: A.13.1.3 -
Automation
Gebruik het onderstaande PowerShell script om deze security control te monitoren en te implementeren. Het script bevat functies voor zowel monitoring (-Monitoring) als remediation (-Remediation).