Skip to content

Device checks

Lookout runs these 41 read-only checks on every Windows device. Each one maps to the requirements it helps prove in every standard Trimtab supports. Thresholds marked default can be adjusted to match your policy.

ID Check Severity Standards
ENC-001 BitLocker protects all fixed drives High CMMC L2, HIPAA, CIS IG1, FTC, NIST CSF, NYDFS, Reg S-P, SOC 2, Insurance
ENC-002 TPM is present and ready Medium CMMC L2, CIS IG1, FTC, NIST CSF, NYDFS, Reg S-P, SOC 2, Insurance
ENC-003 Secure Boot is enabled Medium CMMC L2, CIS IG1, FTC, NIST CSF, NYDFS, Reg S-P, SOC 2, Insurance
AV-001 Antivirus real-time protection is active High CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
AV-002 Antivirus signatures are current High CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
AV-003 Defender tamper protection is on Medium CMMC L2, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
AV-004 Attack surface reduction rules are configured Medium CMMC L2, CMMC L1, FTC, NIST CSF, NYDFS, Reg S-P, SOC 2, Insurance
FW-001 Windows Firewall is on for all profiles High CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
ACC-001 No standing local admin rights for user accounts High CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
ACC-002 Guest account is disabled Medium CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
ACC-003 Built-in Administrator account is disabled Low CMMC L2, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
ACC-004 Account lockout threshold is set High CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
ACC-005 Minimum password length is enforced Medium CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
ACC-006 Password complexity is required Medium CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
ACC-007 Password history prevents reuse Low CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
ACC-008 Local admin password is managed (LAPS) Medium CMMC L2, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
ACC-009 User Account Control is enabled High CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
SES-001 Screen locks after inactivity Medium CMMC L2, HIPAA, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
SES-002 Logon banner is displayed Low CMMC L2, NIST CSF
SES-003 Remote Desktop requires Network Level Authentication High CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
HRD-001 SMBv1 is disabled High CMMC L2, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
HRD-002 LLMNR is disabled Medium CMMC L2, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
HRD-003 NetBIOS over TCP/IP is disabled Low CMMC L2, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
HRD-004 AutoRun is disabled for all drives Medium CMMC L2, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
HRD-005 Removable storage is restricted Medium CMMC L2, FTC, NIST CSF, NYDFS, Reg S-P, SOC 2
HRD-006 FIPS-compliant algorithms are enforced Low CMMC L2, NIST CSF, PCI DSS, NYDFS, SOC 2
HRD-007 LSA protection is enabled Medium CMMC L2, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
HRD-008 Credential Guard is running Medium CMMC L2, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
HRD-009 WDigest does not cache plaintext credentials High CMMC L2, HIPAA, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
AUD-001 Key audit subcategories are enabled High CMMC L2, HIPAA, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
AUD-002 Security event log is large enough Medium CMMC L2, HIPAA, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
AUD-003 PowerShell script block logging is on Medium CMMC L2, HIPAA, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
AUD-004 Process creation events include command line Low CMMC L2, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
AUD-005 Time synchronization is running Low CMMC L2, FTC, NIST CSF, PCI DSS, NYDFS, SOC 2, Insurance
PAT-001 Updates installed recently High CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
PAT-002 No reboot pending Low CMMC L2, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
PAT-003 Operating system is supported High CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
AV-005 Antivirus scans run regularly Medium CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
PAT-004 Automatic updates are on Medium CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
HRD-010 Legacy TLS and SSL are turned off Medium CMMC L2, HIPAA, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, Reg S-P, SOC 2, Insurance
MGT-001 Device is centrally managed Medium CMMC L2, CMMC L1, CIS IG1, FTC, NIST CSF, PCI DSS, NYDFS, SOC 2

Encryption

BitLocker protects all fixed drives (ENC-001)

High Encryption

Fix: Enable BitLocker with TPM protector on the OS drive and all fixed data drives, and escrow the recovery key.

Take the helm: step-by-step
  1. For many devices, use Intune: Endpoint security → Disk encryption → create a BitLocker policy that encrypts OS and fixed drives and backs up recovery keys to Entra ID.
  2. On a single device, open an elevated PowerShell and run Enable-BitLocker -MountPoint C: -EncryptionMethod XtsAes256 -TpmProtector.
  3. Add a recovery password with Add-BitLockerKeyProtector -MountPoint C: -RecoveryPasswordProtector and back it up with BackupToAAD-BitLockerKeyProtector (Entra ID) or Backup-BitLockerKeyProtector (Active Directory) before restarting.
  4. Repeat for each fixed data drive, then confirm with Get-BitLockerVolume.
  5. Windows Home has no full BitLocker. Turn on Settings → Privacy & security → Device encryption, signed in with a Microsoft account so the recovery key is saved there. If that setting is missing, upgrade to Windows Pro.

Maps to:

  • SC.L2-3.13.16 Protect the confidentiality of CUI at rest. BitLocker scrambles everything on the drive, so a lost or stolen computer can't be read without the key.
  • 164.312(a)(2)(iv) Encryption and decryption. BitLocker scrambles everything on the drive, so a lost or stolen computer can't be read without the key.
  • 3.6 Encrypt Data on End-User Devices. BitLocker scrambles everything on the drive, so a lost or stolen computer can't be read without the key.
  • 314.4(c)(3) Encryption. BitLocker scrambles everything on the drive, so a lost or stolen computer can't be read without the key.
  • PR.DS-01 Data at rest protected. BitLocker scrambles everything on the drive, so a lost or stolen computer can't be read without the key.
  • 500.15(a) Encryption. BitLocker scrambles everything on the drive, so a lost or stolen computer can't be read without the key.
  • 248.30(a)(2)(i) Security and confidentiality of customer information. BitLocker scrambles everything on the drive, so a lost or stolen computer can't be read without the key.
  • CC6.1 Logical access security. BitLocker scrambles everything on the drive, so a lost or stolen computer can't be read without the key.
  • CC6.7 Controlling how data leaves. BitLocker scrambles everything on the drive, so a lost or stolen computer can't be read without the key.
  • CI-10 Encrypted laptops. BitLocker scrambles everything on the drive, so a lost or stolen computer can't be read without the key.

TPM is present and ready (ENC-002)

Medium Encryption

Fix: Enable the TPM in firmware and initialize it.

Take the helm: step-by-step
  1. Restart into the firmware setup (often F2, F10, or Del during boot).
  2. Enable the TPM. It may be called Intel PTT or AMD fTPM. Save and exit.
  3. Back in Windows, run Get-Tpm and confirm TpmPresent and TpmReady are True. If it isn't ready, run Initialize-Tpm.
  4. If the device has no TPM, plan a replacement. Windows 11 requires TPM 2.0.

Maps to:

  • SC.L2-3.13.16 Protect the confidentiality of CUI at rest. The TPM chip safely holds the BitLocker key, so drive encryption is strong without users typing an extra password.
  • CM.L2-3.4.2 Establish and enforce security configuration settings. A working TPM is part of the secure standard setup for modern Windows computers.
  • 3.6 Encrypt Data on End-User Devices. The TPM chip safely holds the BitLocker key, so drive encryption is strong without users typing an extra password.
  • 314.4(c)(3) Encryption. The TPM chip safely holds the BitLocker key, so drive encryption is strong without users typing an extra password.
  • PR.DS-01 Data at rest protected. The TPM chip safely holds the BitLocker key, so drive encryption is strong without users typing an extra password.
  • 500.15(a) Encryption. The TPM chip safely holds the BitLocker key, so drive encryption is strong without users typing an extra password.
  • 248.30(a)(2)(i) Security and confidentiality of customer information. The TPM chip safely holds the BitLocker key, so drive encryption is strong without users typing an extra password.
  • CC6.1 Logical access security. The TPM chip safely holds the BitLocker key, so drive encryption is strong without users typing an extra password.
  • CI-10 Encrypted laptops. The TPM chip safely holds the BitLocker key, so drive encryption is strong without users typing an extra password.

Secure Boot is enabled (ENC-003)

Medium Encryption

Fix: Switch firmware to UEFI mode and enable Secure Boot.

Take the helm: step-by-step
  1. If BitLocker is on, suspend it for one restart first: Suspend-BitLocker -MountPoint C: -RebootCount 1.
  2. Check the disk style with Get-Disk. If it's MBR, back up and convert it with mbr2gpt /convert /allowFullOS.
  3. In the firmware setup, switch the boot mode to UEFI (turn off CSM or Legacy) and enable Secure Boot.
  4. Confirm in Windows with Confirm-SecureBootUEFI.

Maps to:

  • CM.L2-3.4.2 Establish and enforce security configuration settings. Secure Boot makes sure only trusted software loads when the computer starts, blocking malware that hides below Windows.
  • 4.1 Establish and Maintain a Secure Configuration Process. Secure Boot makes sure only trusted software loads when the computer starts, blocking malware that hides below Windows.
  • 314.4(c) Safeguards that control identified risks. Secure Boot makes sure only trusted software loads when the computer starts, blocking malware that hides below Windows.
  • PR.PS-01 Configuration management. Secure Boot makes sure only trusted software loads when the computer starts, blocking malware that hides below Windows.
  • 500.3(g) Systems and network security. Secure Boot makes sure only trusted software loads when the computer starts, blocking malware that hides below Windows.
  • 248.30(a)(2)(ii) Protection against anticipated threats. Secure Boot makes sure only trusted software loads when the computer starts, blocking malware that hides below Windows.
  • CC6.8 Preventing malicious software. Secure Boot makes sure only trusted software loads when the computer starts, blocking malware that hides below Windows.
  • CI-09 Hardened configuration. Secure Boot makes sure only trusted software loads when the computer starts, blocking malware that hides below Windows.

Malware Protection

Antivirus real-time protection is active (AV-001)

High Malware Protection

Fix: Enable Defender real-time protection or confirm a third-party AV is installed and running.

Take the helm: step-by-step
  1. Microsoft Defender: Windows Security → Virus & threat protection → Manage settings → turn on Real-time protection, or run Set-MpPreference -DisableRealtimeMonitoring $false.
  2. Check that no Group Policy or Intune setting turns Defender off (Administrative Templates → Windows Components → Microsoft Defender Antivirus).
  3. Third-party antivirus: open its console, confirm the device's agent is installed and protecting, and reinstall the agent if it shows offline.

Maps to:

  • SI.L2-3.14.2 Provide protection from malicious code. Active antivirus is the main protection against malicious code on the computer.
  • SI.L2-3.14.5 Perform periodic and real-time scans. Real-time antivirus checks files the moment they arrive or open, stopping malware before it runs.
  • 164.308(a)(5)(ii)(B) Protection from malicious software. Real-time antivirus checks files the moment they arrive or open, stopping malware before it runs.
  • SI.L1-B.1.XIII Protect against malicious code. Active antivirus is the main protection against malicious code on the computer.
  • SI.L1-B.1.XV Scan systems and files. Real-time antivirus checks files the moment they arrive or open, stopping malware before it runs.
  • 10.1 Deploy and Maintain Anti-Malware Software. Real-time antivirus checks files the moment they arrive or open, stopping malware before it runs.
  • 314.4(c) Safeguards that control identified risks. Antivirus is a basic safeguard against one of the most common risks: malware.
  • 314.4(d)(1) Test and monitor safeguards. Antivirus watches for attacks all the time, so attempted intrusions get noticed.
  • PR.PS-05 Unauthorized software prevented. Real-time antivirus checks files the moment they arrive or open, stopping malware before it runs.
  • DE.CM-09 Computing monitored. Real-time antivirus checks files the moment they arrive or open, stopping malware before it runs.
  • 5.2.1 Anti-malware deployed. Real-time antivirus checks files the moment they arrive or open, stopping malware before it runs.
  • 5.3.2 Anti-malware scans or real-time protection. Real-time antivirus checks files the moment they arrive or open, stopping malware before it runs.
  • 500.14(a)(2) Protection against malicious code. Real-time antivirus checks files the moment they arrive or open, stopping malware before it runs.
  • 248.30(a)(2)(ii) Protection against anticipated threats. Real-time antivirus checks files the moment they arrive or open, stopping malware before it runs.
  • CC6.8 Preventing malicious software. Real-time antivirus checks files the moment they arrive or open, stopping malware before it runs.
  • CI-03 Endpoint protection on every device. Real-time antivirus checks files the moment they arrive or open, stopping malware before it runs.

Antivirus signatures are current (AV-002)

High Malware Protection

Fix: Confirm the device can reach update sources and run a signature update.

Default thresholds: Maximum signature age (days) = 3

Take the helm: step-by-step
  1. Update now with Update-MpSignature (Defender) or the update action in your antivirus console.
  2. Make sure the device can reach its update source and that no proxy or firewall blocks it.
  3. Confirm the signatures are current with Get-MpComputerStatus | Select-Object AntivirusSignatureAge.

Maps to:

  • SI.L2-3.14.4 Update malicious code protection mechanisms. Antivirus only catches threats it knows about. Current definitions mean it recognizes the newest malware.
  • 164.308(a)(5)(ii)(B) Protection from malicious software. Antivirus only catches threats it knows about. Current definitions mean it recognizes the newest malware.
  • SI.L1-B.1.XIV Keep malware protection updated. Antivirus only catches threats it knows about. Current definitions mean it recognizes the newest malware.
  • 10.2 Configure Automatic Anti-Malware Signature Updates. Antivirus only catches threats it knows about. Current definitions mean it recognizes the newest malware.
  • 314.4(c) Safeguards that control identified risks. Antivirus only catches threats it knows about. Current definitions mean it recognizes the newest malware.
  • PR.PS-05 Unauthorized software prevented. Antivirus only catches threats it knows about. Current definitions mean it recognizes the newest malware.
  • 5.3.1 Anti-malware kept current. Antivirus only catches threats it knows about. Current definitions mean it recognizes the newest malware.
  • 500.14(a)(2) Protection against malicious code. Antivirus only catches threats it knows about. Current definitions mean it recognizes the newest malware.
  • 248.30(a)(2)(ii) Protection against anticipated threats. Antivirus only catches threats it knows about. Current definitions mean it recognizes the newest malware.
  • CC6.8 Preventing malicious software. Antivirus only catches threats it knows about. Current definitions mean it recognizes the newest malware.
  • CI-03 Endpoint protection on every device. Antivirus only catches threats it knows about. Current definitions mean it recognizes the newest malware.

Defender tamper protection is on (AV-003)

Medium Malware Protection

Fix: Turn on tamper protection through Intune, Defender for Endpoint, or Windows Security.

Take the helm: step-by-step
  1. For all devices, turn on tamper protection in the Microsoft Defender portal (Settings → Endpoints → Advanced features) or with an Intune Endpoint security → Antivirus policy.
  2. On a single unmanaged device: Windows Security → Virus & threat protection → Manage settings → Tamper Protection: On.
  3. Confirm with Get-MpComputerStatus | Select-Object IsTamperProtected.

Maps to:

  • SI.L2-3.14.2 Provide protection from malicious code. Tamper protection stops malware, or a user, from switching antivirus off, so the protection stays in place.
  • SI.L1-B.1.XIII Protect against malicious code. Tamper protection stops malware, or a user, from switching antivirus off, so the protection stays in place.
  • 10.1 Deploy and Maintain Anti-Malware Software. Tamper protection stops malware, or a user, from switching antivirus off, so the protection stays in place.
  • 314.4(c) Safeguards that control identified risks. Tamper protection stops malware, or a user, from switching antivirus off, so the protection stays in place.
  • PR.PS-05 Unauthorized software prevented. Tamper protection stops malware, or a user, from switching antivirus off, so the protection stays in place.
  • 5.3.5 Anti-malware can't be disabled by users. Tamper protection stops malware, or a user, from switching antivirus off, so the protection stays in place.
  • 500.14(a)(2) Protection against malicious code. Tamper protection stops malware, or a user, from switching antivirus off, so the protection stays in place.
  • 248.30(a)(2)(ii) Protection against anticipated threats. Tamper protection stops malware, or a user, from switching antivirus off, so the protection stays in place.
  • CC6.8 Preventing malicious software. Tamper protection stops malware, or a user, from switching antivirus off, so the protection stays in place.
  • CI-03 Endpoint protection on every device. Tamper protection stops malware, or a user, from switching antivirus off, so the protection stays in place.

Attack surface reduction rules are configured (AV-004)

Medium Malware Protection

Fix: Deploy the standard ASR rule set in Block mode after an Audit period.

Default thresholds: Minimum ASR rules in Block mode = 5

Take the helm: step-by-step
  1. In Intune, create an Endpoint security → Attack surface reduction policy with the standard rules set to Audit.
  2. Review what would have been blocked in the Defender portal (Reports → Attack surface reduction rules) for one to two weeks.
  3. Switch the rules to Block, adding exclusions only where a business app needs one.
  4. On a single device: Add-MpPreference -AttackSurfaceReductionRules_Ids <rule GUID> -AttackSurfaceReductionRules_Actions Enabled.

Maps to:

  • SI.L2-3.14.2 Provide protection from malicious code. Attack surface reduction rules block tricks malware relies on, like Office documents launching programs.
  • CM.L2-3.4.2 Establish and enforce security configuration settings. These rules are part of Microsoft's recommended secure setup for Windows.
  • SI.L1-B.1.XIII Protect against malicious code. Attack surface reduction rules block tricks malware relies on, like Office documents launching programs.
  • 314.4(c) Safeguards that control identified risks. Attack surface reduction rules block tricks malware relies on, like Office documents launching programs.
  • PR.PS-05 Unauthorized software prevented. Attack surface reduction rules block tricks malware relies on, like Office documents launching programs.
  • 500.14(a)(2) Protection against malicious code. Attack surface reduction rules block tricks malware relies on, like Office documents launching programs.
  • 248.30(a)(2)(ii) Protection against anticipated threats. Attack surface reduction rules block tricks malware relies on, like Office documents launching programs.
  • CC6.8 Preventing malicious software. Attack surface reduction rules block tricks malware relies on, like Office documents launching programs.
  • CI-03 Endpoint protection on every device. Attack surface reduction rules block tricks malware relies on, like Office documents launching programs.

Antivirus scans run regularly (AV-005)

Medium Malware Protection

Fix: Schedule at least a weekly quick scan in Microsoft Defender (or your antivirus) and confirm it completes.

Default thresholds: maxDaysSinceScan = 7

Take the helm: step-by-step
  1. Run a scan now to confirm scanning works: Start-MpScan -ScanType QuickScan.
  2. For many devices, use Intune: Endpoint security → Antivirus → Microsoft Defender Antivirus policy → set a daily quick scan time. Or use Group Policy: Computer Configuration → Administrative Templates → Windows Components → Microsoft Defender Antivirus → Scan → Specify the time for a daily quick scan.
  3. On a single device, set a daily quick scan with Set-MpPreference -ScanScheduleQuickScanTime 12:00:00.
  4. Confirm with Get-MpComputerStatus | Select-Object QuickScanAge, FullScanAge (days since each scan).
  5. If you use a third-party antivirus, schedule scans in its console. Lookout reports this check as not applicable for third-party products.

Maps to:

  • SI.L2-3.14.5 Perform periodic and real-time scans. Regular scans find malware that slipped past real-time protection or arrived before definitions were updated.
  • 164.308(a)(5)(ii)(B) Protection from malicious software. Regular scans find malware that slipped past real-time protection or arrived before definitions were updated.
  • SI.L1-B.1.XV Scan systems and files. Regular scans find malware that slipped past real-time protection or arrived before definitions were updated.
  • 10.1 Deploy and Maintain Anti-Malware Software. Regular scans find malware that slipped past real-time protection or arrived before definitions were updated.
  • 314.4(d)(1) Test and monitor safeguards. Scheduled scans regularly test whether anything malicious is already on the computer.
  • DE.CM-09 Computing monitored. Regular scans find malware that slipped past real-time protection or arrived before definitions were updated.
  • 5.3.2 Anti-malware scans or real-time protection. Regular scans find malware that slipped past real-time protection or arrived before definitions were updated.
  • 500.14(a)(2) Protection against malicious code. Regular scans find malware that slipped past real-time protection or arrived before definitions were updated.
  • 248.30(a)(2)(ii) Protection against anticipated threats. Regular scans find malware that slipped past real-time protection or arrived before definitions were updated.
  • CC6.8 Preventing malicious software. Regular scans find malware that slipped past real-time protection or arrived before definitions were updated.
  • CC7.2 Monitoring for attacks. Regular scans find malware that slipped past real-time protection or arrived before definitions were updated.
  • CI-03 Endpoint protection on every device. Regular scans find malware that slipped past real-time protection or arrived before definitions were updated.

Network

Windows Firewall is on for all profiles (FW-001)

High Network

Fix: Enable the firewall for Domain, Private, and Public profiles with inbound default set to Block.

Take the helm: step-by-step
  1. Turn on the firewall for every profile: Set-NetFirewallProfile -Profile Domain,Private,Public -Enabled True -DefaultInboundAction Block.
  2. For many devices, use Intune (Endpoint security → Firewall) or Group Policy (Security Settings → Windows Defender Firewall with Advanced Security).
  3. Make sure no policy turns it back off: Get-NetFirewallProfile -PolicyStore ActiveStore.

Maps to:

  • SC.L2-3.13.1 Monitor, control, and protect communications at system boundaries. The firewall controls what network traffic can reach the computer, on every network it joins.
  • SC.L2-3.13.6 Deny network communications traffic by default. With the firewall on, incoming connections are blocked unless a rule allows them.
  • 164.312(e)(1) Transmission security. The firewall keeps outsiders from connecting to the computer and reaching patient data over the network.
  • SC.L1-B.1.X Protect communications at the boundary. The firewall controls what network traffic can reach the computer, on every network it joins.
  • 4.5 Implement and Manage a Firewall on End-User Devices. The firewall controls what network traffic can reach the computer, on every network it joins.
  • 314.4(c) Safeguards that control identified risks. The firewall controls what network traffic can reach the computer, on every network it joins.
  • PR.IR-01 Networks protected. The firewall controls what network traffic can reach the computer, on every network it joins.
  • 1.5.1 Security controls on devices that use untrusted networks. The firewall controls what network traffic can reach the computer, on every network it joins.
  • 500.3(g) Systems and network security. The firewall controls what network traffic can reach the computer, on every network it joins.
  • 248.30(a)(2)(iii) Protection against unauthorized access. The firewall controls what network traffic can reach the computer, on every network it joins.
  • CC6.6 Protection from outside threats. The firewall controls what network traffic can reach the computer, on every network it joins.
  • CI-08 Secured remote access. The firewall controls what network traffic can reach the computer, on every network it joins.

Accounts

No standing local admin rights for user accounts (ACC-001)

High Accounts

Fix: Remove user accounts from the local Administrators group. Use LAPS or just-in-time elevation for admin tasks.

Take the helm: step-by-step
  1. List current admins: Get-LocalGroupMember -Group Administrators.
  2. Before removing anyone, make sure another admin path works, such as LAPS or a domain admin group.
  3. Remove user accounts that don't need standing admin rights: Remove-LocalGroupMember -Group Administrators -Member 'DOMAIN\user'.
  4. Manage membership centrally (Intune: Endpoint security → Account protection → Local user group membership, or Group Policy Restricted Groups) so it doesn't drift back.
  5. On Windows Home or a single unmanaged device: create a separate admin account, then make your everyday account a standard user (Settings → Accounts → Other users → Change account type).

Maps to:

  • AC.L2-3.1.5 Employ the principle of least privilege. When everyday accounts aren't administrators, a mistake or malware can't take over the whole computer.
  • AC.L2-3.1.6 Use non-privileged accounts for nonsecurity functions. Without standing admin rights, people do daily work from a normal account and only elevate when needed.
  • 164.312(a)(1) Access control. Limiting admin rights keeps people from reaching data and settings their job doesn't need.
  • AC.L1-B.1.II Limit access to permitted functions. When everyday accounts aren't administrators, a mistake or malware can't take over the whole computer.
  • 5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts. When everyday accounts aren't administrators, a mistake or malware can't take over the whole computer.
  • 314.4(c)(1) Access controls. When everyday accounts aren't administrators, a mistake or malware can't take over the whole computer.
  • PR.AA-05 Least privilege. When everyday accounts aren't administrators, a mistake or malware can't take over the whole computer.
  • 7.2.2 Least privilege. When everyday accounts aren't administrators, a mistake or malware can't take over the whole computer.
  • 500.7(a)(2) Limit privileged accounts. When everyday accounts aren't administrators, a mistake or malware can't take over the whole computer.
  • 248.30(a)(2)(iii) Protection against unauthorized access. When everyday accounts aren't administrators, a mistake or malware can't take over the whole computer.
  • CC6.3 Least privilege. When everyday accounts aren't administrators, a mistake or malware can't take over the whole computer.
  • CI-06 Limited admin rights. When everyday accounts aren't administrators, a mistake or malware can't take over the whole computer.

Guest account is disabled (ACC-002)

Medium Accounts

Fix: Disable the built-in Guest account.

Take the helm: step-by-step
  1. Disable the Guest account: Get-LocalUser | Where-Object SID -like '*-501' | Disable-LocalUser.
  2. For many devices, set Group Policy Security Options → 'Accounts: Guest account status' to Disabled.

Maps to:

  • AC.L2-3.1.1 Limit system access to authorized users. The Guest account has no owner and no password, so leaving it on lets anyone sign in.
  • 164.312(a)(1) Access control. The Guest account has no owner and no password, so leaving it on lets anyone sign in.
  • AC.L1-B.1.I Limit access to authorized users. The Guest account has no owner and no password, so leaving it on lets anyone sign in.
  • IA.L1-B.1.V Identify users and devices. A shared Guest login can't be tied to a person. With it off, every sign-in belongs to someone you know.
  • 4.7 Manage Default Accounts on Enterprise Assets and Software. The Guest account has no owner and no password, so leaving it on lets anyone sign in.
  • 314.4(c)(1) Access controls. The Guest account has no owner and no password, so leaving it on lets anyone sign in.
  • PR.AA-01 Identities and credentials managed. The Guest account has no owner and no password, so leaving it on lets anyone sign in.
  • 2.2.2 Vendor default accounts managed. The Guest account has no owner and no password, so leaving it on lets anyone sign in.
  • 8.2.2 Shared accounts limited. The Guest account has no owner and no password, so leaving it on lets anyone sign in.
  • 500.7(a)(4) Remove unneeded accounts. The Guest account has no owner and no password, so leaving it on lets anyone sign in.
  • 248.30(a)(2)(iii) Protection against unauthorized access. The Guest account has no owner and no password, so leaving it on lets anyone sign in.
  • CC6.1 Logical access security. The Guest account has no owner and no password, so leaving it on lets anyone sign in.
  • CI-12 Account and password hygiene. The Guest account has no owner and no password, so leaving it on lets anyone sign in.

Built-in Administrator account is disabled (ACC-003)

Low Accounts

Fix: Disable the built-in Administrator (RID 500) account, or manage it with LAPS.

Take the helm: step-by-step
  1. Confirm another admin account works first.
  2. Disable the built-in Administrator: Get-LocalUser | Where-Object SID -like '*-500' | Disable-LocalUser.
  3. For many devices, set Group Policy Security Options → 'Accounts: Administrator account status' to Disabled. If LAPS manages this account, document that instead.

Maps to:

  • AC.L2-3.1.5 Employ the principle of least privilege. The built-in Administrator account is a well-known target for attackers. Disabling it removes an easy way in.
  • AC.L1-B.1.II Limit access to permitted functions. The built-in Administrator account is a well-known target for attackers. Disabling it removes an easy way in.
  • IA.L1-B.1.V Identify users and devices. The built-in Administrator is shared by nature, so actions taken with it can't be tied to one person.
  • 4.7 Manage Default Accounts on Enterprise Assets and Software. The built-in Administrator account is a well-known target for attackers. Disabling it removes an easy way in.
  • 314.4(c)(1) Access controls. The built-in Administrator account is a well-known target for attackers. Disabling it removes an easy way in.
  • PR.AA-01 Identities and credentials managed. The built-in Administrator account is a well-known target for attackers. Disabling it removes an easy way in.
  • 2.2.2 Vendor default accounts managed. The built-in Administrator account is a well-known target for attackers. Disabling it removes an easy way in.
  • 8.2.2 Shared accounts limited. The built-in Administrator account is a well-known target for attackers. Disabling it removes an easy way in.
  • 500.7(a)(2) Limit privileged accounts. The built-in Administrator account is a well-known target for attackers. Disabling it removes an easy way in.
  • 248.30(a)(2)(iii) Protection against unauthorized access. The built-in Administrator account is a well-known target for attackers. Disabling it removes an easy way in.
  • CC6.1 Logical access security. The built-in Administrator account is a well-known target for attackers. Disabling it removes an easy way in.
  • CI-06 Limited admin rights. The built-in Administrator account is a well-known target for attackers. Disabling it removes an easy way in.

Account lockout threshold is set (ACC-004)

High Accounts

Fix: Set the account lockout threshold between 1 and 10 invalid attempts with a lockout duration of 15+ minutes.

Default thresholds: Maximum lockout threshold = 10

Stricter for PCI DSS clients: Lockout duration (minutes) = 30 or more (or until an admin unlocks the account)

Take the helm: step-by-step
  1. Group Policy: Computer Configuration → Windows Settings → Security Settings → Account Policies → Account Lockout Policy. Set the threshold to 5–10 attempts and the duration and reset counter to 15 minutes (30 for PCI DSS clients).
  2. On a single device: net accounts /lockoutthreshold:10 /lockoutduration:15 /lockoutwindow:15. For PCI DSS, use 30 instead of 15.
  3. Domain accounts follow the domain's policy (Default Domain Policy), so set it there as well.

Maps to:

  • AC.L2-3.1.8 Limit unsuccessful logon attempts. Locking an account after several wrong passwords stops attackers from guessing over and over.
  • 164.308(a)(5)(ii)(C) Log-in monitoring. Lockouts respond automatically to repeated failed sign-ins, a common sign of an attack.
  • IA.L1-B.1.VI Authenticate users and devices. Locking an account after several wrong passwords stops attackers from guessing over and over.
  • 4.1 Establish and Maintain a Secure Configuration Process. Locking an account after several wrong passwords stops attackers from guessing over and over.
  • 314.4(c)(1) Access controls. Locking an account after several wrong passwords stops attackers from guessing over and over.
  • PR.AA-03 Users authenticated. Locking an account after several wrong passwords stops attackers from guessing over and over.
  • 8.3.4 Lockout after failed attempts. Locking an account after several wrong passwords stops attackers from guessing over and over.
  • 500.7(b) Password policy. Locking an account after several wrong passwords stops attackers from guessing over and over.
  • 248.30(a)(2)(iii) Protection against unauthorized access. Locking an account after several wrong passwords stops attackers from guessing over and over.
  • CC6.1 Logical access security. Locking an account after several wrong passwords stops attackers from guessing over and over.
  • CI-12 Account and password hygiene. Locking an account after several wrong passwords stops attackers from guessing over and over.

Minimum password length is enforced (ACC-005)

Medium Accounts

Fix: Set the minimum password length to 14 characters or more.

Default thresholds: Minimum password length = 14

Take the helm: step-by-step
  1. Group Policy: Account Policies → Password Policy → Minimum password length = 14.
  2. On a single device: net accounts /minpwlen:14.
  3. On Entra-joined devices this covers local accounts only; cloud account passwords follow Entra ID policy.

Maps to:

  • IA.L2-3.5.7 Enforce minimum password complexity. Longer passwords are much harder to guess or crack.
  • 164.308(a)(5)(ii)(D) Password management. Longer passwords are much harder to guess or crack.
  • IA.L1-B.1.VI Authenticate users and devices. Longer passwords are much harder to guess or crack.
  • 5.2 Use Unique Passwords. Longer passwords are much harder to guess or crack.
  • 314.4(c)(1) Access controls. Longer passwords are much harder to guess or crack.
  • PR.AA-01 Identities and credentials managed. Longer passwords are much harder to guess or crack.
  • 8.3.6 Password length and complexity. Longer passwords are much harder to guess or crack.
  • 500.7(b) Password policy. Longer passwords are much harder to guess or crack.
  • 248.30(a)(2)(iii) Protection against unauthorized access. Longer passwords are much harder to guess or crack.
  • CC6.1 Logical access security. Longer passwords are much harder to guess or crack.
  • CI-12 Account and password hygiene. Longer passwords are much harder to guess or crack.

Password complexity is required (ACC-006)

Medium Accounts

Fix: Enable 'Password must meet complexity requirements'.

Take the helm: step-by-step
  1. Group Policy: Account Policies → Password Policy → 'Password must meet complexity requirements' = Enabled.
  2. On a single device, set the same option in Local Security Policy (secpol.msc).
  3. Windows Home has no secpol.msc. Use secedit in an elevated PowerShell instead: secedit /export /cfg $env:TEMP\sec.inf /areas SECURITYPOLICY; (Get-Content $env:TEMP\sec.inf) -replace 'PasswordComplexity = 0', 'PasswordComplexity = 1' | Set-Content $env:TEMP\sec.inf -Encoding Unicode; secedit /configure /db $env:TEMP\sec.sdb /cfg $env:TEMP\sec.inf /areas SECURITYPOLICY.

Maps to:

  • IA.L2-3.5.7 Enforce minimum password complexity. Requiring a mix of character types makes passwords harder to guess.
  • 164.308(a)(5)(ii)(D) Password management. Requiring a mix of character types makes passwords harder to guess.
  • IA.L1-B.1.VI Authenticate users and devices. Requiring a mix of character types makes passwords harder to guess.
  • 5.2 Use Unique Passwords. Requiring a mix of character types makes passwords harder to guess.
  • 314.4(c)(1) Access controls. Requiring a mix of character types makes passwords harder to guess.
  • PR.AA-01 Identities and credentials managed. Requiring a mix of character types makes passwords harder to guess.
  • 8.3.6 Password length and complexity. Requiring a mix of character types makes passwords harder to guess.
  • 500.7(b) Password policy. Requiring a mix of character types makes passwords harder to guess.
  • 248.30(a)(2)(iii) Protection against unauthorized access. Requiring a mix of character types makes passwords harder to guess.
  • CC6.1 Logical access security. Requiring a mix of character types makes passwords harder to guess.
  • CI-12 Account and password hygiene. Requiring a mix of character types makes passwords harder to guess.

Password history prevents reuse (ACC-007)

Low Accounts

Fix: Set 'Enforce password history' to 24 or more.

Default thresholds: Passwords remembered = 24

Take the helm: step-by-step
  1. Group Policy: Account Policies → Password Policy → 'Enforce password history' = 24.
  2. On a single device: net accounts /uniquepw:24.

Maps to:

  • IA.L2-3.5.8 Prohibit password reuse for a specified number of generations. Remembering old passwords stops people from switching back to one that may already be exposed.
  • 164.308(a)(5)(ii)(D) Password management. Remembering old passwords stops people from switching back to one that may already be exposed.
  • IA.L1-B.1.VI Authenticate users and devices. Remembering old passwords stops people from switching back to one that may already be exposed.
  • 5.2 Use Unique Passwords. Remembering old passwords stops people from switching back to one that may already be exposed.
  • 314.4(c)(1) Access controls. Remembering old passwords stops people from switching back to one that may already be exposed.
  • PR.AA-01 Identities and credentials managed. Remembering old passwords stops people from switching back to one that may already be exposed.
  • 8.3.7 Password reuse. Remembering old passwords stops people from switching back to one that may already be exposed.
  • 500.7(b) Password policy. Remembering old passwords stops people from switching back to one that may already be exposed.
  • 248.30(a)(2)(iii) Protection against unauthorized access. Remembering old passwords stops people from switching back to one that may already be exposed.
  • CC6.1 Logical access security. Remembering old passwords stops people from switching back to one that may already be exposed.
  • CI-12 Account and password hygiene. Remembering old passwords stops people from switching back to one that may already be exposed.

Local admin password is managed (LAPS) (ACC-008)

Medium Accounts

Fix: Deploy Windows LAPS with backup to Entra ID or Active Directory.

Take the helm: step-by-step
  1. Entra-joined devices: Intune → Endpoint security → Account protection → create a Windows LAPS policy with Backup directory = Azure AD (Entra ID).
  2. Active Directory: run Update-LapsADSchema and Set-LapsADComputerSelfPermission -Identity '<OU>', then set Group Policy → Administrative Templates → System → LAPS → 'Configure password backup directory' = Active Directory.
  3. Confirm a password was stored with Get-LapsAADPassword or Get-LapsADPassword.
  4. Windows Home doesn't support LAPS. Upgrade to Windows Pro, or until then give the local admin account a long, unique password kept in a password manager.

Maps to:

  • AC.L2-3.1.5 Employ the principle of least privilege. With LAPS, the local admin password is only released to the people who need it.
  • IA.L2-3.5.10 Store and transmit only cryptographically-protected passwords. LAPS stores admin passwords encrypted in your directory instead of written down or reused.
  • IA.L1-B.1.VI Authenticate users and devices. LAPS gives every computer its own random admin password and changes it regularly, so one stolen password doesn't open them all.
  • 4.7 Manage Default Accounts on Enterprise Assets and Software. LAPS manages the built-in admin account's password, so that default account never shares one password across computers.
  • 5.2 Use Unique Passwords. LAPS gives every computer its own random admin password and changes it regularly, so one stolen password doesn't open them all.
  • 314.4(c)(1) Access controls. LAPS gives every computer its own random admin password and changes it regularly, so one stolen password doesn't open them all.
  • PR.AA-01 Identities and credentials managed. LAPS gives every computer its own random admin password and changes it regularly, so one stolen password doesn't open them all.
  • 2.2.2 Vendor default accounts managed. LAPS gives every computer its own random admin password and changes it regularly, so one stolen password doesn't open them all.
  • 500.7(a)(2) Limit privileged accounts. LAPS gives every computer its own random admin password and changes it regularly, so one stolen password doesn't open them all.
  • 248.30(a)(2)(iii) Protection against unauthorized access. LAPS gives every computer its own random admin password and changes it regularly, so one stolen password doesn't open them all.
  • CC6.1 Logical access security. LAPS gives every computer its own random admin password and changes it regularly, so one stolen password doesn't open them all.
  • CI-06 Limited admin rights. LAPS gives every computer its own random admin password and changes it regularly, so one stolen password doesn't open them all.

User Account Control is enabled (ACC-009)

High Accounts

Fix: Set EnableLUA to 1 and require consent or credentials for elevation.

Take the helm: step-by-step
  1. Group Policy Security Options: 'User Account Control: Run all administrators in Admin Approval Mode' = Enabled and 'Behavior of the elevation prompt for administrators' = 'Prompt for consent on the secure desktop'.
  2. On a single device: Set-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -Name EnableLUA -Value 1, then restart.

Maps to:

  • AC.L2-3.1.7 Prevent non-privileged users from executing privileged functions. User Account Control asks for approval before anything makes admin-level changes, so programs can't quietly take over.
  • 164.312(a)(1) Access control. User Account Control asks for approval before anything makes admin-level changes, so programs can't quietly take over.
  • AC.L1-B.1.II Limit access to permitted functions. User Account Control asks for approval before anything makes admin-level changes, so programs can't quietly take over.
  • 4.1 Establish and Maintain a Secure Configuration Process. User Account Control asks for approval before anything makes admin-level changes, so programs can't quietly take over.
  • 314.4(c)(1) Access controls. User Account Control asks for approval before anything makes admin-level changes, so programs can't quietly take over.
  • PR.AA-05 Least privilege. User Account Control asks for approval before anything makes admin-level changes, so programs can't quietly take over.
  • 7.2.2 Least privilege. User Account Control asks for approval before anything makes admin-level changes, so programs can't quietly take over.
  • 500.7(a)(2) Limit privileged accounts. User Account Control asks for approval before anything makes admin-level changes, so programs can't quietly take over.
  • 248.30(a)(2)(iii) Protection against unauthorized access. User Account Control asks for approval before anything makes admin-level changes, so programs can't quietly take over.
  • CC6.3 Least privilege. User Account Control asks for approval before anything makes admin-level changes, so programs can't quietly take over.
  • CC6.8 Preventing malicious software. User Account Control asks for approval before anything makes admin-level changes, so programs can't quietly take over.
  • CI-06 Limited admin rights. User Account Control asks for approval before anything makes admin-level changes, so programs can't quietly take over.

Sessions

Screen locks after inactivity (SES-001)

Medium Sessions

Fix: Set the machine inactivity limit (InactivityTimeoutSecs) to 900 seconds or less.

Default thresholds: Maximum idle time (seconds) = 900

Take the helm: step-by-step
  1. Group Policy Security Options: 'Interactive logon: Machine inactivity limit' = 900 seconds or less.
  2. Intune: Settings catalog → Local Policies Security Options → 'Interactive Logon Machine Inactivity Limit'.
  3. On a single device: Set-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -Name InactivityTimeoutSecs -Value 900 -Type DWord.

Maps to:

  • AC.L2-3.1.10 Use session lock with pattern-hiding displays. An automatic screen lock protects an unattended computer from whoever walks up to it.
  • 164.312(a)(2)(iii) Automatic logoff. An automatic screen lock protects an unattended computer from whoever walks up to it.
  • 4.3 Configure Automatic Session Locking on Enterprise Assets. An automatic screen lock protects an unattended computer from whoever walks up to it.
  • 314.4(c)(1) Access controls. An automatic screen lock protects an unattended computer from whoever walks up to it.
  • PR.AA-03 Users authenticated. An automatic screen lock protects an unattended computer from whoever walks up to it.
  • 8.2.8 Idle sessions re-authenticate. An automatic screen lock protects an unattended computer from whoever walks up to it.
  • 500.3(g) Systems and network security. An automatic screen lock protects an unattended computer from whoever walks up to it.
  • 248.30(a)(2)(iii) Protection against unauthorized access. An automatic screen lock protects an unattended computer from whoever walks up to it.
  • CC6.1 Logical access security. An automatic screen lock protects an unattended computer from whoever walks up to it.
  • CI-12 Account and password hygiene. An automatic screen lock protects an unattended computer from whoever walks up to it.

Logon banner is displayed (SES-002)

Low Sessions

Fix: Configure 'Interactive logon: Message title and text for users attempting to log on'.

Take the helm: step-by-step
  1. Write a short notice, for example: 'Authorized use only. Activity on this system is monitored.'
  2. Group Policy Security Options: set 'Interactive logon: Message title for users attempting to log on' and 'Message text for users attempting to log on'.
  3. Intune: Settings catalog → Local Policies Security Options → Interactive Logon Message Title and Message Text.
  4. On a single device: Set-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -Name LegalNoticeCaption -Value 'Notice'; Set-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -Name LegalNoticeText -Value 'Authorized use only.'.

Maps to:

  • AC.L2-3.1.9 Provide privacy and security notices. The sign-in banner tells everyone the system is monitored and only for authorized use.
  • PR.PS-01 Configuration management. The sign-in banner tells everyone the system is monitored and only for authorized use.

Remote Desktop requires Network Level Authentication (SES-003)

High Sessions

Fix: Disable RDP if not needed. If needed, require NLA and restrict access to a VPN or gateway.

Take the helm: step-by-step
  1. If Remote Desktop isn't needed, turn it off: Settings → System → Remote Desktop → Off.
  2. If it is needed, require NLA: Group Policy → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Security → 'Require user authentication for remote connections by using Network Level Authentication' = Enabled.
  3. On a single device: Set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication -Value 1.
  4. Limit who can connect, and reach RDP only through a VPN or gateway.

Maps to:

  • AC.L2-3.1.12 Monitor and control remote access sessions. Requiring sign-in before Remote Desktop connects keeps control over who can reach the computer remotely.
  • 164.312(d) Person or entity authentication. Network Level Authentication makes people prove who they are before a remote session even starts.
  • IA.L1-B.1.VI Authenticate users and devices. Network Level Authentication makes people prove who they are before a remote session even starts.
  • 4.6 Securely Manage Enterprise Assets and Software. Network Level Authentication makes people prove who they are before a remote session even starts.
  • 314.4(c)(1) Access controls. Network Level Authentication makes people prove who they are before a remote session even starts.
  • PR.AA-03 Users authenticated. Network Level Authentication makes people prove who they are before a remote session even starts.
  • PR.IR-01 Networks protected. Network Level Authentication makes people prove who they are before a remote session even starts.
  • 8.4.3 MFA for remote access. Network Level Authentication makes people prove who they are before a remote session even starts.
  • 500.7(a)(5) Remote control protocols. Network Level Authentication makes people prove who they are before a remote session even starts.
  • 248.30(a)(2)(iii) Protection against unauthorized access. Network Level Authentication makes people prove who they are before a remote session even starts.
  • CC6.1 Logical access security. Network Level Authentication makes people prove who they are before a remote session even starts.
  • CC6.6 Protection from outside threats. Network Level Authentication makes people prove who they are before a remote session even starts.
  • CI-08 Secured remote access. Network Level Authentication makes people prove who they are before a remote session even starts.

Hardening

SMBv1 is disabled (HRD-001)

High Hardening

Fix: Disable the SMB1Protocol feature and set EnableSMB1Protocol to false.

Take the helm: step-by-step
  1. Check that no old printers, scanners, or NAS devices still need SMBv1.
  2. Remove it: Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -NoRestart and Set-SmbServerConfiguration -EnableSMB1Protocol $false -Force.
  3. Restart the device.

Maps to:

  • CM.L2-3.4.6 Employ the principle of least functionality. SMBv1 is an outdated file-sharing protocol that attacks like WannaCry exploited. Turning it off closes that door.
  • CM.L2-3.4.7 Restrict nonessential programs, functions, ports, protocols, and services. SMBv1 is an outdated file-sharing protocol that attacks like WannaCry exploited. Turning it off closes that door.
  • 4.1 Establish and Maintain a Secure Configuration Process. SMBv1 is an outdated file-sharing protocol that attacks like WannaCry exploited. Turning it off closes that door.
  • 314.4(c) Safeguards that control identified risks. SMBv1 is an outdated file-sharing protocol that attacks like WannaCry exploited. Turning it off closes that door.
  • PR.PS-01 Configuration management. SMBv1 is an outdated file-sharing protocol that attacks like WannaCry exploited. Turning it off closes that door.
  • 2.2.4 Only necessary services enabled. SMBv1 is an outdated file-sharing protocol that attacks like WannaCry exploited. Turning it off closes that door.
  • 2.2.5 Insecure services justified and secured. SMBv1 is an outdated file-sharing protocol that attacks like WannaCry exploited. Turning it off closes that door.
  • 500.3(g) Systems and network security. SMBv1 is an outdated file-sharing protocol that attacks like WannaCry exploited. Turning it off closes that door.
  • 248.30(a)(2)(ii) Protection against anticipated threats. SMBv1 is an outdated file-sharing protocol that attacks like WannaCry exploited. Turning it off closes that door.
  • CC7.1 Finding vulnerabilities and configuration drift. SMBv1 is an outdated file-sharing protocol that attacks like WannaCry exploited. Turning it off closes that door.
  • CI-09 Hardened configuration. SMBv1 is an outdated file-sharing protocol that attacks like WannaCry exploited. Turning it off closes that door.

LLMNR is disabled (HRD-002)

Medium Hardening

Fix: Set 'Turn off multicast name resolution' to Enabled.

Take the helm: step-by-step
  1. Group Policy: Administrative Templates → Network → DNS Client → 'Turn off multicast name resolution' = Enabled.
  2. On a single device: New-Item 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient' -Force | Out-Null; Set-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient' -Name EnableMulticast -Value 0 -Type DWord.

Maps to:

  • CM.L2-3.4.7 Restrict nonessential programs, functions, ports, protocols, and services. LLMNR lets attackers on the same network trick computers into handing over passwords. Turning it off stops that.
  • 4.1 Establish and Maintain a Secure Configuration Process. LLMNR lets attackers on the same network trick computers into handing over passwords. Turning it off stops that.
  • 314.4(c) Safeguards that control identified risks. LLMNR lets attackers on the same network trick computers into handing over passwords. Turning it off stops that.
  • PR.PS-01 Configuration management. LLMNR lets attackers on the same network trick computers into handing over passwords. Turning it off stops that.
  • PR.IR-01 Networks protected. LLMNR lets attackers on the same network trick computers into handing over passwords. Turning it off stops that.
  • 2.2.4 Only necessary services enabled. LLMNR lets attackers on the same network trick computers into handing over passwords. Turning it off stops that.
  • 500.3(g) Systems and network security. LLMNR lets attackers on the same network trick computers into handing over passwords. Turning it off stops that.
  • 248.30(a)(2)(ii) Protection against anticipated threats. LLMNR lets attackers on the same network trick computers into handing over passwords. Turning it off stops that.
  • CC6.6 Protection from outside threats. LLMNR lets attackers on the same network trick computers into handing over passwords. Turning it off stops that.
  • CC7.1 Finding vulnerabilities and configuration drift. LLMNR lets attackers on the same network trick computers into handing over passwords. Turning it off stops that.
  • CI-09 Hardened configuration. LLMNR lets attackers on the same network trick computers into handing over passwords. Turning it off stops that.

NetBIOS over TCP/IP is disabled (HRD-003)

Low Hardening

Fix: Set NetbiosOptions to 2 on all interfaces, or disable through DHCP option.

Take the helm: step-by-step
  1. Make sure no legacy app relies on NetBIOS name resolution.
  2. Through DHCP (Windows Server): set scope option 001 'Microsoft Disable Netbios Option' to 0x2.
  3. On a single device: Get-ChildItem HKLM:\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces | ForEach-Object { Set-ItemProperty $_.PSPath -Name NetbiosOptions -Value 2 }.

Maps to:

  • CM.L2-3.4.7 Restrict nonessential programs, functions, ports, protocols, and services. NetBIOS is an old naming protocol attackers abuse to capture passwords on the local network.
  • 4.1 Establish and Maintain a Secure Configuration Process. NetBIOS is an old naming protocol attackers abuse to capture passwords on the local network.
  • 314.4(c) Safeguards that control identified risks. NetBIOS is an old naming protocol attackers abuse to capture passwords on the local network.
  • PR.PS-01 Configuration management. NetBIOS is an old naming protocol attackers abuse to capture passwords on the local network.
  • PR.IR-01 Networks protected. NetBIOS is an old naming protocol attackers abuse to capture passwords on the local network.
  • 2.2.4 Only necessary services enabled. NetBIOS is an old naming protocol attackers abuse to capture passwords on the local network.
  • 500.3(g) Systems and network security. NetBIOS is an old naming protocol attackers abuse to capture passwords on the local network.
  • 248.30(a)(2)(ii) Protection against anticipated threats. NetBIOS is an old naming protocol attackers abuse to capture passwords on the local network.
  • CC6.6 Protection from outside threats. NetBIOS is an old naming protocol attackers abuse to capture passwords on the local network.
  • CC7.1 Finding vulnerabilities and configuration drift. NetBIOS is an old naming protocol attackers abuse to capture passwords on the local network.
  • CI-09 Hardened configuration. NetBIOS is an old naming protocol attackers abuse to capture passwords on the local network.

AutoRun is disabled for all drives (HRD-004)

Medium Hardening

Fix: Set NoDriveTypeAutoRun to 255 and NoAutorun to 1.

Take the helm: step-by-step
  1. Group Policy: Administrative Templates → Windows Components → AutoPlay Policies → 'Turn off Autoplay' = Enabled for All drives, and 'Set the default behavior for AutoRun' = Do not execute any autorun commands.
  2. On a single device: Set-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer -Name NoDriveTypeAutoRun -Value 255 -Type DWord.

Maps to:

  • CM.L2-3.4.6 Employ the principle of least functionality. AutoRun is a feature most computers don't need, and it's a common way malware spreads.
  • SI.L2-3.14.2 Provide protection from malicious code. With AutoRun off, plugging in a USB drive can't launch programs on its own.
  • SI.L1-B.1.XIII Protect against malicious code. With AutoRun off, plugging in a USB drive can't launch programs on its own.
  • 10.3 Disable Autorun and Autoplay for Removable Media. With AutoRun off, plugging in a USB drive can't launch programs on its own.
  • 314.4(c) Safeguards that control identified risks. With AutoRun off, plugging in a USB drive can't launch programs on its own.
  • PR.PS-05 Unauthorized software prevented. With AutoRun off, plugging in a USB drive can't launch programs on its own.
  • 2.2.4 Only necessary services enabled. With AutoRun off, plugging in a USB drive can't launch programs on its own.
  • 500.14(a)(2) Protection against malicious code. With AutoRun off, plugging in a USB drive can't launch programs on its own.
  • 248.30(a)(2)(ii) Protection against anticipated threats. With AutoRun off, plugging in a USB drive can't launch programs on its own.
  • CC6.8 Preventing malicious software. With AutoRun off, plugging in a USB drive can't launch programs on its own.
  • CI-09 Hardened configuration. With AutoRun off, plugging in a USB drive can't launch programs on its own.

Removable storage is restricted (HRD-005)

Medium Hardening

Fix: Block or make read-only removable storage through policy or EDR device control.

Take the helm: step-by-step
  1. If your EDR handles device control (for example SentinelOne or Defender for Endpoint), enforce it there and document it as the control.
  2. Otherwise, Group Policy or Intune Settings catalog: Administrative Templates → System → Removable Storage Access → 'All Removable Storage classes: Deny all access' (or deny write only).
  3. On a single device, block writes to USB drives: $k = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\RemovableStorageDevices\{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}'; New-Item $k -Force | Out-Null; Set-ItemProperty $k -Name Deny_Write -Value 1 -Type DWord.
  4. Allow exceptions for approved encrypted drives if needed.

Maps to:

  • MP.L2-3.8.7 Control the use of removable media on system components. Restricting USB drives keeps data from walking out the door and malware from walking in.
  • 314.4(c) Safeguards that control identified risks. Restricting USB drives keeps data from walking out the door and malware from walking in.
  • PR.DS-01 Data at rest protected. Restricting USB drives keeps data from walking out the door and malware from walking in.
  • 500.3(g) Systems and network security. Restricting USB drives keeps data from walking out the door and malware from walking in.
  • 248.30(a)(2)(i) Security and confidentiality of customer information. Restricting USB drives keeps data from walking out the door and malware from walking in.
  • CC6.7 Controlling how data leaves. Restricting USB drives keeps data from walking out the door and malware from walking in.

FIPS-compliant algorithms are enforced (HRD-006)

Low Hardening

Fix: Enable 'System cryptography: Use FIPS compliant algorithms'. Test application impact first.

Take the helm: step-by-step
  1. Test first: some older apps and protocols break in FIPS mode.
  2. Group Policy Security Options: 'System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing' = Enabled.
  3. On a single device: Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy -Name Enabled -Value 1.
  4. If you can't enable it, document that CUI is protected with FIPS-validated modules (BitLocker, TLS) as your approach to 3.13.11.

Maps to:

  • SC.L2-3.13.11 Employ FIPS-validated cryptography to protect CUI. FIPS mode makes Windows use only encryption the U.S. government has tested and approved.
  • PR.DS-02 Data in transit protected. FIPS mode makes Windows use only encryption the U.S. government has tested and approved.
  • 4.2.1 Strong cryptography for card data in transit. FIPS mode makes Windows use only encryption the U.S. government has tested and approved.
  • 500.15(a) Encryption. FIPS mode makes Windows use only encryption the U.S. government has tested and approved.
  • CC6.7 Controlling how data leaves. FIPS mode makes Windows use only encryption the U.S. government has tested and approved.

LSA protection is enabled (HRD-007)

Medium Hardening

Fix: Set RunAsPPL to 1 under HKLM\SYSTEM\CurrentControlSet\Control\Lsa.

Take the helm: step-by-step
  1. Check for unsigned LSA plug-ins (smart card or password filters) in the CodeIntegrity event log before enforcing.
  2. Intune: Settings catalog → Local Security Authority → 'Configure LSA to run as a protected process' = Enabled with UEFI lock.
  3. On a single device: Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\Lsa -Name RunAsPPL -Value 1 -Type DWord, then restart.

Maps to:

  • IA.L2-3.5.10 Store and transmit only cryptographically-protected passwords. LSA protection stops other programs from reading sign-in secrets in memory, a favorite attacker technique.
  • 4.1 Establish and Maintain a Secure Configuration Process. LSA protection stops other programs from reading sign-in secrets in memory, a favorite attacker technique.
  • 314.4(c) Safeguards that control identified risks. LSA protection stops other programs from reading sign-in secrets in memory, a favorite attacker technique.
  • PR.PS-01 Configuration management. LSA protection stops other programs from reading sign-in secrets in memory, a favorite attacker technique.
  • 8.3.2 Authentication factors protected. LSA protection stops other programs from reading sign-in secrets in memory, a favorite attacker technique.
  • 500.3(g) Systems and network security. LSA protection stops other programs from reading sign-in secrets in memory, a favorite attacker technique.
  • 248.30(a)(2)(ii) Protection against anticipated threats. LSA protection stops other programs from reading sign-in secrets in memory, a favorite attacker technique.
  • CC6.1 Logical access security. LSA protection stops other programs from reading sign-in secrets in memory, a favorite attacker technique.
  • CI-09 Hardened configuration. LSA protection stops other programs from reading sign-in secrets in memory, a favorite attacker technique.

Credential Guard is running (HRD-008)

Medium Hardening

Fix: Enable Virtualization-based Security with Credential Guard.

Take the helm: step-by-step
  1. Make sure UEFI, Secure Boot, and CPU virtualization (VT-x or AMD-V) are on in the firmware.
  2. Intune: Endpoint security → Account protection → Credential Guard = Enable with UEFI lock. Group Policy: Administrative Templates → System → Device Guard → 'Turn On Virtualization Based Security' with Credential Guard enabled.
  3. Credential Guard runs only on Windows Enterprise and Education. On Home and Pro, Lookout shows a warning until the device moves to Enterprise (for example, through a Windows Enterprise E3 or Microsoft 365 E3 license).
  4. Restart and confirm in msinfo32 that Credential Guard is listed under Virtualization-based security Services Running.

Maps to:

  • IA.L2-3.5.10 Store and transmit only cryptographically-protected passwords. Credential Guard locks sign-in secrets inside a protected area of the computer, so malware can't steal them.
  • 314.4(c) Safeguards that control identified risks. Credential Guard locks sign-in secrets inside a protected area of the computer, so malware can't steal them.
  • PR.PS-01 Configuration management. Credential Guard locks sign-in secrets inside a protected area of the computer, so malware can't steal them.
  • 8.3.2 Authentication factors protected. Credential Guard locks sign-in secrets inside a protected area of the computer, so malware can't steal them.
  • 500.3(g) Systems and network security. Credential Guard locks sign-in secrets inside a protected area of the computer, so malware can't steal them.
  • 248.30(a)(2)(ii) Protection against anticipated threats. Credential Guard locks sign-in secrets inside a protected area of the computer, so malware can't steal them.
  • CC6.1 Logical access security. Credential Guard locks sign-in secrets inside a protected area of the computer, so malware can't steal them.
  • CI-09 Hardened configuration. Credential Guard locks sign-in secrets inside a protected area of the computer, so malware can't steal them.

WDigest does not cache plaintext credentials (HRD-009)

High Hardening

Fix: Set UseLogonCredential to 0 under WDigest.

Take the helm: step-by-step
  1. Set UseLogonCredential to 0: Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest -Name UseLogonCredential -Value 0 -Type DWord.
  2. For many devices, use the MS Security Guide Group Policy template setting 'WDigest Authentication' = Disabled.

Maps to:

  • IA.L2-3.5.10 Store and transmit only cryptographically-protected passwords. With WDigest off, Windows doesn't keep readable copies of passwords in memory for attackers to grab.
  • 164.312(d) Person or entity authentication. With WDigest off, Windows doesn't keep readable copies of passwords in memory for attackers to grab.
  • 4.1 Establish and Maintain a Secure Configuration Process. With WDigest off, Windows doesn't keep readable copies of passwords in memory for attackers to grab.
  • 314.4(c) Safeguards that control identified risks. With WDigest off, Windows doesn't keep readable copies of passwords in memory for attackers to grab.
  • PR.PS-01 Configuration management. With WDigest off, Windows doesn't keep readable copies of passwords in memory for attackers to grab.
  • 8.3.2 Authentication factors protected. With WDigest off, Windows doesn't keep readable copies of passwords in memory for attackers to grab.
  • 500.3(g) Systems and network security. With WDigest off, Windows doesn't keep readable copies of passwords in memory for attackers to grab.
  • 248.30(a)(2)(ii) Protection against anticipated threats. With WDigest off, Windows doesn't keep readable copies of passwords in memory for attackers to grab.
  • CC6.1 Logical access security. With WDigest off, Windows doesn't keep readable copies of passwords in memory for attackers to grab.
  • CI-09 Hardened configuration. With WDigest off, Windows doesn't keep readable copies of passwords in memory for attackers to grab.

Legacy TLS and SSL are turned off (HRD-010)

Medium Hardening

Fix: Turn off SSL 2.0, SSL 3.0, TLS 1.0, and TLS 1.1 in Schannel for both client and server, leaving TLS 1.2 and later.

Take the helm: step-by-step
  1. Check first: old printers, scanners, line-of-business apps, and servers may still need TLS 1.0 or 1.1. Test on a few devices before rolling out.
  2. For many devices, push the registry values below with Intune (a PowerShell script or Settings catalog) or Group Policy Preferences.
  3. On a single device, run in an elevated PowerShell: foreach ($p in 'SSL 2.0','SSL 3.0','TLS 1.0','TLS 1.1') { foreach ($r in 'Server','Client') { $k = "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\$p\$r"; New-Item $k -Force | Out-Null; Set-ItemProperty $k Enabled 0 -Type DWord; Set-ItemProperty $k DisabledByDefault 1 -Type DWord } }
  4. TLS 1.2 is on by default in Windows 10 and 11. Leave it on, then restart the device.

Maps to:

  • SC.L2-3.13.8 Encrypt CUI in transit. Old SSL and early TLS versions have known weaknesses. Turning them off means connections use modern encryption.
  • 164.312(e)(2)(ii) Encryption in transit. Old SSL and early TLS versions have known weaknesses. Turning them off means connections use modern encryption.
  • SC.L1-B.1.X Protect communications at the boundary. Old SSL and early TLS versions have known weaknesses. Turning them off means connections use modern encryption.
  • 4.1 Establish and Maintain a Secure Configuration Process. Turning off outdated encryption protocols is part of a hardened, secure setup.
  • 314.4(c)(3) Encryption. Old SSL and early TLS versions have known weaknesses. Turning them off means connections use modern encryption.
  • PR.DS-02 Data in transit protected. Old SSL and early TLS versions have known weaknesses. Turning them off means connections use modern encryption.
  • 4.2.1 Strong cryptography for card data in transit. Old SSL and early TLS versions have known weaknesses. Turning them off means connections use modern encryption.
  • 2.2.5 Insecure services justified and secured. Old SSL and early TLS versions have known weaknesses. Turning them off means connections use modern encryption.
  • 500.15(a) Encryption. Old SSL and early TLS versions have known weaknesses. Turning them off means connections use modern encryption.
  • 248.30(a)(2)(i) Security and confidentiality of customer information. Old SSL and early TLS versions have known weaknesses. Turning them off means connections use modern encryption.
  • CC6.7 Controlling how data leaves. Old SSL and early TLS versions have known weaknesses. Turning them off means connections use modern encryption.
  • CI-09 Hardened configuration. Old SSL and early TLS versions have known weaknesses. Turning them off means connections use modern encryption.

Audit

Key audit subcategories are enabled (AUD-001)

High Audit

Fix: Apply an advanced audit policy covering logon, lockout, credential validation, account and group management, process creation, and policy change.

Take the helm: step-by-step
  1. Group Policy: Security Settings → Advanced Audit Policy Configuration. Set Credential Validation, Logon, User Account Management, and Sensitive Privilege Use to Success and Failure; Account Lockout to Failure; Security Group Management, Process Creation, and Audit Policy Change to Success.
  2. Also set Security Options → 'Audit: Force audit policy subcategory settings to override audit policy category settings' = Enabled.
  3. On a single device, for example: auditpol /set /subcategory:"Logon" /success:enable /failure:enable.

Maps to:

  • AU.L2-3.3.1 Create and retain system audit logs. Auditing records sign-ins, account changes, and other key events, so you can see what happened.
  • AU.L2-3.3.2 Ensure actions of individual users can be traced. Each audited event records the account that did it, so actions trace back to a person.
  • 164.312(b) Audit controls. Auditing records sign-ins, account changes, and other key events, so you can see what happened.
  • 164.308(a)(5)(ii)(C) Log-in monitoring. Logging sign-ins lets you spot repeated failures and unusual access.
  • 8.2 Collect Audit Logs. Auditing records sign-ins, account changes, and other key events, so you can see what happened.
  • 314.4(c)(8) Monitor and log user activity. Auditing records sign-ins, account changes, and other key events, so you can see what happened.
  • PR.PS-04 Log records generated. Auditing records sign-ins, account changes, and other key events, so you can see what happened.
  • DE.CM-03 Personnel activity monitored. Auditing records sign-ins, account changes, and other key events, so you can see what happened.
  • 10.2.1 Audit logs enabled. Auditing records sign-ins, account changes, and other key events, so you can see what happened.
  • 500.6(a)(2) Audit trails. Auditing records sign-ins, account changes, and other key events, so you can see what happened.
  • 248.30(a)(2)(i) Security and confidentiality of customer information. Auditing records sign-ins, account changes, and other key events, so you can see what happened.
  • CC7.2 Monitoring for attacks. Auditing records sign-ins, account changes, and other key events, so you can see what happened.
  • CI-11 Logging. Auditing records sign-ins, account changes, and other key events, so you can see what happened.

Security event log is large enough (AUD-002)

Medium Audit

Fix: Set the Security log maximum size to 196,608 KB or more, and forward logs to a central store.

Default thresholds: Minimum Security log size (KB) = 196608

Take the helm: step-by-step
  1. Group Policy: Administrative Templates → Windows Components → Event Log Service → Security → 'Specify the maximum log file size (KB)' = 196608.
  2. On a single device: wevtutil sl Security /ms:201326592.
  3. Forward logs to a SIEM or Log Analytics so they're kept off the device as well.

Maps to:

  • AU.L2-3.3.1 Create and retain system audit logs. A larger log keeps important events long enough to investigate, instead of overwriting them within days.
  • 164.312(b) Audit controls. A larger log keeps important events long enough to investigate, instead of overwriting them within days.
  • 8.3 Ensure Adequate Audit Log Storage. A larger log keeps important events long enough to investigate, instead of overwriting them within days.
  • 314.4(c)(8) Monitor and log user activity. A larger log keeps important events long enough to investigate, instead of overwriting them within days.
  • PR.PS-04 Log records generated. A larger log keeps important events long enough to investigate, instead of overwriting them within days.
  • 10.5.1 Audit log retention. A larger Security log keeps more history on the device. Keeping 12 months usually also means forwarding logs to a central store.
  • 500.6(a)(2) Audit trails. A larger log keeps important events long enough to investigate, instead of overwriting them within days.
  • 248.30(a)(2)(i) Security and confidentiality of customer information. A larger log keeps important events long enough to investigate, instead of overwriting them within days.
  • CC7.2 Monitoring for attacks. A larger log keeps important events long enough to investigate, instead of overwriting them within days.
  • CI-11 Logging. A larger log keeps important events long enough to investigate, instead of overwriting them within days.

PowerShell script block logging is on (AUD-003)

Medium Audit

Fix: Enable 'Turn on PowerShell Script Block Logging'.

Take the helm: step-by-step
  1. Group Policy: Administrative Templates → Windows Components → Windows PowerShell → 'Turn on PowerShell Script Block Logging' = Enabled.
  2. On a single device: New-Item HKLM:\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging -Force | Out-Null; Set-ItemProperty HKLM:\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging -Name EnableScriptBlockLogging -Value 1.

Maps to:

  • AU.L2-3.3.1 Create and retain system audit logs. Script block logging records the PowerShell commands that run. Attackers use PowerShell constantly.
  • AU.L2-3.3.2 Ensure actions of individual users can be traced. Logged PowerShell activity is tied to the account that ran it.
  • 164.312(b) Audit controls. Script block logging records the PowerShell commands that run. Attackers use PowerShell constantly.
  • 8.2 Collect Audit Logs. Script block logging records the PowerShell commands that run. Attackers use PowerShell constantly.
  • 314.4(c)(8) Monitor and log user activity. Script block logging records the PowerShell commands that run. Attackers use PowerShell constantly.
  • PR.PS-04 Log records generated. Script block logging records the PowerShell commands that run. Attackers use PowerShell constantly.
  • DE.CM-09 Computing monitored. Script block logging records the PowerShell commands that run. Attackers use PowerShell constantly.
  • 10.2.1 Audit logs enabled. Script block logging records the PowerShell commands that run. Attackers use PowerShell constantly.
  • 500.6(a)(2) Audit trails. Script block logging records the PowerShell commands that run. Attackers use PowerShell constantly.
  • 248.30(a)(2)(i) Security and confidentiality of customer information. Script block logging records the PowerShell commands that run. Attackers use PowerShell constantly.
  • CC7.2 Monitoring for attacks. Script block logging records the PowerShell commands that run. Attackers use PowerShell constantly.
  • CI-11 Logging. Script block logging records the PowerShell commands that run. Attackers use PowerShell constantly.

Process creation events include command line (AUD-004)

Low Audit

Fix: Enable 'Include command line in process creation events'.

Take the helm: step-by-step
  1. Group Policy: Administrative Templates → System → Audit Process Creation → 'Include command line in process creation events' = Enabled.
  2. On a single device: New-Item HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit -Force | Out-Null; Set-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit -Name ProcessCreationIncludeCmdLine_Enabled -Value 1 -Type DWord.
  3. Make sure Process Creation auditing is on as well (see AUD-001).

Maps to:

  • AU.L2-3.3.2 Ensure actions of individual users can be traced. Recording each program's full command line shows exactly what ran and which account ran it.
  • 8.2 Collect Audit Logs. Recording each program's full command line shows exactly what ran and which account ran it.
  • 314.4(c)(8) Monitor and log user activity. Recording each program's full command line shows exactly what ran and which account ran it.
  • PR.PS-04 Log records generated. Recording each program's full command line shows exactly what ran and which account ran it.
  • 10.2.1 Audit logs enabled. Recording each program's full command line shows exactly what ran and which account ran it.
  • 500.6(a)(2) Audit trails. Recording each program's full command line shows exactly what ran and which account ran it.
  • 248.30(a)(2)(i) Security and confidentiality of customer information. Recording each program's full command line shows exactly what ran and which account ran it.
  • CC7.2 Monitoring for attacks. Recording each program's full command line shows exactly what ran and which account ran it.
  • CI-11 Logging. Recording each program's full command line shows exactly what ran and which account ran it.

Time synchronization is running (AUD-005)

Low Audit

Fix: Set the Windows Time service to start automatically and sync to the domain hierarchy or a trusted NTP source.

Take the helm: step-by-step
  1. Start the time service: Set-Service W32Time -StartupType Automatic; Start-Service W32Time.
  2. Domain-joined devices sync from the domain automatically. Others: w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /update, then w32tm /resync.
  3. Confirm with w32tm /query /status.

Maps to:

  • AU.L2-3.3.7 Synchronize system clocks with an authoritative source. Accurate time on every computer keeps log entries in the right order during an investigation.
  • 314.4(c)(8) Monitor and log user activity. Accurate time on every computer keeps log entries in the right order during an investigation.
  • PR.PS-04 Log records generated. Accurate time on every computer keeps log entries in the right order during an investigation.
  • 10.6.1 Time synchronization. Accurate time on every computer keeps log entries in the right order during an investigation.
  • 500.6(a)(2) Audit trails. Accurate time on every computer keeps log entries in the right order during an investigation.
  • CC7.2 Monitoring for attacks. Accurate time on every computer keeps log entries in the right order during an investigation.
  • CI-11 Logging. Accurate time on every computer keeps log entries in the right order during an investigation.

Patching

Updates installed recently (PAT-001)

High Patching

Fix: Investigate why updates are not installing and apply the latest cumulative update.

Default thresholds: Maximum days since last update = 35

Take the helm: step-by-step
  1. Open Settings → Windows Update → Update history and look for failed updates.
  2. Make sure an update policy (Intune update rings, WSUS, or your RMM) targets this device and isn't paused.
  3. If updates keep failing, free up disk space, restart, and run DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow.

Maps to:

  • SI.L2-3.14.1 Identify, report, and correct system flaws in a timely manner. Recent security updates mean the known flaws attackers use have been fixed.
  • 164.308(a)(1)(ii)(B) Risk management. Installing updates fixes known weak spots, one of the biggest ways to reduce risk.
  • SI.L1-B.1.XII Fix flaws promptly. Recent security updates mean the known flaws attackers use have been fixed.
  • 7.3 Perform Automated Operating System Patch Management. Recent security updates mean the known flaws attackers use have been fixed.
  • 314.4(c) Safeguards that control identified risks. Recent security updates mean the known flaws attackers use have been fixed.
  • PR.PS-02 Software maintained. Recent security updates mean the known flaws attackers use have been fixed.
  • 6.3.3 Security patches installed. Recent security updates mean the known flaws attackers use have been fixed.
  • 500.5(c) Timely remediation of vulnerabilities. Recent security updates mean the known flaws attackers use have been fixed.
  • 248.30(a)(2)(ii) Protection against anticipated threats. Recent security updates mean the known flaws attackers use have been fixed.
  • CC7.1 Finding vulnerabilities and configuration drift. Recent security updates mean the known flaws attackers use have been fixed.
  • CI-04 Prompt security updates. Recent security updates mean the known flaws attackers use have been fixed.

No reboot pending (PAT-002)

Low Patching

Fix: Reboot the device to finish installing updates.

Take the helm: step-by-step
  1. Restart the device to finish installing updates.
  2. Use maintenance windows or Intune update ring deadlines so devices that stay on still restart.

Maps to:

  • SI.L2-3.14.1 Identify, report, and correct system flaws in a timely manner. Many updates only take effect after a restart. A pending reboot means fixes are installed but not active yet.
  • SI.L1-B.1.XII Fix flaws promptly. Many updates only take effect after a restart. A pending reboot means fixes are installed but not active yet.
  • 7.3 Perform Automated Operating System Patch Management. Many updates only take effect after a restart. A pending reboot means fixes are installed but not active yet.
  • 314.4(c) Safeguards that control identified risks. Many updates only take effect after a restart. A pending reboot means fixes are installed but not active yet.
  • PR.PS-02 Software maintained. Many updates only take effect after a restart. A pending reboot means fixes are installed but not active yet.
  • 6.3.3 Security patches installed. Many updates only take effect after a restart. A pending reboot means fixes are installed but not active yet.
  • 500.5(c) Timely remediation of vulnerabilities. Many updates only take effect after a restart. A pending reboot means fixes are installed but not active yet.
  • 248.30(a)(2)(ii) Protection against anticipated threats. Many updates only take effect after a restart. A pending reboot means fixes are installed but not active yet.
  • CC7.1 Finding vulnerabilities and configuration drift. Many updates only take effect after a restart. A pending reboot means fixes are installed but not active yet.
  • CI-04 Prompt security updates. Many updates only take effect after a restart. A pending reboot means fixes are installed but not active yet.

Operating system is supported (PAT-003)

High Patching

Fix: Upgrade to a supported Windows release before end of servicing.

Default thresholds: Warn this many days before end of support = 60

Take the helm: step-by-step
  1. Check hardware compatibility (TPM 2.0, supported CPU) with the PC Health Check app.
  2. Upgrade to a supported Windows release with Windows Update, an Intune feature update policy, or the Installation Assistant.
  3. If the device can't be upgraded, enroll it in Extended Security Updates where available, or replace it.

Maps to:

  • SI.L2-3.14.1 Identify, report, and correct system flaws in a timely manner. Windows versions past end of support no longer get security fixes, so new flaws stay open for good.
  • 164.308(a)(1)(ii)(B) Risk management. Unsupported Windows is a growing risk that can't be patched away. Spotting it early lets you plan the upgrade.
  • SI.L1-B.1.XII Fix flaws promptly. Windows versions past end of support no longer get security fixes, so new flaws stay open for good.
  • 2.2 Ensure Authorized Software is Currently Supported. This confirms the Windows version is still supported by Microsoft, which is exactly what the safeguard asks.
  • 314.4(c) Safeguards that control identified risks. Windows versions past end of support no longer get security fixes, so new flaws stay open for good.
  • PR.PS-02 Software maintained. Windows versions past end of support no longer get security fixes, so new flaws stay open for good.
  • 12.3.4 Technologies reviewed, including end of life. Windows versions past end of support no longer get security fixes, so new flaws stay open for good.
  • 500.3(c) Asset inventory, device management, and end of life. Windows versions past end of support no longer get security fixes, so new flaws stay open for good.
  • 248.30(a)(2)(ii) Protection against anticipated threats. Windows versions past end of support no longer get security fixes, so new flaws stay open for good.
  • CC7.1 Finding vulnerabilities and configuration drift. Windows versions past end of support no longer get security fixes, so new flaws stay open for good.
  • CI-05 No end-of-life systems. Windows versions past end of support no longer get security fixes, so new flaws stay open for good.

Automatic updates are on (PAT-004)

Medium Patching

Fix: Let Windows Update install updates automatically, through Intune update rings or Group Policy, and keep the Windows Update service enabled.

Take the helm: step-by-step
  1. For many devices, use Intune: Devices → Windows → Update rings for Windows 10 and later → set Automatic update behavior to 'Auto install at maintenance time' or 'Reset to default'.
  2. With Group Policy: Computer Configuration → Administrative Templates → Windows Components → Windows Update → Configure Automatic Updates → Enabled, option 4 (Auto download and schedule the install). Make sure no policy sets 'No auto-restart' without a deadline.
  3. On Windows Home or a single device, remove a leftover policy that limits updates: Remove-ItemProperty HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU -Name AUOptions, NoAutoUpdate -ErrorAction SilentlyContinue, then open Settings → Windows Update and select Check for updates.
  4. If the Windows Update service is disabled, re-enable it: Set-Service wuauserv -StartupType Manual then Start-Service wuauserv.
  5. If an RMM or patch tool installs updates and turns off automatic updates on purpose, confirm PAT-001 passes on the device and record the tool in your patch policy.

Maps to:

  • SI.L2-3.14.1 Identify, report, and correct system flaws in a timely manner. Automatic updates keep security fixes arriving without anyone having to remember.
  • 164.308(a)(1)(ii)(B) Risk management. Automatic updates close known weak spots quickly, which lowers risk without extra effort.
  • SI.L1-B.1.XII Fix flaws promptly. Automatic updates keep security fixes arriving without anyone having to remember.
  • 7.3 Perform Automated Operating System Patch Management. Automatic updates keep security fixes arriving without anyone having to remember.
  • 314.4(c) Safeguards that control identified risks. Automatic updates keep security fixes arriving without anyone having to remember.
  • PR.PS-02 Software maintained. Automatic updates keep security fixes arriving without anyone having to remember.
  • 6.3.3 Security patches installed. Automatic updates keep security fixes arriving without anyone having to remember.
  • 500.5(c) Timely remediation of vulnerabilities. Automatic updates keep security fixes arriving without anyone having to remember.
  • 248.30(a)(2)(ii) Protection against anticipated threats. Automatic updates keep security fixes arriving without anyone having to remember.
  • CC7.1 Finding vulnerabilities and configuration drift. Automatic updates keep security fixes arriving without anyone having to remember.
  • CI-04 Prompt security updates. Automatic updates keep security fixes arriving without anyone having to remember.

Management

Device is centrally managed (MGT-001)

Medium Management

Fix: Enroll the device in Intune (or another MDM) or join it to your Active Directory domain, so its settings are managed and it appears in your inventory.

Take the helm: step-by-step
  1. To enroll Entra-joined devices in Intune automatically: Entra admin center → Mobility (MDM and WIP) → Microsoft Intune → set MDM user scope to All (or a group), then have users sign out and back in.
  2. For a single device: Settings → Accounts → Access work or school → Connect (or 'Enroll only in device management') and sign in with a work account.
  3. If you manage devices with Active Directory instead, join the device to the domain so Group Policy applies.
  4. Windows Home can't join a domain, join Entra ID, or enroll in Intune. Upgrade to Windows Pro first (Settings → System → Activation).
  5. Confirm with dsregcmd /status: look for AzureAdJoined or DomainJoined, and an MDMUrl. The device should also appear in Intune or Active Directory.

Maps to:

  • CM.L2-3.4.1 Maintain baseline configurations and inventories. A centrally managed computer shows up in your inventory and gets your approved settings automatically.
  • IA.L1-B.1.V Identify users and devices. Enrolling the device gives it a known identity in your management system.
  • 1.1 Establish and Maintain Detailed Enterprise Asset Inventory. Management enrollment keeps the device in an up-to-date inventory.
  • 4.1 Establish and Maintain a Secure Configuration Process. A centrally managed computer shows up in your inventory and gets your approved settings automatically.
  • 314.4(c)(2) Know your systems and devices. A centrally managed computer shows up in your inventory and gets your approved settings automatically.
  • ID.AM-01 Hardware inventory. A centrally managed computer shows up in your inventory and gets your approved settings automatically.
  • PR.PS-01 Configuration management. A centrally managed computer shows up in your inventory and gets your approved settings automatically.
  • 12.5.1 Inventory of system components. A centrally managed computer shows up in your inventory and gets your approved settings automatically.
  • 500.13(a) Asset inventory. A centrally managed computer shows up in your inventory and gets your approved settings automatically.
  • 500.3(c) Asset inventory, device management, and end of life. A centrally managed computer shows up in your inventory and gets your approved settings automatically.
  • CC6.1 Logical access security. A centrally managed computer shows up in your inventory and gets your approved settings automatically.
  • CC7.1 Finding vulnerabilities and configuration drift. A centrally managed computer shows up in your inventory and gets your approved settings automatically.