HighOS hardeningBLWK-WIN-007

SMBv1 is enabled

What this means

SMBv1 is the obsolete file-sharing protocol behind WannaCry and NotPetya. Nothing modern needs it.

How to fix it

Run Set-SmbServerConfiguration -EnableSMB1Protocol $false in an elevated PowerShell, or remove the SMB 1.0/CIFS File Sharing Support Windows feature.

Check it yourself

Run a scan and look for BLWK-WIN-007 in the results:

bulwark scan

Installed the standalone CLI package instead of the app? The command is bulwarkctl.

How Bulwark decides

Bulwark reads windows_security and reports this check when:

smb1_enabled_known == true and smb1_enabled == true

If a value can't be read, Bulwark reports the check as undetermined rather than passing it. View the rule source.

References

• MITRE ATT&CK T1210

Related checks

• Cron entry runs a downloader piped to a shell · BLWK-ACCT-001
• Password maximum age is excessively long · BLWK-ACCT-002
• Password minimum age is zero · BLWK-ACCT-003
• Password hashing rounds are not explicitly configured · BLWK-ACCT-004
• Default UMASK is not explicitly configured · BLWK-ACCT-005
• A sensitive system file is world-writable · BLWK-FS-001