Description | Tests | Scoring | |||||
---|---|---|---|---|---|---|---|
Pass | Fail | Error | Unkn. | Score | Max | Percent | |
1 Account Policies | 5 | 2 | 0 | 2 | 5.0 | 9.0 | 56% |
1.1 Password Policy | 2 | 2 | 0 | 2 | 2.0 | 6.0 | 33% |
1.2 Account Lockout Policy | 3 | 0 | 0 | 0 | 3.0 | 3.0 | 100% |
2 Local Policies | 92 | 7 | 0 | 1 | 92.0 | 100.0 | 92% |
2.1 Audit Policy | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
2.2 User Rights Assignment | 34 | 3 | 0 | 0 | 34.0 | 37.0 | 92% |
2.3 Security Options | 58 | 4 | 0 | 1 | 58.0 | 63.0 | 92% |
2.3.1 Accounts | 4 | 2 | 0 | 0 | 4.0 | 6.0 | 67% |
2.3.2 Audit | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
2.3.3 DCOM | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
2.3.4 Devices | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
2.3.5 Domain controller | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
2.3.6 Domain member | 6 | 0 | 0 | 0 | 6.0 | 6.0 | 100% |
2.3.7 Interactive logon | 8 | 0 | 0 | 0 | 8.0 | 8.0 | 100% |
2.3.8 Microsoft network client | 3 | 0 | 0 | 0 | 3.0 | 3.0 | 100% |
2.3.9 Microsoft network server | 5 | 0 | 0 | 0 | 5.0 | 5.0 | 100% |
2.3.10 Network access | 9 | 1 | 0 | 1 | 9.0 | 11.0 | 82% |
2.3.11 Network security | 8 | 1 | 0 | 0 | 8.0 | 9.0 | 89% |
2.3.12 Recovery console | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
2.3.13 Shutdown | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
2.3.14 System cryptography | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
2.3.15 System objects | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
2.3.16 System settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
2.3.17 User Account Control | 8 | 0 | 0 | 0 | 8.0 | 8.0 | 100% |
3 Event Log | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
4 Restricted Groups | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
5 System Services | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
6 Registry | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
7 File System | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
8 Wired Network (IEEE 802.3) Policies | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
9 Windows Firewall with Advanced Security | 20 | 6 | 0 | 0 | 20.0 | 26.0 | 77% |
9.1 Domain Profile | 6 | 2 | 0 | 0 | 6.0 | 8.0 | 75% |
9.2 Private Profile | 6 | 2 | 0 | 0 | 6.0 | 8.0 | 75% |
9.3 Public Profile | 8 | 2 | 0 | 0 | 8.0 | 10.0 | 80% |
10 Network List Manager Policies | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
11 Wireless Network (IEEE 802.11) Policies | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
12 Public Key Policies | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
13 Software Restriction Policies | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
14 Network Access Protection NAP Client Configuration | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
15 Application Control Policies | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
16 IP Security Policies | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
17 Advanced Audit Policy Configuration | 0 | 27 | 0 | 0 | 0.0 | 27.0 | 0% |
17.1 Account Logon | 0 | 1 | 0 | 0 | 0.0 | 1.0 | 0% |
17.2 Account Management | 0 | 3 | 0 | 0 | 0.0 | 3.0 | 0% |
17.3 Detailed Tracking | 0 | 2 | 0 | 0 | 0.0 | 2.0 | 0% |
17.4 DS Access | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
17.5 Logon/Logoff | 0 | 6 | 0 | 0 | 0.0 | 6.0 | 0% |
17.6 Object Access | 0 | 4 | 0 | 0 | 0.0 | 4.0 | 0% |
17.7 Policy Change | 0 | 5 | 0 | 0 | 0.0 | 5.0 | 0% |
17.8 Privilege Use | 0 | 1 | 0 | 0 | 0.0 | 1.0 | 0% |
17.9 System | 0 | 5 | 0 | 0 | 0.0 | 5.0 | 0% |
18 Administrative Templates (Computer) | 111 | 7 | 0 | 0 | 111.0 | 118.0 | 94% |
18.1 Control Panel | 3 | 0 | 0 | 0 | 3.0 | 3.0 | 100% |
18.1.1 Personalization | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.1.2 Regional and Language Options | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.1.2.1 Handwriting personalization | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.2 LAPS | 5 | 1 | 0 | 0 | 5.0 | 6.0 | 83% |
18.3 MS Security Guide | 6 | 0 | 0 | 0 | 6.0 | 6.0 | 100% |
18.4 MSS (Legacy) | 8 | 0 | 0 | 0 | 8.0 | 8.0 | 100% |
18.5 Network | 6 | 1 | 0 | 0 | 6.0 | 7.0 | 86% |
18.5.1 Background Intelligent Transfer Service (BITS) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.2 BranchCache | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.3 DirectAccess Client Experience Settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.4 DNS Client | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.5.5 Fonts | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.6 Hotspot Authentication | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.7 Lanman Server | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.8 Lanman Workstation | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.5.9 Link-Layer Topology Discovery | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.10 Microsoft Peer-to-Peer Networking Services | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.10.1 Peer Name Resolution Protocol | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.11 Network Connections | 3 | 0 | 0 | 0 | 3.0 | 3.0 | 100% |
18.5.11.1 Windows Defender Firewall (formerly Windows Firewall) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.12 Network Connectivity Status Indicator | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.13 Network Isolation | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.14 Network Provider | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.5.15 Offline Files | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.16 QoS Packet Scheduler | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.17 SNMP | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.18 SSL Configuration Settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.19 TCPIP Settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.19.1 IPv6 Transition Technologies | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.19.2 Parameters | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.20 Windows Connect Now | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.5.21 Windows Connection Manager | 0 | 1 | 0 | 0 | 0.0 | 1.0 | 0% |
18.6 Printers | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.7 Start Menu and Taskbar | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.7.1 Notifications | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8 System | 23 | 0 | 0 | 0 | 23.0 | 23.0 | 100% |
18.8.1 Access-Denied Assistance | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.2 App-V | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.3 Audit Process Creation | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.8.4 Credentials Delegation | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.8.5 Device Guard | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.6 Device Health Attestation Service | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.7 Device Installation | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.7.1 Device Installation Restrictions | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.8 Device Redirection | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.9 Disk NV Cache | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.10 Disk Quotas | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.11 Display | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.12 Distributed COM | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.13 Driver Installation | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.14 Early Launch Antimalware | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.8.15 Enhanced Storage Access | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.16 File Classification Infrastructure | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.17 File Share Shadow Copy Agent | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.18 File Share Shadow Copy Provider | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.19 Filesystem (formerly NTFS Filesystem) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.20 Folder Redirection | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.21 Group Policy | 4 | 0 | 0 | 0 | 4.0 | 4.0 | 100% |
18.8.21.1 Logging and tracing | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.22 Internet Communication Management | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.8.22.1 Internet Communication settings | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.8.23 iSCSI | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.24 KDC | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.25 Kerberos | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.26 Kernel DMA Protection | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.8.27 Locale Services | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.28 Logon | 7 | 0 | 0 | 0 | 7.0 | 7.0 | 100% |
18.8.29 Mitigation Options | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.30 Net Logon | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.31 OS Policies | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.32 Performance Control Panel | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.33 PIN Complexity | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.34 Power Management | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.8.34.1 Button Settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.34.2 Energy Saver Settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.34.3 Hard Disk Settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.34.4 Notification Settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.34.5 Power Throttling Settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.34.6 Sleep Settings | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.8.35 Recovery | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.36 Remote Assistance | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.8.37 Remote Procedure Call | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.8.38 Removable Storage Access | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.39 Scripts | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.40 Server Manager | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.41 Service Control Manager Settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.42 Shutdown | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.43 Shutdown Options | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.44 Storage Health | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.45 Storage Sense | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.46 System Restore | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.47 Troubleshooting and Diagnostics | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.47.1 Application Compatibility Diagnostics | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.47.2 Corrupted File Recovery | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.47.3 Disk Diagnostic | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.47.4 Fault Tolerant Heap | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.47.5 Microsoft Support Diagnostic Tool | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.47.6 MSI Corrupted File Recovery | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.47.7 Scheduled Maintenance | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.47.8 Scripted Diagnostics | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.47.9 Windows Boot Performance Diagnostics | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.47.10 Windows Memory Leak Diagnosis | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.47.11 Windows Performance PerfTrack | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.48 Trusted Platform Module Services | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.49 User Profiles | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.50 Windows File Protection | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.51 Windows HotStart | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.52 Windows Time Service | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.8.52.1 Time Providers | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9 Windows Components | 60 | 5 | 0 | 0 | 60.0 | 65.0 | 92% |
18.9.1 Active Directory Federation Services | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.2 ActiveX Installer Service | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.3 Add features to Windows 8 / 8.1 / 10 (formerly Windows Anytime Upgrade) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.4 App Package Deployment | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.5 App Privacy | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.6 App runtime | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.7 Application Compatibility | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.8 AutoPlay Policies | 3 | 0 | 0 | 0 | 3.0 | 3.0 | 100% |
18.9.9 Backup | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.10 Biometrics | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.10.1 Facial Features | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.11 BitLocker Drive Encryption | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.12 Camera | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.13 Cloud Content | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.14 Connect | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.15 Credential User Interface | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.9.16 Data Collection and Preview Builds | 3 | 0 | 0 | 0 | 3.0 | 3.0 | 100% |
18.9.17 Delivery Optimization | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.18 Desktop Gadgets | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.19 Desktop Window Manager | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.20 Device and Driver Compatibility | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.21 Device Registration (formerly Workplace Join) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.22 Digital Locker | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.23 Edge UI | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.24 EMET | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.25 Event Forwarding | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.26 Event Log Service | 8 | 0 | 0 | 0 | 8.0 | 8.0 | 100% |
18.9.26.1 Application | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.9.26.2 Security | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.9.26.3 Setup | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.9.26.4 System | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.9.27 Event Logging | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.28 Event Viewer | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.29 Family Safety (formerly Parental Controls) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.30 File Explorer (formerly Windows Explorer) | 3 | 0 | 0 | 0 | 3.0 | 3.0 | 100% |
18.9.30.1 Previous Versions | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.31 File History | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.32 Find My Device | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.33 Game Explorer | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.34 Handwriting | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.35 HomeGroup | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.36 Import Video | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.37 Internet Explorer | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.38 Internet Information Services | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.39 Location and Sensors | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.39.1 Windows Location Provider | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.40 Maintenance Scheduler | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.41 Maps | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.42 MDM | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.43 Messaging | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.44 Microsoft account | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.45 Microsoft Edge | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.46 Microsoft FIDO Authentication | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.47 Microsoft Secondary Authentication Factor | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.48 Microsoft User Experience Virtualization | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.49 NetMeeting | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.50 Network Access Protection | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.51 Network Projector | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.52 OneDrive (formerly SkyDrive) | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.53 Online Assistance | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.54 OOBE | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.55 Password Synchronization | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.56 Portable Operating System | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.57 Presentation Settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.58 Push To Install | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.59 Remote Desktop Services (formerly Terminal Services) | 5 | 4 | 0 | 0 | 5.0 | 9.0 | 56% |
18.9.59.1 RD Licensing (formerly TS Licensing) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.59.2 Remote Desktop Connection Client | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.59.2.1 RemoteFX USB Device Redirection | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.59.3 Remote Desktop Session Host (formerly Terminal Server) | 4 | 4 | 0 | 0 | 4.0 | 8.0 | 50% |
18.9.59.3.1 Application Compatibility | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.59.3.2 Connections | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.59.3.3 Device and Resource Redirection | 0 | 1 | 0 | 0 | 0.0 | 1.0 | 0% |
18.9.59.3.4 Licensing | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.59.3.5 Printer Redirection | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.59.3.6 Profiles | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.59.3.7 RD Connection Broker (formerly TS Connection Broker) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.59.3.8 Remote Session Environment | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.59.3.9 Security | 2 | 3 | 0 | 0 | 2.0 | 5.0 | 40% |
18.9.59.3.10 Session Time Limits | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.59.3.11 Temporary folders | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.9.60 RSS Feeds | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.61 Search | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.61.1 OCR | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.62 Security Center | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.63 Server for NIS | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.64 Shutdown Options | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.65 Smart Card | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.66 Software Protection Platform | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.67 Sound Recorder | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.68 Speech | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.69 Store | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.70 Sync your settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.71 Tablet PC | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.72 Task Scheduler | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.73 Text Input | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.74 Windows Calendar | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.75 Windows Color System | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.76 Windows Customer Experience Improvement Program | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.77 Windows Defender Antivirus (formerly Windows Defender) | 9 | 0 | 0 | 0 | 9.0 | 9.0 | 100% |
18.9.77.1 Client Interface | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.77.2 Exclusions | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.77.3 MAPS | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.77.4 MpEngine | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.77.5 Network Inspection System | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.77.6 Quarantine | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.77.7 Real-time Protection | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.77.8 Remediation | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.77.9 Reporting | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.77.10 Scan | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.9.77.11 Security Intelligence Updates (formerly Signature Updates) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.77.12 Threats | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.77.13 Windows Defender Exploit Guard | 3 | 0 | 0 | 0 | 3.0 | 3.0 | 100% |
18.9.77.13.1 Attack Surface Reduction | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.9.77.13.2 Controlled Folder Access | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.77.13.3 Network Protection | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.78 Windows Defender Application Guard | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.79 Windows Defender Exploit Guard | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.80 Windows Defender SmartScreen | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.80.1 Explorer | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.81 Windows Error Reporting | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.82 Windows Game Recording and Broadcasting | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.83 Windows Hello for Business (formerly Microsoft Passport for Work) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.84 Windows Ink Workspace | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.85 Windows Installer | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.9.86 Windows Logon Options | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.87 Windows Mail | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.88 Windows Media Center | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.89 Windows Media Digital Rights Management | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.90 Windows Media Player | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.91 Windows Meeting Space | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.92 Windows Messenger | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.93 Windows Mobility Center | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.94 Windows Movie Maker | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.95 Windows PowerShell | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
18.9.96 Windows Reliability Analysis | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.97 Windows Remote Management (WinRM) | 6 | 0 | 0 | 0 | 6.0 | 6.0 | 100% |
18.9.97.1 WinRM Client | 3 | 0 | 0 | 0 | 3.0 | 3.0 | 100% |
18.9.97.2 WinRM Service | 3 | 0 | 0 | 0 | 3.0 | 3.0 | 100% |
18.9.98 Windows Remote Shell | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.99 Windows Security (formerly Windows Defender Security Center) | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.99.1 Account protection | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.99.2 App and browser protection | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
18.9.100 Windows SideShow | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.101 Windows System Resource Manager | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
18.9.102 Windows Update | 5 | 1 | 0 | 0 | 5.0 | 6.0 | 83% |
18.9.102.1 Windows Update for Business (formerly Defer Windows Updates) | 3 | 0 | 0 | 0 | 3.0 | 3.0 | 100% |
19 Administrative Templates (User) | 7 | 4 | 0 | 0 | 7.0 | 11.0 | 64% |
19.1 Control Panel | 0 | 4 | 0 | 0 | 0.0 | 4.0 | 0% |
19.1.1 Add or Remove Programs | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.1.2 Display | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.1.3 Personalization (formerly Desktop Themes) | 0 | 4 | 0 | 0 | 0.0 | 4.0 | 0% |
19.2 Desktop | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.3 Network | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.4 Shared Folders | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.5 Start Menu and Taskbar | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
19.5.1 Notifications | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
19.6 System | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.6.1 Ctrl+Alt+Del Options | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.6.2 Display | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.6.3 Driver Installation | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.6.4 Folder Redirection | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.6.5 Group Policy | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.6.6 Internet Communication Management | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.6.6.1 Internet Communication settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7 Windows Components | 6 | 0 | 0 | 0 | 6.0 | 6.0 | 100% |
19.7.1 Add features to Windows 8 / 8.1 / 10 (formerly Windows Anytime Upgrade) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.2 App runtime | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.3 Application Compatibility | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.4 Attachment Manager | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
19.7.5 AutoPlay Policies | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.6 Backup | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.7 Cloud Content | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
19.7.8 Credential User Interface | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.9 Data Collection and Preview Builds | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.10 Desktop Gadgets | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.11 Desktop Window Manager | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.12 Digital Locker | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.13 Edge UI | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.14 File Explorer (formerly Windows Explorer) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.15 File Revocation | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.16 IME | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.17 Import Video | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.18 Instant Search | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.19 Internet Explorer | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.20 Location and Sensors | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.21 Microsoft Edge | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.22 Microsoft Management Console | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.23 Microsoft User Experience Virtualization | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.24 NetMeeting | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.25 Network Projector | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.26 Network Sharing | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
19.7.27 OOBE | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.28 Presentation Settings | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.29 Remote Desktop Services (formerly Terminal Services) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.30 RSS Feeds | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.31 Search | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.32 Sound Recorder | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.33 Store | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.34 Tablet PC | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.35 Task Scheduler | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.36 Windows Calendar | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.37 Windows Color System | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.38 Windows Defender SmartScreen | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.39 Windows Error Reporting | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.40 Windows Hello for Business (formerly Microsoft Passport for Work) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.41 Windows Installer | 1 | 0 | 0 | 0 | 1.0 | 1.0 | 100% |
19.7.42 Windows Logon Options | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.43 Windows Mail | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.44 Windows Media Center | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.45 Windows Media Player | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.45.1 Networking | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
19.7.45.2 Playback | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
Total | 235 | 53 | 0 | 3 | 235.0 | 291.0 | 81% |
This benchmark contains 6 profiles.The Level 1 - Member Server profile was used for this assessment.
Title | Description |
---|---|
Level 1 - Domain Controller |
Items in this profile apply to Domain Controllers and intend to:
Show
<xccdf:Profile xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="xccdf_org.cisecurity.benchmarks_profile_Level_1_-_Domain_Controller"> <xccdf:title xml:lang="en">Level 1 - Domain Controller</xccdf:title> <xccdf:description xml:lang="en"> <xhtml:p>Items in this profile apply to Domain Controllers and intend to:</xhtml:p> <xhtml:ul> <xhtml:li>be practical and prudent;</xhtml:li> <xhtml:li>provide a clear security benefit; and</xhtml:li> <xhtml:li>not inhibit the utility of the technology beyond acceptable means.</xhtml:li> </xhtml:ul> </xccdf:description> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1_L1_Ensure_Enforce_password_history_is_set_to_24_or_more_passwords" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.2_L1_Ensure_Maximum_password_age_is_set_to_60_or_fewer_days_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.3_L1_Ensure_Minimum_password_age_is_set_to_1_or_more_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.4_L1_Ensure_Minimum_password_length_is_set_to_14_or_more_characters" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.5_L1_Ensure_Password_must_meet_complexity_requirements_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.6_L1_Ensure_Store_passwords_using_reversible_encryption_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.1_L1_Ensure_Account_lockout_duration_is_set_to_15_or_more_minutes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.2_L1_Ensure_Account_lockout_threshold_is_set_to_10_or_fewer_invalid_logon_attempts_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.3_L1_Ensure_Reset_account_lockout_counter_after_is_set_to_15_or_more_minutes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1_L1_Ensure_Access_Credential_Manager_as_a_trusted_caller_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.2_L1_Ensure_Access_this_computer_from_the_network_is_set_to_Administrators_Authenticated_Users_ENTERPRISE_DOMAIN_CONTROLLERS_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.4_L1_Ensure_Act_as_part_of_the_operating_system_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.5_L1_Ensure_Add_workstations_to_domain_is_set_to_Administrators_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.6_L1_Ensure_Adjust_memory_quotas_for_a_process_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.7_L1_Ensure_Allow_log_on_locally_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.8_L1_Ensure_Allow_log_on_through_Remote_Desktop_Services_is_set_to_Administrators_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.10_L1_Ensure_Back_up_files_and_directories_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.11_L1_Ensure_Change_the_system_time_is_set_to_Administrators_LOCAL_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.12_L1_Ensure_Change_the_time_zone_is_set_to_Administrators_LOCAL_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.13_L1_Ensure_Create_a_pagefile_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.14_L1_Ensure_Create_a_token_object_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.15_L1_Ensure_Create_global_objects_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.16_L1_Ensure_Create_permanent_shared_objects_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.17_L1_Ensure_Create_symbolic_links_is_set_to_Administrators_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.19_L1_Ensure_Debug_programs_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.20_L1_Ensure_Deny_access_to_this_computer_from_the_network_to_include_Guests_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.22_L1_Ensure_Deny_log_on_as_a_batch_job_to_include_Guests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.23_L1_Ensure_Deny_log_on_as_a_service_to_include_Guests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.24_L1_Ensure_Deny_log_on_locally_to_include_Guests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.25_L1_Ensure_Deny_log_on_through_Remote_Desktop_Services_to_include_Guests_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.27_L1_Ensure_Enable_computer_and_user_accounts_to_be_trusted_for_delegation_is_set_to_Administrators_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.29_L1_Ensure_Force_shutdown_from_a_remote_system_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.30_L1_Ensure_Generate_security_audits_is_set_to_LOCAL_SERVICE_NETWORK_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.31_L1_Ensure_Impersonate_a_client_after_authentication_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE_SERVICE_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.33_L1_Ensure_Increase_scheduling_priority_is_set_to_Administrators_Window_ManagerWindow_Manager_Group" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.34_L1_Ensure_Load_and_unload_device_drivers_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.35_L1_Ensure_Lock_pages_in_memory_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.37_L1_Ensure_Manage_auditing_and_security_log_is_set_to_Administrators_and_when_Exchange_is_running_in_the_environment_Exchange_Servers_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.39_L1_Ensure_Modify_an_object_label_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.40_L1_Ensure_Modify_firmware_environment_values_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.41_L1_Ensure_Perform_volume_maintenance_tasks_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.42_L1_Ensure_Profile_single_process_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.43_L1_Ensure_Profile_system_performance_is_set_to_Administrators_NT_SERVICEWdiServiceHost" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.44_L1_Ensure_Replace_a_process_level_token_is_set_to_LOCAL_SERVICE_NETWORK_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.45_L1_Ensure_Restore_files_and_directories_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.46_L1_Ensure_Shut_down_the_system_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.47_L1_Ensure_Synchronize_directory_service_data_is_set_to_No_One_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.48_L1_Ensure_Take_ownership_of_files_or_other_objects_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.2_L1_Ensure_Accounts_Block_Microsoft_accounts_is_set_to_Users_cant_add_or_log_on_with_Microsoft_accounts" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.4_L1_Ensure_Accounts_Limit_local_account_use_of_blank_passwords_to_console_logon_only_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.5_L1_Configure_Accounts_Rename_administrator_account" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.6_L1_Configure_Accounts_Rename_guest_account" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_L1_Ensure_Audit_Force_audit_policy_subcategory_settings_Windows_Vista_or_later_to_override_audit_policy_category_settings_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_L1_Ensure_Audit_Shut_down_system_immediately_if_unable_to_log_security_audits_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4.1_L1_Ensure_Devices_Allowed_to_format_and_eject_removable_media_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4.2_L1_Ensure_Devices_Prevent_users_from_installing_printer_drivers_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.5.1_L1_Ensure_Domain_controller_Allow_server_operators_to_schedule_tasks_is_set_to_Disabled_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.5.2_L1_Ensure_Domain_controller_LDAP_server_signing_requirements_is_set_to_Require_signing_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.5.3_L1_Ensure_Domain_controller_Refuse_machine_account_password_changes_is_set_to_Disabled_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.1_L1_Ensure_Domain_member_Digitally_encrypt_or_sign_secure_channel_data_always_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.2_L1_Ensure_Domain_member_Digitally_encrypt_secure_channel_data_when_possible_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.3_L1_Ensure_Domain_member_Digitally_sign_secure_channel_data_when_possible_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.4_L1_Ensure_Domain_member_Disable_machine_account_password_changes_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.5_L1_Ensure_Domain_member_Maximum_machine_account_password_age_is_set_to_30_or_fewer_days_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.6_L1_Ensure_Domain_member_Require_strong_Windows_2000_or_later_session_key_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.1_L1_Ensure_Interactive_logon_Do_not_require_CTRLALTDEL_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.2_L1_Ensure_Interactive_logon_Dont_display_last_signed-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.3_L1_Ensure_Interactive_logon_Machine_inactivity_limit_is_set_to_900_or_fewer_seconds_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.4_L1_Configure_Interactive_logon_Message_text_for_users_attempting_to_log_on" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.5_L1_Configure_Interactive_logon_Message_title_for_users_attempting_to_log_on" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.7_L1_Ensure_Interactive_logon_Prompt_user_to_change_password_before_expiration_is_set_to_between_5_and_14_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.9_L1_Ensure_Interactive_logon_Smart_card_removal_behavior_is_set_to_Lock_Workstation_or_higher" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.1_L1_Ensure_Microsoft_network_client_Digitally_sign_communications_always_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.2_L1_Ensure_Microsoft_network_client_Digitally_sign_communications_if_server_agrees_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.3_L1_Ensure_Microsoft_network_client_Send_unencrypted_password_to_third-party_SMB_servers_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.1_L1_Ensure_Microsoft_network_server_Amount_of_idle_time_required_before_suspending_session_is_set_to_15_or_fewer_minutes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.2_L1_Ensure_Microsoft_network_server_Digitally_sign_communications_always_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.3_L1_Ensure_Microsoft_network_server_Digitally_sign_communications_if_client_agrees_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.4_L1_Ensure_Microsoft_network_server_Disconnect_clients_when_logon_hours_expire_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.1_L1_Ensure_Network_access_Allow_anonymous_SIDName_translation_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.5_L1_Ensure_Network_access_Let_Everyone_permissions_apply_to_anonymous_users_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.6_L1_Configure_Network_access_Named_Pipes_that_can_be_accessed_anonymously_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.8_L1_Configure_Network_access_Remotely_accessible_registry_paths" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.9_L1_Configure_Network_access_Remotely_accessible_registry_paths_and_sub-paths" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.10_L1_Ensure_Network_access_Restrict_anonymous_access_to_Named_Pipes_and_Shares_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.12_L1_Ensure_Network_access_Shares_that_can_be_accessed_anonymously_is_set_to_None" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.13_L1_Ensure_Network_access_Sharing_and_security_model_for_local_accounts_is_set_to_Classic_-_local_users_authenticate_as_themselves" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.1_L1_Ensure_Network_security_Allow_Local_System_to_use_computer_identity_for_NTLM_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.2_L1_Ensure_Network_security_Allow_LocalSystem_NULL_session_fallback_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.3_L1_Ensure_Network_Security_Allow_PKU2U_authentication_requests_to_this_computer_to_use_online_identities_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.4_L1_Ensure_Network_security_Configure_encryption_types_allowed_for_Kerberos_is_set_to_AES128_HMAC_SHA1_AES256_HMAC_SHA1_Future_encryption_types" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.5_L1_Ensure_Network_security_Do_not_store_LAN_Manager_hash_value_on_next_password_change_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.6_L1_Ensure_Network_security_Force_logoff_when_logon_hours_expire_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.7_L1_Ensure_Network_security_LAN_Manager_authentication_level_is_set_to_Send_NTLMv2_response_only._Refuse_LM__NTLM" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.8_L1_Ensure_Network_security_LDAP_client_signing_requirements_is_set_to_Negotiate_signing_or_higher" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.9_L1_Ensure_Network_security_Minimum_session_security_for_NTLM_SSP_based_including_secure_RPC_clients_is_set_to_Require_NTLMv2_session_security_Require_128-bit_encryption" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.10_L1_Ensure_Network_security_Minimum_session_security_for_NTLM_SSP_based_including_secure_RPC_servers_is_set_to_Require_NTLMv2_session_security_Require_128-bit_encryption" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.13.1_L1_Ensure_Shutdown_Allow_system_to_be_shut_down_without_having_to_log_on_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.15.1_L1_Ensure_System_objects_Require_case_insensitivity_for_non-Windows_subsystems_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.15.2_L1_Ensure_System_objects_Strengthen_default_permissions_of_internal_system_objects_e.g._Symbolic_Links_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.1_L1_Ensure_User_Account_Control_Admin_Approval_Mode_for_the_Built-in_Administrator_account_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.2_L1_Ensure_User_Account_Control_Behavior_of_the_elevation_prompt_for_administrators_in_Admin_Approval_Mode_is_set_to_Prompt_for_consent_on_the_secure_desktop" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.3_L1_Ensure_User_Account_Control_Behavior_of_the_elevation_prompt_for_standard_users_is_set_to_Automatically_deny_elevation_requests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.4_L1_Ensure_User_Account_Control_Detect_application_installations_and_prompt_for_elevation_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.5_L1_Ensure_User_Account_Control_Only_elevate_UIAccess_applications_that_are_installed_in_secure_locations_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.6_L1_Ensure_User_Account_Control_Run_all_administrators_in_Admin_Approval_Mode_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.7_L1_Ensure_User_Account_Control_Switch_to_the_secure_desktop_when_prompting_for_elevation_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.8_L1_Ensure_User_Account_Control_Virtualize_file_and_registry_write_failures_to_per-user_locations_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.1_L1_Ensure_Windows_Firewall_Domain_Firewall_state_is_set_to_On_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.2_L1_Ensure_Windows_Firewall_Domain_Inbound_connections_is_set_to_Block_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.3_L1_Ensure_Windows_Firewall_Domain_Outbound_connections_is_set_to_Allow_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.4_L1_Ensure_Windows_Firewall_Domain_Settings_Display_a_notification_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.5_L1_Ensure_Windows_Firewall_Domain_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewalldomainfw.log" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.6_L1_Ensure_Windows_Firewall_Domain_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.7_L1_Ensure_Windows_Firewall_Domain_Logging_Log_dropped_packets_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.8_L1_Ensure_Windows_Firewall_Domain_Logging_Log_successful_connections_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.1_L1_Ensure_Windows_Firewall_Private_Firewall_state_is_set_to_On_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.2_L1_Ensure_Windows_Firewall_Private_Inbound_connections_is_set_to_Block_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.3_L1_Ensure_Windows_Firewall_Private_Outbound_connections_is_set_to_Allow_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.4_L1_Ensure_Windows_Firewall_Private_Settings_Display_a_notification_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.5_L1_Ensure_Windows_Firewall_Private_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewallprivatefw.log" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.6_L1_Ensure_Windows_Firewall_Private_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.7_L1_Ensure_Windows_Firewall_Private_Logging_Log_dropped_packets_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.8_L1_Ensure_Windows_Firewall_Private_Logging_Log_successful_connections_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.1_L1_Ensure_Windows_Firewall_Public_Firewall_state_is_set_to_On_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.2_L1_Ensure_Windows_Firewall_Public_Inbound_connections_is_set_to_Block_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.3_L1_Ensure_Windows_Firewall_Public_Outbound_connections_is_set_to_Allow_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.4_L1_Ensure_Windows_Firewall_Public_Settings_Display_a_notification_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.5_L1_Ensure_Windows_Firewall_Public_Settings_Apply_local_firewall_rules_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.6_L1_Ensure_Windows_Firewall_Public_Settings_Apply_local_connection_security_rules_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.7_L1_Ensure_Windows_Firewall_Public_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewallpublicfw.log" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.8_L1_Ensure_Windows_Firewall_Public_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.9_L1_Ensure_Windows_Firewall_Public_Logging_Log_dropped_packets_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.10_L1_Ensure_Windows_Firewall_Public_Logging_Log_successful_connections_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.1.1_L1_Ensure_Audit_Credential_Validation_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.1.2_L1_Ensure_Audit_Kerberos_Authentication_Service_is_set_to_Success_and_Failure_DC_Only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.1.3_L1_Ensure_Audit_Kerberos_Service_Ticket_Operations_is_set_to_Success_and_Failure_DC_Only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.1_L1_Ensure_Audit_Application_Group_Management_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.2_L1_Ensure_Audit_Computer_Account_Management_is_set_to_include_Success_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.3_L1_Ensure_Audit_Distribution_Group_Management_is_set_to_include_Success_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.4_L1_Ensure_Audit_Other_Account_Management_Events_is_set_to_include_Success_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.5_L1_Ensure_Audit_Security_Group_Management_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.6_L1_Ensure_Audit_User_Account_Management_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.3.1_L1_Ensure_Audit_PNP_Activity_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.3.2_L1_Ensure_Audit_Process_Creation_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.4.1_L1_Ensure_Audit_Directory_Service_Access_is_set_to_include_Failure_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.4.2_L1_Ensure_Audit_Directory_Service_Changes_is_set_to_include_Success_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.1_L1_Ensure_Audit_Account_Lockout_is_set_to_include_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.2_L1_Ensure_Audit_Group_Membership_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.3_L1_Ensure_Audit_Logoff_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.4_L1_Ensure_Audit_Logon_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.5_L1_Ensure_Audit_Other_LogonLogoff_Events_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.6_L1_Ensure_Audit_Special_Logon_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.1_L1_Ensure_Audit_Detailed_File_Share_is_set_to_include_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.2_L1_Ensure_Audit_File_Share_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.3_L1_Ensure_Audit_Other_Object_Access_Events_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.4_L1_Ensure_Audit_Removable_Storage_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.1_L1_Ensure_Audit_Audit_Policy_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.2_L1_Ensure_Audit_Authentication_Policy_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.3_L1_Ensure_Audit_Authorization_Policy_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.4_L1_Ensure_Audit_MPSSVC_Rule-Level_Policy_Change_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.5_L1_Ensure_Audit_Other_Policy_Change_Events_is_set_to_include_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.8.1_L1_Ensure_Audit_Sensitive_Privilege_Use_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.1_L1_Ensure_Audit_IPsec_Driver_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.2_L1_Ensure_Audit_Other_System_Events_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.3_L1_Ensure_Audit_Security_State_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.4_L1_Ensure_Audit_Security_System_Extension_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.5_L1_Ensure_Audit_System_Integrity_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.1.1_L1_Ensure_Prevent_enabling_lock_screen_camera_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.1.2_L1_Ensure_Prevent_enabling_lock_screen_slide_show_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.2.2_L1_Ensure_Allow_users_to_enable_online_speech_recognition_services_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.2_L1_Ensure_Configure_SMB_v1_client_driver_is_set_to_Enabled_Disable_driver_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.3_L1_Ensure_Configure_SMB_v1_server_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.4_L1_Ensure_Enable_Structured_Exception_Handling_Overwrite_Protection_SEHOP_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.5_L1_Ensure_Extended_Protection_for_LDAP_Authentication_Domain_Controllers_only_is_set_to_Enabled_Enabled_always_recommended_DC_Only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.6_L1_Ensure_NetBT_NodeType_configuration_is_set_to_Enabled_P-node_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.7_L1_Ensure_WDigest_Authentication_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.1_L1_Ensure_MSS_AutoAdminLogon_Enable_Automatic_Logon_not_recommended_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.2_L1_Ensure_MSS_DisableIPSourceRouting_IPv6_IP_source_routing_protection_level_protects_against_packet_spoofing_is_set_to_Enabled_Highest_protection_source_routing_is_completely_disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.3_L1_Ensure_MSS_DisableIPSourceRouting_IP_source_routing_protection_level_protects_against_packet_spoofing_is_set_to_Enabled_Highest_protection_source_routing_is_completely_disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.4_L1_Ensure_MSS_EnableICMPRedirect_Allow_ICMP_redirects_to_override_OSPF_generated_routes_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.6_L1_Ensure_MSS_NoNameReleaseOnDemand_Allow_the_computer_to_ignore_NetBIOS_name_release_requests_except_from_WINS_servers_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.8_L1_Ensure_MSS_SafeDllSearchMode_Enable_Safe_DLL_search_mode_recommended_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.9_L1_Ensure_MSS_ScreenSaverGracePeriod_The_time_in_seconds_before_the_screen_saver_grace_period_expires_0_recommended_is_set_to_Enabled_5_or_fewer_seconds" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.12_L1_Ensure_MSS_WarningLevel_Percentage_threshold_for_the_security_event_log_at_which_the_system_will_generate_a_warning_is_set_to_Enabled_90_or_less" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.4.1_L1_Ensure_Turn_off_multicast_name_resolution_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.8.1_L1_Ensure_Enable_insecure_guest_logons_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.2_L1_Ensure_Prohibit_installation_and_configuration_of_Network_Bridge_on_your_DNS_domain_network_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.3_L1_Ensure_Prohibit_use_of_Internet_Connection_Sharing_on_your_DNS_domain_network_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.4_L1_Ensure_Require_domain_users_to_elevate_when_setting_a_networks_location_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.14.1_L1_Ensure_Hardened_UNC_Paths_is_set_to_Enabled_with_Require_Mutual_Authentication_and_Require_Integrity_set_for_all_NETLOGON_and_SYSVOL_shares" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.21.1_L1_Ensure_Minimize_the_number_of_simultaneous_connections_to_the_Internet_or_a_Windows_Domain_is_set_to_Enabled_3__Prevent_Wi-Fi_when_on_Ethernet" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.3.1_L1_Ensure_Include_command_line_in_process_creation_events_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.4.1_L1_Ensure_Encryption_Oracle_Remediation_is_set_to_Enabled_Force_Updated_Clients" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.4.2_L1_Ensure_Remote_host_allows_delegation_of_non-exportable_credentials_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.14.1_L1_Ensure_Boot-Start_Driver_Initialization_Policy_is_set_to_Enabled_Good_unknown_and_bad_but_critical" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.2_L1_Ensure_Configure_registry_policy_processing_Do_not_apply_during_periodic_background_processing_is_set_to_Enabled_FALSE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.3_L1_Ensure_Configure_registry_policy_processing_Process_even_if_the_Group_Policy_objects_have_not_changed_is_set_to_Enabled_TRUE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.4_L1_Ensure_Continue_experiences_on_this_device_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.5_L1_Ensure_Turn_off_background_refresh_of_Group_Policy_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.1_L1_Ensure_Turn_off_downloading_of_print_drivers_over_HTTP_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.5_L1_Ensure_Turn_off_Internet_download_for_Web_publishing_and_online_ordering_wizards_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.26.1_L1_Ensure_Enumeration_policy_for_external_devices_incompatible_with_Kernel_DMA_Protection_is_set_to_Enabled_Block_All" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.1_L1_Ensure_Block_user_from_showing_account_details_on_sign-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.2_L1_Ensure_Do_not_display_network_selection_UI_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.3_L1_Ensure_Do_not_enumerate_connected_users_on_domain-joined_computers_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.5_L1_Ensure_Turn_off_app_notifications_on_the_lock_screen_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.6_L1_Ensure_Turn_off_picture_password_sign-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.7_L1_Ensure_Turn_on_convenience_PIN_sign-in_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.3_L1_Ensure_Require_a_password_when_a_computer_wakes_on_battery_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.4_L1_Ensure_Require_a_password_when_a_computer_wakes_plugged_in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.36.1_L1_Ensure_Configure_Offer_Remote_Assistance_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.36.2_L1_Ensure_Configure_Solicited_Remote_Assistance_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.6.1_L1_Ensure_Allow_Microsoft_accounts_to_be_optional_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.1_L1_Ensure_Disallow_Autoplay_for_non-volume_devices_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.2_L1_Ensure_Set_the_default_behavior_for_AutoRun_is_set_to_Enabled_Do_not_execute_any_autorun_commands" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.3_L1_Ensure_Turn_off_Autoplay_is_set_to_Enabled_All_drives" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.10.1.1_L1_Ensure_Configure_enhanced_anti-spoofing_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.13.1_L1_Ensure_Turn_off_Microsoft_consumer_experiences_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.14.1_L1_Ensure_Require_pin_for_pairing_is_set_to_Enabled_First_Time_OR_Enabled_Always" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.15.1_L1_Ensure_Do_not_display_the_password_reveal_button_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.15.2_L1_Ensure_Enumerate_administrator_accounts_on_elevation_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.1_L1_Ensure_Allow_Telemetry_is_set_to_Enabled_0_-_Security_Enterprise_Only_or_Enabled_1_-_Basic" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.3_L1_Ensure_Do_not_show_feedback_notifications_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.4_L1_Ensure_Toggle_user_control_over_Insider_builds_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.1.1_L1_Ensure_Application_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.1.2_L1_Ensure_Application_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.2.1_L1_Ensure_Security_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.2.2_L1_Ensure_Security_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_196608_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.3.1_L1_Ensure_Setup_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.3.2_L1_Ensure_Setup_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.4.1_L1_Ensure_System_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.4.2_L1_Ensure_System_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.2_L1_Ensure_Turn_off_Data_Execution_Prevention_for_Explorer_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.3_L1_Ensure_Turn_off_heap_termination_on_corruption_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.4_L1_Ensure_Turn_off_shell_protocol_protected_mode_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.44.1_L1_Ensure_Block_all_consumer_Microsoft_account_user_authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.52.1_L1_Ensure_Prevent_the_usage_of_OneDrive_for_file_storage_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.2.2_L1_Ensure_Do_not_allow_passwords_to_be_saved_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.3.2_L1_Ensure_Do_not_allow_drive_redirection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.1_L1_Ensure_Always_prompt_for_password_upon_connection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.2_L1_Ensure_Require_secure_RPC_communication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.3_L1_Ensure_Require_use_of_specific_security_layer_for_remote_RDP_connections_is_set_to_Enabled_SSL" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.4_L1_Ensure_Require_user_authentication_for_remote_connections_by_using_Network_Level_Authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.5_L1_Ensure_Set_client_connection_encryption_level_is_set_to_Enabled_High_Level" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.11.1_L1_Ensure_Do_not_delete_temp_folders_upon_exit_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.11.2_L1_Ensure_Do_not_use_temporary_folders_per_session_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.60.1_L1_Ensure_Prevent_downloading_of_enclosures_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.61.3_L1_Ensure_Allow_indexing_of_encrypted_files_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.3.1_L1_Ensure_Configure_local_setting_override_for_reporting_to_Microsoft_MAPS_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.7.1_L1_Ensure_Turn_on_behavior_monitoring_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.10.1_L1_Ensure_Scan_removable_drives_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.10.2_L1_Ensure_Turn_on_e-mail_scanning_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.1.1_L1_Ensure_Configure_Attack_Surface_Reduction_rules_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.1.2_L1_Ensure_Configure_Attack_Surface_Reduction_rules_Set_the_state_for_each_ASR_rule_is_configured" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.3.1_L1_Ensure_Prevent_users_and_apps_from_accessing_dangerous_websites_is_set_to_Enabled_Block" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.14_L1_Ensure_Configure_detection_for_potentially_unwanted_applications_is_set_to_Enabled_Block" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.15_L1_Ensure_Turn_off_Windows_Defender_AntiVirus_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.80.1.1_L1_Ensure_Configure_Windows_Defender_SmartScreen_is_set_to_Enabled_Warn_and_prevent_bypass" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.84.2_L1_Ensure_Allow_Windows_Ink_Workspace_is_set_to_Enabled_On_but_disallow_access_above_lock_OR_Disabled_but_not_Enabled_On" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.85.1_L1_Ensure_Allow_user_control_over_installs_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.85.2_L1_Ensure_Always_install_with_elevated_privileges_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.86.1_L1_Ensure_Sign-in_and_lock_last_interactive_user_automatically_after_a_restart_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.95.1_L1_Ensure_Turn_on_PowerShell_Script_Block_Logging_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.95.2_L1_Ensure_Turn_on_PowerShell_Transcription_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.1_L1_Ensure_Allow_Basic_authentication_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.2_L1_Ensure_Allow_unencrypted_traffic_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.3_L1_Ensure_Disallow_Digest_authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.1_L1_Ensure_Allow_Basic_authentication_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.3_L1_Ensure_Allow_unencrypted_traffic_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.4_L1_Ensure_Disallow_WinRM_from_storing_RunAs_credentials_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.99.2.1_L1_Ensure_Prevent_users_from_modifying_settings_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.1_L1_Ensure_Manage_preview_builds_is_set_to_Enabled_Disable_preview_builds" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.2_L1_Ensure_Select_when_Preview_Builds_and_Feature_Updates_are_received_is_set_to_Enabled_Semi-Annual_Channel_180_or_more_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.3_L1_Ensure_Select_when_Quality_Updates_are_received_is_set_to_Enabled_0_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.2_L1_Ensure_Configure_Automatic_Updates_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.3_L1_Ensure_Configure_Automatic_Updates_Scheduled_install_day_is_set_to_0_-_Every_day" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.4_L1_Ensure_No_auto-restart_with_logged_on_users_for_scheduled_automatic_updates_installations_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.1_L1_Ensure_Enable_screen_saver_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.2_L1_Ensure_Force_specific_screen_saver_Screen_saver_executable_name_is_set_to_Enabled_scrnsave.scr" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.3_L1_Ensure_Password_protect_the_screen_saver_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.4_L1_Ensure_Screen_saver_timeout_is_set_to_Enabled_900_seconds_or_fewer_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.5.1.1_L1_Ensure_Turn_off_toast_notifications_on_the_lock_screen_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.4.1_L1_Ensure_Do_not_preserve_zone_information_in_file_attachments_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.4.2_L1_Ensure_Notify_antivirus_programs_when_opening_attachments_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.1_L1_Ensure_Configure_Windows_spotlight_on_lock_screen_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.2_L1_Ensure_Do_not_suggest_third-party_content_in_Windows_spotlight_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.26.1_L1_Ensure_Prevent_users_from_sharing_files_within_their_profile._is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.41.1_L1_Ensure_Always_install_with_elevated_privileges_is_set_to_Disabled" selected="true"/> </xccdf:Profile> |
Level 1 - Member Server |
Items in this profile apply to Member Servers and intend to:
Items in this profile also apply to Member Servers that have the following Roles enabled:
Show
<xccdf:Profile xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="xccdf_org.cisecurity.benchmarks_profile_Level_1_-_Member_Server"> <xccdf:title xml:lang="en">Level 1 - Member Server</xccdf:title> <xccdf:description xml:lang="en"> <xhtml:p>Items in this profile apply to Member Servers and intend to:</xhtml:p> <xhtml:ul> <xhtml:li>be practical and prudent;</xhtml:li> <xhtml:li>provide a clear security benefit; and</xhtml:li> <xhtml:li>not inhibit the utility of the technology beyond acceptable means.</xhtml:li> </xhtml:ul> <xhtml:p>Items in this profile also apply to Member Servers that have the following Roles enabled:</xhtml:p> <xhtml:ul> <xhtml:li>AD Certificate Services</xhtml:li> <xhtml:li>DHCP Server</xhtml:li> <xhtml:li>DNS Server</xhtml:li> <xhtml:li>File Server</xhtml:li> <xhtml:li>Hyper-V</xhtml:li> <xhtml:li>Network Policy and Access Services</xhtml:li> <xhtml:li>Print Server</xhtml:li> <xhtml:li>Remote Access Services</xhtml:li> <xhtml:li>Remote Desktop Services</xhtml:li> <xhtml:li>Web Server</xhtml:li> </xhtml:ul> </xccdf:description> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1_L1_Ensure_Enforce_password_history_is_set_to_24_or_more_passwords" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.2_L1_Ensure_Maximum_password_age_is_set_to_60_or_fewer_days_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.3_L1_Ensure_Minimum_password_age_is_set_to_1_or_more_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.4_L1_Ensure_Minimum_password_length_is_set_to_14_or_more_characters" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.5_L1_Ensure_Password_must_meet_complexity_requirements_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.6_L1_Ensure_Store_passwords_using_reversible_encryption_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.1_L1_Ensure_Account_lockout_duration_is_set_to_15_or_more_minutes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.2_L1_Ensure_Account_lockout_threshold_is_set_to_10_or_fewer_invalid_logon_attempts_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.3_L1_Ensure_Reset_account_lockout_counter_after_is_set_to_15_or_more_minutes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1_L1_Ensure_Access_Credential_Manager_as_a_trusted_caller_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.3_L1_Ensure_Access_this_computer_from_the_network__is_set_to_Administrators_Authenticated_Users_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.4_L1_Ensure_Act_as_part_of_the_operating_system_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.6_L1_Ensure_Adjust_memory_quotas_for_a_process_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.7_L1_Ensure_Allow_log_on_locally_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.9_L1_Ensure_Allow_log_on_through_Remote_Desktop_Services_is_set_to_Administrators_Remote_Desktop_Users_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.10_L1_Ensure_Back_up_files_and_directories_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.11_L1_Ensure_Change_the_system_time_is_set_to_Administrators_LOCAL_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.12_L1_Ensure_Change_the_time_zone_is_set_to_Administrators_LOCAL_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.13_L1_Ensure_Create_a_pagefile_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.14_L1_Ensure_Create_a_token_object_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.15_L1_Ensure_Create_global_objects_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.16_L1_Ensure_Create_permanent_shared_objects_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.18_L1_Ensure_Create_symbolic_links_is_set_to_Administrators_NT_VIRTUAL_MACHINEVirtual_Machines_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.19_L1_Ensure_Debug_programs_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.21_L1_Ensure_Deny_access_to_this_computer_from_the_network_to_include_Guests_Local_account_and_member_of_Administrators_group_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.22_L1_Ensure_Deny_log_on_as_a_batch_job_to_include_Guests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.23_L1_Ensure_Deny_log_on_as_a_service_to_include_Guests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.24_L1_Ensure_Deny_log_on_locally_to_include_Guests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.26_L1_Ensure_Deny_log_on_through_Remote_Desktop_Services_is_set_to_Guests_Local_account_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.28_L1_Ensure_Enable_computer_and_user_accounts_to_be_trusted_for_delegation_is_set_to_No_One_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.29_L1_Ensure_Force_shutdown_from_a_remote_system_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.30_L1_Ensure_Generate_security_audits_is_set_to_LOCAL_SERVICE_NETWORK_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.32_L1_Ensure_Impersonate_a_client_after_authentication_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE_SERVICE_and_when_the_Web_Server_IIS_Role_with_Web_Services_Role_Service_is_installed_IIS_IUSRS_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.33_L1_Ensure_Increase_scheduling_priority_is_set_to_Administrators_Window_ManagerWindow_Manager_Group" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.34_L1_Ensure_Load_and_unload_device_drivers_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.35_L1_Ensure_Lock_pages_in_memory_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.38_L1_Ensure_Manage_auditing_and_security_log_is_set_to_Administrators_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.39_L1_Ensure_Modify_an_object_label_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.40_L1_Ensure_Modify_firmware_environment_values_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.41_L1_Ensure_Perform_volume_maintenance_tasks_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.42_L1_Ensure_Profile_single_process_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.43_L1_Ensure_Profile_system_performance_is_set_to_Administrators_NT_SERVICEWdiServiceHost" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.44_L1_Ensure_Replace_a_process_level_token_is_set_to_LOCAL_SERVICE_NETWORK_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.45_L1_Ensure_Restore_files_and_directories_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.46_L1_Ensure_Shut_down_the_system_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.48_L1_Ensure_Take_ownership_of_files_or_other_objects_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_L1_Ensure_Accounts_Administrator_account_status_is_set_to_Disabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.2_L1_Ensure_Accounts_Block_Microsoft_accounts_is_set_to_Users_cant_add_or_log_on_with_Microsoft_accounts" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.3_L1_Ensure_Accounts_Guest_account_status_is_set_to_Disabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.4_L1_Ensure_Accounts_Limit_local_account_use_of_blank_passwords_to_console_logon_only_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.5_L1_Configure_Accounts_Rename_administrator_account" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.6_L1_Configure_Accounts_Rename_guest_account" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_L1_Ensure_Audit_Force_audit_policy_subcategory_settings_Windows_Vista_or_later_to_override_audit_policy_category_settings_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_L1_Ensure_Audit_Shut_down_system_immediately_if_unable_to_log_security_audits_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4.1_L1_Ensure_Devices_Allowed_to_format_and_eject_removable_media_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4.2_L1_Ensure_Devices_Prevent_users_from_installing_printer_drivers_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.1_L1_Ensure_Domain_member_Digitally_encrypt_or_sign_secure_channel_data_always_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.2_L1_Ensure_Domain_member_Digitally_encrypt_secure_channel_data_when_possible_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.3_L1_Ensure_Domain_member_Digitally_sign_secure_channel_data_when_possible_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.4_L1_Ensure_Domain_member_Disable_machine_account_password_changes_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.5_L1_Ensure_Domain_member_Maximum_machine_account_password_age_is_set_to_30_or_fewer_days_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.6_L1_Ensure_Domain_member_Require_strong_Windows_2000_or_later_session_key_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.1_L1_Ensure_Interactive_logon_Do_not_require_CTRLALTDEL_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.2_L1_Ensure_Interactive_logon_Dont_display_last_signed-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.3_L1_Ensure_Interactive_logon_Machine_inactivity_limit_is_set_to_900_or_fewer_seconds_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.4_L1_Configure_Interactive_logon_Message_text_for_users_attempting_to_log_on" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.5_L1_Configure_Interactive_logon_Message_title_for_users_attempting_to_log_on" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.7_L1_Ensure_Interactive_logon_Prompt_user_to_change_password_before_expiration_is_set_to_between_5_and_14_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.8_L1_Ensure_Interactive_logon_Require_Domain_Controller_Authentication_to_unlock_workstation_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.9_L1_Ensure_Interactive_logon_Smart_card_removal_behavior_is_set_to_Lock_Workstation_or_higher" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.1_L1_Ensure_Microsoft_network_client_Digitally_sign_communications_always_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.2_L1_Ensure_Microsoft_network_client_Digitally_sign_communications_if_server_agrees_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.3_L1_Ensure_Microsoft_network_client_Send_unencrypted_password_to_third-party_SMB_servers_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.1_L1_Ensure_Microsoft_network_server_Amount_of_idle_time_required_before_suspending_session_is_set_to_15_or_fewer_minutes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.2_L1_Ensure_Microsoft_network_server_Digitally_sign_communications_always_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.3_L1_Ensure_Microsoft_network_server_Digitally_sign_communications_if_client_agrees_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.4_L1_Ensure_Microsoft_network_server_Disconnect_clients_when_logon_hours_expire_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.5_L1_Ensure_Microsoft_network_server_Server_SPN_target_name_validation_level_is_set_to_Accept_if_provided_by_client_or_higher_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.1_L1_Ensure_Network_access_Allow_anonymous_SIDName_translation_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.2_L1_Ensure_Network_access_Do_not_allow_anonymous_enumeration_of_SAM_accounts_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.3_L1_Ensure_Network_access_Do_not_allow_anonymous_enumeration_of_SAM_accounts_and_shares_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.5_L1_Ensure_Network_access_Let_Everyone_permissions_apply_to_anonymous_users_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.7_L1_Configure_Network_access_Named_Pipes_that_can_be_accessed_anonymously_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.8_L1_Configure_Network_access_Remotely_accessible_registry_paths" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.9_L1_Configure_Network_access_Remotely_accessible_registry_paths_and_sub-paths" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.10_L1_Ensure_Network_access_Restrict_anonymous_access_to_Named_Pipes_and_Shares_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.11_L1_Ensure_Network_access_Restrict_clients_allowed_to_make_remote_calls_to_SAM_is_set_to_Administrators_Remote_Access_Allow_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.12_L1_Ensure_Network_access_Shares_that_can_be_accessed_anonymously_is_set_to_None" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.13_L1_Ensure_Network_access_Sharing_and_security_model_for_local_accounts_is_set_to_Classic_-_local_users_authenticate_as_themselves" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.1_L1_Ensure_Network_security_Allow_Local_System_to_use_computer_identity_for_NTLM_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.2_L1_Ensure_Network_security_Allow_LocalSystem_NULL_session_fallback_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.3_L1_Ensure_Network_Security_Allow_PKU2U_authentication_requests_to_this_computer_to_use_online_identities_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.4_L1_Ensure_Network_security_Configure_encryption_types_allowed_for_Kerberos_is_set_to_AES128_HMAC_SHA1_AES256_HMAC_SHA1_Future_encryption_types" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.5_L1_Ensure_Network_security_Do_not_store_LAN_Manager_hash_value_on_next_password_change_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.6_L1_Ensure_Network_security_Force_logoff_when_logon_hours_expire_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.7_L1_Ensure_Network_security_LAN_Manager_authentication_level_is_set_to_Send_NTLMv2_response_only._Refuse_LM__NTLM" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.8_L1_Ensure_Network_security_LDAP_client_signing_requirements_is_set_to_Negotiate_signing_or_higher" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.9_L1_Ensure_Network_security_Minimum_session_security_for_NTLM_SSP_based_including_secure_RPC_clients_is_set_to_Require_NTLMv2_session_security_Require_128-bit_encryption" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.10_L1_Ensure_Network_security_Minimum_session_security_for_NTLM_SSP_based_including_secure_RPC_servers_is_set_to_Require_NTLMv2_session_security_Require_128-bit_encryption" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.13.1_L1_Ensure_Shutdown_Allow_system_to_be_shut_down_without_having_to_log_on_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.15.1_L1_Ensure_System_objects_Require_case_insensitivity_for_non-Windows_subsystems_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.15.2_L1_Ensure_System_objects_Strengthen_default_permissions_of_internal_system_objects_e.g._Symbolic_Links_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.1_L1_Ensure_User_Account_Control_Admin_Approval_Mode_for_the_Built-in_Administrator_account_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.2_L1_Ensure_User_Account_Control_Behavior_of_the_elevation_prompt_for_administrators_in_Admin_Approval_Mode_is_set_to_Prompt_for_consent_on_the_secure_desktop" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.3_L1_Ensure_User_Account_Control_Behavior_of_the_elevation_prompt_for_standard_users_is_set_to_Automatically_deny_elevation_requests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.4_L1_Ensure_User_Account_Control_Detect_application_installations_and_prompt_for_elevation_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.5_L1_Ensure_User_Account_Control_Only_elevate_UIAccess_applications_that_are_installed_in_secure_locations_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.6_L1_Ensure_User_Account_Control_Run_all_administrators_in_Admin_Approval_Mode_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.7_L1_Ensure_User_Account_Control_Switch_to_the_secure_desktop_when_prompting_for_elevation_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.8_L1_Ensure_User_Account_Control_Virtualize_file_and_registry_write_failures_to_per-user_locations_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.1_L1_Ensure_Windows_Firewall_Domain_Firewall_state_is_set_to_On_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.2_L1_Ensure_Windows_Firewall_Domain_Inbound_connections_is_set_to_Block_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.3_L1_Ensure_Windows_Firewall_Domain_Outbound_connections_is_set_to_Allow_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.4_L1_Ensure_Windows_Firewall_Domain_Settings_Display_a_notification_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.5_L1_Ensure_Windows_Firewall_Domain_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewalldomainfw.log" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.6_L1_Ensure_Windows_Firewall_Domain_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.7_L1_Ensure_Windows_Firewall_Domain_Logging_Log_dropped_packets_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.8_L1_Ensure_Windows_Firewall_Domain_Logging_Log_successful_connections_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.1_L1_Ensure_Windows_Firewall_Private_Firewall_state_is_set_to_On_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.2_L1_Ensure_Windows_Firewall_Private_Inbound_connections_is_set_to_Block_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.3_L1_Ensure_Windows_Firewall_Private_Outbound_connections_is_set_to_Allow_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.4_L1_Ensure_Windows_Firewall_Private_Settings_Display_a_notification_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.5_L1_Ensure_Windows_Firewall_Private_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewallprivatefw.log" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.6_L1_Ensure_Windows_Firewall_Private_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.7_L1_Ensure_Windows_Firewall_Private_Logging_Log_dropped_packets_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.8_L1_Ensure_Windows_Firewall_Private_Logging_Log_successful_connections_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.1_L1_Ensure_Windows_Firewall_Public_Firewall_state_is_set_to_On_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.2_L1_Ensure_Windows_Firewall_Public_Inbound_connections_is_set_to_Block_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.3_L1_Ensure_Windows_Firewall_Public_Outbound_connections_is_set_to_Allow_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.4_L1_Ensure_Windows_Firewall_Public_Settings_Display_a_notification_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.5_L1_Ensure_Windows_Firewall_Public_Settings_Apply_local_firewall_rules_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.6_L1_Ensure_Windows_Firewall_Public_Settings_Apply_local_connection_security_rules_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.7_L1_Ensure_Windows_Firewall_Public_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewallpublicfw.log" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.8_L1_Ensure_Windows_Firewall_Public_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.9_L1_Ensure_Windows_Firewall_Public_Logging_Log_dropped_packets_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.10_L1_Ensure_Windows_Firewall_Public_Logging_Log_successful_connections_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.1.1_L1_Ensure_Audit_Credential_Validation_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.1_L1_Ensure_Audit_Application_Group_Management_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.5_L1_Ensure_Audit_Security_Group_Management_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.6_L1_Ensure_Audit_User_Account_Management_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.3.1_L1_Ensure_Audit_PNP_Activity_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.3.2_L1_Ensure_Audit_Process_Creation_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.1_L1_Ensure_Audit_Account_Lockout_is_set_to_include_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.2_L1_Ensure_Audit_Group_Membership_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.3_L1_Ensure_Audit_Logoff_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.4_L1_Ensure_Audit_Logon_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.5_L1_Ensure_Audit_Other_LogonLogoff_Events_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.6_L1_Ensure_Audit_Special_Logon_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.1_L1_Ensure_Audit_Detailed_File_Share_is_set_to_include_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.2_L1_Ensure_Audit_File_Share_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.3_L1_Ensure_Audit_Other_Object_Access_Events_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.4_L1_Ensure_Audit_Removable_Storage_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.1_L1_Ensure_Audit_Audit_Policy_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.2_L1_Ensure_Audit_Authentication_Policy_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.3_L1_Ensure_Audit_Authorization_Policy_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.4_L1_Ensure_Audit_MPSSVC_Rule-Level_Policy_Change_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.5_L1_Ensure_Audit_Other_Policy_Change_Events_is_set_to_include_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.8.1_L1_Ensure_Audit_Sensitive_Privilege_Use_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.1_L1_Ensure_Audit_IPsec_Driver_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.2_L1_Ensure_Audit_Other_System_Events_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.3_L1_Ensure_Audit_Security_State_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.4_L1_Ensure_Audit_Security_System_Extension_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.5_L1_Ensure_Audit_System_Integrity_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.1.1_L1_Ensure_Prevent_enabling_lock_screen_camera_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.1.2_L1_Ensure_Prevent_enabling_lock_screen_slide_show_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.2.2_L1_Ensure_Allow_users_to_enable_online_speech_recognition_services_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.2.1_L1_Ensure_LAPS_AdmPwd_GPO_Extension__CSE_is_installed_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.2.2_L1_Ensure_Do_not_allow_password_expiration_time_longer_than_required_by_policy_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.2.3_L1_Ensure_Enable_Local_Admin_Password_Management_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.2.4_L1_Ensure_Password_Settings_Password_Complexity_is_set_to_Enabled_Large_letters__small_letters__numbers__special_characters_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.2.5_L1_Ensure_Password_Settings_Password_Length_is_set_to_Enabled_15_or_more_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.2.6_L1_Ensure_Password_Settings_Password_Age_Days_is_set_to_Enabled_30_or_fewer_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.1_L1_Ensure_Apply_UAC_restrictions_to_local_accounts_on_network_logons_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.2_L1_Ensure_Configure_SMB_v1_client_driver_is_set_to_Enabled_Disable_driver_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.3_L1_Ensure_Configure_SMB_v1_server_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.4_L1_Ensure_Enable_Structured_Exception_Handling_Overwrite_Protection_SEHOP_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.6_L1_Ensure_NetBT_NodeType_configuration_is_set_to_Enabled_P-node_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.7_L1_Ensure_WDigest_Authentication_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.1_L1_Ensure_MSS_AutoAdminLogon_Enable_Automatic_Logon_not_recommended_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.2_L1_Ensure_MSS_DisableIPSourceRouting_IPv6_IP_source_routing_protection_level_protects_against_packet_spoofing_is_set_to_Enabled_Highest_protection_source_routing_is_completely_disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.3_L1_Ensure_MSS_DisableIPSourceRouting_IP_source_routing_protection_level_protects_against_packet_spoofing_is_set_to_Enabled_Highest_protection_source_routing_is_completely_disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.4_L1_Ensure_MSS_EnableICMPRedirect_Allow_ICMP_redirects_to_override_OSPF_generated_routes_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.6_L1_Ensure_MSS_NoNameReleaseOnDemand_Allow_the_computer_to_ignore_NetBIOS_name_release_requests_except_from_WINS_servers_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.8_L1_Ensure_MSS_SafeDllSearchMode_Enable_Safe_DLL_search_mode_recommended_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.9_L1_Ensure_MSS_ScreenSaverGracePeriod_The_time_in_seconds_before_the_screen_saver_grace_period_expires_0_recommended_is_set_to_Enabled_5_or_fewer_seconds" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.12_L1_Ensure_MSS_WarningLevel_Percentage_threshold_for_the_security_event_log_at_which_the_system_will_generate_a_warning_is_set_to_Enabled_90_or_less" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.4.1_L1_Ensure_Turn_off_multicast_name_resolution_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.8.1_L1_Ensure_Enable_insecure_guest_logons_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.2_L1_Ensure_Prohibit_installation_and_configuration_of_Network_Bridge_on_your_DNS_domain_network_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.3_L1_Ensure_Prohibit_use_of_Internet_Connection_Sharing_on_your_DNS_domain_network_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.4_L1_Ensure_Require_domain_users_to_elevate_when_setting_a_networks_location_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.14.1_L1_Ensure_Hardened_UNC_Paths_is_set_to_Enabled_with_Require_Mutual_Authentication_and_Require_Integrity_set_for_all_NETLOGON_and_SYSVOL_shares" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.21.1_L1_Ensure_Minimize_the_number_of_simultaneous_connections_to_the_Internet_or_a_Windows_Domain_is_set_to_Enabled_3__Prevent_Wi-Fi_when_on_Ethernet" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.3.1_L1_Ensure_Include_command_line_in_process_creation_events_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.4.1_L1_Ensure_Encryption_Oracle_Remediation_is_set_to_Enabled_Force_Updated_Clients" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.4.2_L1_Ensure_Remote_host_allows_delegation_of_non-exportable_credentials_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.14.1_L1_Ensure_Boot-Start_Driver_Initialization_Policy_is_set_to_Enabled_Good_unknown_and_bad_but_critical" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.2_L1_Ensure_Configure_registry_policy_processing_Do_not_apply_during_periodic_background_processing_is_set_to_Enabled_FALSE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.3_L1_Ensure_Configure_registry_policy_processing_Process_even_if_the_Group_Policy_objects_have_not_changed_is_set_to_Enabled_TRUE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.4_L1_Ensure_Continue_experiences_on_this_device_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.5_L1_Ensure_Turn_off_background_refresh_of_Group_Policy_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.1_L1_Ensure_Turn_off_downloading_of_print_drivers_over_HTTP_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.5_L1_Ensure_Turn_off_Internet_download_for_Web_publishing_and_online_ordering_wizards_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.26.1_L1_Ensure_Enumeration_policy_for_external_devices_incompatible_with_Kernel_DMA_Protection_is_set_to_Enabled_Block_All" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.1_L1_Ensure_Block_user_from_showing_account_details_on_sign-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.2_L1_Ensure_Do_not_display_network_selection_UI_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.3_L1_Ensure_Do_not_enumerate_connected_users_on_domain-joined_computers_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.4_L1_Ensure_Enumerate_local_users_on_domain-joined_computers_is_set_to_Disabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.5_L1_Ensure_Turn_off_app_notifications_on_the_lock_screen_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.6_L1_Ensure_Turn_off_picture_password_sign-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.7_L1_Ensure_Turn_on_convenience_PIN_sign-in_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.3_L1_Ensure_Require_a_password_when_a_computer_wakes_on_battery_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.4_L1_Ensure_Require_a_password_when_a_computer_wakes_plugged_in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.36.1_L1_Ensure_Configure_Offer_Remote_Assistance_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.36.2_L1_Ensure_Configure_Solicited_Remote_Assistance_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.37.1_L1_Ensure_Enable_RPC_Endpoint_Mapper_Client_Authentication_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.6.1_L1_Ensure_Allow_Microsoft_accounts_to_be_optional_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.1_L1_Ensure_Disallow_Autoplay_for_non-volume_devices_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.2_L1_Ensure_Set_the_default_behavior_for_AutoRun_is_set_to_Enabled_Do_not_execute_any_autorun_commands" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.3_L1_Ensure_Turn_off_Autoplay_is_set_to_Enabled_All_drives" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.10.1.1_L1_Ensure_Configure_enhanced_anti-spoofing_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.13.1_L1_Ensure_Turn_off_Microsoft_consumer_experiences_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.14.1_L1_Ensure_Require_pin_for_pairing_is_set_to_Enabled_First_Time_OR_Enabled_Always" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.15.1_L1_Ensure_Do_not_display_the_password_reveal_button_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.15.2_L1_Ensure_Enumerate_administrator_accounts_on_elevation_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.1_L1_Ensure_Allow_Telemetry_is_set_to_Enabled_0_-_Security_Enterprise_Only_or_Enabled_1_-_Basic" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.3_L1_Ensure_Do_not_show_feedback_notifications_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.4_L1_Ensure_Toggle_user_control_over_Insider_builds_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.1.1_L1_Ensure_Application_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.1.2_L1_Ensure_Application_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.2.1_L1_Ensure_Security_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.2.2_L1_Ensure_Security_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_196608_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.3.1_L1_Ensure_Setup_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.3.2_L1_Ensure_Setup_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.4.1_L1_Ensure_System_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.4.2_L1_Ensure_System_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.2_L1_Ensure_Turn_off_Data_Execution_Prevention_for_Explorer_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.3_L1_Ensure_Turn_off_heap_termination_on_corruption_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.4_L1_Ensure_Turn_off_shell_protocol_protected_mode_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.44.1_L1_Ensure_Block_all_consumer_Microsoft_account_user_authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.52.1_L1_Ensure_Prevent_the_usage_of_OneDrive_for_file_storage_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.2.2_L1_Ensure_Do_not_allow_passwords_to_be_saved_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.3.2_L1_Ensure_Do_not_allow_drive_redirection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.1_L1_Ensure_Always_prompt_for_password_upon_connection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.2_L1_Ensure_Require_secure_RPC_communication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.3_L1_Ensure_Require_use_of_specific_security_layer_for_remote_RDP_connections_is_set_to_Enabled_SSL" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.4_L1_Ensure_Require_user_authentication_for_remote_connections_by_using_Network_Level_Authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.5_L1_Ensure_Set_client_connection_encryption_level_is_set_to_Enabled_High_Level" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.11.1_L1_Ensure_Do_not_delete_temp_folders_upon_exit_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.11.2_L1_Ensure_Do_not_use_temporary_folders_per_session_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.60.1_L1_Ensure_Prevent_downloading_of_enclosures_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.61.3_L1_Ensure_Allow_indexing_of_encrypted_files_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.3.1_L1_Ensure_Configure_local_setting_override_for_reporting_to_Microsoft_MAPS_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.7.1_L1_Ensure_Turn_on_behavior_monitoring_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.10.1_L1_Ensure_Scan_removable_drives_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.10.2_L1_Ensure_Turn_on_e-mail_scanning_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.1.1_L1_Ensure_Configure_Attack_Surface_Reduction_rules_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.1.2_L1_Ensure_Configure_Attack_Surface_Reduction_rules_Set_the_state_for_each_ASR_rule_is_configured" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.3.1_L1_Ensure_Prevent_users_and_apps_from_accessing_dangerous_websites_is_set_to_Enabled_Block" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.14_L1_Ensure_Configure_detection_for_potentially_unwanted_applications_is_set_to_Enabled_Block" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.15_L1_Ensure_Turn_off_Windows_Defender_AntiVirus_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.80.1.1_L1_Ensure_Configure_Windows_Defender_SmartScreen_is_set_to_Enabled_Warn_and_prevent_bypass" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.84.2_L1_Ensure_Allow_Windows_Ink_Workspace_is_set_to_Enabled_On_but_disallow_access_above_lock_OR_Disabled_but_not_Enabled_On" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.85.1_L1_Ensure_Allow_user_control_over_installs_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.85.2_L1_Ensure_Always_install_with_elevated_privileges_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.86.1_L1_Ensure_Sign-in_and_lock_last_interactive_user_automatically_after_a_restart_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.95.1_L1_Ensure_Turn_on_PowerShell_Script_Block_Logging_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.95.2_L1_Ensure_Turn_on_PowerShell_Transcription_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.1_L1_Ensure_Allow_Basic_authentication_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.2_L1_Ensure_Allow_unencrypted_traffic_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.3_L1_Ensure_Disallow_Digest_authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.1_L1_Ensure_Allow_Basic_authentication_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.3_L1_Ensure_Allow_unencrypted_traffic_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.4_L1_Ensure_Disallow_WinRM_from_storing_RunAs_credentials_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.99.2.1_L1_Ensure_Prevent_users_from_modifying_settings_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.1_L1_Ensure_Manage_preview_builds_is_set_to_Enabled_Disable_preview_builds" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.2_L1_Ensure_Select_when_Preview_Builds_and_Feature_Updates_are_received_is_set_to_Enabled_Semi-Annual_Channel_180_or_more_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.3_L1_Ensure_Select_when_Quality_Updates_are_received_is_set_to_Enabled_0_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.2_L1_Ensure_Configure_Automatic_Updates_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.3_L1_Ensure_Configure_Automatic_Updates_Scheduled_install_day_is_set_to_0_-_Every_day" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.4_L1_Ensure_No_auto-restart_with_logged_on_users_for_scheduled_automatic_updates_installations_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.1_L1_Ensure_Enable_screen_saver_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.2_L1_Ensure_Force_specific_screen_saver_Screen_saver_executable_name_is_set_to_Enabled_scrnsave.scr" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.3_L1_Ensure_Password_protect_the_screen_saver_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.4_L1_Ensure_Screen_saver_timeout_is_set_to_Enabled_900_seconds_or_fewer_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.5.1.1_L1_Ensure_Turn_off_toast_notifications_on_the_lock_screen_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.4.1_L1_Ensure_Do_not_preserve_zone_information_in_file_attachments_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.4.2_L1_Ensure_Notify_antivirus_programs_when_opening_attachments_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.1_L1_Ensure_Configure_Windows_spotlight_on_lock_screen_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.2_L1_Ensure_Do_not_suggest_third-party_content_in_Windows_spotlight_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.26.1_L1_Ensure_Prevent_users_from_sharing_files_within_their_profile._is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.41.1_L1_Ensure_Always_install_with_elevated_privileges_is_set_to_Disabled" selected="true"/> </xccdf:Profile> |
Level 2 - Domain Controller |
This profile extends the "Level 1 - Domain Controller" profile. Items in this profile exhibit one or more of the following characteristics:
Show
<xccdf:Profile xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="xccdf_org.cisecurity.benchmarks_profile_Level_2_-_Domain_Controller"> <xccdf:title xml:lang="en">Level 2 - Domain Controller</xccdf:title> <xccdf:description xml:lang="en"> <xhtml:p>This profile extends the "Level 1 - Domain Controller" profile. Items in this profile exhibit one or more of the following characteristics:</xhtml:p> <xhtml:ul> <xhtml:li>are intended for environments or use cases where security is paramount</xhtml:li> <xhtml:li>acts as defense in depth measure</xhtml:li> <xhtml:li>may negatively inhibit the utility or performance of the technology</xhtml:li> </xhtml:ul> </xccdf:description> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1_L1_Ensure_Enforce_password_history_is_set_to_24_or_more_passwords" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.2_L1_Ensure_Maximum_password_age_is_set_to_60_or_fewer_days_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.3_L1_Ensure_Minimum_password_age_is_set_to_1_or_more_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.4_L1_Ensure_Minimum_password_length_is_set_to_14_or_more_characters" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.5_L1_Ensure_Password_must_meet_complexity_requirements_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.6_L1_Ensure_Store_passwords_using_reversible_encryption_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.1_L1_Ensure_Account_lockout_duration_is_set_to_15_or_more_minutes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.2_L1_Ensure_Account_lockout_threshold_is_set_to_10_or_fewer_invalid_logon_attempts_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.3_L1_Ensure_Reset_account_lockout_counter_after_is_set_to_15_or_more_minutes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1_L1_Ensure_Access_Credential_Manager_as_a_trusted_caller_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.2_L1_Ensure_Access_this_computer_from_the_network_is_set_to_Administrators_Authenticated_Users_ENTERPRISE_DOMAIN_CONTROLLERS_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.4_L1_Ensure_Act_as_part_of_the_operating_system_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.5_L1_Ensure_Add_workstations_to_domain_is_set_to_Administrators_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.6_L1_Ensure_Adjust_memory_quotas_for_a_process_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.7_L1_Ensure_Allow_log_on_locally_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.8_L1_Ensure_Allow_log_on_through_Remote_Desktop_Services_is_set_to_Administrators_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.10_L1_Ensure_Back_up_files_and_directories_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.11_L1_Ensure_Change_the_system_time_is_set_to_Administrators_LOCAL_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.12_L1_Ensure_Change_the_time_zone_is_set_to_Administrators_LOCAL_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.13_L1_Ensure_Create_a_pagefile_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.14_L1_Ensure_Create_a_token_object_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.15_L1_Ensure_Create_global_objects_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.16_L1_Ensure_Create_permanent_shared_objects_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.17_L1_Ensure_Create_symbolic_links_is_set_to_Administrators_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.19_L1_Ensure_Debug_programs_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.20_L1_Ensure_Deny_access_to_this_computer_from_the_network_to_include_Guests_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.22_L1_Ensure_Deny_log_on_as_a_batch_job_to_include_Guests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.23_L1_Ensure_Deny_log_on_as_a_service_to_include_Guests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.24_L1_Ensure_Deny_log_on_locally_to_include_Guests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.25_L1_Ensure_Deny_log_on_through_Remote_Desktop_Services_to_include_Guests_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.27_L1_Ensure_Enable_computer_and_user_accounts_to_be_trusted_for_delegation_is_set_to_Administrators_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.29_L1_Ensure_Force_shutdown_from_a_remote_system_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.30_L1_Ensure_Generate_security_audits_is_set_to_LOCAL_SERVICE_NETWORK_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.31_L1_Ensure_Impersonate_a_client_after_authentication_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE_SERVICE_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.33_L1_Ensure_Increase_scheduling_priority_is_set_to_Administrators_Window_ManagerWindow_Manager_Group" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.34_L1_Ensure_Load_and_unload_device_drivers_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.35_L1_Ensure_Lock_pages_in_memory_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.36_L2_Ensure_Log_on_as_a_batch_job_is_set_to_Administrators_DC_Only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.37_L1_Ensure_Manage_auditing_and_security_log_is_set_to_Administrators_and_when_Exchange_is_running_in_the_environment_Exchange_Servers_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.39_L1_Ensure_Modify_an_object_label_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.40_L1_Ensure_Modify_firmware_environment_values_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.41_L1_Ensure_Perform_volume_maintenance_tasks_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.42_L1_Ensure_Profile_single_process_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.43_L1_Ensure_Profile_system_performance_is_set_to_Administrators_NT_SERVICEWdiServiceHost" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.44_L1_Ensure_Replace_a_process_level_token_is_set_to_LOCAL_SERVICE_NETWORK_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.45_L1_Ensure_Restore_files_and_directories_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.46_L1_Ensure_Shut_down_the_system_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.47_L1_Ensure_Synchronize_directory_service_data_is_set_to_No_One_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.48_L1_Ensure_Take_ownership_of_files_or_other_objects_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.2_L1_Ensure_Accounts_Block_Microsoft_accounts_is_set_to_Users_cant_add_or_log_on_with_Microsoft_accounts" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.4_L1_Ensure_Accounts_Limit_local_account_use_of_blank_passwords_to_console_logon_only_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.5_L1_Configure_Accounts_Rename_administrator_account" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.6_L1_Configure_Accounts_Rename_guest_account" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_L1_Ensure_Audit_Force_audit_policy_subcategory_settings_Windows_Vista_or_later_to_override_audit_policy_category_settings_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_L1_Ensure_Audit_Shut_down_system_immediately_if_unable_to_log_security_audits_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4.1_L1_Ensure_Devices_Allowed_to_format_and_eject_removable_media_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4.2_L1_Ensure_Devices_Prevent_users_from_installing_printer_drivers_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.5.1_L1_Ensure_Domain_controller_Allow_server_operators_to_schedule_tasks_is_set_to_Disabled_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.5.2_L1_Ensure_Domain_controller_LDAP_server_signing_requirements_is_set_to_Require_signing_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.5.3_L1_Ensure_Domain_controller_Refuse_machine_account_password_changes_is_set_to_Disabled_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.1_L1_Ensure_Domain_member_Digitally_encrypt_or_sign_secure_channel_data_always_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.2_L1_Ensure_Domain_member_Digitally_encrypt_secure_channel_data_when_possible_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.3_L1_Ensure_Domain_member_Digitally_sign_secure_channel_data_when_possible_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.4_L1_Ensure_Domain_member_Disable_machine_account_password_changes_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.5_L1_Ensure_Domain_member_Maximum_machine_account_password_age_is_set_to_30_or_fewer_days_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.6_L1_Ensure_Domain_member_Require_strong_Windows_2000_or_later_session_key_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.1_L1_Ensure_Interactive_logon_Do_not_require_CTRLALTDEL_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.2_L1_Ensure_Interactive_logon_Dont_display_last_signed-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.3_L1_Ensure_Interactive_logon_Machine_inactivity_limit_is_set_to_900_or_fewer_seconds_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.4_L1_Configure_Interactive_logon_Message_text_for_users_attempting_to_log_on" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.5_L1_Configure_Interactive_logon_Message_title_for_users_attempting_to_log_on" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.7_L1_Ensure_Interactive_logon_Prompt_user_to_change_password_before_expiration_is_set_to_between_5_and_14_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.9_L1_Ensure_Interactive_logon_Smart_card_removal_behavior_is_set_to_Lock_Workstation_or_higher" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.1_L1_Ensure_Microsoft_network_client_Digitally_sign_communications_always_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.2_L1_Ensure_Microsoft_network_client_Digitally_sign_communications_if_server_agrees_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.3_L1_Ensure_Microsoft_network_client_Send_unencrypted_password_to_third-party_SMB_servers_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.1_L1_Ensure_Microsoft_network_server_Amount_of_idle_time_required_before_suspending_session_is_set_to_15_or_fewer_minutes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.2_L1_Ensure_Microsoft_network_server_Digitally_sign_communications_always_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.3_L1_Ensure_Microsoft_network_server_Digitally_sign_communications_if_client_agrees_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.4_L1_Ensure_Microsoft_network_server_Disconnect_clients_when_logon_hours_expire_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.1_L1_Ensure_Network_access_Allow_anonymous_SIDName_translation_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.4_L2_Ensure_Network_access_Do_not_allow_storage_of_passwords_and_credentials_for_network_authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.5_L1_Ensure_Network_access_Let_Everyone_permissions_apply_to_anonymous_users_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.6_L1_Configure_Network_access_Named_Pipes_that_can_be_accessed_anonymously_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.8_L1_Configure_Network_access_Remotely_accessible_registry_paths" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.9_L1_Configure_Network_access_Remotely_accessible_registry_paths_and_sub-paths" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.10_L1_Ensure_Network_access_Restrict_anonymous_access_to_Named_Pipes_and_Shares_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.12_L1_Ensure_Network_access_Shares_that_can_be_accessed_anonymously_is_set_to_None" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.13_L1_Ensure_Network_access_Sharing_and_security_model_for_local_accounts_is_set_to_Classic_-_local_users_authenticate_as_themselves" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.1_L1_Ensure_Network_security_Allow_Local_System_to_use_computer_identity_for_NTLM_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.2_L1_Ensure_Network_security_Allow_LocalSystem_NULL_session_fallback_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.3_L1_Ensure_Network_Security_Allow_PKU2U_authentication_requests_to_this_computer_to_use_online_identities_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.4_L1_Ensure_Network_security_Configure_encryption_types_allowed_for_Kerberos_is_set_to_AES128_HMAC_SHA1_AES256_HMAC_SHA1_Future_encryption_types" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.5_L1_Ensure_Network_security_Do_not_store_LAN_Manager_hash_value_on_next_password_change_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.6_L1_Ensure_Network_security_Force_logoff_when_logon_hours_expire_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.7_L1_Ensure_Network_security_LAN_Manager_authentication_level_is_set_to_Send_NTLMv2_response_only._Refuse_LM__NTLM" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.8_L1_Ensure_Network_security_LDAP_client_signing_requirements_is_set_to_Negotiate_signing_or_higher" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.9_L1_Ensure_Network_security_Minimum_session_security_for_NTLM_SSP_based_including_secure_RPC_clients_is_set_to_Require_NTLMv2_session_security_Require_128-bit_encryption" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.10_L1_Ensure_Network_security_Minimum_session_security_for_NTLM_SSP_based_including_secure_RPC_servers_is_set_to_Require_NTLMv2_session_security_Require_128-bit_encryption" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.13.1_L1_Ensure_Shutdown_Allow_system_to_be_shut_down_without_having_to_log_on_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.15.1_L1_Ensure_System_objects_Require_case_insensitivity_for_non-Windows_subsystems_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.15.2_L1_Ensure_System_objects_Strengthen_default_permissions_of_internal_system_objects_e.g._Symbolic_Links_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.1_L1_Ensure_User_Account_Control_Admin_Approval_Mode_for_the_Built-in_Administrator_account_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.2_L1_Ensure_User_Account_Control_Behavior_of_the_elevation_prompt_for_administrators_in_Admin_Approval_Mode_is_set_to_Prompt_for_consent_on_the_secure_desktop" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.3_L1_Ensure_User_Account_Control_Behavior_of_the_elevation_prompt_for_standard_users_is_set_to_Automatically_deny_elevation_requests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.4_L1_Ensure_User_Account_Control_Detect_application_installations_and_prompt_for_elevation_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.5_L1_Ensure_User_Account_Control_Only_elevate_UIAccess_applications_that_are_installed_in_secure_locations_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.6_L1_Ensure_User_Account_Control_Run_all_administrators_in_Admin_Approval_Mode_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.7_L1_Ensure_User_Account_Control_Switch_to_the_secure_desktop_when_prompting_for_elevation_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.8_L1_Ensure_User_Account_Control_Virtualize_file_and_registry_write_failures_to_per-user_locations_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.1_L1_Ensure_Windows_Firewall_Domain_Firewall_state_is_set_to_On_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.2_L1_Ensure_Windows_Firewall_Domain_Inbound_connections_is_set_to_Block_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.3_L1_Ensure_Windows_Firewall_Domain_Outbound_connections_is_set_to_Allow_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.4_L1_Ensure_Windows_Firewall_Domain_Settings_Display_a_notification_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.5_L1_Ensure_Windows_Firewall_Domain_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewalldomainfw.log" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.6_L1_Ensure_Windows_Firewall_Domain_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.7_L1_Ensure_Windows_Firewall_Domain_Logging_Log_dropped_packets_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.8_L1_Ensure_Windows_Firewall_Domain_Logging_Log_successful_connections_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.1_L1_Ensure_Windows_Firewall_Private_Firewall_state_is_set_to_On_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.2_L1_Ensure_Windows_Firewall_Private_Inbound_connections_is_set_to_Block_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.3_L1_Ensure_Windows_Firewall_Private_Outbound_connections_is_set_to_Allow_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.4_L1_Ensure_Windows_Firewall_Private_Settings_Display_a_notification_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.5_L1_Ensure_Windows_Firewall_Private_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewallprivatefw.log" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.6_L1_Ensure_Windows_Firewall_Private_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.7_L1_Ensure_Windows_Firewall_Private_Logging_Log_dropped_packets_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.8_L1_Ensure_Windows_Firewall_Private_Logging_Log_successful_connections_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.1_L1_Ensure_Windows_Firewall_Public_Firewall_state_is_set_to_On_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.2_L1_Ensure_Windows_Firewall_Public_Inbound_connections_is_set_to_Block_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.3_L1_Ensure_Windows_Firewall_Public_Outbound_connections_is_set_to_Allow_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.4_L1_Ensure_Windows_Firewall_Public_Settings_Display_a_notification_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.5_L1_Ensure_Windows_Firewall_Public_Settings_Apply_local_firewall_rules_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.6_L1_Ensure_Windows_Firewall_Public_Settings_Apply_local_connection_security_rules_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.7_L1_Ensure_Windows_Firewall_Public_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewallpublicfw.log" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.8_L1_Ensure_Windows_Firewall_Public_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.9_L1_Ensure_Windows_Firewall_Public_Logging_Log_dropped_packets_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.10_L1_Ensure_Windows_Firewall_Public_Logging_Log_successful_connections_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.1.1_L1_Ensure_Audit_Credential_Validation_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.1.2_L1_Ensure_Audit_Kerberos_Authentication_Service_is_set_to_Success_and_Failure_DC_Only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.1.3_L1_Ensure_Audit_Kerberos_Service_Ticket_Operations_is_set_to_Success_and_Failure_DC_Only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.1_L1_Ensure_Audit_Application_Group_Management_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.2_L1_Ensure_Audit_Computer_Account_Management_is_set_to_include_Success_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.3_L1_Ensure_Audit_Distribution_Group_Management_is_set_to_include_Success_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.4_L1_Ensure_Audit_Other_Account_Management_Events_is_set_to_include_Success_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.5_L1_Ensure_Audit_Security_Group_Management_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.6_L1_Ensure_Audit_User_Account_Management_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.3.1_L1_Ensure_Audit_PNP_Activity_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.3.2_L1_Ensure_Audit_Process_Creation_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.4.1_L1_Ensure_Audit_Directory_Service_Access_is_set_to_include_Failure_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.4.2_L1_Ensure_Audit_Directory_Service_Changes_is_set_to_include_Success_DC_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.1_L1_Ensure_Audit_Account_Lockout_is_set_to_include_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.2_L1_Ensure_Audit_Group_Membership_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.3_L1_Ensure_Audit_Logoff_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.4_L1_Ensure_Audit_Logon_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.5_L1_Ensure_Audit_Other_LogonLogoff_Events_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.6_L1_Ensure_Audit_Special_Logon_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.1_L1_Ensure_Audit_Detailed_File_Share_is_set_to_include_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.2_L1_Ensure_Audit_File_Share_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.3_L1_Ensure_Audit_Other_Object_Access_Events_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.4_L1_Ensure_Audit_Removable_Storage_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.1_L1_Ensure_Audit_Audit_Policy_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.2_L1_Ensure_Audit_Authentication_Policy_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.3_L1_Ensure_Audit_Authorization_Policy_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.4_L1_Ensure_Audit_MPSSVC_Rule-Level_Policy_Change_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.5_L1_Ensure_Audit_Other_Policy_Change_Events_is_set_to_include_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.8.1_L1_Ensure_Audit_Sensitive_Privilege_Use_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.1_L1_Ensure_Audit_IPsec_Driver_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.2_L1_Ensure_Audit_Other_System_Events_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.3_L1_Ensure_Audit_Security_State_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.4_L1_Ensure_Audit_Security_System_Extension_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.5_L1_Ensure_Audit_System_Integrity_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.1.1_L1_Ensure_Prevent_enabling_lock_screen_camera_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.1.2_L1_Ensure_Prevent_enabling_lock_screen_slide_show_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.2.2_L1_Ensure_Allow_users_to_enable_online_speech_recognition_services_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.3_L2_Ensure_Allow_Online_Tips_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.2_L1_Ensure_Configure_SMB_v1_client_driver_is_set_to_Enabled_Disable_driver_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.3_L1_Ensure_Configure_SMB_v1_server_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.4_L1_Ensure_Enable_Structured_Exception_Handling_Overwrite_Protection_SEHOP_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.5_L1_Ensure_Extended_Protection_for_LDAP_Authentication_Domain_Controllers_only_is_set_to_Enabled_Enabled_always_recommended_DC_Only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.6_L1_Ensure_NetBT_NodeType_configuration_is_set_to_Enabled_P-node_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.7_L1_Ensure_WDigest_Authentication_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.1_L1_Ensure_MSS_AutoAdminLogon_Enable_Automatic_Logon_not_recommended_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.2_L1_Ensure_MSS_DisableIPSourceRouting_IPv6_IP_source_routing_protection_level_protects_against_packet_spoofing_is_set_to_Enabled_Highest_protection_source_routing_is_completely_disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.3_L1_Ensure_MSS_DisableIPSourceRouting_IP_source_routing_protection_level_protects_against_packet_spoofing_is_set_to_Enabled_Highest_protection_source_routing_is_completely_disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.4_L1_Ensure_MSS_EnableICMPRedirect_Allow_ICMP_redirects_to_override_OSPF_generated_routes_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.5_L2_Ensure_MSS_KeepAliveTime_How_often_keep-alive_packets_are_sent_in_milliseconds_is_set_to_Enabled_300000_or_5_minutes_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.6_L1_Ensure_MSS_NoNameReleaseOnDemand_Allow_the_computer_to_ignore_NetBIOS_name_release_requests_except_from_WINS_servers_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.7_L2_Ensure_MSS_PerformRouterDiscovery_Allow_IRDP_to_detect_and_configure_Default_Gateway_addresses_could_lead_to_DoS_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.8_L1_Ensure_MSS_SafeDllSearchMode_Enable_Safe_DLL_search_mode_recommended_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.9_L1_Ensure_MSS_ScreenSaverGracePeriod_The_time_in_seconds_before_the_screen_saver_grace_period_expires_0_recommended_is_set_to_Enabled_5_or_fewer_seconds" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.10_L2_Ensure_MSS_TcpMaxDataRetransmissions_IPv6_How_many_times_unacknowledged_data_is_retransmitted_is_set_to_Enabled_3" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.11_L2_Ensure_MSS_TcpMaxDataRetransmissions_How_many_times_unacknowledged_data_is_retransmitted_is_set_to_Enabled_3" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.12_L1_Ensure_MSS_WarningLevel_Percentage_threshold_for_the_security_event_log_at_which_the_system_will_generate_a_warning_is_set_to_Enabled_90_or_less" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.4.1_L1_Ensure_Turn_off_multicast_name_resolution_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.5.1_L2_Ensure_Enable_Font_Providers_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.8.1_L1_Ensure_Enable_insecure_guest_logons_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.9.1_L2_Ensure_Turn_on_Mapper_IO_LLTDIO_driver_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.9.2_L2_Ensure_Turn_on_Responder_RSPNDR_driver_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.10.2_L2_Ensure_Turn_off_Microsoft_Peer-to-Peer_Networking_Services_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.2_L1_Ensure_Prohibit_installation_and_configuration_of_Network_Bridge_on_your_DNS_domain_network_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.3_L1_Ensure_Prohibit_use_of_Internet_Connection_Sharing_on_your_DNS_domain_network_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.4_L1_Ensure_Require_domain_users_to_elevate_when_setting_a_networks_location_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.14.1_L1_Ensure_Hardened_UNC_Paths_is_set_to_Enabled_with_Require_Mutual_Authentication_and_Require_Integrity_set_for_all_NETLOGON_and_SYSVOL_shares" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.19.2.1_L2_Disable_IPv6_Ensure_TCPIP6_Parameter_DisabledComponents_is_set_to_0xff_255" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.20.1_L2_Ensure_Configuration_of_wireless_settings_using_Windows_Connect_Now_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.20.2_L2_Ensure_Prohibit_access_of_the_Windows_Connect_Now_wizards_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.21.1_L1_Ensure_Minimize_the_number_of_simultaneous_connections_to_the_Internet_or_a_Windows_Domain_is_set_to_Enabled_3__Prevent_Wi-Fi_when_on_Ethernet" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.7.1.1_L2_Ensure_Turn_off_notifications_network_usage_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.3.1_L1_Ensure_Include_command_line_in_process_creation_events_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.4.1_L1_Ensure_Encryption_Oracle_Remediation_is_set_to_Enabled_Force_Updated_Clients" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.4.2_L1_Ensure_Remote_host_allows_delegation_of_non-exportable_credentials_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.14.1_L1_Ensure_Boot-Start_Driver_Initialization_Policy_is_set_to_Enabled_Good_unknown_and_bad_but_critical" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.2_L1_Ensure_Configure_registry_policy_processing_Do_not_apply_during_periodic_background_processing_is_set_to_Enabled_FALSE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.3_L1_Ensure_Configure_registry_policy_processing_Process_even_if_the_Group_Policy_objects_have_not_changed_is_set_to_Enabled_TRUE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.4_L1_Ensure_Continue_experiences_on_this_device_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.5_L1_Ensure_Turn_off_background_refresh_of_Group_Policy_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.1_L1_Ensure_Turn_off_downloading_of_print_drivers_over_HTTP_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.2_L2_Ensure_Turn_off_handwriting_personalization_data_sharing_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.3_L2_Ensure_Turn_off_handwriting_recognition_error_reporting_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.4_L2_Ensure_Turn_off_Internet_Connection_Wizard_if_URL_connection_is_referring_to_Microsoft.com_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.5_L1_Ensure_Turn_off_Internet_download_for_Web_publishing_and_online_ordering_wizards_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.6_L2_Ensure_Turn_off_printing_over_HTTP_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.7_L2_Ensure_Turn_off_Registration_if_URL_connection_is_referring_to_Microsoft.com_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.8_L2_Ensure_Turn_off_Search_Companion_content_file_updates_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.9_L2_Ensure_Turn_off_the_Order_Prints_picture_task_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.10_L2_Ensure_Turn_off_the_Publish_to_Web_task_for_files_and_folders_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.11_L2_Ensure_Turn_off_the_Windows_Messenger_Customer_Experience_Improvement_Program_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.12_L2_Ensure_Turn_off_Windows_Customer_Experience_Improvement_Program_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.13_L2_Ensure_Turn_off_Windows_Error_Reporting_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.25.1_L2_Ensure_Support_device_authentication_using_certificate_is_set_to_Enabled_Automatic" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.26.1_L1_Ensure_Enumeration_policy_for_external_devices_incompatible_with_Kernel_DMA_Protection_is_set_to_Enabled_Block_All" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.27.1_L2_Ensure_Disallow_copying_of_user_input_methods_to_the_system_account_for_sign-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.1_L1_Ensure_Block_user_from_showing_account_details_on_sign-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.2_L1_Ensure_Do_not_display_network_selection_UI_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.3_L1_Ensure_Do_not_enumerate_connected_users_on_domain-joined_computers_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.5_L1_Ensure_Turn_off_app_notifications_on_the_lock_screen_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.6_L1_Ensure_Turn_off_picture_password_sign-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.7_L1_Ensure_Turn_on_convenience_PIN_sign-in_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.31.1_L2_Ensure_Allow_Clipboard_synchronization_across_devices_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.31.2_L2_Ensure_Allow_upload_of_User_Activities_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.1_L2_Ensure_Allow_network_connectivity_during_connected-standby_on_battery_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.2_L2_Ensure_Allow_network_connectivity_during_connected-standby_plugged_in_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.3_L1_Ensure_Require_a_password_when_a_computer_wakes_on_battery_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.4_L1_Ensure_Require_a_password_when_a_computer_wakes_plugged_in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.36.1_L1_Ensure_Configure_Offer_Remote_Assistance_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.36.2_L1_Ensure_Configure_Solicited_Remote_Assistance_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.47.5.1_L2_Ensure_Microsoft_Support_Diagnostic_Tool_Turn_on_MSDT_interactive_communication_with_support_provider_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.47.11.1_L2_Ensure_EnableDisable_PerfTrack_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.49.1_L2_Ensure_Turn_off_the_advertising_ID_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.52.1.1_L2_Ensure_Enable_Windows_NTP_Client_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.4.1_L2_Ensure_Allow_a_Windows_app_to_share_application_data_between_users_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.6.1_L1_Ensure_Allow_Microsoft_accounts_to_be_optional_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.1_L1_Ensure_Disallow_Autoplay_for_non-volume_devices_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.2_L1_Ensure_Set_the_default_behavior_for_AutoRun_is_set_to_Enabled_Do_not_execute_any_autorun_commands" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.3_L1_Ensure_Turn_off_Autoplay_is_set_to_Enabled_All_drives" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.10.1.1_L1_Ensure_Configure_enhanced_anti-spoofing_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.12.1_L2_Ensure_Allow_Use_of_Camera_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.13.1_L1_Ensure_Turn_off_Microsoft_consumer_experiences_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.14.1_L1_Ensure_Require_pin_for_pairing_is_set_to_Enabled_First_Time_OR_Enabled_Always" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.15.1_L1_Ensure_Do_not_display_the_password_reveal_button_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.15.2_L1_Ensure_Enumerate_administrator_accounts_on_elevation_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.1_L1_Ensure_Allow_Telemetry_is_set_to_Enabled_0_-_Security_Enterprise_Only_or_Enabled_1_-_Basic" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.2_L2_Ensure_Configure_Authenticated_Proxy_usage_for_the_Connected_User_Experience_and_Telemetry_service_is_set_to_Enabled_Disable_Authenticated_Proxy_usage" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.3_L1_Ensure_Do_not_show_feedback_notifications_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.4_L1_Ensure_Toggle_user_control_over_Insider_builds_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.1.1_L1_Ensure_Application_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.1.2_L1_Ensure_Application_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.2.1_L1_Ensure_Security_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.2.2_L1_Ensure_Security_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_196608_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.3.1_L1_Ensure_Setup_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.3.2_L1_Ensure_Setup_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.4.1_L1_Ensure_System_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.4.2_L1_Ensure_System_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.2_L1_Ensure_Turn_off_Data_Execution_Prevention_for_Explorer_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.3_L1_Ensure_Turn_off_heap_termination_on_corruption_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.4_L1_Ensure_Turn_off_shell_protocol_protected_mode_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.39.2_L2_Ensure_Turn_off_location_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.43.1_L2_Ensure_Allow_Message_Service_Cloud_Sync_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.44.1_L1_Ensure_Block_all_consumer_Microsoft_account_user_authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.52.1_L1_Ensure_Prevent_the_usage_of_OneDrive_for_file_storage_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.2.2_L1_Ensure_Do_not_allow_passwords_to_be_saved_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.2.1_L2_Ensure_Restrict_Remote_Desktop_Services_users_to_a_single_Remote_Desktop_Services_session_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.3.1_L2_Ensure_Do_not_allow_COM_port_redirection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.3.2_L1_Ensure_Do_not_allow_drive_redirection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.3.3_L2_Ensure_Do_not_allow_LPT_port_redirection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.3.4_L2_Ensure_Do_not_allow_supported_Plug_and_Play_device_redirection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.1_L1_Ensure_Always_prompt_for_password_upon_connection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.2_L1_Ensure_Require_secure_RPC_communication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.3_L1_Ensure_Require_use_of_specific_security_layer_for_remote_RDP_connections_is_set_to_Enabled_SSL" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.4_L1_Ensure_Require_user_authentication_for_remote_connections_by_using_Network_Level_Authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.5_L1_Ensure_Set_client_connection_encryption_level_is_set_to_Enabled_High_Level" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.10.1_L2_Ensure_Set_time_limit_for_active_but_idle_Remote_Desktop_Services_sessions_is_set_to_Enabled_15_minutes_or_less" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.10.2_L2_Ensure_Set_time_limit_for_disconnected_sessions_is_set_to_Enabled_1_minute" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.11.1_L1_Ensure_Do_not_delete_temp_folders_upon_exit_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.11.2_L1_Ensure_Do_not_use_temporary_folders_per_session_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.60.1_L1_Ensure_Prevent_downloading_of_enclosures_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.61.2_L2_Ensure_Allow_Cloud_Search_is_set_to_Enabled_Disable_Cloud_Search" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.61.3_L1_Ensure_Allow_indexing_of_encrypted_files_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.66.1_L2_Ensure_Turn_off_KMS_Client_Online_AVS_Validation_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.3.1_L1_Ensure_Configure_local_setting_override_for_reporting_to_Microsoft_MAPS_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.3.2_L2_Ensure_Join_Microsoft_MAPS_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.7.1_L1_Ensure_Turn_on_behavior_monitoring_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.9.1_L2_Ensure_Configure_Watson_events_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.10.1_L1_Ensure_Scan_removable_drives_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.10.2_L1_Ensure_Turn_on_e-mail_scanning_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.1.1_L1_Ensure_Configure_Attack_Surface_Reduction_rules_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.1.2_L1_Ensure_Configure_Attack_Surface_Reduction_rules_Set_the_state_for_each_ASR_rule_is_configured" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.3.1_L1_Ensure_Prevent_users_and_apps_from_accessing_dangerous_websites_is_set_to_Enabled_Block" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.14_L1_Ensure_Configure_detection_for_potentially_unwanted_applications_is_set_to_Enabled_Block" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.15_L1_Ensure_Turn_off_Windows_Defender_AntiVirus_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.80.1.1_L1_Ensure_Configure_Windows_Defender_SmartScreen_is_set_to_Enabled_Warn_and_prevent_bypass" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.84.1_L2_Ensure_Allow_suggested_apps_in_Windows_Ink_Workspace_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.84.2_L1_Ensure_Allow_Windows_Ink_Workspace_is_set_to_Enabled_On_but_disallow_access_above_lock_OR_Disabled_but_not_Enabled_On" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.85.1_L1_Ensure_Allow_user_control_over_installs_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.85.2_L1_Ensure_Always_install_with_elevated_privileges_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.85.3_L2_Ensure_Prevent_Internet_Explorer_security_prompt_for_Windows_Installer_scripts_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.86.1_L1_Ensure_Sign-in_and_lock_last_interactive_user_automatically_after_a_restart_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.95.1_L1_Ensure_Turn_on_PowerShell_Script_Block_Logging_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.95.2_L1_Ensure_Turn_on_PowerShell_Transcription_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.1_L1_Ensure_Allow_Basic_authentication_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.2_L1_Ensure_Allow_unencrypted_traffic_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.3_L1_Ensure_Disallow_Digest_authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.1_L1_Ensure_Allow_Basic_authentication_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.2_L2_Ensure_Allow_remote_server_management_through_WinRM_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.3_L1_Ensure_Allow_unencrypted_traffic_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.4_L1_Ensure_Disallow_WinRM_from_storing_RunAs_credentials_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.98.1_L2_Ensure_Allow_Remote_Shell_Access_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.99.2.1_L1_Ensure_Prevent_users_from_modifying_settings_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.1_L1_Ensure_Manage_preview_builds_is_set_to_Enabled_Disable_preview_builds" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.2_L1_Ensure_Select_when_Preview_Builds_and_Feature_Updates_are_received_is_set_to_Enabled_Semi-Annual_Channel_180_or_more_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.3_L1_Ensure_Select_when_Quality_Updates_are_received_is_set_to_Enabled_0_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.2_L1_Ensure_Configure_Automatic_Updates_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.3_L1_Ensure_Configure_Automatic_Updates_Scheduled_install_day_is_set_to_0_-_Every_day" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.4_L1_Ensure_No_auto-restart_with_logged_on_users_for_scheduled_automatic_updates_installations_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.1_L1_Ensure_Enable_screen_saver_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.2_L1_Ensure_Force_specific_screen_saver_Screen_saver_executable_name_is_set_to_Enabled_scrnsave.scr" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.3_L1_Ensure_Password_protect_the_screen_saver_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.4_L1_Ensure_Screen_saver_timeout_is_set_to_Enabled_900_seconds_or_fewer_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.5.1.1_L1_Ensure_Turn_off_toast_notifications_on_the_lock_screen_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.6.6.1.1_L2_Ensure_Turn_off_Help_Experience_Improvement_Program_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.4.1_L1_Ensure_Do_not_preserve_zone_information_in_file_attachments_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.4.2_L1_Ensure_Notify_antivirus_programs_when_opening_attachments_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.1_L1_Ensure_Configure_Windows_spotlight_on_lock_screen_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.2_L1_Ensure_Do_not_suggest_third-party_content_in_Windows_spotlight_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.3_L2_Ensure_Do_not_use_diagnostic_data_for_tailored_experiences_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.4_L2_Ensure_Turn_off_all_Windows_spotlight_features_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.26.1_L1_Ensure_Prevent_users_from_sharing_files_within_their_profile._is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.41.1_L1_Ensure_Always_install_with_elevated_privileges_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.45.2.1_L2_Ensure_Prevent_Codec_Download_is_set_to_Enabled" selected="true"/> </xccdf:Profile> |
Level 2 - Member Server |
This profile extends the "Level 1 - Member Server" profile. Items in this profile exhibit one or more of the following characteristics:
Show
<xccdf:Profile xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="xccdf_org.cisecurity.benchmarks_profile_Level_2_-_Member_Server"> <xccdf:title xml:lang="en">Level 2 - Member Server</xccdf:title> <xccdf:description xml:lang="en"> <xhtml:p>This profile extends the "Level 1 - Member Server" profile. Items in this profile exhibit one or more of the following characteristics:</xhtml:p> <xhtml:ul> <xhtml:li>are intended for environments or use cases where security is paramount</xhtml:li> <xhtml:li>acts as defense in depth measure</xhtml:li> <xhtml:li>may negatively inhibit the utility or performance of the technology</xhtml:li> </xhtml:ul> </xccdf:description> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1_L1_Ensure_Enforce_password_history_is_set_to_24_or_more_passwords" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.2_L1_Ensure_Maximum_password_age_is_set_to_60_or_fewer_days_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.3_L1_Ensure_Minimum_password_age_is_set_to_1_or_more_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.4_L1_Ensure_Minimum_password_length_is_set_to_14_or_more_characters" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.5_L1_Ensure_Password_must_meet_complexity_requirements_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.6_L1_Ensure_Store_passwords_using_reversible_encryption_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.1_L1_Ensure_Account_lockout_duration_is_set_to_15_or_more_minutes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.2_L1_Ensure_Account_lockout_threshold_is_set_to_10_or_fewer_invalid_logon_attempts_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.3_L1_Ensure_Reset_account_lockout_counter_after_is_set_to_15_or_more_minutes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1_L1_Ensure_Access_Credential_Manager_as_a_trusted_caller_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.3_L1_Ensure_Access_this_computer_from_the_network__is_set_to_Administrators_Authenticated_Users_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.4_L1_Ensure_Act_as_part_of_the_operating_system_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.6_L1_Ensure_Adjust_memory_quotas_for_a_process_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.7_L1_Ensure_Allow_log_on_locally_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.9_L1_Ensure_Allow_log_on_through_Remote_Desktop_Services_is_set_to_Administrators_Remote_Desktop_Users_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.10_L1_Ensure_Back_up_files_and_directories_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.11_L1_Ensure_Change_the_system_time_is_set_to_Administrators_LOCAL_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.12_L1_Ensure_Change_the_time_zone_is_set_to_Administrators_LOCAL_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.13_L1_Ensure_Create_a_pagefile_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.14_L1_Ensure_Create_a_token_object_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.15_L1_Ensure_Create_global_objects_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.16_L1_Ensure_Create_permanent_shared_objects_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.18_L1_Ensure_Create_symbolic_links_is_set_to_Administrators_NT_VIRTUAL_MACHINEVirtual_Machines_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.19_L1_Ensure_Debug_programs_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.21_L1_Ensure_Deny_access_to_this_computer_from_the_network_to_include_Guests_Local_account_and_member_of_Administrators_group_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.22_L1_Ensure_Deny_log_on_as_a_batch_job_to_include_Guests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.23_L1_Ensure_Deny_log_on_as_a_service_to_include_Guests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.24_L1_Ensure_Deny_log_on_locally_to_include_Guests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.26_L1_Ensure_Deny_log_on_through_Remote_Desktop_Services_is_set_to_Guests_Local_account_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.28_L1_Ensure_Enable_computer_and_user_accounts_to_be_trusted_for_delegation_is_set_to_No_One_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.29_L1_Ensure_Force_shutdown_from_a_remote_system_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.30_L1_Ensure_Generate_security_audits_is_set_to_LOCAL_SERVICE_NETWORK_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.32_L1_Ensure_Impersonate_a_client_after_authentication_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE_SERVICE_and_when_the_Web_Server_IIS_Role_with_Web_Services_Role_Service_is_installed_IIS_IUSRS_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.33_L1_Ensure_Increase_scheduling_priority_is_set_to_Administrators_Window_ManagerWindow_Manager_Group" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.34_L1_Ensure_Load_and_unload_device_drivers_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.35_L1_Ensure_Lock_pages_in_memory_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.38_L1_Ensure_Manage_auditing_and_security_log_is_set_to_Administrators_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.39_L1_Ensure_Modify_an_object_label_is_set_to_No_One" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.40_L1_Ensure_Modify_firmware_environment_values_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.41_L1_Ensure_Perform_volume_maintenance_tasks_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.42_L1_Ensure_Profile_single_process_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.43_L1_Ensure_Profile_system_performance_is_set_to_Administrators_NT_SERVICEWdiServiceHost" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.44_L1_Ensure_Replace_a_process_level_token_is_set_to_LOCAL_SERVICE_NETWORK_SERVICE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.45_L1_Ensure_Restore_files_and_directories_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.46_L1_Ensure_Shut_down_the_system_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.48_L1_Ensure_Take_ownership_of_files_or_other_objects_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_L1_Ensure_Accounts_Administrator_account_status_is_set_to_Disabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.2_L1_Ensure_Accounts_Block_Microsoft_accounts_is_set_to_Users_cant_add_or_log_on_with_Microsoft_accounts" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.3_L1_Ensure_Accounts_Guest_account_status_is_set_to_Disabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.4_L1_Ensure_Accounts_Limit_local_account_use_of_blank_passwords_to_console_logon_only_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.5_L1_Configure_Accounts_Rename_administrator_account" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.6_L1_Configure_Accounts_Rename_guest_account" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_L1_Ensure_Audit_Force_audit_policy_subcategory_settings_Windows_Vista_or_later_to_override_audit_policy_category_settings_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_L1_Ensure_Audit_Shut_down_system_immediately_if_unable_to_log_security_audits_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4.1_L1_Ensure_Devices_Allowed_to_format_and_eject_removable_media_is_set_to_Administrators" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4.2_L1_Ensure_Devices_Prevent_users_from_installing_printer_drivers_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.1_L1_Ensure_Domain_member_Digitally_encrypt_or_sign_secure_channel_data_always_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.2_L1_Ensure_Domain_member_Digitally_encrypt_secure_channel_data_when_possible_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.3_L1_Ensure_Domain_member_Digitally_sign_secure_channel_data_when_possible_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.4_L1_Ensure_Domain_member_Disable_machine_account_password_changes_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.5_L1_Ensure_Domain_member_Maximum_machine_account_password_age_is_set_to_30_or_fewer_days_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.6_L1_Ensure_Domain_member_Require_strong_Windows_2000_or_later_session_key_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.1_L1_Ensure_Interactive_logon_Do_not_require_CTRLALTDEL_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.2_L1_Ensure_Interactive_logon_Dont_display_last_signed-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.3_L1_Ensure_Interactive_logon_Machine_inactivity_limit_is_set_to_900_or_fewer_seconds_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.4_L1_Configure_Interactive_logon_Message_text_for_users_attempting_to_log_on" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.5_L1_Configure_Interactive_logon_Message_title_for_users_attempting_to_log_on" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.6_L2_Ensure_Interactive_logon_Number_of_previous_logons_to_cache_in_case_domain_controller_is_not_available_is_set_to_4_or_fewer_logons_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.7_L1_Ensure_Interactive_logon_Prompt_user_to_change_password_before_expiration_is_set_to_between_5_and_14_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.8_L1_Ensure_Interactive_logon_Require_Domain_Controller_Authentication_to_unlock_workstation_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.9_L1_Ensure_Interactive_logon_Smart_card_removal_behavior_is_set_to_Lock_Workstation_or_higher" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.1_L1_Ensure_Microsoft_network_client_Digitally_sign_communications_always_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.2_L1_Ensure_Microsoft_network_client_Digitally_sign_communications_if_server_agrees_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.3_L1_Ensure_Microsoft_network_client_Send_unencrypted_password_to_third-party_SMB_servers_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.1_L1_Ensure_Microsoft_network_server_Amount_of_idle_time_required_before_suspending_session_is_set_to_15_or_fewer_minutes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.2_L1_Ensure_Microsoft_network_server_Digitally_sign_communications_always_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.3_L1_Ensure_Microsoft_network_server_Digitally_sign_communications_if_client_agrees_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.4_L1_Ensure_Microsoft_network_server_Disconnect_clients_when_logon_hours_expire_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.5_L1_Ensure_Microsoft_network_server_Server_SPN_target_name_validation_level_is_set_to_Accept_if_provided_by_client_or_higher_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.1_L1_Ensure_Network_access_Allow_anonymous_SIDName_translation_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.2_L1_Ensure_Network_access_Do_not_allow_anonymous_enumeration_of_SAM_accounts_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.3_L1_Ensure_Network_access_Do_not_allow_anonymous_enumeration_of_SAM_accounts_and_shares_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.4_L2_Ensure_Network_access_Do_not_allow_storage_of_passwords_and_credentials_for_network_authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.5_L1_Ensure_Network_access_Let_Everyone_permissions_apply_to_anonymous_users_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.7_L1_Configure_Network_access_Named_Pipes_that_can_be_accessed_anonymously_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.8_L1_Configure_Network_access_Remotely_accessible_registry_paths" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.9_L1_Configure_Network_access_Remotely_accessible_registry_paths_and_sub-paths" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.10_L1_Ensure_Network_access_Restrict_anonymous_access_to_Named_Pipes_and_Shares_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.11_L1_Ensure_Network_access_Restrict_clients_allowed_to_make_remote_calls_to_SAM_is_set_to_Administrators_Remote_Access_Allow_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.12_L1_Ensure_Network_access_Shares_that_can_be_accessed_anonymously_is_set_to_None" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.13_L1_Ensure_Network_access_Sharing_and_security_model_for_local_accounts_is_set_to_Classic_-_local_users_authenticate_as_themselves" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.1_L1_Ensure_Network_security_Allow_Local_System_to_use_computer_identity_for_NTLM_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.2_L1_Ensure_Network_security_Allow_LocalSystem_NULL_session_fallback_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.3_L1_Ensure_Network_Security_Allow_PKU2U_authentication_requests_to_this_computer_to_use_online_identities_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.4_L1_Ensure_Network_security_Configure_encryption_types_allowed_for_Kerberos_is_set_to_AES128_HMAC_SHA1_AES256_HMAC_SHA1_Future_encryption_types" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.5_L1_Ensure_Network_security_Do_not_store_LAN_Manager_hash_value_on_next_password_change_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.6_L1_Ensure_Network_security_Force_logoff_when_logon_hours_expire_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.7_L1_Ensure_Network_security_LAN_Manager_authentication_level_is_set_to_Send_NTLMv2_response_only._Refuse_LM__NTLM" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.8_L1_Ensure_Network_security_LDAP_client_signing_requirements_is_set_to_Negotiate_signing_or_higher" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.9_L1_Ensure_Network_security_Minimum_session_security_for_NTLM_SSP_based_including_secure_RPC_clients_is_set_to_Require_NTLMv2_session_security_Require_128-bit_encryption" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.10_L1_Ensure_Network_security_Minimum_session_security_for_NTLM_SSP_based_including_secure_RPC_servers_is_set_to_Require_NTLMv2_session_security_Require_128-bit_encryption" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.13.1_L1_Ensure_Shutdown_Allow_system_to_be_shut_down_without_having_to_log_on_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.15.1_L1_Ensure_System_objects_Require_case_insensitivity_for_non-Windows_subsystems_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.15.2_L1_Ensure_System_objects_Strengthen_default_permissions_of_internal_system_objects_e.g._Symbolic_Links_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.1_L1_Ensure_User_Account_Control_Admin_Approval_Mode_for_the_Built-in_Administrator_account_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.2_L1_Ensure_User_Account_Control_Behavior_of_the_elevation_prompt_for_administrators_in_Admin_Approval_Mode_is_set_to_Prompt_for_consent_on_the_secure_desktop" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.3_L1_Ensure_User_Account_Control_Behavior_of_the_elevation_prompt_for_standard_users_is_set_to_Automatically_deny_elevation_requests" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.4_L1_Ensure_User_Account_Control_Detect_application_installations_and_prompt_for_elevation_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.5_L1_Ensure_User_Account_Control_Only_elevate_UIAccess_applications_that_are_installed_in_secure_locations_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.6_L1_Ensure_User_Account_Control_Run_all_administrators_in_Admin_Approval_Mode_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.7_L1_Ensure_User_Account_Control_Switch_to_the_secure_desktop_when_prompting_for_elevation_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.8_L1_Ensure_User_Account_Control_Virtualize_file_and_registry_write_failures_to_per-user_locations_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.1_L1_Ensure_Windows_Firewall_Domain_Firewall_state_is_set_to_On_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.2_L1_Ensure_Windows_Firewall_Domain_Inbound_connections_is_set_to_Block_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.3_L1_Ensure_Windows_Firewall_Domain_Outbound_connections_is_set_to_Allow_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.4_L1_Ensure_Windows_Firewall_Domain_Settings_Display_a_notification_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.5_L1_Ensure_Windows_Firewall_Domain_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewalldomainfw.log" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.6_L1_Ensure_Windows_Firewall_Domain_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.7_L1_Ensure_Windows_Firewall_Domain_Logging_Log_dropped_packets_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.1.8_L1_Ensure_Windows_Firewall_Domain_Logging_Log_successful_connections_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.1_L1_Ensure_Windows_Firewall_Private_Firewall_state_is_set_to_On_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.2_L1_Ensure_Windows_Firewall_Private_Inbound_connections_is_set_to_Block_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.3_L1_Ensure_Windows_Firewall_Private_Outbound_connections_is_set_to_Allow_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.4_L1_Ensure_Windows_Firewall_Private_Settings_Display_a_notification_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.5_L1_Ensure_Windows_Firewall_Private_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewallprivatefw.log" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.6_L1_Ensure_Windows_Firewall_Private_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.7_L1_Ensure_Windows_Firewall_Private_Logging_Log_dropped_packets_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.2.8_L1_Ensure_Windows_Firewall_Private_Logging_Log_successful_connections_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.1_L1_Ensure_Windows_Firewall_Public_Firewall_state_is_set_to_On_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.2_L1_Ensure_Windows_Firewall_Public_Inbound_connections_is_set_to_Block_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.3_L1_Ensure_Windows_Firewall_Public_Outbound_connections_is_set_to_Allow_default" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.4_L1_Ensure_Windows_Firewall_Public_Settings_Display_a_notification_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.5_L1_Ensure_Windows_Firewall_Public_Settings_Apply_local_firewall_rules_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.6_L1_Ensure_Windows_Firewall_Public_Settings_Apply_local_connection_security_rules_is_set_to_No" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.7_L1_Ensure_Windows_Firewall_Public_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewallpublicfw.log" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.8_L1_Ensure_Windows_Firewall_Public_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.9_L1_Ensure_Windows_Firewall_Public_Logging_Log_dropped_packets_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_9.3.10_L1_Ensure_Windows_Firewall_Public_Logging_Log_successful_connections_is_set_to_Yes" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.1.1_L1_Ensure_Audit_Credential_Validation_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.1_L1_Ensure_Audit_Application_Group_Management_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.5_L1_Ensure_Audit_Security_Group_Management_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.2.6_L1_Ensure_Audit_User_Account_Management_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.3.1_L1_Ensure_Audit_PNP_Activity_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.3.2_L1_Ensure_Audit_Process_Creation_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.1_L1_Ensure_Audit_Account_Lockout_is_set_to_include_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.2_L1_Ensure_Audit_Group_Membership_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.3_L1_Ensure_Audit_Logoff_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.4_L1_Ensure_Audit_Logon_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.5_L1_Ensure_Audit_Other_LogonLogoff_Events_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.5.6_L1_Ensure_Audit_Special_Logon_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.1_L1_Ensure_Audit_Detailed_File_Share_is_set_to_include_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.2_L1_Ensure_Audit_File_Share_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.3_L1_Ensure_Audit_Other_Object_Access_Events_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.6.4_L1_Ensure_Audit_Removable_Storage_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.1_L1_Ensure_Audit_Audit_Policy_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.2_L1_Ensure_Audit_Authentication_Policy_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.3_L1_Ensure_Audit_Authorization_Policy_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.4_L1_Ensure_Audit_MPSSVC_Rule-Level_Policy_Change_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.7.5_L1_Ensure_Audit_Other_Policy_Change_Events_is_set_to_include_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.8.1_L1_Ensure_Audit_Sensitive_Privilege_Use_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.1_L1_Ensure_Audit_IPsec_Driver_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.2_L1_Ensure_Audit_Other_System_Events_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.3_L1_Ensure_Audit_Security_State_Change_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.4_L1_Ensure_Audit_Security_System_Extension_is_set_to_include_Success" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_17.9.5_L1_Ensure_Audit_System_Integrity_is_set_to_Success_and_Failure" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.1.1_L1_Ensure_Prevent_enabling_lock_screen_camera_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.1.2_L1_Ensure_Prevent_enabling_lock_screen_slide_show_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.2.2_L1_Ensure_Allow_users_to_enable_online_speech_recognition_services_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.1.3_L2_Ensure_Allow_Online_Tips_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.2.1_L1_Ensure_LAPS_AdmPwd_GPO_Extension__CSE_is_installed_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.2.2_L1_Ensure_Do_not_allow_password_expiration_time_longer_than_required_by_policy_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.2.3_L1_Ensure_Enable_Local_Admin_Password_Management_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.2.4_L1_Ensure_Password_Settings_Password_Complexity_is_set_to_Enabled_Large_letters__small_letters__numbers__special_characters_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.2.5_L1_Ensure_Password_Settings_Password_Length_is_set_to_Enabled_15_or_more_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.2.6_L1_Ensure_Password_Settings_Password_Age_Days_is_set_to_Enabled_30_or_fewer_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.1_L1_Ensure_Apply_UAC_restrictions_to_local_accounts_on_network_logons_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.2_L1_Ensure_Configure_SMB_v1_client_driver_is_set_to_Enabled_Disable_driver_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.3_L1_Ensure_Configure_SMB_v1_server_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.4_L1_Ensure_Enable_Structured_Exception_Handling_Overwrite_Protection_SEHOP_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.6_L1_Ensure_NetBT_NodeType_configuration_is_set_to_Enabled_P-node_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.3.7_L1_Ensure_WDigest_Authentication_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.1_L1_Ensure_MSS_AutoAdminLogon_Enable_Automatic_Logon_not_recommended_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.2_L1_Ensure_MSS_DisableIPSourceRouting_IPv6_IP_source_routing_protection_level_protects_against_packet_spoofing_is_set_to_Enabled_Highest_protection_source_routing_is_completely_disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.3_L1_Ensure_MSS_DisableIPSourceRouting_IP_source_routing_protection_level_protects_against_packet_spoofing_is_set_to_Enabled_Highest_protection_source_routing_is_completely_disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.4_L1_Ensure_MSS_EnableICMPRedirect_Allow_ICMP_redirects_to_override_OSPF_generated_routes_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.5_L2_Ensure_MSS_KeepAliveTime_How_often_keep-alive_packets_are_sent_in_milliseconds_is_set_to_Enabled_300000_or_5_minutes_recommended" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.6_L1_Ensure_MSS_NoNameReleaseOnDemand_Allow_the_computer_to_ignore_NetBIOS_name_release_requests_except_from_WINS_servers_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.7_L2_Ensure_MSS_PerformRouterDiscovery_Allow_IRDP_to_detect_and_configure_Default_Gateway_addresses_could_lead_to_DoS_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.8_L1_Ensure_MSS_SafeDllSearchMode_Enable_Safe_DLL_search_mode_recommended_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.9_L1_Ensure_MSS_ScreenSaverGracePeriod_The_time_in_seconds_before_the_screen_saver_grace_period_expires_0_recommended_is_set_to_Enabled_5_or_fewer_seconds" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.10_L2_Ensure_MSS_TcpMaxDataRetransmissions_IPv6_How_many_times_unacknowledged_data_is_retransmitted_is_set_to_Enabled_3" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.11_L2_Ensure_MSS_TcpMaxDataRetransmissions_How_many_times_unacknowledged_data_is_retransmitted_is_set_to_Enabled_3" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.4.12_L1_Ensure_MSS_WarningLevel_Percentage_threshold_for_the_security_event_log_at_which_the_system_will_generate_a_warning_is_set_to_Enabled_90_or_less" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.4.1_L1_Ensure_Turn_off_multicast_name_resolution_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.5.1_L2_Ensure_Enable_Font_Providers_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.8.1_L1_Ensure_Enable_insecure_guest_logons_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.9.1_L2_Ensure_Turn_on_Mapper_IO_LLTDIO_driver_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.9.2_L2_Ensure_Turn_on_Responder_RSPNDR_driver_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.10.2_L2_Ensure_Turn_off_Microsoft_Peer-to-Peer_Networking_Services_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.2_L1_Ensure_Prohibit_installation_and_configuration_of_Network_Bridge_on_your_DNS_domain_network_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.3_L1_Ensure_Prohibit_use_of_Internet_Connection_Sharing_on_your_DNS_domain_network_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.4_L1_Ensure_Require_domain_users_to_elevate_when_setting_a_networks_location_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.14.1_L1_Ensure_Hardened_UNC_Paths_is_set_to_Enabled_with_Require_Mutual_Authentication_and_Require_Integrity_set_for_all_NETLOGON_and_SYSVOL_shares" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.19.2.1_L2_Disable_IPv6_Ensure_TCPIP6_Parameter_DisabledComponents_is_set_to_0xff_255" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.20.1_L2_Ensure_Configuration_of_wireless_settings_using_Windows_Connect_Now_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.20.2_L2_Ensure_Prohibit_access_of_the_Windows_Connect_Now_wizards_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.21.1_L1_Ensure_Minimize_the_number_of_simultaneous_connections_to_the_Internet_or_a_Windows_Domain_is_set_to_Enabled_3__Prevent_Wi-Fi_when_on_Ethernet" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.5.21.2_L2_Ensure_Prohibit_connection_to_non-domain_networks_when_connected_to_domain_authenticated_network_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.7.1.1_L2_Ensure_Turn_off_notifications_network_usage_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.3.1_L1_Ensure_Include_command_line_in_process_creation_events_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.4.1_L1_Ensure_Encryption_Oracle_Remediation_is_set_to_Enabled_Force_Updated_Clients" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.4.2_L1_Ensure_Remote_host_allows_delegation_of_non-exportable_credentials_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.14.1_L1_Ensure_Boot-Start_Driver_Initialization_Policy_is_set_to_Enabled_Good_unknown_and_bad_but_critical" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.2_L1_Ensure_Configure_registry_policy_processing_Do_not_apply_during_periodic_background_processing_is_set_to_Enabled_FALSE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.3_L1_Ensure_Configure_registry_policy_processing_Process_even_if_the_Group_Policy_objects_have_not_changed_is_set_to_Enabled_TRUE" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.4_L1_Ensure_Continue_experiences_on_this_device_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.5_L1_Ensure_Turn_off_background_refresh_of_Group_Policy_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.1_L1_Ensure_Turn_off_downloading_of_print_drivers_over_HTTP_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.2_L2_Ensure_Turn_off_handwriting_personalization_data_sharing_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.3_L2_Ensure_Turn_off_handwriting_recognition_error_reporting_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.4_L2_Ensure_Turn_off_Internet_Connection_Wizard_if_URL_connection_is_referring_to_Microsoft.com_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.5_L1_Ensure_Turn_off_Internet_download_for_Web_publishing_and_online_ordering_wizards_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.6_L2_Ensure_Turn_off_printing_over_HTTP_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.7_L2_Ensure_Turn_off_Registration_if_URL_connection_is_referring_to_Microsoft.com_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.8_L2_Ensure_Turn_off_Search_Companion_content_file_updates_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.9_L2_Ensure_Turn_off_the_Order_Prints_picture_task_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.10_L2_Ensure_Turn_off_the_Publish_to_Web_task_for_files_and_folders_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.11_L2_Ensure_Turn_off_the_Windows_Messenger_Customer_Experience_Improvement_Program_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.12_L2_Ensure_Turn_off_Windows_Customer_Experience_Improvement_Program_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.13_L2_Ensure_Turn_off_Windows_Error_Reporting_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.25.1_L2_Ensure_Support_device_authentication_using_certificate_is_set_to_Enabled_Automatic" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.26.1_L1_Ensure_Enumeration_policy_for_external_devices_incompatible_with_Kernel_DMA_Protection_is_set_to_Enabled_Block_All" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.27.1_L2_Ensure_Disallow_copying_of_user_input_methods_to_the_system_account_for_sign-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.1_L1_Ensure_Block_user_from_showing_account_details_on_sign-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.2_L1_Ensure_Do_not_display_network_selection_UI_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.3_L1_Ensure_Do_not_enumerate_connected_users_on_domain-joined_computers_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.4_L1_Ensure_Enumerate_local_users_on_domain-joined_computers_is_set_to_Disabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.5_L1_Ensure_Turn_off_app_notifications_on_the_lock_screen_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.6_L1_Ensure_Turn_off_picture_password_sign-in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.7_L1_Ensure_Turn_on_convenience_PIN_sign-in_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.31.1_L2_Ensure_Allow_Clipboard_synchronization_across_devices_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.31.2_L2_Ensure_Allow_upload_of_User_Activities_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.1_L2_Ensure_Allow_network_connectivity_during_connected-standby_on_battery_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.2_L2_Ensure_Allow_network_connectivity_during_connected-standby_plugged_in_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.3_L1_Ensure_Require_a_password_when_a_computer_wakes_on_battery_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.4_L1_Ensure_Require_a_password_when_a_computer_wakes_plugged_in_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.36.1_L1_Ensure_Configure_Offer_Remote_Assistance_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.36.2_L1_Ensure_Configure_Solicited_Remote_Assistance_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.37.1_L1_Ensure_Enable_RPC_Endpoint_Mapper_Client_Authentication_is_set_to_Enabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.37.2_L2_Ensure_Restrict_Unauthenticated_RPC_clients_is_set_to_Enabled_Authenticated_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.47.5.1_L2_Ensure_Microsoft_Support_Diagnostic_Tool_Turn_on_MSDT_interactive_communication_with_support_provider_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.47.11.1_L2_Ensure_EnableDisable_PerfTrack_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.49.1_L2_Ensure_Turn_off_the_advertising_ID_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.52.1.1_L2_Ensure_Enable_Windows_NTP_Client_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.52.1.2_L2_Ensure_Enable_Windows_NTP_Server_is_set_to_Disabled_MS_only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.4.1_L2_Ensure_Allow_a_Windows_app_to_share_application_data_between_users_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.6.1_L1_Ensure_Allow_Microsoft_accounts_to_be_optional_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.1_L1_Ensure_Disallow_Autoplay_for_non-volume_devices_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.2_L1_Ensure_Set_the_default_behavior_for_AutoRun_is_set_to_Enabled_Do_not_execute_any_autorun_commands" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.3_L1_Ensure_Turn_off_Autoplay_is_set_to_Enabled_All_drives" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.10.1.1_L1_Ensure_Configure_enhanced_anti-spoofing_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.12.1_L2_Ensure_Allow_Use_of_Camera_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.13.1_L1_Ensure_Turn_off_Microsoft_consumer_experiences_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.14.1_L1_Ensure_Require_pin_for_pairing_is_set_to_Enabled_First_Time_OR_Enabled_Always" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.15.1_L1_Ensure_Do_not_display_the_password_reveal_button_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.15.2_L1_Ensure_Enumerate_administrator_accounts_on_elevation_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.1_L1_Ensure_Allow_Telemetry_is_set_to_Enabled_0_-_Security_Enterprise_Only_or_Enabled_1_-_Basic" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.2_L2_Ensure_Configure_Authenticated_Proxy_usage_for_the_Connected_User_Experience_and_Telemetry_service_is_set_to_Enabled_Disable_Authenticated_Proxy_usage" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.3_L1_Ensure_Do_not_show_feedback_notifications_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.4_L1_Ensure_Toggle_user_control_over_Insider_builds_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.1.1_L1_Ensure_Application_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.1.2_L1_Ensure_Application_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.2.1_L1_Ensure_Security_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.2.2_L1_Ensure_Security_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_196608_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.3.1_L1_Ensure_Setup_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.3.2_L1_Ensure_Setup_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.4.1_L1_Ensure_System_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.4.2_L1_Ensure_System_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.2_L1_Ensure_Turn_off_Data_Execution_Prevention_for_Explorer_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.3_L1_Ensure_Turn_off_heap_termination_on_corruption_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.4_L1_Ensure_Turn_off_shell_protocol_protected_mode_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.39.2_L2_Ensure_Turn_off_location_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.43.1_L2_Ensure_Allow_Message_Service_Cloud_Sync_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.44.1_L1_Ensure_Block_all_consumer_Microsoft_account_user_authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.52.1_L1_Ensure_Prevent_the_usage_of_OneDrive_for_file_storage_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.2.2_L1_Ensure_Do_not_allow_passwords_to_be_saved_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.2.1_L2_Ensure_Restrict_Remote_Desktop_Services_users_to_a_single_Remote_Desktop_Services_session_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.3.1_L2_Ensure_Do_not_allow_COM_port_redirection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.3.2_L1_Ensure_Do_not_allow_drive_redirection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.3.3_L2_Ensure_Do_not_allow_LPT_port_redirection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.3.4_L2_Ensure_Do_not_allow_supported_Plug_and_Play_device_redirection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.1_L1_Ensure_Always_prompt_for_password_upon_connection_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.2_L1_Ensure_Require_secure_RPC_communication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.3_L1_Ensure_Require_use_of_specific_security_layer_for_remote_RDP_connections_is_set_to_Enabled_SSL" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.4_L1_Ensure_Require_user_authentication_for_remote_connections_by_using_Network_Level_Authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.5_L1_Ensure_Set_client_connection_encryption_level_is_set_to_Enabled_High_Level" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.10.1_L2_Ensure_Set_time_limit_for_active_but_idle_Remote_Desktop_Services_sessions_is_set_to_Enabled_15_minutes_or_less" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.10.2_L2_Ensure_Set_time_limit_for_disconnected_sessions_is_set_to_Enabled_1_minute" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.11.1_L1_Ensure_Do_not_delete_temp_folders_upon_exit_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.11.2_L1_Ensure_Do_not_use_temporary_folders_per_session_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.60.1_L1_Ensure_Prevent_downloading_of_enclosures_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.61.2_L2_Ensure_Allow_Cloud_Search_is_set_to_Enabled_Disable_Cloud_Search" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.61.3_L1_Ensure_Allow_indexing_of_encrypted_files_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.66.1_L2_Ensure_Turn_off_KMS_Client_Online_AVS_Validation_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.3.1_L1_Ensure_Configure_local_setting_override_for_reporting_to_Microsoft_MAPS_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.3.2_L2_Ensure_Join_Microsoft_MAPS_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.7.1_L1_Ensure_Turn_on_behavior_monitoring_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.9.1_L2_Ensure_Configure_Watson_events_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.10.1_L1_Ensure_Scan_removable_drives_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.10.2_L1_Ensure_Turn_on_e-mail_scanning_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.1.1_L1_Ensure_Configure_Attack_Surface_Reduction_rules_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.1.2_L1_Ensure_Configure_Attack_Surface_Reduction_rules_Set_the_state_for_each_ASR_rule_is_configured" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.3.1_L1_Ensure_Prevent_users_and_apps_from_accessing_dangerous_websites_is_set_to_Enabled_Block" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.14_L1_Ensure_Configure_detection_for_potentially_unwanted_applications_is_set_to_Enabled_Block" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.15_L1_Ensure_Turn_off_Windows_Defender_AntiVirus_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.80.1.1_L1_Ensure_Configure_Windows_Defender_SmartScreen_is_set_to_Enabled_Warn_and_prevent_bypass" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.84.1_L2_Ensure_Allow_suggested_apps_in_Windows_Ink_Workspace_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.84.2_L1_Ensure_Allow_Windows_Ink_Workspace_is_set_to_Enabled_On_but_disallow_access_above_lock_OR_Disabled_but_not_Enabled_On" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.85.1_L1_Ensure_Allow_user_control_over_installs_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.85.2_L1_Ensure_Always_install_with_elevated_privileges_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.85.3_L2_Ensure_Prevent_Internet_Explorer_security_prompt_for_Windows_Installer_scripts_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.86.1_L1_Ensure_Sign-in_and_lock_last_interactive_user_automatically_after_a_restart_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.95.1_L1_Ensure_Turn_on_PowerShell_Script_Block_Logging_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.95.2_L1_Ensure_Turn_on_PowerShell_Transcription_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.1_L1_Ensure_Allow_Basic_authentication_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.2_L1_Ensure_Allow_unencrypted_traffic_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.3_L1_Ensure_Disallow_Digest_authentication_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.1_L1_Ensure_Allow_Basic_authentication_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.2_L2_Ensure_Allow_remote_server_management_through_WinRM_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.3_L1_Ensure_Allow_unencrypted_traffic_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.4_L1_Ensure_Disallow_WinRM_from_storing_RunAs_credentials_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.98.1_L2_Ensure_Allow_Remote_Shell_Access_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.99.2.1_L1_Ensure_Prevent_users_from_modifying_settings_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.1_L1_Ensure_Manage_preview_builds_is_set_to_Enabled_Disable_preview_builds" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.2_L1_Ensure_Select_when_Preview_Builds_and_Feature_Updates_are_received_is_set_to_Enabled_Semi-Annual_Channel_180_or_more_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.3_L1_Ensure_Select_when_Quality_Updates_are_received_is_set_to_Enabled_0_days" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.2_L1_Ensure_Configure_Automatic_Updates_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.3_L1_Ensure_Configure_Automatic_Updates_Scheduled_install_day_is_set_to_0_-_Every_day" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.4_L1_Ensure_No_auto-restart_with_logged_on_users_for_scheduled_automatic_updates_installations_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.1_L1_Ensure_Enable_screen_saver_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.2_L1_Ensure_Force_specific_screen_saver_Screen_saver_executable_name_is_set_to_Enabled_scrnsave.scr" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.3_L1_Ensure_Password_protect_the_screen_saver_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.4_L1_Ensure_Screen_saver_timeout_is_set_to_Enabled_900_seconds_or_fewer_but_not_0" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.5.1.1_L1_Ensure_Turn_off_toast_notifications_on_the_lock_screen_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.6.6.1.1_L2_Ensure_Turn_off_Help_Experience_Improvement_Program_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.4.1_L1_Ensure_Do_not_preserve_zone_information_in_file_attachments_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.4.2_L1_Ensure_Notify_antivirus_programs_when_opening_attachments_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.1_L1_Ensure_Configure_Windows_spotlight_on_lock_screen_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.2_L1_Ensure_Do_not_suggest_third-party_content_in_Windows_spotlight_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.3_L2_Ensure_Do_not_use_diagnostic_data_for_tailored_experiences_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.4_L2_Ensure_Turn_off_all_Windows_spotlight_features_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.26.1_L1_Ensure_Prevent_users_from_sharing_files_within_their_profile._is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.41.1_L1_Ensure_Always_install_with_elevated_privileges_is_set_to_Disabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_19.7.45.2.1_L2_Ensure_Prevent_Codec_Download_is_set_to_Enabled" selected="true"/> </xccdf:Profile> |
Next Generation Windows Security - Domain Controller |
This profile contains advanced Windows security features that have specific configuration dependencies, and may not be compatible with all systems. It therefore requires special attention to detail and testing before implementation. If your environment supports these features, they are highly recommended as they have tangible security benefits. This profile is intended to be an optional "add-on" to the Level 1 or Level 2 profiles.
Show
<xccdf:Profile xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="xccdf_org.cisecurity.benchmarks_profile_Next_Generation_Windows_Security_-_Domain_Controller"> <xccdf:title xml:lang="en">Next Generation Windows Security - Domain Controller</xccdf:title> <xccdf:description xml:lang="en"> <xhtml:p>This profile contains advanced Windows security features that have specific configuration dependencies, and may not be compatible with all systems. It therefore requires special attention to detail and testing before implementation. If your environment supports these features, they are highly recommended as they have tangible security benefits. This profile is intended to be an optional "add-on" to the Level 1 or Level 2 profiles.</xhtml:p> </xccdf:description> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.5.1_NG_Ensure_Turn_On_Virtualization_Based_Security_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.5.2_NG_Ensure_Turn_On_Virtualization_Based_Security_Select_Platform_Security_Level_is_set_to_Secure_Boot_and_DMA_Protection" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.5.3_NG_Ensure_Turn_On_Virtualization_Based_Security_Virtualization_Based_Protection_of_Code_Integrity_is_set_to_Enabled_with_UEFI_lock" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.5.4_NG_Ensure_Turn_On_Virtualization_Based_Security_Require_UEFI_Memory_Attributes_Table_is_set_to_True_checked" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.5.6_NG_Ensure_Turn_On_Virtualization_Based_Security_Credential_Guard_Configuration_is_set_to_Disabled_DC_Only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.5.7_NG_Ensure_Turn_On_Virtualization_Based_Security_Secure_Launch_Configuration_is_set_to_Enabled" selected="true"/> </xccdf:Profile> |
Next Generation Windows Security - Member Server |
This profile contains advanced Windows security features that have specific configuration dependencies, and may not be compatible with all systems. It therefore requires special attention to detail and testing before implementation. If your environment supports these features, they are highly recommended as they have tangible security benefits. This profile is intended to be an optional "add-on" to the Level 1 or Level 2 profiles.
Show
<xccdf:Profile xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="xccdf_org.cisecurity.benchmarks_profile_Next_Generation_Windows_Security_-_Member_Server"> <xccdf:title xml:lang="en">Next Generation Windows Security - Member Server</xccdf:title> <xccdf:description xml:lang="en"> <xhtml:p>This profile contains advanced Windows security features that have specific configuration dependencies, and may not be compatible with all systems. It therefore requires special attention to detail and testing before implementation. If your environment supports these features, they are highly recommended as they have tangible security benefits. This profile is intended to be an optional "add-on" to the Level 1 or Level 2 profiles.</xhtml:p> </xccdf:description> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.5.1_NG_Ensure_Turn_On_Virtualization_Based_Security_is_set_to_Enabled" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.5.2_NG_Ensure_Turn_On_Virtualization_Based_Security_Select_Platform_Security_Level_is_set_to_Secure_Boot_and_DMA_Protection" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.5.3_NG_Ensure_Turn_On_Virtualization_Based_Security_Virtualization_Based_Protection_of_Code_Integrity_is_set_to_Enabled_with_UEFI_lock" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.5.4_NG_Ensure_Turn_On_Virtualization_Based_Security_Require_UEFI_Memory_Attributes_Table_is_set_to_True_checked" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.5.5_NG_Ensure_Turn_On_Virtualization_Based_Security_Credential_Guard_Configuration_is_set_to_Enabled_with_UEFI_lock_MS_Only" selected="true"/> <xccdf:select idref="xccdf_org.cisecurity.benchmarks_rule_18.8.5.7_NG_Ensure_Turn_On_Virtualization_Based_Security_Secure_Launch_Configuration_is_set_to_Enabled" selected="true"/> </xccdf:Profile> |
This section contains recommendations for account policies.
This section contains recommendations for password policy.
This policy setting determines the number of renewed, unique passwords that have to be associated with a user account before you can reuse an old password. The value for this policy setting must be between 0 and 24 passwords. The default value for Windows Vista is 0 passwords, but the default setting in a domain is 24 passwords. To maintain the effectiveness of this policy setting, use the Minimum password age setting to prevent users from repeatedly changing their password.
The recommended state for this setting is: 24 or more password(s) .
The longer a user uses the same password, the greater the chance that an attacker can determine the password through brute force attacks. Also, any accounts that may have been compromised will remain exploitable for as long as the password is left unchanged. If password changes are required but password reuse is not prevented, or if users continually reuse a small number of passwords, the effectiveness of a good password policy is greatly reduced.
If you specify a low number for this policy setting, users will be able to use the same small number of passwords repeatedly. If you do not also configure the Minimum password age setting, users might repeatedly change their passwords until they can reuse their original password.
To establish the recommended configuration via GP, set the following UI path to 24 or more password(s) :
Computer Configuration\Policies\Windows Settings\Security Settings\Account Policies\Password Policy\Enforce password history
Impact:
The major impact of this configuration is that users must create a new password every time they are required to change their old one. If users are required to change their passwords to new unique values, there is an increased risk of users who write their passwords somewhere so that they do not forget them. Another risk is that users may create passwords that change incrementally (for example, password01, password02, and so on) to facilitate memorization but make them easier to guess. Also, an excessively low value for the Minimum password age setting will likely increase administrative overhead, because users who forget their passwords might ask the help desk to reset them frequently.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1_L1_Ensure_Enforce_password_history_is_set_to_24_or_more_passwords" role="full" severity="unknown" time="2020-04-22T15:48:23.133-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37166-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.133-05:00" start-time="2020-04-22T15:48:22.772-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Password Hist Len' is 'Greater Than Or Equal' to '24'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817043" result="true" testref="oval:org.cisecurity.benchmarks:tst:817043" type="passwordpolicy_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817043"> <cis:evidence_item itemref="896"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="24" dt="int" ev="24" name="password_hist_len" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817043" value-id="xccdf_org.cisecurity.benchmarks_value_817043_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817043"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37166-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This policy setting defines how long a user can use their password before it expires.
Values for this policy setting range from 0 to 999 days. If you set the value to 0, the password will never expire.
Because attackers can crack passwords, the more frequently you change the password the less opportunity an attacker has to use a cracked password. However, the lower this value is set, the higher the potential for an increase in calls to help desk support due to users having to change their password or forgetting which password is current.
The recommended state for this setting is 60 or fewer days, but not 0 .
The longer a password exists the higher the likelihood that it will be compromised by a brute force attack, by an attacker gaining general knowledge about the user, or by the user sharing the password. Configuring the Maximum password age setting to 0 so that users are never required to change their passwords is a major security risk because that allows a compromised password to be used by the malicious user for as long as the valid user has authorized access.
To establish the recommended configuration via GP, set the following UI path to 60 or fewer days, but not 0 :
Computer Configuration\Policies\Windows Settings\Security Settings\Account Policies\Password Policy\Maximum password age
Impact:
If the Maximum password age setting is too low, users are required to change their passwords very often. Such a configuration can reduce security in the organization, because users might write their passwords in an insecure location or lose them. If the value for this policy setting is too high, the level of security within an organization is reduced because it allows potential attackers more time in which to discover user passwords or to use compromised accounts.
All of the following tests or sub-groups must pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_1.1.2_L1_Ensure_Maximum_password_age_is_set_to_60_or_fewer_days_but_not_0" role="full" severity="unknown" time="2020-04-22T15:48:23.149-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/10" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37167-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.149-05:00" start-time="2020-04-22T15:48:23.149-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Max Passwd Age' is 'Less Than Or Equal' to '5184000'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817045" result="false" testref="oval:org.cisecurity.benchmarks:tst:817045" type="passwordpolicy_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817045"> <cis:evidence_item itemref="896"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="15552000" dt="int" ev="5184000" name="max_passwd_age" op="less than or equal" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Max Passwd Age' is 'Greater Than' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817046" result="true" testref="oval:org.cisecurity.benchmarks:tst:817046" type="passwordpolicy_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817046"> <cis:evidence_item itemref="896"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="15552000" dt="int" ev="0" name="max_passwd_age" op="greater than" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817045" value-id="xccdf_org.cisecurity.benchmarks_value_817045_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817045"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817046" value-id="xccdf_org.cisecurity.benchmarks_value_817046_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817046"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37167-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.10 |
Label: | Ensure All Accounts Have An Expiration Date |
Description: | Ensure that all accounts have an expiration date that is monitored and enforced. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This policy setting determines the number of days that you must use a password before you can change it. The range of values for this policy setting is between 1 and 999 days. (You may also set the value to 0 to allow immediate password changes.) The default value for this setting is 0 days.
The recommended state for this setting is: 1 or more day(s) .
Users may have favorite passwords that they like to use because they are easy to remember and they believe that their password choice is secure from compromise. Unfortunately, passwords are compromised and if an attacker is targeting a specific individual user account, with foreknowledge of data about that user, reuse of old passwords can cause a security breach. To address password reuse a combination of security settings is required. Using this policy setting with the Enforce password history setting prevents the easy reuse of old passwords. For example, if you configure the Enforce password history setting to ensure that users cannot reuse any of their last 12 passwords, they could change their password 13 times in a few minutes and reuse the password they started with, unless you also configure the Minimum password age setting to a number that is greater than 0. You must configure this policy setting to a number that is greater than 0 for the Enforce password history setting to be effective.
To establish the recommended configuration via GP, set the following UI path to 1 or more day(s) :
Computer Configuration\Policies\Windows Settings\Security Settings\Account Policies\Password Policy\Minimum password age
Impact:
If an administrator sets a password for a user but wants that user to change the password when the user first logs on, the administrator must select the User must change password at next logon check box, or the user will not be able to change the password until the next day.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_1.1.3_L1_Ensure_Minimum_password_age_is_set_to_1_or_more_days" role="full" severity="unknown" time="2020-04-22T15:48:23.149-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/10" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37073-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.164-05:00" start-time="2020-04-22T15:48:23.149-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Min Passwd Age' is 'Greater Than Or Equal' to '86400'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817048" result="true" testref="oval:org.cisecurity.benchmarks:tst:817048" type="passwordpolicy_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817048"> <cis:evidence_item itemref="896"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="86400" dt="int" ev="86400" name="min_passwd_age" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817048" value-id="xccdf_org.cisecurity.benchmarks_value_817048_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817048"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37073-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.10 |
Label: | Ensure All Accounts Have An Expiration Date |
Description: | Ensure that all accounts have an expiration date that is monitored and enforced. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This policy setting determines the least number of characters that make up a password for a user account. There are many different theories about how to determine the best password length for an organization, but perhaps "pass phrase" is a better term than "password." In Microsoft Windows 2000 and newer, pass phrases can be quite long and can include spaces. Therefore, a phrase such as "I want to drink a $5 milkshake" is a valid pass phrase; it is a considerably stronger password than an 8 or 10 character string of random numbers and letters, and yet is easier to remember. Users must be educated about the proper selection and maintenance of passwords, especially with regard to password length. In enterprise environments, the ideal value for the Minimum password length setting is 14 characters, however you should adjust this value to meet your organization's business requirements.
The recommended state for this setting is: 14 or more character(s) .
Types of password attacks include dictionary attacks (which attempt to use common words and phrases) and brute force attacks (which try every possible combination of characters). Also, attackers sometimes try to obtain the account database so they can use tools to discover the accounts and passwords.
To establish the recommended configuration via GP, set the following UI path to 14 or more character(s) :
Computer Configuration\Policies\Windows Settings\Security Settings\Account Policies\Password Policy\Minimum password length
Impact:
Requirements for extremely long passwords can actually decrease the security of an organization, because users might leave the information in an insecure location or lose it. If very long passwords are required, mistyped passwords could cause account lockouts and increase the volume of help desk calls. If your organization has issues with forgotten passwords due to password length requirements, consider teaching your users about pass phrases, which are often easier to remember and, due to the larger number of character combinations, much harder to discover.
Note: Older versions of Windows such as Windows 98 and Windows NT 4.0 do not support passwords that are longer than 14 characters. Computers that run these older operating systems are unable to authenticate with computers or domains that use accounts that require long passwords.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_1.1.4_L1_Ensure_Minimum_password_length_is_set_to_14_or_more_characters" role="full" severity="unknown" time="2020-04-22T15:48:23.164-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/12" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36534-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.164-05:00" start-time="2020-04-22T15:48:23.164-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Min Passwd Len' is 'Greater Than Or Equal' to '14'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817052" result="false" testref="oval:org.cisecurity.benchmarks:tst:817052" type="passwordpolicy_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817052"> <cis:evidence_item itemref="896"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="12" dt="int" ev="14" name="min_passwd_len" op="greater than or equal" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817052" value-id="xccdf_org.cisecurity.benchmarks_value_817052_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817052"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36534-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.7 |
Label: | User Accounts Shall Use Long Passwords |
Description: | Where multi-factor authentication is not supported, user accounts shall be required to use long passwords on the system (longer than 14 characters). |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.12 |
Label: | Use Long Passwords For All User Accounts |
Description: | Where multi-factor authentication is not supported, user accounts shall be required to use long passwords on the system (longer than 14 characters). |
This policy setting checks all new passwords to ensure that they meet basic requirements for strong passwords.
When this policy is enabled, passwords must meet the following minimum requirements:
Not contain the user's account name or parts of the user's full name that exceed two consecutive characters
Be at least six characters in length
Contain characters from three of the following categories:
English uppercase characters (A through Z)
English lowercase characters (a through z)
Base 10 digits (0 through 9)
Non-alphabetic characters (for example, !, $, #, %)
A catch-all category of any Unicode character that does not fall under the previous four categories. This fifth category can be regionally specific.
Each additional character in a password increases its complexity exponentially. For instance, a seven-character, all lower-case alphabetic password would have 267 (approximately 8 x 109 or 8 billion) possible combinations. At 1,000,000 attempts per second (a capability of many password-cracking utilities), it would only take 133 minutes to crack. A seven-character alphabetic password with case sensitivity has 527 combinations. A seven-character case-sensitive alphanumeric password without punctuation has 627 combinations. An eight-character password has 268 (or 2 x 1011) possible combinations. Although this might seem to be a large number, at 1,000,000 attempts per second it would take only 59 hours to try all possible passwords. Remember, these times will significantly increase for passwords that use ALT characters and other special keyboard characters such as "!" or "@". Proper use of the password settings can help make it difficult to mount a brute force attack.
The recommended state for this setting is: Enabled .
Passwords that contain only alphanumeric characters are extremely easy to discover with several publicly available tools.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Account Policies\Password Policy\Password must meet complexity requirements
Impact:
If the default password complexity configuration is retained, additional help desk calls for locked-out accounts could occur because users might not be accustomed to passwords that contain non-alphabetic characters. However, all users should be able to comply with the complexity requirement with minimal difficulty.
If your organization has more stringent security requirements, you can create a custom version of the Passfilt.dll file that allows the use of arbitrarily complex password strength rules. For example, a custom password filter might require the use of non-upper row characters. (Upper row characters are those that require you to hold down the SHIFT key and press any of the digits between 1 and 0.) A custom password filter might also perform a dictionary check to verify that the proposed password does not contain common dictionary words or fragments.
Also, the use of ALT key character combinations can greatly enhance the complexity of a password. However, such stringent password requirements can result in unhappy users and an extremely busy help desk. Alternatively, your organization could consider a requirement for all administrator passwords to use ALT characters in the 0128 - 0159 range. (ALT characters outside of this range can represent standard alphanumeric characters that would not add additional complexity to the password.)
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_1.1.5_L1_Ensure_Password_must_meet_complexity_requirements_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:23.164-05:00" version="1" weight="1.0"> <result>unknown</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37063-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.164-05:00" start-time="2020-04-22T15:48:23.164-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Password Complexity' is 'Equals' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817054" result="unknown" testref="oval:org.cisecurity.benchmarks:tst:817054" type="passwordpolicy_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817054"> <cis:evidence_item itemref="896"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="Unknown" dt="boolean" ev="1" name="password_complexity" op="equals" result="unknown"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817054" value-id="xccdf_org.cisecurity.benchmarks_value_817054_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817054"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37063-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This policy setting determines whether the operating system stores passwords in a way that uses reversible encryption, which provides support for application protocols that require knowledge of the user's password for authentication purposes. Passwords that are stored with reversible encryption are essentially the same as plaintext versions of the passwords.
The recommended state for this setting is: Disabled .
Enabling this policy setting allows the operating system to store passwords in a weaker format that is much more susceptible to compromise and weakens your system security.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Account Policies\Password Policy\Store passwords using reversible encryption
Impact:
If your organization uses either the CHAP authentication protocol through remote access or IAS services or Digest Authentication in IIS, you must configure this policy setting to Enabled. This setting is extremely dangerous to apply through Group Policy on a user-by-user basis, because it requires the appropriate user account object to be opened in Active Directory Users and Computers.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_1.1.6_L1_Ensure_Store_passwords_using_reversible_encryption_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:23.180-05:00" version="1" weight="1.0"> <result>unknown</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36286-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.180-05:00" start-time="2020-04-22T15:48:23.164-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Reversible Encryption' is 'Equals' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817057" result="unknown" testref="oval:org.cisecurity.benchmarks:tst:817057" type="passwordpolicy_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817057"> <cis:evidence_item itemref="896"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="Unknown" dt="boolean" ev="0" name="reversible_encryption" op="equals" result="unknown"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817057" value-id="xccdf_org.cisecurity.benchmarks_value_817057_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817057"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36286-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Encrypt or Hash all Authentication Credentials |
Description: | Encrypt or hash with a salt all authentication credentials when stored. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.14 |
Label: | Encrypt/Hash All Authentication Files And Monitor Their Access |
Description: | Verify that all authentication files are encrypted or hashed and that these files cannot be accessed without root or administrator privileges. Audit all access to password files in the system. |
This section contains recommendations for account lockout policy.
This policy setting determines the length of time that must pass before a locked account is unlocked and a user can try to log on again. The setting does this by specifying the number of minutes a locked out account will remain unavailable. If the value for this policy setting is configured to 0, locked out accounts will remain locked out until an administrator manually unlocks them.
Although it might seem like a good idea to configure the value for this policy setting to a high value, such a configuration will likely increase the number of calls that the help desk receives to unlock accounts locked by mistake. Users should be aware of the length of time a lock remains in place, so that they realize they only need to call the help desk if they have an extremely urgent need to regain access to their computer.
The recommended state for this setting is: 15 or more minute(s) .
A denial of service (DoS) condition can be created if an attacker abuses the Account lockout threshold and repeatedly attempts to log on with a specific account. Once you configure the Account lockout threshold setting, the account will be locked out after the specified number of failed attempts. If you configure the Account lockout duration setting to 0, then the account will remain locked out until an administrator unlocks it manually.
To establish the recommended configuration via GP, set the following UI path to 15 or more minute(s) :
Computer Configuration\Policies\Windows Settings\Security Settings\Account Policies\Account Lockout Policy\Account lockout duration
Impact:
Although it may seem like a good idea to configure this policy setting to never automatically unlock an account, such a configuration can increase the number of requests that your organization's help desk receives to unlock accounts that were locked by mistake.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_1.2.1_L1_Ensure_Account_lockout_duration_is_set_to_15_or_more_minutes" role="full" severity="unknown" time="2020-04-22T15:48:23.305-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37034-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.305-05:00" start-time="2020-04-22T15:48:23.180-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Account lockout duration' is set to '15 or more minute(s)'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817044" result="true" testref="oval:org.cisecurity.benchmarks:tst:817044" type="lockoutpolicy_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817044"> <cis:evidence_item itemref="898"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="900" dt="int" ev="900" name="lockout_duration" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817044" value-id="xccdf_org.cisecurity.benchmarks_value_817044_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817044"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37034-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.7 |
Label: | Configure Account Lockouts |
Description: | Use and configure account lockouts such that after a set number of failed login attempts the account is locked for a standard period of time. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines the number of failed logon attempts before the account is locked. Setting this policy to 0 does not conform to the benchmark as doing so disables the account lockout threshold.
The recommended state for this setting is: 10 or fewer invalid logon attempt(s), but not 0 .
Setting an account lockout threshold reduces the likelihood that an online password brute force attack will be successful. Setting the account lockout threshold too low introduces risk of increased accidental lockouts and/or a malicious actor intentionally locking out accounts.
To establish the recommended configuration via GP, set the following UI path to 10 or fewer invalid login attempt(s), but not 0 :
Computer Configuration\Policies\Windows Settings\Security Settings\Account Policies\Account Lockout Policy\Account lockout threshold
Impact:
If this policy setting is enabled, a locked-out account will not be usable until it is reset by an administrator or until the account lockout duration expires. This setting may generate additional help desk calls.
If you enforce this setting an attacker could cause a denial of service condition by deliberately generating failed logons for multiple user, therefore you should also configure the Account Lockout Duration to a relatively low value.
If you configure the Account Lockout Threshold to 0, there is a possibility that an attacker's attempt to discover passwords with a brute force password attack might go undetected if a robust audit mechanism is not in place.
All of the following tests or sub-groups must pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_1.2.2_L1_Ensure_Account_lockout_threshold_is_set_to_10_or_fewer_invalid_logon_attempts_but_not_0" role="full" severity="unknown" time="2020-04-22T15:48:23.305-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36008-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.305-05:00" start-time="2020-04-22T15:48:23.305-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Account lockout threshold' is set to '10 or fewer invalid logon attempt(s)'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817049" result="true" testref="oval:org.cisecurity.benchmarks:tst:817049" type="lockoutpolicy_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817049"> <cis:evidence_item itemref="898"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="10" dt="int" ev="10" name="lockout_threshold" op="less than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Account lockout threshold' is set to 'Not 0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817050" result="true" testref="oval:org.cisecurity.benchmarks:tst:817050" type="lockoutpolicy_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817050"> <cis:evidence_item itemref="898"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="10" dt="int" ev="0" name="lockout_threshold" op="greater than" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817049" value-id="xccdf_org.cisecurity.benchmarks_value_817049_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817049"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817050" value-id="xccdf_org.cisecurity.benchmarks_value_817050_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817050"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36008-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.7 |
Label: | Configure Account Lockouts |
Description: | Use and configure account lockouts such that after a set number of failed login attempts the account is locked for a standard period of time. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines the length of time before the Account lockout threshold resets to zero. The default value for this policy setting is Not Defined. If the Account lockout threshold is defined, this reset time must be less than or equal to the value for the Account lockout duration setting.
If you leave this policy setting at its default value or configure the value to an interval that is too long, your environment could be vulnerable to a DoS attack. An attacker could maliciously perform a number of failed logon attempts on all users in the organization, which will lock out their accounts. If no policy were determined to reset the account lockout, it would be a manual task for administrators. Conversely, if a reasonable time value is configured for this policy setting, users would be locked out for a set period until all of the accounts are unlocked automatically.
The recommended state for this setting is: 15 or more minute(s) .
Users can accidentally lock themselves out of their accounts if they mistype their password multiple times. To reduce the chance of such accidental lockouts, the Reset account lockout counter after setting determines the number of minutes that must elapse before the counter that tracks failed logon attempts and triggers lockouts is reset to 0.
To establish the recommended configuration via GP, set the following UI path to 15 or more minute(s) :
Computer Configuration\Policies\Windows Settings\Security Settings\Account Policies\Account Lockout Policy\Reset account lockout counter after
Impact:
If you do not configure this policy setting or if the value is configured to an interval that is too long, a DoS attack could occur. An attacker could maliciously attempt to log on to each user's account numerous times and lock out their accounts as described in the preceding paragraphs. If you do not configure the Reset account lockout counter after setting, administrators would have to manually unlock all accounts. If you configure this policy setting to a reasonable value the users would be locked out for some period, after which their accounts would unlock automatically. Be sure that you notify users of the values used for this policy setting so that they will wait for the lockout timer to expire before they call the help desk about their inability to log on.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_1.2.3_L1_Ensure_Reset_account_lockout_counter_after_is_set_to_15_or_more_minutes" role="full" severity="unknown" time="2020-04-22T15:48:23.305-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36883-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.305-05:00" start-time="2020-04-22T15:48:23.305-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Reset account lockout counter after' is set to '15 or more minute(s)'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817053" result="true" testref="oval:org.cisecurity.benchmarks:tst:817053" type="lockoutpolicy_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817053"> <cis:evidence_item itemref="898"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="900" dt="int" ev="900" name="lockout_observation_window" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817053" value-id="xccdf_org.cisecurity.benchmarks_value_817053_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817053"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36883-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.7 |
Label: | Configure Account Lockouts |
Description: | Use and configure account lockouts such that after a set number of failed login attempts the account is locked for a standard period of time. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This section contains recommendations for local policies.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section contains recommendations for user rights assignments.
This security setting is used by Credential Manager during Backup and Restore. No accounts should have this user right, as it is only assigned to Winlogon. Users' saved credentials might be compromised if this user right is assigned to other entities.
The recommended state for this setting is: No One .
If an account is given this right the user of the account may create an application that calls into Credential Manager and is returned the credentials for another user.
To establish the recommended configuration via GP, set the following UI path to No One :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Access Credential Manager as a trusted caller
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1_L1_Ensure_Access_Credential_Manager_as_a_trusted_caller_is_set_to_No_One" role="full" severity="unknown" time="2020-04-22T15:48:35.211-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37056-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817047" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="none_exist" comment="Ensure 'setrustedcredmanaccessnameright' is set to 'No One'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817047" result="true" testref="oval:org.cisecurity.benchmarks:tst:817047" type="userright_test"> <cis:evidence_object> <cis:evidence_item itemref="1080"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="userright" value="SE_TRUSTED_CREDMAN_ACCESS_NAME"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817047"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37056-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.8 |
Label: | Log and Alert on Changes to Administrative Group Membership |
Description: | Configure systems to issue a log entry and alert when an account is added to or removed from any group assigned administrative privileges. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting allows other users on the network to connect to the computer and is required by various network protocols that include Server Message Block (SMB)-based protocols, NetBIOS, Common Internet File System (CIFS), and Component Object Model Plus (COM+).
The recommended state for this setting is: Administrators, Authenticated Users .
Users who can connect from their computer to the network can access resources on target computers for which they have permission. For example, the Access this computer from the network user right is required for users to connect to shared printers and folders. If this user right is assigned to the Everyone group, then anyone will be able to read the files in those shared folders. However, this situation is unlikely for new installations of Windows Server 2003 with Service Pack 1 (SP1), because the default share and NTFS permissions in Windows Server 2003 do not include the Everyone group. This vulnerability may have a higher level of risk for computers that you upgrade from Windows NT 4.0 or Windows 2000, because the default permissions for these operating systems are not as restrictive as the default permissions in Windows Server 2003.
To establish the recommended configuration via GP, configure the following UI path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Access this computer from the network
Impact:
If you remove the Access this computer from the network user right on Domain Controllers for all users, no one will be able to log on to the domain or use network resources. If you remove this user right on Member Servers, users will not be able to connect to those servers through the network. Successful negotiation of IPsec connections requires that the initiating machine has this right, therefore if using IPsec, it is recommended that it is assigned to the Authenticated Users group. If you have installed optional components such as ASP.NET or Internet Information Services (IIS), you may need to assign this user right to additional accounts that are required by those components. It is important to verify that authorized users are assigned this user right for the computers they need to access the network.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.3_L1_Ensure_Access_this_computer_from_the_network__is_set_to_Administrators_Authenticated_Users_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:36.242-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-35818-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817051" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'senetworklogonright' is set to 'Administrators, Authenticated Users' - MS" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817051" result="true" testref="oval:org.cisecurity.benchmarks:tst:817051" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817051"> <cis:evidence_item itemref="1100"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_NETWORK_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-(32-544|11)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1101"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_NETWORK_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-11" dt="string" ev="S-1-5-(32-544|11)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817051"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-35818-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
This policy setting allows a process to assume the identity of any user and thus gain access to the resources that the user is authorized to access.
The recommended state for this setting is: No One .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
The Act as part of the operating system user right is extremely powerful. Anyone with this user right can take complete control of the computer and erase evidence of their activities.
To establish the recommended configuration via GP, set the following UI path to No One :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Act as part of the operating system
Impact:
There should be little or no impact because the Act as part of the operating system user right is rarely needed by any accounts other than the Local System account, which implicitly has this right.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.4_L1_Ensure_Act_as_part_of_the_operating_system_is_set_to_No_One" role="full" severity="unknown" time="2020-04-22T15:48:36.836-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36876-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817056" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="none_exist" comment="Ensure 'setcbprivilege' is set to 'No one'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817056" result="true" testref="oval:org.cisecurity.benchmarks:tst:817056" type="userright_test"> <cis:evidence_object> <cis:evidence_item itemref="1112"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="userright" value="SE_TCB_NAME"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817056"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36876-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.8 |
Label: | Log and Alert on Changes to Administrative Group Membership |
Description: | Configure systems to issue a log entry and alert when an account is added to or removed from any group assigned administrative privileges. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting allows a user to adjust the maximum amount of memory that is available to a process. The ability to adjust memory quotas is useful for system tuning, but it can be abused. In the wrong hands, it could be used to launch a denial of service (DoS) attack.
The recommended state for this setting is: Administrators, LOCAL SERVICE, NETWORK SERVICE .
Note: A Member Server that holds the Web Server (IIS) Role with Web Server Role Service will require a special exception to this recommendation, to allow IIS application pool(s) to be granted this user right.
Note #2: A Member Server with Microsoft SQL Server installed will require a special exception to this recommendation for additional SQL-generated entries to be granted this user right.
A user with the Adjust memory quotas for a process user right can reduce the amount of memory that is available to any process, which could cause business-critical network applications to become slow or to fail. In the wrong hands, this privilege could be used to start a denial of service (DoS) attack.
To establish the recommended configuration via GP, set the following UI path to Administrators, LOCAL SERVICE, NETWORK SERVICE :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Adjust memory quotas for a process
Impact:
Organizations that have not restricted users to roles with limited privileges will find it difficult to impose this countermeasure. Also, if you have installed optional components such as ASP.NET or IIS, you may need to assign the Adjust memory quotas for a process user right to additional accounts that are required by those components. Otherwise, this countermeasure should have no impact on most computers. If this user right is necessary for a user account, it can be assigned to a local computer account instead of a domain account.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.6_L1_Ensure_Adjust_memory_quotas_for_a_process_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE" role="full" severity="unknown" time="2020-04-22T15:48:36.914-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37071-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817064" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'seincreasequotaprivilege' is set to 'Administrators, LOCAL SERVICE, NETWORK SERVICE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817064" result="true" testref="oval:org.cisecurity.benchmarks:tst:817064" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817064"> <cis:evidence_item itemref="1113"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_INCREASE_QUOTA_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-(32-544|19|20)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1114"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_INCREASE_QUOTA_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-20" dt="string" ev="S-1-5-(32-544|19|20)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1115"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_INCREASE_QUOTA_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-19" dt="string" ev="S-1-5-(32-544|19|20)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817064"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37071-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.8 |
Label: | Log and Alert on Changes to Administrative Group Membership |
Description: | Configure systems to issue a log entry and alert when an account is added to or removed from any group assigned administrative privileges. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting determines which users can interactively log on to computers in your environment. Logons that are initiated by pressing the CTRL+ALT+DEL key sequence on the client computer keyboard require this user right. Users who attempt to log on through Terminal Services / Remote Desktop Services or IIS also require this user right.
The recommended state for this setting is: Administrators .
Note: This user right should generally be restricted to the Administrators group. Assign this user right to the Backup Operators group if your organization requires that they have this capability.
Any account with the Allow log on locally user right can log on at the console of the computer. If you do not restrict this user right to legitimate users who need to be able to log on to the console of the computer, unauthorized users could download and run malicious software to elevate their privileges.
To establish the recommended configuration via GP, configure the following UI path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Allow log on locally
Impact:
If you remove these default groups, you could limit the abilities of users who are assigned to specific administrative roles in your environment. You should confirm that delegated activities will not be adversely affected by any changes that you make to the Allow log on locally user right.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.7_L1_Ensure_Allow_log_on_locally_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:36.993-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37659-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817072" definition_negate="false"> <cis:and negated="false" result="false"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'seinteractivelogonright' is set to 'Administrators'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817072" result="false" testref="oval:org.cisecurity.benchmarks:tst:817072" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817072"> <cis:evidence_item itemref="1116"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_INTERACTIVE_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-555" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="false"/> </cis:evidence_item> <cis:evidence_item itemref="1117"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_INTERACTIVE_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817072"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37659-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.1 |
Label: | Maintain Inventory of Administrative Accounts |
Description: | Use automated tools to inventory all administrative accounts, including domain and local accounts, to ensure that only authorized individuals have elevated privileges. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.5 |
Label: | Use Multifactor Authentication For All Administrative Access |
Description: | Use multi-factor authentication and encrypted channels for all administrative account access. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines which users or groups have the right to log on as a Remote Desktop Services client. If your organization uses Remote Assistance as part of its help desk strategy, create a group and assign it this user right through Group Policy. If the help desk in your organization does not use Remote Assistance, assign this user right only to the Administrators group or use the Restricted Groups feature to ensure that no user accounts are part of the Remote Desktop Users group.
Restrict this user right to the Administrators group, and possibly the Remote Desktop Users group, to prevent unwanted users from gaining access to computers on your network by means of the Remote Assistance feature.
The recommended state for this setting is: Administrators, Remote Desktop Users .
Note: A Member Server that holds the Remote Desktop Services Role with Remote Desktop Connection Broker Role Service will require a special exception to this recommendation, to allow the Authenticated Users group to be granted this user right.
Note #2: The above lists are to be treated as whitelists, which implies that the above principals need not be present for assessment of this recommendation to pass.
Note #3: In all versions of Windows Server prior to Server 2008 R2, Remote Desktop Services was known as Terminal Services , so you should substitute the older term if comparing against an older OS.
Any account with the Allow log on through Remote Desktop Services user right can log on to the remote console of the computer. If you do not restrict this user right to legitimate users who need to log on to the console of the computer, unauthorized users could download and run malicious software to elevate their privileges.
To establish the recommended configuration via GP, configure the following UI path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Allow log on through Remote Desktop Services
Impact:
Removal of the Allow log on through Remote Desktop Services user right from other groups or membership changes in these default groups could limit the abilities of users who perform specific administrative roles in your environment. You should confirm that delegated activities will not be adversely affected.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.9_L1_Ensure_Allow_log_on_through_Remote_Desktop_Services_is_set_to_Administrators_Remote_Desktop_Users_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:37.055-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37072-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817083" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'seremoteinteractivelogonright' is set to 'Administrators, Remote Desktop Users' - MS" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817083" result="true" testref="oval:org.cisecurity.benchmarks:tst:817083" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817083"> <cis:evidence_item itemref="1118"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_REMOTE_INTERACTIVE_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-555" dt="string" ev="S-1-5-32-(544|555)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1119"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_REMOTE_INTERACTIVE_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-(544|555)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817083"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37072-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.1 |
Label: | Maintain Inventory of Administrative Accounts |
Description: | Use automated tools to inventory all administrative accounts, including domain and local accounts, to ensure that only authorized individuals have elevated privileges. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.5 |
Label: | Use Multifactor Authentication For All Administrative Access |
Description: | Use multi-factor authentication and encrypted channels for all administrative account access. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.8 |
Label: | Log and Alert on Changes to Administrative Group Membership |
Description: | Configure systems to issue a log entry and alert when an account is added to or removed from any group assigned administrative privileges. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting allows users to circumvent file and directory permissions to back up the system. This user right is enabled only when an application (such as NTBACKUP ) attempts to access a file or directory through the NTFS file system backup application programming interface (API). Otherwise, the assigned file and directory permissions apply.
The recommended state for this setting is: Administrators .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
Users who are able to back up data from a computer could take the backup media to a non-domain computer on which they have administrative privileges and restore the data. They could take ownership of the files and view any unencrypted data that is contained within the backup set.
To establish the recommended configuration via GP, set the following UI path to Administrators .
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Back up files and directories
Impact:
Changes in the membership of the groups that have the Back up files and directories user right could limit the abilities of users who are assigned to specific administrative roles in your environment. You should confirm that authorized backup administrators are still able to perform backup operations.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.10_L1_Ensure_Back_up_files_and_directories_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:34.617-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-35912-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817092" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'sebackupprivilege' is set to 'Administrator'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817092" result="true" testref="oval:org.cisecurity.benchmarks:tst:817092" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817092"> <cis:evidence_item itemref="1066"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_BACKUP_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817092"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-35912-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.1 |
Label: | Maintain Inventory of Administrative Accounts |
Description: | Use automated tools to inventory all administrative accounts, including domain and local accounts, to ensure that only authorized individuals have elevated privileges. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting determines which users and groups can change the time and date on the internal clock of the computers in your environment. Users who are assigned this user right can affect the appearance of event logs. When a computer's time setting is changed, logged events reflect the new time, not the actual time that the events occurred.
The recommended state for this setting is: Administrators, LOCAL SERVICE .
Note: Discrepancies between the time on the local computer and on the Domain Controllers in your environment may cause problems for the Kerberos authentication protocol, which could make it impossible for users to log on to the domain or obtain authorization to access domain resources after they are logged on. Also, problems will occur when Group Policy is applied to client computers if the system time is not synchronized with the Domain Controllers.
Users who can change the time on a computer could cause several problems. For example, time stamps on event log entries could be made inaccurate, time stamps on files and folders that are created or modified could be incorrect, and computers that belong to a domain may not be able to authenticate themselves or users who try to log on to the domain from them. Also, because the Kerberos authentication protocol requires that the requestor and authenticator have their clocks synchronized within an administrator-defined skew period, an attacker who changes a computer's time may cause that computer to be unable to obtain or grant Kerberos tickets.
The risk from these types of events is mitigated on most Domain Controllers, Member Servers, and end-user computers because the Windows Time service automatically synchronizes time with Domain Controllers in the following ways:
This vulnerability becomes much more serious if an attacker is able to change the system time and then stop the Windows Time service or reconfigure it to synchronize with a time server that is not accurate.
To establish the recommended configuration via GP, set the following UI path to Administrators, LOCAL SERVICE :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Change the system time
Impact:
There should be no impact, because time synchronization for most organizations should be fully automated for all computers that belong to the domain. Computers that do not belong to the domain should be configured to synchronize with an external source.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.11_L1_Ensure_Change_the_system_time_is_set_to_Administrators_LOCAL_SERVICE" role="full" severity="unknown" time="2020-04-22T15:48:34.696-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37452-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817100" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'sesystemtimeprivilege' is set to 'Administrators, LOCAL SERVICE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817100" result="true" testref="oval:org.cisecurity.benchmarks:tst:817100" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817100"> <cis:evidence_item itemref="1067"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_SYSTEMTIME_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-(32-544|19)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1068"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_SYSTEMTIME_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-19" dt="string" ev="S-1-5-(32-544|19)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817100"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37452-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This setting determines which users can change the time zone of the computer. This ability holds no great danger for the computer and may be useful for mobile workers.
The recommended state for this setting is: Administrators, LOCAL SERVICE .
Changing the time zone represents little vulnerability because the system time is not affected. This setting merely enables users to display their preferred time zone while being synchronized with Domain Controllers in different time zones.
To establish the recommended configuration via GP, set the following UI path to Administrators, LOCAL SERVICE :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Change the time zone
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.12_L1_Ensure_Change_the_time_zone_is_set_to_Administrators_LOCAL_SERVICE" role="full" severity="unknown" time="2020-04-22T15:48:34.758-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37700-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817109" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'setimezoneprivilege' is set to 'Administrators, LOCAL SERVICE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817109" result="true" testref="oval:org.cisecurity.benchmarks:tst:817109" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817109"> <cis:evidence_item itemref="1069"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_TIME_ZONE_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-(32-544|19)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1070"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_TIME_ZONE_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-19" dt="string" ev="S-1-5-(32-544|19)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817109"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37700-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting allows users to change the size of the pagefile. By making the pagefile extremely large or extremely small, an attacker could easily affect the performance of a compromised computer.
The recommended state for this setting is: Administrators .
Users who can change the page file size could make it extremely small or move the file to a highly fragmented storage volume, which could cause reduced computer performance.
To establish the recommended configuration via GP, set the following UI path to Administrators :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Create a pagefile
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.13_L1_Ensure_Create_a_pagefile_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:34.821-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-35821-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817120" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'secreatepagefileprivilege' is set to 'Administrators'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817120" result="true" testref="oval:org.cisecurity.benchmarks:tst:817120" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817120"> <cis:evidence_item itemref="1071"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_CREATE_PAGEFILE_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817120"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-35821-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.1 |
Label: | Maintain Inventory of Administrative Accounts |
Description: | Use automated tools to inventory all administrative accounts, including domain and local accounts, to ensure that only authorized individuals have elevated privileges. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting allows a process to create an access token, which may provide elevated rights to access sensitive data.
The recommended state for this setting is: No One .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
A user account that is given this user right has complete control over the system and can lead to the system being compromised. It is highly recommended that you do not assign any user accounts this right.
The operating system examines a user's access token to determine the level of the user's privileges. Access tokens are built when users log on to the local computer or connect to a remote computer over a network. When you revoke a privilege, the change is immediately recorded, but the change is not reflected in the user's access token until the next time the user logs on or connects. Users with the ability to create or modify tokens can change the level of access for any currently logged on account. They could escalate their own privileges or create a DoS condition.
To establish the recommended configuration via GP, set the following UI path to No One :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Create a token object
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.14_L1_Ensure_Create_a_token_object_is_set_to_No_One" role="full" severity="unknown" time="2020-04-22T15:48:34.883-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36861-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817130" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="none_exist" comment="Ensure 'secreatetokenprivilege' is set to 'No One'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817130" result="true" testref="oval:org.cisecurity.benchmarks:tst:817130" type="userright_test"> <cis:evidence_object> <cis:evidence_item itemref="1072"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="userright" value="SE_CREATE_TOKEN_NAME"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817130"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36861-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.8 |
Label: | Log and Alert on Changes to Administrative Group Membership |
Description: | Configure systems to issue a log entry and alert when an account is added to or removed from any group assigned administrative privileges. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting determines whether users can create global objects that are available to all sessions. Users can still create objects that are specific to their own session if they do not have this user right.
Users who can create global objects could affect processes that run under other users' sessions. This capability could lead to a variety of problems, such as application failure or data corruption.
The recommended state for this setting is: Administrators, LOCAL SERVICE, NETWORK SERVICE, SERVICE .
Note: A Member Server with Microsoft SQL Server and its optional "Integration Services" component installed will require a special exception to this recommendation for additional SQL-generated entries to be granted this user right.
Users who can create global objects could affect Windows services and processes that run under other user or system accounts. This capability could lead to a variety of problems, such as application failure, data corruption and elevation of privilege.
To establish the recommended configuration via GP, set the following UI path to Administrators, LOCAL SERVICE, NETWORK SERVICE, SERVICE :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Create global objects
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.15_L1_Ensure_Create_global_objects_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE_SERVICE" role="full" severity="unknown" time="2020-04-22T15:48:34.946-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37453-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817145" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'secreateglobalprivilege' is set to 'Administrators, LOCAL SERVICE, NETWORK SERVICE, SERVICE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817145" result="true" testref="oval:org.cisecurity.benchmarks:tst:817145" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817145"> <cis:evidence_item itemref="1073"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_CREATE_GLOBAL_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-6" dt="string" ev="S-1-5-(32-544|19|20|6)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1074"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_CREATE_GLOBAL_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-(32-544|19|20|6)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1075"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_CREATE_GLOBAL_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-20" dt="string" ev="S-1-5-(32-544|19|20|6)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1076"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_CREATE_GLOBAL_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-19" dt="string" ev="S-1-5-(32-544|19|20|6)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817145"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37453-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This user right is useful to kernel-mode components that extend the object namespace. However, components that run in kernel mode have this user right inherently. Therefore, it is typically not necessary to specifically assign this user right.
The recommended state for this setting is: No One .
Users who have the Create permanent shared objects user right could create new shared objects and expose sensitive data to the network.
To establish the recommended configuration via GP, set the following UI path to No One :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Create permanent shared objects
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.16_L1_Ensure_Create_permanent_shared_objects_is_set_to_No_One" role="full" severity="unknown" time="2020-04-22T15:48:35.024-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36532-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817152" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="none_exist" comment="Ensure 'secreatepermanentprivilege' is set to 'No One'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817152" result="true" testref="oval:org.cisecurity.benchmarks:tst:817152" type="userright_test"> <cis:evidence_object> <cis:evidence_item itemref="1077"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="userright" value="SE_CREATE_PERMANENT_NAME"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817152"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36532-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.8 |
Label: | Log and Alert on Changes to Administrative Group Membership |
Description: | Configure systems to issue a log entry and alert when an account is added to or removed from any group assigned administrative privileges. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting determines which users can create symbolic links. In Windows Vista, existing NTFS file system objects, such as files and folders, can be accessed by referring to a new kind of file system object called a symbolic link. A symbolic link is a pointer (much like a shortcut or .lnk file) to another file system object, which can be a file, folder, shortcut or another symbolic link. The difference between a shortcut and a symbolic link is that a shortcut only works from within the Windows shell. To other programs and applications, shortcuts are just another file, whereas with symbolic links, the concept of a shortcut is implemented as a feature of the NTFS file system.
Symbolic links can potentially expose security vulnerabilities in applications that are not designed to use them. For this reason, the privilege for creating symbolic links should only be assigned to trusted users. By default, only Administrators can create symbolic links.
The recommended state for this setting is: Administrators and (when the Hyper-V Role is installed) NT VIRTUAL MACHINE\Virtual Machines .
Users who have the Create symbolic links user right could inadvertently or maliciously expose your system to symbolic link attacks. Symbolic link attacks can be used to change the permissions on a file, to corrupt data, to destroy data, or as a Denial of Service attack.
To implement the recommended configuration state, configure the following UI path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Create symbolic links
Impact:
In most cases there will be no impact because this is the default configuration. However, on Windows Servers with the Hyper-V server role installed, this user right should also be granted to the special group Virtual Machines - otherwise you will not be able to create new virtual machines.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.18_L1_Ensure_Create_symbolic_links_is_set_to_Administrators_NT_VIRTUAL_MACHINEVirtual_Machines_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:35.086-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-35823-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817162" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'secreatesymboliclinkprivilege' is set to 'Administrators, NT VIRTUAL MACHINE\Virtual Machines' - MS" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817162" result="true" testref="oval:org.cisecurity.benchmarks:tst:817162" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817162"> <cis:evidence_item itemref="1078"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_CREATE_SYMBOLIC_LINK_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-(32-544|83-0)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817162"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-35823-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.1 |
Label: | Maintain Inventory of Administrative Accounts |
Description: | Use automated tools to inventory all administrative accounts, including domain and local accounts, to ensure that only authorized individuals have elevated privileges. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting determines which user accounts will have the right to attach a debugger to any process or to the kernel, which provides complete access to sensitive and critical operating system components. Developers who are debugging their own applications do not need to be assigned this user right; however, developers who are debugging new system components will need it.
The recommended state for this setting is: Administrators .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
The Debug programs user right can be exploited to capture sensitive computer information from system memory, or to access and modify kernel or application structures. Some attack tools exploit this user right to extract hashed passwords and other private security information, or to insert rootkit code. By default, the Debug programs user right is assigned only to administrators, which helps to mitigate the risk from this vulnerability.
To establish the recommended configuration via GP, set the following UI path to Administrators :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Debug programs
Impact:
If you revoke this user right, no one will be able to debug programs. However, typical circumstances rarely require this capability on production computers. If a problem arises that requires an application to be debugged on a production server, you can move the server to a different OU temporarily and assign the Debug programs user right to a separate Group Policy for that OU.
The service account that is used for the cluster service needs the Debug programs user right; if it does not have it, Windows Clustering will fail.
Tools that are used to manage processes will be unable to affect processes that are not owned by the person who runs the tools. For example, the Windows Server 2003 Resource Kit tool Kill.exe requires this user right for administrators to terminate processes that they did not start.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.19_L1_Ensure_Debug_programs_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:35.149-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37075-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817175" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'sedebugprivilege' is set to 'Administrators'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817175" result="true" testref="oval:org.cisecurity.benchmarks:tst:817175" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817175"> <cis:evidence_item itemref="1079"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_DEBUG_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817175"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37075-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.1 |
Label: | Maintain Inventory of Administrative Accounts |
Description: | Use automated tools to inventory all administrative accounts, including domain and local accounts, to ensure that only authorized individuals have elevated privileges. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting prohibits users from connecting to a computer from across the network, which would allow users to access and potentially modify data remotely. In high security environments, there should be no need for remote users to access data on a computer. Instead, file sharing should be accomplished through the use of network servers. This user right supersedes the Access this computer from the network user right if an account is subject to both policies.
The recommended state for this setting is to include: Guests, Local account and member of Administrators group .
Caution: Configuring a standalone (non-domain-joined) server as described above may result in an inability to remotely administer the server.
Note: The security identifier Local account and member of Administrators group is not available in Server 2008 R2 and Server 2012 (non-R2) unless MSKB 2871997 has been installed.
Note #2: Configuring a Member Server or standalone server as described above may adversely affect applications that create a local service account and place it in the Administrators group - in which case you must either convert the application to use a domain-hosted service account, or remove Local account and member of Administrators group from this User Right Assignment. Using a domain-hosted service account is strongly preferred over making an exception to this rule, where possible.
Users who can log on to the computer over the network can enumerate lists of account names, group names, and shared resources. Users with permission to access shared folders and files can connect over the network and possibly view or modify data.
To establish the recommended configuration via GP, configure the following UI path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Deny access to this computer from the network
Impact:
If you configure the Deny access to this computer from the network user right for other groups, you could limit the abilities of users who are assigned to specific administrative roles in your environment. You should verify that delegated tasks will not be negatively affected.
All of the following tests or sub-groups must pass: | ||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.21_L1_Ensure_Deny_access_to_this_computer_from_the_network_to_include_Guests_Local_account_and_member_of_Administrators_group_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:35.289-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37954-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817186" definition_negate="false"> <cis:and negated="false" result="false"> <cis:evidence_test check="at least one" check_existence="at_least_one_exists" comment="Ensure 'sedenynetworklogonright' to include 'Guests, Local account and member of Administrators group' - MS" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817186" result="true" testref="oval:org.cisecurity.benchmarks:tst:8171861" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:8171861"> <cis:evidence_item itemref="1081"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_DENY_NETWORK_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-546" dt="string" ev="S-1-5-32-546" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="at least one" check_existence="at_least_one_exists" comment="Ensure 'sedenynetworklogonright' to include 'Guests, Local account and member of Administrators group' - MS" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817186" result="false" testref="oval:org.cisecurity.benchmarks:tst:8171862" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:8171862"> <cis:evidence_item itemref="1081"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_DENY_NETWORK_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-546" dt="string" ev="S-1-5-114" name="trustee_sid" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817186"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37954-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.8 |
Label: | Disable Any Unassociated Accounts |
Description: | Disable any account that cannot be associated with a business process or business owner. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines which accounts will not be able to log on to the computer as a batch job. A batch job is not a batch (.bat) file, but rather a batch-queue facility. Accounts that use the Task Scheduler to schedule jobs need this user right.
This user right supersedes the Log on as a batch job user right, which could be used to allow accounts to schedule jobs that consume excessive system resources. Such an occurrence could cause a DoS condition. Failure to assign this user right to the recommended accounts can be a security risk.
The recommended state for this setting is to include: Guests .
Accounts that have the Log on as a batch job user right could be used to schedule jobs that could consume excessive computer resources and cause a DoS condition.
To establish the recommended configuration via GP, set the following UI path to include Guests :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Deny log on as a batch job
Impact:
If you assign the Deny log on as a batch job user right to other accounts, you could deny users who are assigned to specific administrative roles the ability to perform their required job activities. You should confirm that delegated tasks will not be affected adversely.
For example, if you assign this user right to the IWAM_ (ComputerName) account, the MSM Management Point will fail. On a newly installed computer that runs Windows Server 2003 this account does not belong to the Guests group, but on a computer that was upgraded from Windows 2000 this account is a member of the Guests group. Therefore, it is important that you understand which accounts belong to any groups that you assign the Deny log on as a batch job user right.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.22_L1_Ensure_Deny_log_on_as_a_batch_job_to_include_Guests" role="full" severity="unknown" time="2020-04-22T15:48:35.352-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36923-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817194" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="at least one" check_existence="at_least_one_exists" comment="Ensure 'sedenybatchLogonright' to include 'Guests'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817194" result="true" testref="oval:org.cisecurity.benchmarks:tst:8171941" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:8171941"> <cis:evidence_item itemref="1082"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_DENY_BATCH_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-546" dt="string" ev="S-1-5-32-546" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817194"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36923-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.8 |
Label: | Disable Any Unassociated Accounts |
Description: | Disable any account that cannot be associated with a business process or business owner. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This security setting determines which service accounts are prevented from registering a process as a service. This user right supersedes the Log on as a service user right if an account is subject to both policies.
The recommended state for this setting is to include: Guests .
Note: This security setting does not apply to the System , Local Service , or Network Service accounts.
Accounts that can log on as a service could be used to configure and start new unauthorized services, such as a keylogger or other malicious software. The benefit of the specified countermeasure is somewhat reduced by the fact that only users with administrative privileges can install and configure services, and an attacker who has already attained that level of access could configure the service to run with the System account.
To establish the recommended configuration via GP, set the following UI path to include Guests :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Deny log on as a service
Impact:
If you assign the Deny log on as a service user right to specific accounts, services may not be able to start and a DoS condition could result.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.23_L1_Ensure_Deny_log_on_as_a_service_to_include_Guests" role="full" severity="unknown" time="2020-04-22T15:48:35.430-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36877-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817204" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="at least one" check_existence="at_least_one_exists" comment="Ensure 'SE_DENY_SERVICE_LOGON_NAME' to include 'Guests'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817204" result="true" testref="oval:org.cisecurity.benchmarks:tst:8172041" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:8172041"> <cis:evidence_item itemref="1083"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_DENY_SERVICE_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-546" dt="string" ev="S-1-5-32-546" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817204"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36877-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.8 |
Label: | Disable Any Unassociated Accounts |
Description: | Disable any account that cannot be associated with a business process or business owner. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This security setting determines which users are prevented from logging on at the computer. This policy setting supersedes the Allow log on locally policy setting if an account is subject to both policies.
The recommended state for this setting is to include: Guests .
Important: If you apply this security policy to the Everyone group, no one will be able to log on locally.
Any account with the ability to log on locally could be used to log on at the console of the computer. If this user right is not restricted to legitimate users who need to log on to the console of the computer, unauthorized users might download and run malicious software that elevates their privileges.
To establish the recommended configuration via GP, set the following UI path to include Guests :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Deny log on locally
Impact:
If you assign the Deny log on locally user right to additional accounts, you could limit the abilities of users who are assigned to specific roles in your environment. However, this user right should explicitly be assigned to the ASPNET account on computers that run IIS 6.0. You should confirm that delegated activities will not be adversely affected.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.24_L1_Ensure_Deny_log_on_locally_to_include_Guests" role="full" severity="unknown" time="2020-04-22T15:48:35.493-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37146-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817214" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="at least one" check_existence="at_least_one_exists" comment="Ensure 'sedenyinteractivelogonright' to include 'Guests'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817214" result="true" testref="oval:org.cisecurity.benchmarks:tst:8172141" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:8172141"> <cis:evidence_item itemref="1084"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_DENY_INTERACTIVE_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-546" dt="string" ev="S-1-5-32-546" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817214"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37146-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.8 |
Label: | Disable Any Unassociated Accounts |
Description: | Disable any account that cannot be associated with a business process or business owner. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines whether users can log on as Remote Desktop clients. After the baseline Member Server is joined to a domain environment, there is no need to use local accounts to access the server from the network. Domain accounts can access the server for administration and end-user processing. This user right supersedes the Allow log on through Remote Desktop Services user right if an account is subject to both policies.
The recommended state for this setting is: Guests, Local account .
Caution: Configuring a standalone (non-domain-joined) server as described above may result in an inability to remotely administer the server.
Note: The security identifier Local account is not available in Server 2008 R2 and Server 2012 (non-R2) unless MSKB 2871997 has been installed.
Note #2: In all versions of Windows Server prior to Server 2008 R2, Remote Desktop Services was known as Terminal Services , so you should substitute the older term if comparing against an older OS.
Any account with the right to log on through Remote Desktop Services could be used to log on to the remote console of the computer. If this user right is not restricted to legitimate users who need to log on to the console of the computer, unauthorized users might download and run malicious software that elevates their privileges.
To establish the recommended configuration via GP, configure the following UI path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Deny log on through Remote Desktop Services
Impact:
If you assign the Deny log on through Remote Desktop Services user right to other groups, you could limit the abilities of users who are assigned to specific administrative roles in your environment. Accounts that have this user right will be unable to connect to the computer through either Remote Desktop Services or Remote Assistance. You should confirm that delegated tasks will not be negatively impacted.
All of the following tests or sub-groups must pass: | ||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.26_L1_Ensure_Deny_log_on_through_Remote_Desktop_Services_is_set_to_Guests_Local_account_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:35.555-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36867-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817226" definition_negate="false"> <cis:and negated="false" result="false"> <cis:evidence_test check="at least one" check_existence="at_least_one_exists" comment="Ensure 'sedenyremoteInteractivelogonright' is set to 'Guests, Local account'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817226" result="true" testref="oval:org.cisecurity.benchmarks:tst:8172261" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:8172261"> <cis:evidence_item itemref="1085"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_DENY_REMOTE_INTERACTIVE_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-546" dt="string" ev="S-1-5-32-546" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="at least one" check_existence="at_least_one_exists" comment="Ensure 'sedenyremoteInteractivelogonright' is set to 'Guests, Local account'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817226" result="false" testref="oval:org.cisecurity.benchmarks:tst:8172262" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:8172262"> <cis:evidence_item itemref="1085"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_DENY_REMOTE_INTERACTIVE_LOGON_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-546" dt="string" ev="S-1-5-113" name="trustee_sid" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817226"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36867-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.8 |
Label: | Disable Any Unassociated Accounts |
Description: | Disable any account that cannot be associated with a business process or business owner. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting allows users to change the Trusted for Delegation setting on a computer object in Active Directory. Abuse of this privilege could allow unauthorized users to impersonate other users on the network.
The recommended state for this setting is: No One .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
Misuse of the Enable computer and user accounts to be trusted for delegation user right could allow unauthorized users to impersonate other users on the network. An attacker could exploit this privilege to gain access to network resources and make it difficult to determine what has happened after a security incident.
To establish the recommended configuration via GP, configure the following UI path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Enable computer and user accounts to be trusted for delegation
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.28_L1_Ensure_Enable_computer_and_user_accounts_to_be_trusted_for_delegation_is_set_to_No_One_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:35.633-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36860-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817234" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="none_exist" comment="Ensure 'seenabledelegationprivilege' is set to 'No One' - MS" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817234" result="true" testref="oval:org.cisecurity.benchmarks:tst:817234" type="userright_test"> <cis:evidence_object> <cis:evidence_item itemref="1086"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="userright" value="SE_ENABLE_DELEGATION_NAME"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817234"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36860-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.8 |
Label: | Log and Alert on Changes to Administrative Group Membership |
Description: | Configure systems to issue a log entry and alert when an account is added to or removed from any group assigned administrative privileges. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting allows users to shut down Windows Vista-based and newer computers from remote locations on the network. Anyone who has been assigned this user right can cause a denial of service (DoS) condition, which would make the computer unavailable to service user requests. Therefore, it is recommended that only highly trusted administrators be assigned this user right.
The recommended state for this setting is: Administrators .
Any user who can shut down a computer could cause a DoS condition to occur. Therefore, this user right should be tightly restricted.
To establish the recommended configuration via GP, set the following UI path to Administrators :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Force shutdown from a remote system
Impact:
If you remove the Force shutdown from a remote system user right from the Server Operator group you could limit the abilities of users who are assigned to specific administrative roles in your environment. You should confirm that delegated activities will not be adversely affected.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.29_L1_Ensure_Force_shutdown_from_a_remote_system_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:35.696-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37877-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817243" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'seremoteshutdownprivilege' is set to 'Administrators'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817243" result="true" testref="oval:org.cisecurity.benchmarks:tst:817243" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817243"> <cis:evidence_item itemref="1087"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_REMOTE_SHUTDOWN_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817243"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37877-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.1 |
Label: | Maintain Inventory of Administrative Accounts |
Description: | Use automated tools to inventory all administrative accounts, including domain and local accounts, to ensure that only authorized individuals have elevated privileges. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting determines which users or processes can generate audit records in the Security log.
The recommended state for this setting is: LOCAL SERVICE, NETWORK SERVICE .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
Note #2: A Member Server that holds the Web Server (IIS) Role with Web Server Role Service will require a special exception to this recommendation, to allow IIS application pool(s) to be granted this user right.
Note #3: A Member Server that holds the Active Directory Federation Services Role will require a special exception to this recommendation, to allow the NT SERVICE\ADFSSrv and NT SERVICE\DRS services, as well as the associated Active Directory Federation Services service account, to be granted this user right.
An attacker could use this capability to create a large number of audited events, which would make it more difficult for a system administrator to locate any illicit activity. Also, if the event log is configured to overwrite events as needed, any evidence of unauthorized activities could be overwritten by a large number of unrelated events.
To establish the recommended configuration via GP, set the following UI path to LOCAL SERVICE, NETWORK SERVICE :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Generate security audits
Impact:
On most computers, this is the default configuration and there will be no negative impact. However, if you have installed the Web Server (IIS) Role with Web Services Role Service, you will need to allow the IIS application pool(s) to be granted this user right.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.30_L1_Ensure_Generate_security_audits_is_set_to_LOCAL_SERVICE_NETWORK_SERVICE" role="full" severity="unknown" time="2020-04-22T15:48:35.758-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37639-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817263" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'seauditprivilege' is set to 'LOCAL SERVICE, NETWORK SERVICE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817263" result="true" testref="oval:org.cisecurity.benchmarks:tst:817263" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817263"> <cis:evidence_item itemref="1088"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_AUDIT_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-20" dt="string" ev="S-1-5-(19|20)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1089"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_AUDIT_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-19" dt="string" ev="S-1-5-(19|20)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817263"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37639-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
The policy setting allows programs that run on behalf of a user to impersonate that user (or another specified account) so that they can act on behalf of the user. If this user right is required for this kind of impersonation, an unauthorized user will not be able to convince a client to connect—for example, by remote procedure call (RPC) or named pipes—to a service that they have created to impersonate that client, which could elevate the unauthorized user's permissions to administrative or system levels.
Services that are started by the Service Control Manager have the built-in Service group added by default to their access tokens. COM servers that are started by the COM infrastructure and configured to run under a specific account also have the Service group added to their access tokens. As a result, these processes are assigned this user right when they are started.
Also, a user can impersonate an access token if any of the following conditions exist:
An attacker with the Impersonate a client after authentication user right could create a service, trick a client to make them connect to the service, and then impersonate that client to elevate the attacker's level of access to that of the client.
The recommended state for this setting is: Administrators, LOCAL SERVICE, NETWORK SERVICE, SERVICE and (when the Web Server (IIS) Role with Web Services Role Service is installed) IIS_IUSRS .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
Note #2: A Member Server with Microsoft SQL Server and its optional "Integration Services" component installed will require a special exception to this recommendation for additional SQL-generated entries to be granted this user right.
An attacker with the Impersonate a client after authentication user right could create a service, trick a client to make them connect to the service, and then impersonate that client to elevate the attacker's level of access to that of the client.
To establish the recommended configuration via GP, configure the following UI path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Impersonate a client after authentication
Impact:
In most cases this configuration will have no impact. If you have installed the Web Server (IIS) Role with Web Services Role Service, you will need to also assign the user right to IIS_IUSRS .
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.32_L1_Ensure_Impersonate_a_client_after_authentication_is_set_to_Administrators_LOCAL_SERVICE_NETWORK_SERVICE_SERVICE_and_when_the_Web_Server_IIS_Role_with_Web_Services_Role_Service_is_installed_IIS_IUSRS_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:35.836-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37106-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817274" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'seimpersonateprivilege' is set to 'Administrators, LOCAL SERVICE, NETWORK SERVICE, SERVICE, IIS_IUSRS' -MS" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817274" result="true" testref="oval:org.cisecurity.benchmarks:tst:817274" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817274"> <cis:evidence_item itemref="1090"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_IMPERSONATE_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-6" dt="string" ev="S-1-5-(32-544|19|20|6|32-568)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1091"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_IMPERSONATE_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-(32-544|19|20|6|32-568)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1092"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_IMPERSONATE_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-20" dt="string" ev="S-1-5-(32-544|19|20|6|32-568)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1093"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_IMPERSONATE_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-19" dt="string" ev="S-1-5-(32-544|19|20|6|32-568)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817274"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37106-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting determines whether users can increase the base priority class of a process. (It is not a privileged operation to increase relative priority within a priority class.) This user right is not required by administrative tools that are supplied with the operating system but might be required by software development tools.
The recommended state for this setting is: Administrators, Window Manager\Window Manager Group .
A user who is assigned this user right could increase the scheduling priority of a process to Real-Time, which would leave little processing time for all other processes and could lead to a DoS condition.
To establish the recommended configuration via GP, set the following UI path to Administrators, Window Manager\Window Manager Group :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Increase scheduling priority
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.33_L1_Ensure_Increase_scheduling_priority_is_set_to_Administrators_Window_ManagerWindow_Manager_Group" role="full" severity="unknown" time="2020-04-22T15:48:35.914-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38326-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817284" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'seincreasebasepriorityprivilege' is set to 'Administrators, Window Manager\Window Manager Group'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817284" result="true" testref="oval:org.cisecurity.benchmarks:tst:817284" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817284"> <cis:evidence_item itemref="1094"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_INC_BASE_PRIORITY_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-90-0" dt="string" ev="S-1-5-(32-544|90-0)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1095"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_INC_BASE_PRIORITY_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-(32-544|90-0)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817284"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38326-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.1 |
Label: | Maintain Inventory of Administrative Accounts |
Description: | Use automated tools to inventory all administrative accounts, including domain and local accounts, to ensure that only authorized individuals have elevated privileges. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting allows users to dynamically load a new device driver on a system. An attacker could potentially use this capability to install malicious code that appears to be a device driver. This user right is required for users to add local printers or printer drivers in Windows Vista.
The recommended state for this setting is: Administrators .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
Device drivers run as highly privileged code. A user who has the Load and unload device drivers user right could unintentionally install malicious code that masquerades as a device driver. Administrators should exercise greater care and install only drivers with verified digital signatures.
To establish the recommended configuration via GP, set the following UI path to Administrators :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Load and unload device drivers
Impact:
If you remove the Load and unload device drivers user right from the Print Operators group or other accounts you could limit the abilities of users who are assigned to specific administrative roles in your environment. You should ensure that delegated tasks will not be negatively affected.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.34_L1_Ensure_Load_and_unload_device_drivers_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:35.977-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36318-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817295" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'seloaddriverprivilege' is set to 'Administrators'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817295" result="true" testref="oval:org.cisecurity.benchmarks:tst:817295" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817295"> <cis:evidence_item itemref="1096"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_LOAD_DRIVER_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817295"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36318-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.1 |
Label: | Maintain Inventory of Administrative Accounts |
Description: | Use automated tools to inventory all administrative accounts, including domain and local accounts, to ensure that only authorized individuals have elevated privileges. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting allows a process to keep data in physical memory, which prevents the system from paging the data to virtual memory on disk. If this user right is assigned, significant degradation of system performance can occur.
The recommended state for this setting is: No One .
Note: A Member Server with Microsoft SQL Server installed will require a special exception to this recommendation for additional SQL-generated entries to be granted this user right.
Users with the Lock pages in memory user right could assign physical memory to several processes, which could leave little or no RAM for other processes and result in a DoS condition.
To establish the recommended configuration via GP, set the following UI path to No One :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Lock pages in memory
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.35_L1_Ensure_Lock_pages_in_memory_is_set_to_No_One" role="full" severity="unknown" time="2020-04-22T15:48:36.039-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36495-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817301" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="none_exist" comment="Ensure 'selockmemoryprivilege' is set to 'No One'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817301" result="true" testref="oval:org.cisecurity.benchmarks:tst:817301" type="userright_test"> <cis:evidence_object> <cis:evidence_item itemref="1097"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="userright" value="SE_LOCK_MEMORY_NAME"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817301"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36495-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.8 |
Label: | Log and Alert on Changes to Administrative Group Membership |
Description: | Configure systems to issue a log entry and alert when an account is added to or removed from any group assigned administrative privileges. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines which users can change the auditing options for files and directories and clear the Security log.
For environments running Microsoft Exchange Server, the Exchange Servers group must possess this privilege on Domain Controllers to properly function. Given this, DCs that grant the Exchange Servers group this privilege also conform to this benchmark. If the environment does not use Microsoft Exchange Server, then this privilege should be limited to only Administrators on DCs.
The recommended state for this setting is: Administrators .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
The ability to manage the Security event log is a powerful user right and it should be closely guarded. Anyone with this user right can clear the Security log to erase important evidence of unauthorized activity.
To establish the recommended configuration via GP, configure the following UI path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Manage auditing and security log
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.38_L1_Ensure_Manage_auditing_and_security_log_is_set_to_Administrators_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:36.102-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-35906-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817326" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'sesecurityprivilege' is set to 'Administrators' - MS" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817326" result="true" testref="oval:org.cisecurity.benchmarks:tst:817326" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817326"> <cis:evidence_item itemref="1098"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_SECURITY_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817326"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-35906-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.1 |
Label: | Maintain Inventory of Administrative Accounts |
Description: | Use automated tools to inventory all administrative accounts, including domain and local accounts, to ensure that only authorized individuals have elevated privileges. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This privilege determines which user accounts can modify the integrity label of objects, such as files, registry keys, or processes owned by other users. Processes running under a user account can modify the label of an object owned by that user to a lower level without this privilege.
The recommended state for this setting is: No One .
By modifying the integrity label of an object owned by another user a malicious user may cause them to execute code at a higher level of privilege than intended.
To establish the recommended configuration via GP, set the following UI path to No One :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Modify an object label
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.39_L1_Ensure_Modify_an_object_label_is_set_to_No_One" role="full" severity="unknown" time="2020-04-22T15:48:36.164-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36054-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817342" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="none_exist" comment="Ensure 'serelabelprivilege' is set to 'No One'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817342" result="true" testref="oval:org.cisecurity.benchmarks:tst:817342" type="userright_test"> <cis:evidence_object> <cis:evidence_item itemref="1099"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="userright" value="SE_RELABEL_NAME"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817342"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36054-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.8 |
Label: | Log and Alert on Changes to Administrative Group Membership |
Description: | Configure systems to issue a log entry and alert when an account is added to or removed from any group assigned administrative privileges. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting allows users to configure the system-wide environment variables that affect hardware configuration. This information is typically stored in the Last Known Good Configuration. Modification of these values and could lead to a hardware failure that would result in a denial of service condition.
The recommended state for this setting is: Administrators .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
Anyone who is assigned the Modify firmware environment values user right could configure the settings of a hardware component to cause it to fail, which could lead to data corruption or a DoS condition.
To establish the recommended configuration via GP, set the following UI path to Administrators :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Modify firmware environment values
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.40_L1_Ensure_Modify_firmware_environment_values_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:36.305-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38113-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817352" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'sesystemenvironmentprivilege' is set to 'Administrators'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817352" result="true" testref="oval:org.cisecurity.benchmarks:tst:817352" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817352"> <cis:evidence_item itemref="1102"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_SYSTEM_ENVIRONMENT_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817352"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38113-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting allows users to manage the system's volume or disk configuration, which could allow a user to delete a volume and cause data loss as well as a denial-of-service condition.
The recommended state for this setting is: Administrators .
A user who is assigned the Perform volume maintenance tasks user right could delete a volume, which could result in the loss of data or a DoS condition.
To establish the recommended configuration via GP, set the following UI path to Administrators :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Perform volume maintenance tasks
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.41_L1_Ensure_Perform_volume_maintenance_tasks_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:36.368-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36143-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817358" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'semanagevolumeprivilege' is set to 'Administrators'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817358" result="true" testref="oval:org.cisecurity.benchmarks:tst:817358" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817358"> <cis:evidence_item itemref="1103"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_MANAGE_VOLUME_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817358"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36143-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting determines which users can use tools to monitor the performance of non-system processes. Typically, you do not need to configure this user right to use the Microsoft Management Console (MMC) Performance snap-in. However, you do need this user right if System Monitor is configured to collect data using Windows Management Instrumentation (WMI). Restricting the Profile single process user right prevents intruders from gaining additional information that could be used to mount an attack on the system.
The recommended state for this setting is: Administrators .
The Profile single process user right presents a moderate vulnerability. An attacker with this user right could monitor a computer's performance to help identify critical processes that they might wish to attack directly. The attacker may also be able to determine what processes run on the computer so that they could identify countermeasures that they may need to avoid, such as antivirus software, an intrusion-detection system, or which other users are logged on to a computer.
To establish the recommended configuration via GP, set the following UI path to Administrators :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Profile single process
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.42_L1_Ensure_Profile_single_process_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:36.446-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37131-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817366" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'seprofilesingleprocessprivilege' is set to 'Administrators'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817366" result="true" testref="oval:org.cisecurity.benchmarks:tst:817366" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817366"> <cis:evidence_item itemref="1104"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_PROF_SINGLE_PROCESS_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817366"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37131-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting allows users to use tools to view the performance of different system processes, which could be abused to allow attackers to determine a system's active processes and provide insight into the potential attack surface of the computer.
The recommended state for this setting is: Administrators, NT SERVICE\WdiServiceHost .
The Profile system performance user right poses a moderate vulnerability. Attackers with this user right could monitor a computer's performance to help identify critical processes that they might wish to attack directly. Attackers may also be able to determine what processes are active on the computer so that they could identify countermeasures that they may need to avoid, such as antivirus software or an intrusion detection system.
To establish the recommended configuration via GP, set the following UI path to Administrators, NT SERVICE\WdiServiceHost :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Profile system performance
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.43_L1_Ensure_Profile_system_performance_is_set_to_Administrators_NT_SERVICEWdiServiceHost" role="full" severity="unknown" time="2020-04-22T15:48:36.508-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36052-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817376" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'sesystemprofileprivilege' is set to 'Administrators, NT SERVICE\WdiServiceHost'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817376" result="true" testref="oval:org.cisecurity.benchmarks:tst:817376" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817376"> <cis:evidence_item itemref="1105"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_SYSTEM_PROFILE_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-80-3139157870-2983391045-3678747466-658725712-1809340420" dt="string" ev="S-1-5-(32-544|80(-\d{9,10}){1,5})" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1106"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_SYSTEM_PROFILE_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-(32-544|80(-\d{9,10}){1,5})" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817376"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36052-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting allows one process or service to start another service or process with a different security access token, which can be used to modify the security access token of that sub-process and result in the escalation of privileges.
The recommended state for this setting is: LOCAL SERVICE, NETWORK SERVICE .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
Note #2: A Member Server that holds the Web Server (IIS) Role with Web Server Role Service will require a special exception to this recommendation, to allow IIS application pool(s) to be granted this user right.
Note #3: A Member Server with Microsoft SQL Server installed will require a special exception to this recommendation for additional SQL-generated entries to be granted this user right.
Users with the Replace a process level token privilege are able to start processes as other users whose credentials they know. They could use this method to hide their unauthorized actions on the computer. (On Windows 2000-based computers, use of the Replace a process level token user right also requires the user to have the Adjust memory quotas for a process user right that is discussed earlier in this section.)
To establish the recommended configuration via GP, set the following UI path to LOCAL SERVICE, NETWORK SERVICE :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Replace a process level token
Impact:
On most computers, this is the default configuration and there will be no negative impact. However, if you have installed the Web Server (IIS) Role with Web Services Role Service, you will need to allow the IIS application pool(s) to be granted this User Right Assignment.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.44_L1_Ensure_Replace_a_process_level_token_is_set_to_LOCAL_SERVICE_NETWORK_SERVICE" role="full" severity="unknown" time="2020-04-22T15:48:36.571-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37430-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817395" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'seassignprimarytokenprivilege' is set to 'LOCAL SERVICE, NETWORK SERVICE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817395" result="true" testref="oval:org.cisecurity.benchmarks:tst:817395" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817395"> <cis:evidence_item itemref="1107"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_ASSIGNPRIMARYTOKEN_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-20" dt="string" ev="S-1-5-(19|20)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> <cis:evidence_item itemref="1108"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_ASSIGNPRIMARYTOKEN_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-19" dt="string" ev="S-1-5-(19|20)" name="trustee_sid" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817395"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37430-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines which users can bypass file, directory, registry, and other persistent object permissions when restoring backed up files and directories on computers that run Windows Vista (or newer) in your environment. This user right also determines which users can set valid security principals as object owners; it is similar to the Back up files and directories user right.
The recommended state for this setting is: Administrators .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
An attacker with the Restore files and directories user right could restore sensitive data to a computer and overwrite data that is more recent, which could lead to loss of important data, data corruption, or a denial of service. Attackers could overwrite executable files that are used by legitimate administrators or system services with versions that include malicious software to grant themselves elevated privileges, compromise data, or install backdoors for continued access to the computer.
Note: Even if the following countermeasure is configured, an attacker could still restore data to a computer in a domain that is controlled by the attacker. Therefore, it is critical that organizations carefully protect the media that is used to back up data.
To establish the recommended configuration via GP, set the following UI path to Administrators :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Restore files and directories
Impact:
If you remove the Restore files and directories user right from the Backup Operators group and other accounts you could make it impossible for users who have been delegated specific tasks to perform those tasks. You should verify that this change won't negatively affect the ability of your organization's personnel to do their jobs.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.45_L1_Ensure_Restore_files_and_directories_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:36.649-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37613-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817407" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'serestoreprivilege' is set to 'Administrators'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817407" result="true" testref="oval:org.cisecurity.benchmarks:tst:817407" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817407"> <cis:evidence_item itemref="1109"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_RESTORE_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817407"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37613-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting determines which users who are logged on locally to the computers in your environment can shut down the operating system with the Shut Down command. Misuse of this user right can result in a denial of service condition.
The recommended state for this setting is: Administrators .
The ability to shut down Domain Controllers and Member Servers should be limited to a very small number of trusted Administrators. Although the Shut down the system user right requires the ability to log on to the server, you should be very careful about which accounts and groups you allow to shut down a Domain Controller or Member Server.
When a Domain Controller is shut down, it is no longer available to process logons, serve Group Policy, and answer Lightweight Directory Access Protocol (LDAP) queries. If you shut down Domain Controllers that possess Flexible Single Master Operations (FSMO) roles, you can disable key domain functionality, such as processing logons for new passwords — one of the functions of the Primary Domain Controller (PDC) Emulator role.
To establish the recommended configuration via GP, set the following UI path to Administrators :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Shut down the system
Impact:
The impact of removing these default groups from the Shut down the system user right could limit the delegated abilities of assigned roles in your environment. You should confirm that delegated activities will not be adversely affected.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.46_L1_Ensure_Shut_down_the_system_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:36.711-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38328-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817417" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'seshutdownprivilege' is set to 'Administrators'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817417" result="true" testref="oval:org.cisecurity.benchmarks:tst:817417" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817417"> <cis:evidence_item itemref="1110"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_SHUTDOWN_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817417"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38328-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting allows users to take ownership of files, folders, registry keys, processes, or threads. This user right bypasses any permissions that are in place to protect objects to give ownership to the specified user.
The recommended state for this setting is: Administrators .
Note: This user right is considered a "sensitive privilege" for the purposes of auditing.
Any users with the Take ownership of files or other objects user right can take control of any object, regardless of the permissions on that object, and then make any changes they wish to that object. Such changes could result in exposure of data, corruption of data, or a DoS condition.
To establish the recommended configuration via GP, set the following UI path to Administrators :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Take ownership of files or other objects
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.2.48_L1_Ensure_Take_ownership_of_files_or_other_objects_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:36.774-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38325-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817441" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="'setakeownershipprivilege' is set to 'Administrators'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817441" result="true" testref="oval:org.cisecurity.benchmarks:tst:817441" type="userright_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817441"> <cis:evidence_item itemref="1111"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="userright" value="SE_TAKE_OWNERSHIP_NAME"/> </cis:evidence_item_pk> <cis:evidence_field cv="S-1-5-32-544" dt="string" ev="S-1-5-32-544" name="trustee_sid" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817441"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38325-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This section contains recommendations for security options.
This section contains recommendations related to default accounts.
This policy setting enables or disables the Administrator account during normal operation. When a computer is booted into safe mode, the Administrator account is always enabled, regardless of how this setting is configured. Note that this setting will have no impact when applied to the Domain Controllers organizational unit via group policy because Domain Controllers have no local account database. It can be configured at the domain level via group policy, similar to account lockout and password policy settings.
The recommended state for this setting is: Disabled .
In some organizations, it can be a daunting management challenge to maintain a regular schedule for periodic password changes for local accounts. Therefore, you may want to disable the built-in Administrator account instead of relying on regular password changes to protect it from attack. Another reason to disable this built-in account is that it cannot be locked out no matter how many failed logons it accrues, which makes it a prime target for brute force attacks that attempt to guess passwords. Also, this account has a well-known security identifier (SID) and there are third-party tools that allow authentication by using the SID rather than the account name. This capability means that even if you rename the Administrator account, an attacker could launch a brute force attack by using the SID to log on.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Accounts: Administrator account status
Impact:
Maintenance issues can arise under certain circumstances if you disable the Administrator account. For example, if the secure channel between a member computer and the Domain Controller fails in a domain environment for any reason and there is no other local Administrator account, you must restart in safe mode to fix the problem that broke the secure channel.
If the current Administrator password does not meet the password requirements, you will not be able to re-enable the Administrator account after it is disabled. If this situation occurs, another member of the Administrators group must set the password on the Administrator account with the Local Users and Groups tool.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_L1_Ensure_Accounts_Administrator_account_status_is_set_to_Disabled_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:37.180-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37953-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:37.180-05:00" start-time="2020-04-22T15:48:37.071-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '^S\-1\-5\-21\-\d+\-\d+\-\d+\-500$' is 'Equals' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817155" result="false" testref="oval:org.cisecurity.benchmarks:tst:817155" type="user_sid55_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817155"> <cis:evidence_item itemref="1121"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="user_sid" value="S-1-5-21-3050897948-969533551-3432263440-500"/> </cis:evidence_item_pk> <cis:evidence_field cv="true" dt="boolean" ev="0" name="enabled" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817155" value-id="xccdf_org.cisecurity.benchmarks_value_817155_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817155"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37953-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.8 |
Label: | Disable Any Unassociated Accounts |
Description: | Disable any account that cannot be associated with a business process or business owner. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting prevents users from adding new Microsoft accounts on this computer.
The recommended state for this setting is: Users can't add or log on with Microsoft accounts .
Organizations that want to effectively implement identity management policies and maintain firm control of what accounts are used to log onto their computers will probably want to block Microsoft accounts. Organizations may also need to block Microsoft accounts in order to meet the requirements of compliance standards that apply to their information systems.
To establish the recommended configuration via GP, set the following UI path to Users can't add or log on with Microsoft accounts :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Accounts: Block Microsoft accounts
Impact:
Users will not be able to log onto the computer with their Microsoft account.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.2_L1_Ensure_Accounts_Block_Microsoft_accounts_is_set_to_Users_cant_add_or_log_on_with_Microsoft_accounts" role="full" severity="unknown" time="2020-04-22T15:48:37.243-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36147-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:37.243-05:00" start-time="2020-04-22T15:48:37.180-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoConnectedUser' is 'Windows: Registry Value' to '3'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817159" result="true" testref="oval:org.cisecurity.benchmarks:tst:817159" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817159"> <cis:evidence_item itemref="1122"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="NoConnectedUser"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="3" dt="int" ev="3" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171591" value-id="xccdf_org.cisecurity.benchmarks_value_817159_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171592" value-id="xccdf_org.cisecurity.benchmarks_value_817159_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817159"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36147-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.8 |
Label: | Disable Any Unassociated Accounts |
Description: | Disable any account that cannot be associated with a business process or business owner. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines whether the Guest account is enabled or disabled. The Guest account allows unauthenticated network users to gain access to the system.
The recommended state for this setting is: Disabled .
Note: This setting will have no impact when applied to the Domain Controllers organizational unit via group policy because Domain Controllers have no local account database. It can be configured at the domain level via group policy, similar to account lockout and password policy settings.
The default Guest account allows unauthenticated network users to log on as Guest with no password. These unauthorized users could access any resources that are accessible to the Guest account over the network. This capability means that any network shares with permissions that allow access to the Guest account, the Guests group, or the Everyone group will be accessible over the network, which could lead to the exposure or corruption of data.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Accounts: Guest account status
Impact:
All network users will need to authenticate before they can access shared resources. If you disable the Guest account and the Network Access: Sharing and Security Model option is set to Guest Only, network logons, such as those performed by the Microsoft Network Server (SMB Service), will fail. This policy setting should have little impact on most organizations because it is the default setting in Microsoft Windows 2000, Windows XP, and Windows Server™ 2003.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.3_L1_Ensure_Accounts_Guest_account_status_is_set_to_Disabled_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:37.336-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37432-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:37.336-05:00" start-time="2020-04-22T15:48:37.243-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '^S\-1\-5\-21\-\d+\-\d+\-\d+\-501$' is 'Equals' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817179" result="true" testref="oval:org.cisecurity.benchmarks:tst:817179" type="user_sid55_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817179"> <cis:evidence_item itemref="1123"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="user_sid" value="S-1-5-21-3050897948-969533551-3432263440-501"/> </cis:evidence_item_pk> <cis:evidence_field cv="false" dt="boolean" ev="0" name="enabled" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817179" value-id="xccdf_org.cisecurity.benchmarks_value_817179_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817179"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37432-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.8 |
Label: | Disable Any Unassociated Accounts |
Description: | Disable any account that cannot be associated with a business process or business owner. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.1 |
Label: | Perform Regular Account Reviews |
Description: | Review all system accounts and disable any account that cannot be associated with a business process and owner. |
This policy setting determines whether local accounts that are not password protected can be used to log on from locations other than the physical computer console. If you enable this policy setting, local accounts that have blank passwords will not be able to log on to the network from remote client computers. Such accounts will only be able to log on at the keyboard of the computer.
The recommended state for this setting is: Enabled .
Blank passwords are a serious threat to computer security and should be forbidden through both organizational policy and suitable technical measures. In fact, the default settings for Active Directory domains require complex passwords of at least seven characters. However, if users with the ability to create new accounts bypass your domain-based password policies, they could create accounts with blank passwords. For example, a user could build a stand-alone computer, create one or more accounts with blank passwords, and then join the computer to the domain. The local accounts with blank passwords would still function. Anyone who knows the name of one of these unprotected accounts could then use it to log on.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Accounts: Limit local account use of blank passwords to console logon only
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.4_L1_Ensure_Accounts_Limit_local_account_use_of_blank_passwords_to_console_logon_only_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:37.399-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37615-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:37.399-05:00" start-time="2020-04-22T15:48:37.336-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LimitBlankPasswordUse' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817164" result="true" testref="oval:org.cisecurity.benchmarks:tst:817164" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817164"> <cis:evidence_item itemref="1124"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa"/> <cis:evidence_item_pk_field name="name" value="LimitBlankPasswordUse"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171641" value-id="xccdf_org.cisecurity.benchmarks_value_817164_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171642" value-id="xccdf_org.cisecurity.benchmarks_value_817164_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817164"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37615-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
The built-in local administrator account is a well-known account name that attackers will target. It is recommended to choose another name for this account, and to avoid names that denote administrative or elevated access accounts. Be sure to also change the default description for the local administrator (through the Computer Management console). On Domain Controllers, since they do not have their own local accounts, this rule refers to the built-in Administrator account that was established when the domain was first created.
The Administrator account exists on all computers that run the Windows 2000 or newer operating systems. If you rename this account, it is slightly more difficult for unauthorized persons to guess this privileged user name and password combination.
The built-in Administrator account cannot be locked out, regardless of how many times an attacker might use a bad password. This capability makes the Administrator account a popular target for brute force attacks that attempt to guess passwords. The value of this countermeasure is lessened because this account has a well-known SID, and there are third-party tools that allow authentication by using the SID rather than the account name. Therefore, even if you rename the Administrator account, an attacker could launch a brute force attack by using the SID to log on.
To establish the recommended configuration via GP, configure the following UI path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Accounts: Rename administrator account
Impact:
You will have to inform users who are authorized to use this account of the new account name. (The guidance for this setting assumes that the Administrator account was not disabled, which was recommended earlier in this chapter.)
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.5_L1_Configure_Accounts_Rename_administrator_account" role="full" severity="unknown" time="2020-04-22T15:48:37.774-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38233-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817168" definition_negate="false"> <cis:and negated="false" result="false"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '^S\-1\-5\-21\-\d+\-\d+\-\d+\-500$' is 'case insensitive not equal' 'Administrator'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817168" result="false" testref="oval:org.cisecurity.benchmarks:tst:817168" type="sid_sid_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817168"> <cis:evidence_item itemref="1128"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="trustee_sid" value="S-1-5-21-3050897948-969533551-3432263440-500"/> </cis:evidence_item_pk> <cis:evidence_field cv="Administrator" dt="string" ev="Administrator" name="trustee_name" op="not equal" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817168" value-id="xccdf_org.cisecurity.benchmarks_value_817168_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817168"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38233-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.8 |
Label: | Disable Any Unassociated Accounts |
Description: | Disable any account that cannot be associated with a business process or business owner. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
The built-in local guest account is another well-known name to attackers. It is recommended to rename this account to something that does not indicate its purpose. Even if you disable this account, which is recommended, ensure that you rename it for added security. On Domain Controllers, since they do not have their own local accounts, this rule refers to the built-in Guest account that was established when the domain was first created.
The Guest account exists on all computers that run the Windows 2000 or newer operating systems. If you rename this account, it is slightly more difficult for unauthorized persons to guess this privileged user name and password combination.
To establish the recommended configuration via GP, configure the following UI path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Accounts: Rename guest account
Impact:
There should be little impact, because the Guest account is disabled by default.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1.6_L1_Configure_Accounts_Rename_guest_account" role="full" severity="unknown" time="2020-04-22T15:48:37.774-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38027-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817174" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '^S\-1\-5\-21\-\d+\-\d+\-\d+\-501$' is 'case insensitive not equal' 'Guest'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817174" result="true" testref="oval:org.cisecurity.benchmarks:tst:817174" type="sid_sid_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817174"> <cis:evidence_item itemref="1131"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="trustee_sid" value="S-1-5-21-3050897948-969533551-3432263440-501"/> </cis:evidence_item_pk> <cis:evidence_field cv="CISGUEST" dt="string" ev="Guest" name="trustee_name" op="not equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817174" value-id="xccdf_org.cisecurity.benchmarks_value_817174_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817174"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38027-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.8 |
Label: | Disable Any Unassociated Accounts |
Description: | Disable any account that cannot be associated with a business process or business owner. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This section contains recommendations related to auditing controls.
This policy setting allows administrators to enable the more precise auditing capabilities present in Windows Vista.
The Audit Policy settings available in Windows Server 2003 Active Directory do not yet contain settings for managing the new auditing subcategories. To properly apply the auditing policies prescribed in this baseline, the Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings setting needs to be configured to Enabled.
The recommended state for this setting is: Enabled .
Important: Be very cautious about audit settings that can generate a large volume of traffic. For example, if you enable either success or failure auditing for all of the Privilege Use subcategories, the high volume of audit events generated can make it difficult to find other types of entries in the Security log. Such a configuration could also have a significant impact on system performance.
Prior to the introduction of auditing subcategories in Windows Vista, it was difficult to track events at a per-system or per-user level. The larger event categories created too many events and the key information that needed to be audited was difficult to find.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_L1_Ensure_Audit_Force_audit_policy_subcategory_settings_Windows_Vista_or_later_to_override_audit_policy_category_settings_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:40.071-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37850-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.071-05:00" start-time="2020-04-22T15:48:40.008-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'SCENoApplyLegacyAuditPolicy' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817177" result="true" testref="oval:org.cisecurity.benchmarks:tst:817177" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817177"> <cis:evidence_item itemref="1231"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa"/> <cis:evidence_item_pk_field name="name" value="SCENoApplyLegacyAuditPolicy"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171771" value-id="xccdf_org.cisecurity.benchmarks_value_817177_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171772" value-id="xccdf_org.cisecurity.benchmarks_value_817177_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817177"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37850-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Activate audit logging |
Description: | Ensure that local logging has been enabled on all systems and networking devices. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Ensure Audit Log Settings Support Appropriate Log Entry Formating |
Description: | Validate audit log settings for each hardware device and the software installed on it, ensuring that logs include a date, timestamp, source addresses, destination addresses, and various other useful elements of each packet and/or transaction. Systems should record logs in a standardized format such as syslog entries or those outlined by the Common Event Expression initiative. If systems cannot generate logs in a standardized format, log normalization tools can be deployed to convert logs into such a format. |
This policy setting determines whether the system shuts down if it is unable to log Security events. It is a requirement for Trusted Computer System Evaluation Criteria (TCSEC)-C2 and Common Criteria certification to prevent auditable events from occurring if the audit system is unable to log them. Microsoft has chosen to meet this requirement by halting the system and displaying a stop message if the auditing system experiences a failure. When this policy setting is enabled, the system will be shut down if a security audit cannot be logged for any reason.
If the Audit: Shut down system immediately if unable to log security audits setting is enabled, unplanned system failures can occur. The administrative burden can be significant, especially if you also configure the Retention method for the Security log to Do not overwrite events (clear log manually). This configuration causes a repudiation threat (a backup operator could deny that they backed up or restored data) to become a denial of service (DoS) vulnerability, because a server could be forced to shut down if it is overwhelmed with logon events and other security events that are written to the Security log. Also, because the shutdown is not graceful, it is possible that irreparable damage to the operating system, applications, or data could result. Although the NTFS file system guarantees its integrity when an ungraceful computer shutdown occurs, it cannot guarantee that every data file for every application will still be in a usable form when the computer restarts.
The recommended state for this setting is: Disabled .
If the computer is unable to record events to the Security log, critical evidence or important troubleshooting information may not be available for review after a security incident. Also, an attacker could potentially generate a large volume of Security log events to purposely force a computer shutdown.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Audit: Shut down system immediately if unable to log security audits
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_L1_Ensure_Audit_Shut_down_system_immediately_if_unable_to_log_security_audits_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:40.149-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-35907-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.149-05:00" start-time="2020-04-22T15:48:40.071-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'CrashOnAuditFail' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817193" result="true" testref="oval:org.cisecurity.benchmarks:tst:817193" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817193"> <cis:evidence_item itemref="1232"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\LSA"/> <cis:evidence_item_pk_field name="name" value="CrashOnAuditFail"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171931" value-id="xccdf_org.cisecurity.benchmarks_value_817193_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171932" value-id="xccdf_org.cisecurity.benchmarks_value_817193_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817193"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-35907-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Activate audit logging |
Description: | Ensure that local logging has been enabled on all systems and networking devices. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section contains recommendations related to managing devices.
This policy setting determines who is allowed to format and eject removable NTFS media. You can use this policy setting to prevent unauthorized users from removing data on one computer to access it on another computer on which they have local administrator privileges.
The recommended state for this setting is: Administrators .
Users may be able to move data on removable disks to a different computer where they have administrative privileges. The user could then take ownership of any file, grant themselves full control, and view or modify any file. The fact that most removable storage devices will eject media by pressing a mechanical button diminishes the advantage of this policy setting.
To establish the recommended configuration via GP, set the following UI path to Administrators :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Devices: Allowed to format and eject removable media
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4.1_L1_Ensure_Devices_Allowed_to_format_and_eject_removable_media_is_set_to_Administrators" role="full" severity="unknown" time="2020-04-22T15:48:40.211-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/13/subcontrol/7" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37701-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.211-05:00" start-time="2020-04-22T15:48:40.149-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllocateDASD' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817161" result="true" testref="oval:org.cisecurity.benchmarks:tst:817161" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817161"> <cis:evidence_item itemref="1233"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows NT\CurrentVersion\Winlogon"/> <cis:evidence_item_pk_field name="name" value="AllocateDASD"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="string" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171611" value-id="xccdf_org.cisecurity.benchmarks_value_817161_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171612" value-id="xccdf_org.cisecurity.benchmarks_value_817161_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817161"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37701-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Configure Anti-Malware Scanning of Removable Devices |
Description: | Configure devices so that they automatically conduct an anti-malware scan of removable media when inserted or connected. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
Subcontrol: | 13.7 |
Label: | Manage USB Devices |
Description: | If USB storage devices are required, enterprise software should be used that can configure systems to allow the use of specific devices. An inventory of such devices should be maintained. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
For a computer to print to a shared printer, the driver for that shared printer must be installed on the local computer. This security setting determines who is allowed to install a printer driver as part of connecting to a shared printer.
The recommended state for this setting is: Enabled .
Note: This setting does not affect the ability to add a local printer. This setting does not affect Administrators.
It may be appropriate in some organizations to allow users to install printer drivers on their own workstations. However, you should allow only Administrators, not users, to do so on servers, because printer driver installation on a server may unintentionally cause the computer to become less stable. A malicious user could install inappropriate printer drivers in a deliberate attempt to damage the computer, or a user might accidentally install malicious software that masquerades as a printer driver. It is feasible for an attacker to disguise a Trojan horse program as a printer driver. The program may appear to users as if they must use it to print, but such a program could unleash malicious code on your computer network.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Devices: Prevent users from installing printer drivers
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4.2_L1_Ensure_Devices_Prevent_users_from_installing_printer_drivers_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:40.274-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37942-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.274-05:00" start-time="2020-04-22T15:48:40.211-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AddPrinterDrivers' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817166" result="true" testref="oval:org.cisecurity.benchmarks:tst:817166" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817166"> <cis:evidence_item itemref="1234"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers"/> <cis:evidence_item_pk_field name="name" value="AddPrinterDrivers"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171661" value-id="xccdf_org.cisecurity.benchmarks_value_817166_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171662" value-id="xccdf_org.cisecurity.benchmarks_value_817166_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817166"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37942-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This section contains recommendations related to Domain Controllers.
This section contains recommendations related to domain membership.
This policy setting determines whether all secure channel traffic that is initiated by the domain member must be signed or encrypted.
The recommended state for this setting is: Enabled .
When a computer joins a domain, a computer account is created. After it joins the domain, the computer uses the password for that account to create a secure channel with the Domain Controller for its domain every time that it restarts. Requests that are sent on the secure channel are authenticated—and sensitive information such as passwords are encrypted—but the channel is not integrity-checked, and not all information is encrypted.
Digital encryption and signing of the secure channel is a good idea where it is supported. The secure channel protects domain credentials as they are sent to the Domain Controller.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Domain member: Digitally encrypt or sign secure channel data (always)
Impact:
None - this is the default behavior. However, only Windows NT 4.0 with Service Pack 6a (SP6a) and subsequent versions of the Windows operating system support digital encryption and signing of the secure channel. Windows 98 Second Edition clients do not support it unless they have Dsclient installed. Therefore, you cannot enable the Domain member: Digitally encrypt or sign secure channel data (always) setting on Domain Controllers that support Windows 98 clients as members of the domain. Potential impacts can include the following:
You can enable this policy setting after you eliminate all Windows 9x clients from the domain and upgrade all Windows NT 4.0 servers and Domain Controllers from trusted/trusting domains to Windows NT 4.0 with SP6a.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.1_L1_Ensure_Domain_member_Digitally_encrypt_or_sign_secure_channel_data_always_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:40.352-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/13/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36142-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.352-05:00" start-time="2020-04-22T15:48:40.274-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'RequireSignOrSeal' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817183" result="true" testref="oval:org.cisecurity.benchmarks:tst:817183" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817183"> <cis:evidence_item itemref="1235"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\Netlogon\Parameters"/> <cis:evidence_item_pk_field name="name" value="RequireSignOrSeal"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171831" value-id="xccdf_org.cisecurity.benchmarks_value_817183_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171832" value-id="xccdf_org.cisecurity.benchmarks_value_817183_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817183"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36142-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
Subcontrol: | 13.3 |
Label: | Monitor and Block Unauthorized Network Traffic |
Description: | Deploy an automated tool on network perimeters that monitors for unauthorized transfer of sensitive information and blocks such transfers while alerting information security professionals. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting determines whether a domain member should attempt to negotiate encryption for all secure channel traffic that it initiates.
The recommended state for this setting is: Enabled .
When a computer joins a domain, a computer account is created. After it joins the domain, the computer uses the password for that account to create a secure channel with the Domain Controller for its domain every time that it restarts. Requests that are sent on the secure channel are authenticated—and sensitive information such as passwords are encrypted—but the channel is not integrity-checked, and not all information is encrypted.
Digital encryption and signing of the secure channel is a good idea where it is supported. The secure channel protects domain credentials as they are sent to the Domain Controller.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Domain member: Digitally encrypt secure channel data (when possible)
Impact:
None - this is the default behavior. However, only Windows NT 4.0 Service Pack 6a (SP6a) and subsequent versions of the Windows operating system support digital encryption and signing of the secure channel. Windows 98 Second Edition clients do not support it unless they have Dsclient installed.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.2_L1_Ensure_Domain_member_Digitally_encrypt_secure_channel_data_when_possible_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:40.414-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/13/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37130-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.414-05:00" start-time="2020-04-22T15:48:40.352-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'SealSecureChannel' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817189" result="true" testref="oval:org.cisecurity.benchmarks:tst:817189" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817189"> <cis:evidence_item itemref="1236"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\Netlogon\Parameters"/> <cis:evidence_item_pk_field name="name" value="SealSecureChannel"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171891" value-id="xccdf_org.cisecurity.benchmarks_value_817189_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171892" value-id="xccdf_org.cisecurity.benchmarks_value_817189_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817189"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37130-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
Subcontrol: | 13.3 |
Label: | Monitor and Block Unauthorized Network Traffic |
Description: | Deploy an automated tool on network perimeters that monitors for unauthorized transfer of sensitive information and blocks such transfers while alerting information security professionals. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting determines whether a domain member should attempt to negotiate whether all secure channel traffic that it initiates must be digitally signed. Digital signatures protect the traffic from being modified by anyone who captures the data as it traverses the network.
The recommended state for this setting is: Enabled .
When a computer joins a domain, a computer account is created. After it joins the domain, the computer uses the password for that account to create a secure channel with the Domain Controller for its domain every time that it restarts. Requests that are sent on the secure channel are authenticated—and sensitive information such as passwords are encrypted—but the channel is not integrity-checked, and not all information is encrypted.
Digital encryption and signing of the secure channel is a good idea where it is supported. The secure channel protects domain credentials as they are sent to the Domain Controller.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Domain member: Digitally sign secure channel data (when possible)
Impact:
None - this is the default behavior. However, only Windows NT 4.0 with Service Pack 6a (SP6a) and subsequent versions of the Windows operating system support digital encryption and signing of the secure channel. Windows 98 Second Edition clients do not support it unless they have Dsclient installed.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.3_L1_Ensure_Domain_member_Digitally_sign_secure_channel_data_when_possible_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:40.477-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/13/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37222-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.477-05:00" start-time="2020-04-22T15:48:40.414-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'SignSecureChannel' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817195" result="true" testref="oval:org.cisecurity.benchmarks:tst:817195" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817195"> <cis:evidence_item itemref="1237"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\Netlogon\Parameters"/> <cis:evidence_item_pk_field name="name" value="SignSecureChannel"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171951" value-id="xccdf_org.cisecurity.benchmarks_value_817195_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171952" value-id="xccdf_org.cisecurity.benchmarks_value_817195_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817195"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37222-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
Subcontrol: | 13.3 |
Label: | Monitor and Block Unauthorized Network Traffic |
Description: | Deploy an automated tool on network perimeters that monitors for unauthorized transfer of sensitive information and blocks such transfers while alerting information security professionals. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting determines whether a domain member can periodically change its computer account password. Computers that cannot automatically change their account passwords are potentially vulnerable, because an attacker might be able to determine the password for the system's domain account.
The recommended state for this setting is: Disabled .
Note: Some problems can occur as a result of machine account password expiration, particularly if a machine is reverted to a previous point-in-time state, as is common with virtual machines. Depending on how far back the reversion is, the older machine account password stored on the machine may no longer be recognized by the domain controllers, and therefore the computer loses its domain trust. This can also disrupt non-persistent VDI implementations, and devices with write filters that disallow permanent changes to the OS volume. Some organizations may choose to exempt themselves from this recommendation and disable machine account password expiration for these situations.
The default configuration for Windows Server 2003-based computers that belong to a domain is that they are automatically required to change the passwords for their accounts every 30 days. If you disable this policy setting, computers that run Windows Server 2003 will retain the same passwords as their computer accounts. Computers that are no longer able to automatically change their account password are at risk from an attacker who could determine the password for the computer's domain account.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Domain member: Disable machine account password changes
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.4_L1_Ensure_Domain_member_Disable_machine_account_password_changes_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:40.555-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37508-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.555-05:00" start-time="2020-04-22T15:48:40.477-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisablePasswordChange' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817201" result="true" testref="oval:org.cisecurity.benchmarks:tst:817201" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817201"> <cis:evidence_item itemref="1238"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\Netlogon\Parameters"/> <cis:evidence_item_pk_field name="name" value="DisablePasswordChange"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172011" value-id="xccdf_org.cisecurity.benchmarks_value_817201_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172012" value-id="xccdf_org.cisecurity.benchmarks_value_817201_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817201"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37508-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines the maximum allowable age for a computer account password. By default, domain members automatically change their domain passwords every 30 days.
The recommended state for this setting is: 30 or fewer days, but not 0 .
Note: A value of 0 does not conform to the benchmark as it disables maximum password age.
Note #2: Some problems can occur as a result of machine account password expiration, particularly if a machine is reverted to a previous point-in-time state, as is common with virtual machines. Depending on how far back the reversion is, the older machine account password stored on the machine may no longer be recognized by the domain controllers, and therefore the computer loses its domain trust. This can also disrupt non-persistent VDI implementations, and devices with write filters that disallow permanent changes to the OS volume. Some organizations may choose to exempt themselves from this recommendation and disable machine account password expiration for these situations.
In Active Directory-based domains, each computer has an account and password just like every user. By default, the domain members automatically change their domain password every 30 days. If you increase this interval significantly, or set it to 0 so that the computers no longer change their passwords, an attacker will have more time to undertake a brute force attack to guess the passwords of computer accounts.
To establish the recommended configuration via GP, set the following UI path to 30 or fewer days, but not 0 :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Domain member: Maximum machine account password age
Impact:
None - this is the default behavior.
All of the following tests or sub-groups must pass: | ||||||||||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.5_L1_Ensure_Domain_member_Maximum_machine_account_password_age_is_set_to_30_or_fewer_days_but_not_0" role="full" severity="unknown" time="2020-04-22T15:48:40.618-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37431-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.618-05:00" start-time="2020-04-22T15:48:40.555-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'MaximumPasswordAge' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817206" result="true" testref="oval:org.cisecurity.benchmarks:tst:817206" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817206"> <cis:evidence_item itemref="1239"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\Netlogon\Parameters"/> <cis:evidence_item_pk_field name="name" value="MaximumPasswordAge"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="30" dt="int" ev="0" name="value" op="greater than" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'MaximumPasswordAge' is 'Windows: Registry Value' to '30'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817212" result="true" testref="oval:org.cisecurity.benchmarks:tst:817212" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817212"> <cis:evidence_item itemref="1240"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\Netlogon\Parameters"/> <cis:evidence_item_pk_field name="name" value="MaximumPasswordAge"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="30" dt="int" ev="30" name="value" op="less than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172061" value-id="xccdf_org.cisecurity.benchmarks_value_817206_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172062" value-id="xccdf_org.cisecurity.benchmarks_value_817206_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817206"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172121" value-id="xccdf_org.cisecurity.benchmarks_value_817212_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172122" value-id="xccdf_org.cisecurity.benchmarks_value_817212_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817212"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37431-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
When this policy setting is enabled, a secure channel can only be established with Domain Controllers that are capable of encrypting secure channel data with a strong (128-bit) session key.
To enable this policy setting, all Domain Controllers in the domain must be able to encrypt secure channel data with a strong key, which means all Domain Controllers must be running Microsoft Windows 2000 or newer.
The recommended state for this setting is: Enabled .
Session keys that are used to establish secure channel communications between Domain Controllers and member computers are much stronger in Windows 2000 than they were in previous Microsoft operating systems. Whenever possible, you should take advantage of these stronger session keys to help protect secure channel communications from attacks that attempt to hijack network sessions and eavesdropping. (Eavesdropping is a form of hacking in which network data is read or altered in transit. The data can be modified to hide or change the sender, or be redirected.)
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Domain member: Require strong (Windows 2000 or later) session key
Impact:
None - this is the default behavior. However, computers will not be able to join Windows NT 4.0 domains, and trusts between Active Directory domains and Windows NT-style domains may not work properly. Also, Domain Controllers with this setting configured will not allow older pre-Windows 2000 clients (that that do not support this policy setting) to join the domain.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.6.6_L1_Ensure_Domain_member_Require_strong_Windows_2000_or_later_session_key_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:40.696-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37614-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.696-05:00" start-time="2020-04-22T15:48:40.618-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'RequireStrongKey' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817218" result="true" testref="oval:org.cisecurity.benchmarks:tst:817218" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817218"> <cis:evidence_item itemref="1241"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\Netlogon\Parameters"/> <cis:evidence_item_pk_field name="name" value="RequireStrongKey"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172181" value-id="xccdf_org.cisecurity.benchmarks_value_817218_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172182" value-id="xccdf_org.cisecurity.benchmarks_value_817218_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817218"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37614-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This section contains recommendations related to interactive logons.
This policy setting determines whether users must press CTRL+ALT+DEL before they log on.
The recommended state for this setting is: Disabled .
Microsoft developed this feature to make it easier for users with certain types of physical impairments to log on to computers that run Windows. If users are not required to press CTRL+ALT+DEL, they are susceptible to attacks that attempt to intercept their passwords. If CTRL+ALT+DEL is required before logon, user passwords are communicated by means of a trusted path.
An attacker could install a Trojan horse program that looks like the standard Windows logon dialog box and capture the user's password. The attacker would then be able to log on to the compromised account with whatever level of privilege that user has.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Do not require CTRL+ALT+DEL
Impact:
Users must press CTRL+ALT+DEL before they log on to Windows unless they use a smart card for Windows logon. A smart card is a tamper-proof device that stores security information.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.1_L1_Ensure_Interactive_logon_Do_not_require_CTRLALTDEL_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:40.758-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37637-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.758-05:00" start-time="2020-04-22T15:48:40.696-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableCAD' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817192" result="true" testref="oval:org.cisecurity.benchmarks:tst:817192" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817192"> <cis:evidence_item itemref="1242"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="DisableCAD"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171921" value-id="xccdf_org.cisecurity.benchmarks_value_817192_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171922" value-id="xccdf_org.cisecurity.benchmarks_value_817192_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817192"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37637-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
This policy setting determines whether the account name of the last user to log on to the client computers in your organization will be displayed in each computer's respective Windows logon screen. Enable this policy setting to prevent intruders from collecting account names visually from the screens of desktop or laptop computers in your organization.
The recommended state for this setting is: Enabled .
An attacker with access to the console (for example, someone with physical access or someone who is able to connect to the server through Remote Desktop Services) could view the name of the last user who logged on to the server. The attacker could then try to guess the password, use a dictionary, or use a brute-force attack to try and log on.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Don't display last signed-in
Note: In older versions of Microsoft Windows, this setting was named Interactive logon: Do not display last user name , but it was renamed starting with Windows Server 2019.
Impact:
The name of the last user to successfully log on will not be displayed in the Windows logon screen.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.2_L1_Ensure_Interactive_logon_Dont_display_last_signed-in_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:40.836-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36056-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.836-05:00" start-time="2020-04-22T15:48:40.758-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DontDisplayLastUserName' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817188" result="true" testref="oval:org.cisecurity.benchmarks:tst:817188" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817188"> <cis:evidence_item itemref="1243"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="DontDisplayLastUserName"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171881" value-id="xccdf_org.cisecurity.benchmarks_value_817188_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171882" value-id="xccdf_org.cisecurity.benchmarks_value_817188_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817188"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36056-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
Windows notices inactivity of a logon session, and if the amount of inactive time exceeds the inactivity limit, then the screen saver will run, locking the session.
The recommended state for this setting is: 900 or fewer second(s), but not 0 .
Note: A value of 0 does not conform to the benchmark as it disables the machine inactivity limit.
If a user forgets to lock their computer when they walk away it's possible that a passerby will hijack it.
To establish the recommended configuration via GP, set the following UI path to 900 or fewer seconds, but not 0 :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Machine inactivity limit
Impact:
The screen saver will automatically activate when the computer has been unattended for the amount of time specified. The impact should be minimal since the screen saver is enabled by default.
All of the following tests or sub-groups must pass: | ||||||||||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.3_L1_Ensure_Interactive_logon_Machine_inactivity_limit_is_set_to_900_or_fewer_seconds_but_not_0" role="full" severity="unknown" time="2020-04-22T15:48:40.899-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38235-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.899-05:00" start-time="2020-04-22T15:48:40.836-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'InactivityTimeoutSecs' is 'Windows: Registry Value' to '900'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817203" result="true" testref="oval:org.cisecurity.benchmarks:tst:817203" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817203"> <cis:evidence_item itemref="1244"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="InactivityTimeoutSecs"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="900" dt="int" ev="900" name="value" op="less than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'InactivityTimeoutSecs' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817200" result="true" testref="oval:org.cisecurity.benchmarks:tst:817200" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817200"> <cis:evidence_item itemref="1245"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="InactivityTimeoutSecs"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="900" dt="int" ev="0" name="value" op="not equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172001" value-id="xccdf_org.cisecurity.benchmarks_value_817200_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172002" value-id="xccdf_org.cisecurity.benchmarks_value_817200_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817200"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172031" value-id="xccdf_org.cisecurity.benchmarks_value_817203_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172032" value-id="xccdf_org.cisecurity.benchmarks_value_817203_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817203"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38235-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This policy setting specifies a text message that displays to users when they log on. Configure this setting in a manner that is consistent with the security and operational requirements of your organization.
Displaying a warning message before logon may help prevent an attack by warning the attacker about the consequences of their misconduct before it happens. It may also help to reinforce corporate policy by notifying employees of the appropriate policy during the logon process. This text is often used for legal reasons—for example, to warn users about the ramifications of misusing company information or to warn them that their actions may be audited.
Note: Any warning that you display should first be approved by your organization's legal and human resources representatives.
To establish the recommended configuration via GP, configure the following UI path to a value that is consistent with the security and operational requirements of your organization:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Message text for users attempting to log on
Impact:
Users will have to acknowledge a dialog box containing the configured text before they can log on to the computer.
Note: Windows Vista and Windows XP Professional support logon banners that can exceed 512 characters in length and that can also contain carriage-return line-feed sequences. However, Windows 2000-based clients cannot interpret and display these messages. You must use a Windows 2000-based computer to create a logon message policy that applies to Windows 2000-based computers.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.4_L1_Configure_Interactive_logon_Message_text_for_users_attempting_to_log_on" role="full" severity="unknown" time="2020-04-22T15:48:40.961-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37226-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.961-05:00" start-time="2020-04-22T15:48:40.899-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LegalNoticeText' is 'Windows: Registry Value' to '.+'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817211" result="true" testref="oval:org.cisecurity.benchmarks:tst:817211" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817211"> <cis:evidence_item itemref="1246"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="LegalNoticeText"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="Authorized users only. Actual or attempted unauthorized use of this computer system may result in criminal and/or civil prosecution and/or University disciplinary action. We reserve the right to view,monitor,and record activity on this system without notice or permission. Any information obtained by monitoring,reviewing,or recording is subject to review by release to law enforcement organizations in connection with the investigation or prosecution of possible criminal unauthorized activity on the system in accordance with Federal law,State statute,and University policy. If you are not an authorized user of this system,exit the system at this time." dt="string" ev=".+" name="value" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172111" value-id="xccdf_org.cisecurity.benchmarks_value_817211_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172112" value-id="xccdf_org.cisecurity.benchmarks_value_817211_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817211"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37226-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
This policy setting specifies the text displayed in the title bar of the window that users see when they log on to the system. Configure this setting in a manner that is consistent with the security and operational requirements of your organization.
Displaying a warning message before logon may help prevent an attack by warning the attacker about the consequences of their misconduct before it happens. It may also help to reinforce corporate policy by notifying employees of the appropriate policy during the logon process.
To establish the recommended configuration via GP, configure the following UI path to a value that is consistent with the security and operational requirements of your organization:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Message title for users attempting to log on
Impact:
Users will have to acknowledge a dialog box with the configured title before they can log on to the computer.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.5_L1_Configure_Interactive_logon_Message_title_for_users_attempting_to_log_on" role="full" severity="unknown" time="2020-04-22T15:48:41.039-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37512-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:41.039-05:00" start-time="2020-04-22T15:48:40.961-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LegalNoticeCaption' is 'Windows: Registry Value' to '.+'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817216" result="true" testref="oval:org.cisecurity.benchmarks:tst:817216" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817216"> <cis:evidence_item itemref="1247"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="LegalNoticeCaption"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="Authorized Users Only" dt="string" ev=".+" name="value" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172161" value-id="xccdf_org.cisecurity.benchmarks_value_817216_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172162" value-id="xccdf_org.cisecurity.benchmarks_value_817216_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817216"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37512-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
This policy setting determines how far in advance users are warned that their password will expire. It is recommended that you configure this policy setting to at least 5 days but no more than 14 days to sufficiently warn users when their passwords will expire.
The recommended state for this setting is: between 5 and 14 days .
It is recommended that user passwords be configured to expire periodically. Users will need to be warned that their passwords are going to expire, or they may inadvertently be locked out of the computer when their passwords expire. This condition could lead to confusion for users who access the network locally, or make it impossible for users to access your organization's network through dial-up or virtual private network (VPN) connections.
To establish the recommended configuration via GP, set the following UI path to a value between 5 and 14 days :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Prompt user to change password before expiration
Impact:
Users will see a dialog box prompt to change their password each time that they log on to the domain when their password is configured to expire between 5 and 14 days.
All of the following tests or sub-groups must pass: | ||||||||||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.7_L1_Ensure_Interactive_logon_Prompt_user_to_change_password_before_expiration_is_set_to_between_5_and_14_days" role="full" severity="unknown" time="2020-04-22T15:48:41.164-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37622-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:41.164-05:00" start-time="2020-04-22T15:48:41.039-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'PasswordExpiryWarning' is 'Windows: Registry Value' to '14'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817228" result="true" testref="oval:org.cisecurity.benchmarks:tst:817228" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817228"> <cis:evidence_item itemref="1248"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows NT\CurrentVersion\Winlogon"/> <cis:evidence_item_pk_field name="name" value="PasswordExpiryWarning"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="14" dt="int" ev="14" name="value" op="less than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'passwordexpirywarning' is 'Windows: Registry Value' to '5'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817233" result="true" testref="oval:org.cisecurity.benchmarks:tst:817233" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817233"> <cis:evidence_item itemref="1249"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows NT\CurrentVersion\Winlogon"/> <cis:evidence_item_pk_field name="name" value="passwordexpirywarning"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="14" dt="int" ev="5" name="value" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172281" value-id="xccdf_org.cisecurity.benchmarks_value_817228_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172282" value-id="xccdf_org.cisecurity.benchmarks_value_817228_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817228"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172331" value-id="xccdf_org.cisecurity.benchmarks_value_817233_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172332" value-id="xccdf_org.cisecurity.benchmarks_value_817233_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817233"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37622-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Logon information is required to unlock a locked computer. For domain accounts, this security setting determines whether it is necessary to contact a Domain Controller to unlock a computer.
The recommended state for this setting is: Enabled .
By default, the computer caches in memory the credentials of any users who are authenticated locally. The computer uses these cached credentials to authenticate anyone who attempts to unlock the console. When cached credentials are used, any changes that have recently been made to the account — such as user rights assignments, account lockout, or the account being disabled — are not considered or applied after the account is authenticated. User privileges are not updated, and (more importantly) disabled accounts are still able to unlock the console of the computer.
To implement the recommended configuration via GP, set the following UI path to Enabled:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Require Domain Controller Authentication to unlock workstation
Impact:
When the console on a computer is locked, either by a user or automatically by a screen saver time-out, the console can only be unlocked if a Domain Controller is available to re-authenticate the domain account that is being used to unlock the computer. If no Domain Controller is available, the user cannot unlock the computer.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.8_L1_Ensure_Interactive_logon_Require_Domain_Controller_Authentication_to_unlock_workstation_is_set_to_Enabled_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:41.227-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38240-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:41.227-05:00" start-time="2020-04-22T15:48:41.164-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ForceUnlockLogon' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817237" result="true" testref="oval:org.cisecurity.benchmarks:tst:817237" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817237"> <cis:evidence_item itemref="1250"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows NT\CurrentVersion\Winlogon"/> <cis:evidence_item_pk_field name="name" value="ForceUnlockLogon"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172371" value-id="xccdf_org.cisecurity.benchmarks_value_817237_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172372" value-id="xccdf_org.cisecurity.benchmarks_value_817237_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817237"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38240-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.9 |
Label: | Configure Account Access Centrally |
Description: | Configure access for all accounts through a centralized point of authentication, for example Active Directory or LDAP. Configure network and security devices for centralized authentication as well. |
This policy setting determines what happens when the smart card for a logged-on user is removed from the smart card reader.
The recommended state for this setting is: Lock Workstation . Configuring this setting to Force Logoff or Disconnect if a Remote Desktop Services session also conforms to the benchmark.
Users sometimes forget to lock their workstations when they are away from them, allowing the possibility for malicious users to access their computers. If smart cards are used for authentication, the computer should automatically lock itself when the card is removed to ensure that only the user with the smart card is accessing resources using those credentials.
To establish the recommended configuration via GP, set the following UI path to Lock Workstation (or, if applicable for your environment, Force Logoff or Disconnect if a Remote Desktop Services session ):
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Smart card removal behavior
Impact:
If you select Lock Workstation , the workstation is locked when the smart card is removed, allowing users to leave the area, take their smart card with them, and still maintain a protected session.
If you select Force Logoff , users are automatically logged off when their smart card is removed.
If you select Disconnect if a Remote Desktop Services session , removal of the smart card disconnects the session without logging the users off. This allows the user to insert the smart card and resume the session later, or at another smart card reader-equipped computer, without having to log on again. If the session is local, this policy will function identically to Lock Workstation .
Enforcing this setting on computers used by people who must log onto multiple computers in order to perform their duties could be frustrating and lower productivity. For example, if network administrators are limited to a single account but need to log into several computers simultaneously in order to effectively manage the network enforcing this setting will limit them to logging onto one computer at a time. For these reasons it is recommended that this setting only be enforced on workstations used for purposes commonly associated with typical users such as document creation and email.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.7.9_L1_Ensure_Interactive_logon_Smart_card_removal_behavior_is_set_to_Lock_Workstation_or_higher" role="full" severity="unknown" time="2020-04-22T15:48:41.289-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38333-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:41.289-05:00" start-time="2020-04-22T15:48:41.227-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ScRemoveOption' is 'Windows: Registry Value' to '^(1|2|3)$'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817245" result="true" testref="oval:org.cisecurity.benchmarks:tst:817245" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817245"> <cis:evidence_item itemref="1251"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows NT\CurrentVersion\Winlogon"/> <cis:evidence_item_pk_field name="name" value="ScRemoveOption"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="string" ev="^(1|2|3)$" name="value" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172451" value-id="xccdf_org.cisecurity.benchmarks_value_817245_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172452" value-id="xccdf_org.cisecurity.benchmarks_value_817245_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817245"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38333-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This section contains recommendations related to configuring the Microsoft network client.
This policy setting determines whether packet signing is required by the SMB client component.
Note: When Windows Vista-based computers have this policy setting enabled and they connect to file or print shares on remote servers, it is important that the setting is synchronized with its companion setting, Microsoft network server: Digitally sign communications (always) , on those servers. For more information about these settings, see the "Microsoft network client and server: Digitally sign communications (four related settings)" section in Chapter 5 of the Threats and Countermeasures guide.
The recommended state for this setting is: Enabled .
Session hijacking uses tools that allow attackers who have access to the same network as the client or server to interrupt, end, or steal a session in progress. Attackers can potentially intercept and modify unsigned SMB packets and then modify the traffic and forward it so that the server might perform undesirable actions. Alternatively, the attacker could pose as the server or client after legitimate authentication and gain unauthorized access to data.
SMB is the resource sharing protocol that is supported by many Windows operating systems. It is the basis of NetBIOS and many other protocols. SMB signatures authenticate both users and the servers that host the data. If either side fails the authentication process, data transmission will not take place.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (always)
Impact:
The Microsoft network client will not communicate with a Microsoft network server unless that server agrees to perform SMB packet signing.
The Windows 2000 Server, Windows 2000 Professional, Windows Server 2003, Windows XP Professional and Windows Vista implementations of the SMB file and print sharing protocol support mutual authentication, which prevents session hijacking attacks and supports message authentication to prevent man-in-the-middle attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.
Implementation of SMB signing may negatively affect performance, because each packet needs to be signed and verified. If these settings are enabled on a server that is performing multiple roles, such as a small business server that is serving as a Domain Controller, file server, print server, and application server performance may be substantially slowed. Additionally, if you configure computers to ignore all unsigned SMB communications, older applications and operating systems will not be able to connect. However, if you completely disable all SMB signing, computers will be vulnerable to session hijacking attacks.
When SMB signing policies are enabled on Domain Controllers running Windows Server 2003 and member computers running Windows Vista SP1 or Windows Server 2008 group policy processing will fail. A hotfix is available from Microsoft that resolves this issue; see Microsoft Knowledge Base article 950876 for more details: Group Policy settings are not applied on member computers that are running Windows Server 2008 or Windows Vista SP1 when certain SMB signing policies are enabled .
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.1_L1_Ensure_Microsoft_network_client_Digitally_sign_communications_always_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:41.352-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36325-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:41.352-05:00" start-time="2020-04-22T15:48:41.289-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'RequireSecuritySignature' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817197" result="true" testref="oval:org.cisecurity.benchmarks:tst:817197" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817197"> <cis:evidence_item itemref="1252"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\LanmanWorkstation\Parameters"/> <cis:evidence_item_pk_field name="name" value="RequireSecuritySignature"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171971" value-id="xccdf_org.cisecurity.benchmarks_value_817197_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171972" value-id="xccdf_org.cisecurity.benchmarks_value_817197_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817197"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36325-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting determines whether the SMB client will attempt to negotiate SMB packet signing.
Note: Enabling this policy setting on SMB clients on your network makes them fully effective for packet signing with all clients and servers in your environment.
The recommended state for this setting is: Enabled .
Session hijacking uses tools that allow attackers who have access to the same network as the client or server to interrupt, end, or steal a session in progress. Attackers can potentially intercept and modify unsigned SMB packets and then modify the traffic and forward it so that the server might perform undesirable actions. Alternatively, the attacker could pose as the server or client after legitimate authentication and gain unauthorized access to data.
SMB is the resource sharing protocol that is supported by many Windows operating systems. It is the basis of NetBIOS and many other protocols. SMB signatures authenticate both users and the servers that host the data. If either side fails the authentication process, data transmission will not take place.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (if server agrees)
Impact:
None - this is the default behavior.
The Windows 2000 Server, Windows 2000 Professional, Windows Server 2003, Windows XP Professional and Windows Vista implementations of the SMB file and print sharing protocol support mutual authentication, which prevents session hijacking attacks and supports message authentication to prevent man-in-the-middle attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.
Implementation of SMB signing may negatively affect performance, because each packet needs to be signed and verified. If these settings are enabled on a server that is performing multiple roles, such as a small business server that is serving as a Domain Controller, file server, print server, and application server performance may be substantially slowed. Additionally, if you configure computers to ignore all unsigned SMB communications, older applications and operating systems will not be able to connect. However, if you completely disable all SMB signing, computers will be vulnerable to session hijacking attacks.
When SMB signing policies are enabled on Domain Controllers running Windows Server 2003 and member computers running Windows Vista SP1 or Windows Server 2008 group policy processing will fail. A hotfix is available from Microsoft that resolves this issue; see Microsoft Knowledge Base article 950876 for more details: Group Policy settings are not applied on member computers that are running Windows Server 2008 or Windows Vista SP1 when certain SMB signing policies are enabled .
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.2_L1_Ensure_Microsoft_network_client_Digitally_sign_communications_if_server_agrees_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:41.430-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36269-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:41.430-05:00" start-time="2020-04-22T15:48:41.352-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableSecuritySignature' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817210" result="true" testref="oval:org.cisecurity.benchmarks:tst:817210" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817210"> <cis:evidence_item itemref="1253"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\LanmanWorkstation\Parameters"/> <cis:evidence_item_pk_field name="name" value="EnableSecuritySignature"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172101" value-id="xccdf_org.cisecurity.benchmarks_value_817210_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172102" value-id="xccdf_org.cisecurity.benchmarks_value_817210_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817210"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36269-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting determines whether the SMB redirector will send plaintext passwords during authentication to third-party SMB servers that do not support password encryption.
It is recommended that you disable this policy setting unless there is a strong business case to enable it. If this policy setting is enabled, unencrypted passwords will be allowed across the network.
The recommended state for this setting is: Disabled .
If you enable this policy setting, the server can transmit passwords in plaintext across the network to other computers that offer SMB services, which is a significant security risk. These other computers may not use any of the SMB security mechanisms that are included with Windows Server 2003.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Send unencrypted password to third-party SMB servers
Impact:
None - this is the default behavior.
Some very old applications and operating systems such as MS-DOS, Windows for Workgroups 3.11, and Windows 95a may not be able to communicate with the servers in your organization by means of the SMB protocol.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.8.3_L1_Ensure_Microsoft_network_client_Send_unencrypted_password_to_third-party_SMB_servers_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:41.492-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37863-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:41.492-05:00" start-time="2020-04-22T15:48:41.430-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnablePlainTextPassword' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817224" result="true" testref="oval:org.cisecurity.benchmarks:tst:817224" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817224"> <cis:evidence_item itemref="1254"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\LanmanWorkstation\Parameters"/> <cis:evidence_item_pk_field name="name" value="EnablePlainTextPassword"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172241" value-id="xccdf_org.cisecurity.benchmarks_value_817224_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172242" value-id="xccdf_org.cisecurity.benchmarks_value_817224_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817224"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37863-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This section contains recommendations related to configuring the Microsoft network server.
This policy setting allows you to specify the amount of continuous idle time that must pass in an SMB session before the session is suspended because of inactivity. Administrators can use this policy setting to control when a computer suspends an inactive SMB session. If client activity resumes, the session is automatically reestablished.
The maximum value is 99999, which is over 69 days; in effect, this value disables the setting.
The recommended state for this setting is: 15 or fewer minute(s) .
Each SMB session consumes server resources, and numerous null sessions will slow the server or possibly cause it to fail. An attacker could repeatedly establish SMB sessions until the server's SMB services become slow or unresponsive.
To establish the recommended configuration via GP, set the following UI path to 15 or fewer minute(s) :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network server: Amount of idle time required before suspending session
Impact:
There will be little impact because SMB sessions will be re-established automatically if the client resumes activity.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.1_L1_Ensure_Microsoft_network_server_Amount_of_idle_time_required_before_suspending_session_is_set_to_15_or_fewer_minutes" role="full" severity="unknown" time="2020-04-22T15:48:41.555-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38046-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817190" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AutoDisconnect' is 'Windows: Registry Value' less than or equal to '15'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817190" result="true" testref="oval:org.cisecurity.benchmarks:tst:817190" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817190"> <cis:evidence_item itemref="1255"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\LanManServer\Parameters"/> <cis:evidence_item_pk_field name="name" value="AutoDisconnect"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="15" dt="int" ev="15" name="value" op="less than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171901" value-id="xccdf_org.cisecurity.benchmarks_value_817190_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171902" value-id="xccdf_org.cisecurity.benchmarks_value_817190_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817190"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38046-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
This policy setting determines whether packet signing is required by the SMB server component. Enable this policy setting in a mixed environment to prevent downstream clients from using the workstation as a network server.
The recommended state for this setting is: Enabled .
Session hijacking uses tools that allow attackers who have access to the same network as the client or server to interrupt, end, or steal a session in progress. Attackers can potentially intercept and modify unsigned SMB packets and then modify the traffic and forward it so that the server might perform undesirable actions. Alternatively, the attacker could pose as the server or client after legitimate authentication and gain unauthorized access to data.
SMB is the resource sharing protocol that is supported by many Windows operating systems. It is the basis of NetBIOS and many other protocols. SMB signatures authenticate both users and the servers that host the data. If either side fails the authentication process, data transmission will not take place.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network server: Digitally sign communications (always)
Impact:
The Microsoft network server will not communicate with a Microsoft network client unless that client agrees to perform SMB packet signing.
The Windows 2000 Server, Windows 2000 Professional, Windows Server 2003, Windows XP Professional and Windows Vista implementations of the SMB file and print sharing protocol support mutual authentication, which prevents session hijacking attacks and supports message authentication to prevent man-in-the-middle attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.
Implementation of SMB signing may negatively affect performance, because each packet needs to be signed and verified. If these settings are enabled on a server that is performing multiple roles, such as a small business server that is serving as a Domain Controller, file server, print server, and application server performance may be substantially slowed. Additionally, if you configure computers to ignore all unsigned SMB communications, older applications and operating systems will not be able to connect. However, if you completely disable all SMB signing, computers will be vulnerable to session hijacking attacks.
When SMB signing policies are enabled on Domain Controllers running Windows Server 2003 and member computers running Windows Vista SP1 or Windows Server 2008 group policy processing will fail. A hotfix is available from Microsoft that resolves this issue; see Microsoft Knowledge Base article 950876 for more details: Group Policy settings are not applied on member computers that are running Windows Server 2008 or Windows Vista SP1 when certain SMB signing policies are enabled .
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.2_L1_Ensure_Microsoft_network_server_Digitally_sign_communications_always_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:41.618-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37864-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:41.618-05:00" start-time="2020-04-22T15:48:41.555-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'RequireSecuritySignature' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817196" result="true" testref="oval:org.cisecurity.benchmarks:tst:817196" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817196"> <cis:evidence_item itemref="1256"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\LanManServer\Parameters"/> <cis:evidence_item_pk_field name="name" value="RequireSecuritySignature"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171961" value-id="xccdf_org.cisecurity.benchmarks_value_817196_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171962" value-id="xccdf_org.cisecurity.benchmarks_value_817196_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817196"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37864-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting determines whether the SMB server will negotiate SMB packet signing with clients that request it. If no signing request comes from the client, a connection will be allowed without a signature if the Microsoft network server: Digitally sign communications (always) setting is not enabled.
Note: Enable this policy setting on SMB clients on your network to make them fully effective for packet signing with all clients and servers in your environment.
The recommended state for this setting is: Enabled .
Session hijacking uses tools that allow attackers who have access to the same network as the client or server to interrupt, end, or steal a session in progress. Attackers can potentially intercept and modify unsigned SMB packets and then modify the traffic and forward it so that the server might perform undesirable actions. Alternatively, the attacker could pose as the server or client after legitimate authentication and gain unauthorized access to data.
SMB is the resource sharing protocol that is supported by many Windows operating systems. It is the basis of NetBIOS and many other protocols. SMB signatures authenticate both users and the servers that host the data. If either side fails the authentication process, data transmission will not take place.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network server: Digitally sign communications (if client agrees)
Impact:
The Microsoft network server will negotiate SMB packet signing as requested by the client. That is, if packet signing has been enabled on the client, packet signing will be negotiated.
The Windows 2000 Server, Windows 2000 Professional, Windows Server 2003, Windows XP Professional and Windows Vista implementations of the SMB file and print sharing protocol support mutual authentication, which prevents session hijacking attacks and supports message authentication to prevent man-in-the-middle attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.
Implementation of SMB signing may negatively affect performance, because each packet needs to be signed and verified. If these settings are enabled on a server that is performing multiple roles, such as a small business server that is serving as a Domain Controller, file server, print server, and application server performance may be substantially slowed. Additionally, if you configure computers to ignore all unsigned SMB communications, older applications and operating systems will not be able to connect. However, if you completely disable all SMB signing, computers will be vulnerable to session hijacking attacks.
When SMB signing policies are enabled on Domain Controllers running Windows Server 2003 and member computers running Windows Vista SP1 or Windows Server 2008 group policy processing will fail. A hotfix is available from Microsoft that resolves this issue; see Microsoft Knowledge Base article 950876 for more details: Group Policy settings are not applied on member computers that are running Windows Server 2008 or Windows Vista SP1 when certain SMB signing policies are enabled .
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.3_L1_Ensure_Microsoft_network_server_Digitally_sign_communications_if_client_agrees_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:41.680-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-35988-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:41.680-05:00" start-time="2020-04-22T15:48:41.618-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableSecuritySignature' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817202" result="true" testref="oval:org.cisecurity.benchmarks:tst:817202" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817202"> <cis:evidence_item itemref="1257"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\LanManServer\Parameters"/> <cis:evidence_item_pk_field name="name" value="EnableSecuritySignature"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172021" value-id="xccdf_org.cisecurity.benchmarks_value_817202_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172022" value-id="xccdf_org.cisecurity.benchmarks_value_817202_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817202"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-35988-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This security setting determines whether to disconnect users who are connected to the local computer outside their user account's valid logon hours. This setting affects the Server Message Block (SMB) component. If you enable this policy setting you should also enable Network security: Force logoff when logon hours expire (Rule 2.3.11.6).
If your organization configures logon hours for users, this policy setting is necessary to ensure they are effective.
The recommended state for this setting is: Enabled .
If your organization configures logon hours for users, then it makes sense to enable this policy setting. Otherwise, users who should not have access to network resources outside of their logon hours may actually be able to continue to use those resources with sessions that were established during allowed hours.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network server: Disconnect clients when logon hours expire
Impact:
None - this is the default behavior. If logon hours are not used in your organization, this policy setting will have no impact. If logon hours are used, existing user sessions will be forcibly terminated when their logon hours expire.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.4_L1_Ensure_Microsoft_network_server_Disconnect_clients_when_logon_hours_expire_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:41.743-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/13" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37972-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:41.743-05:00" start-time="2020-04-22T15:48:41.680-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'enableforcedlogoff' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817208" result="true" testref="oval:org.cisecurity.benchmarks:tst:817208" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817208"> <cis:evidence_item itemref="1258"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\LanManServer\Parameters"/> <cis:evidence_item_pk_field name="name" value="enableforcedlogoff"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172081" value-id="xccdf_org.cisecurity.benchmarks_value_817208_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172082" value-id="xccdf_org.cisecurity.benchmarks_value_817208_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817208"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37972-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.13 |
Label: | Alert on Account Login Behavior Deviation |
Description: | Alert when users deviate from normal login behavior, such as time-of-day, workstation location and duration. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting controls the level of validation a computer with shared folders or printers (the server) performs on the service principal name (SPN) that is provided by the client computer when it establishes a session using the server message block (SMB) protocol.
The server message block (SMB) protocol provides the basis for file and print sharing and other networking operations, such as remote Windows administration. The SMB protocol supports validating the SMB server service principal name (SPN) within the authentication blob provided by a SMB client to prevent a class of attacks against SMB servers referred to as SMB relay attacks. This setting will affect both SMB1 and SMB2.
The recommended state for this setting is: Accept if provided by client . Configuring this setting to Required from client also conforms to the benchmark.
Note: Since the release of the MS KB3161561 security patch, this setting can cause significant issues (such as replication problems, group policy editing issues and blue screen crashes) on Domain Controllers when used simultaneously with UNC path hardening (i.e. Rule 18.5.14.1). CIS therefore recommends against deploying this setting on Domain Controllers.
The identity of a computer can be spoofed to gain unauthorized access to network resources.
To establish the recommended configuration via GP, set the following UI path to Accept if provided by client (configuring to Required from client also conforms to the benchmark):
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network server: Server SPN target name validation level
Impact:
All Windows operating systems support both a client-side SMB component and a server-side SMB component. This setting affects the server SMB behavior, and its implementation should be carefully evaluated and tested to prevent disruptions to file and print serving capabilities.
If configured to Accept if provided by client , the SMB server will accept and validate the SPN provided by the SMB client and allow a session to be established if it matches the SMB server’s list of SPN’s for itself. If the SPN does NOT match, the session request for that SMB client will be denied.
If configured to Required from client , the SMB client MUST send a SPN name in session setup, and the SPN name provided MUST match the SMB server that is being requested to establish a connection. If no SPN is provided by client, or the SPN provided does not match, the session is denied.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.9.5_L1_Ensure_Microsoft_network_server_Server_SPN_target_name_validation_level_is_set_to_Accept_if_provided_by_client_or_higher_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:41.821-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36170-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:41.821-05:00" start-time="2020-04-22T15:48:41.743-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'SMBServerNameHardeningLevel' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817215" result="true" testref="oval:org.cisecurity.benchmarks:tst:817215" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817215"> <cis:evidence_item itemref="1259"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\LanManServer\Parameters"/> <cis:evidence_item_pk_field name="name" value="SMBServerNameHardeningLevel"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172151" value-id="xccdf_org.cisecurity.benchmarks_value_817215_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172152" value-id="xccdf_org.cisecurity.benchmarks_value_817215_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817215"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36170-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
This section contains recommendations related to network access.
This policy setting determines whether an anonymous user can request security identifier (SID) attributes for another user, or use a SID to obtain its corresponding user name.
The recommended state for this setting is: Disabled .
If this policy setting is enabled, a user with local access could use the well-known Administrator's SID to learn the real name of the built-in Administrator account, even if it has been renamed. That person could then use the account name to initiate a password guessing attack.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network access: Allow anonymous SID/Name translation
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.1_L1_Ensure_Network_access_Allow_anonymous_SIDName_translation_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:38.274-05:00" version="1" weight="1.0"> <result>unknown</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36065-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:38.274-05:00" start-time="2020-04-22T15:48:38.086-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LSAAnonymousNameLookup' is 'Equals' to 'False'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817205" result="unknown" testref="oval:org.cisecurity.benchmarks:tst:817205" type="wmi57_test"> <cis:evidence_object> <cis:evidence_item itemref="1204"> <cis:evidence_item_pk status="not collected"> <cis:evidence_item_pk_field name="namespace" value="root\rsop\computer"/> <cis:evidence_item_pk_field name="wql" value="SELECT Setting FROM RSOP_SecuritySettingBoolean WHERE KeyName='LSAAnonymousNameLookup' AND Precedence=1"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817205" value-id="xccdf_org.cisecurity.benchmarks_value_817205_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817205"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36065-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting controls the ability of anonymous users to enumerate the accounts in the Security Accounts Manager (SAM). If you enable this policy setting, users with anonymous connections will not be able to enumerate domain account user names on the systems in your environment. This policy setting also allows additional restrictions on anonymous connections.
The recommended state for this setting is: Enabled .
Note: This policy has no effect on Domain Controllers.
An unauthorized user could anonymously list account names and use the information to attempt to guess passwords or perform social engineering attacks. (Social engineering attacks try to deceive users in some way to obtain passwords or some form of security information.)
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network access: Do not allow anonymous enumeration of SAM accounts
Impact:
None - this is the default behavior. It will be impossible to establish trusts with Windows NT 4.0-based domains. Also, client computers that run older versions of the Windows operating system such as Windows NT 3.51 and Windows 95 will experience problems when they try to use resources on the server.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.2_L1_Ensure_Network_access_Do_not_allow_anonymous_enumeration_of_SAM_accounts_is_set_to_Enabled_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:38.336-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36316-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:38.336-05:00" start-time="2020-04-22T15:48:38.274-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'RestrictAnonymousSAM' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817217" result="true" testref="oval:org.cisecurity.benchmarks:tst:817217" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817217"> <cis:evidence_item itemref="1205"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa"/> <cis:evidence_item_pk_field name="name" value="RestrictAnonymousSAM"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172171" value-id="xccdf_org.cisecurity.benchmarks_value_817217_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172172" value-id="xccdf_org.cisecurity.benchmarks_value_817217_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817217"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36316-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting controls the ability of anonymous users to enumerate SAM accounts as well as shares. If you enable this policy setting, anonymous users will not be able to enumerate domain account user names and network share names on the systems in your environment.
The recommended state for this setting is: Enabled .
Note: This policy has no effect on Domain Controllers.
An unauthorized user could anonymously list account names and shared resources and use the information to attempt to guess passwords or perform social engineering attacks. (Social engineering attacks try to deceive users in some way to obtain passwords or some form of security information.)
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network access: Do not allow anonymous enumeration of SAM accounts and shares
Impact:
It will be impossible to establish trusts with Windows NT 4.0-based domains. Also, client computers that run older versions of the Windows operating system such as Windows NT 3.51 and Windows 95 will experience problems when they try to use resources on the server. Users who access file and print servers anonymously will be unable to list the shared network resources on those servers; the users will have to authenticate before they can view the lists of shared folders and printers. However, even with this policy setting enabled, anonymous users will have access to resources with permissions that explicitly include the built-in group, ANONYMOUS LOGON .
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.3_L1_Ensure_Network_access_Do_not_allow_anonymous_enumeration_of_SAM_accounts_and_shares_is_set_to_Enabled_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:38.414-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36077-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:38.414-05:00" start-time="2020-04-22T15:48:38.336-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'RestrictAnonymous' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817229" result="true" testref="oval:org.cisecurity.benchmarks:tst:817229" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817229"> <cis:evidence_item itemref="1206"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa"/> <cis:evidence_item_pk_field name="name" value="RestrictAnonymous"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172291" value-id="xccdf_org.cisecurity.benchmarks_value_817229_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172292" value-id="xccdf_org.cisecurity.benchmarks_value_817229_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817229"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36077-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines what additional permissions are assigned for anonymous connections to the computer.
The recommended state for this setting is: Disabled .
An unauthorized user could anonymously list account names and shared resources and use the information to attempt to guess passwords, perform social engineering attacks, or launch DoS attacks.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network access: Let Everyone permissions apply to anonymous users
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.5_L1_Ensure_Network_access_Let_Everyone_permissions_apply_to_anonymous_users_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:38.477-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36148-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:38.477-05:00" start-time="2020-04-22T15:48:38.414-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EveryoneIncludesAnonymous' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817258" result="true" testref="oval:org.cisecurity.benchmarks:tst:817258" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817258"> <cis:evidence_item itemref="1207"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa"/> <cis:evidence_item_pk_field name="name" value="EveryoneIncludesAnonymous"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172581" value-id="xccdf_org.cisecurity.benchmarks_value_817258_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172582" value-id="xccdf_org.cisecurity.benchmarks_value_817258_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817258"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36148-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines which communication sessions, or pipes, will have attributes and permissions that allow anonymous access.
The recommended state for this setting is: <blank> (i.e. None), or (when the legacy Computer Browser service is enabled) BROWSER .
Note: A Member Server that holds the Remote Desktop Services Role with Remote Desktop Licensing Role Service will require a special exception to this recommendation, to allow the HydraLSPipe and TermServLicensing Named Pipes to be accessed anonymously.
Limiting named pipes that can be accessed anonymously will reduce the attack surface of the system.
To establish the recommended configuration via GP, configure the following UI path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network access: Named Pipes that can be accessed anonymously
Impact:
Null session access over null session access over named pipes will be disabled unless they are included, and applications that rely on this feature or on unauthenticated access to named pipes will no longer function. The BROWSER named pipe may need to be added to this list if the Computer Browser service is needed for supporting legacy components. The Computer Browser service is disabled by default.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.7_L1_Configure_Network_access_Named_Pipes_that_can_be_accessed_anonymously_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:38.539-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38258-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817276" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NullSessionPipes' is 'Set Is Empty' to '' - MS" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817276" result="true" testref="oval:org.cisecurity.benchmarks:tst:817276" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817276"> <cis:evidence_item entity_check="none exist" itemref="1208"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SYSTEM\CurrentControlSet\Services\LanManServer\Parameters"/> <cis:evidence_item_pk_field name="name" value="NullSessionPipes"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_multi_sz" dt="string" ev="reg_multi_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="" dt="string" ev=".+" name="value" op="pattern match" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172761" value-id="xccdf_org.cisecurity.benchmarks_value_817276_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172762" value-id="xccdf_org.cisecurity.benchmarks_value_817276_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817276"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38258-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.1 |
Label: | Segment the Network Based on Sensitivity |
Description: | Segment the network based on the label or classification level of the information stored on the servers, locate all sensitive information on separated Virtual Local Area Networks (VLANs). |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.2 |
Label: | Enable Firewall Filtering Between VLANs |
Description: | Enable firewall filtering between VLANs to ensure that only authorized systems are able to communicate with other systems necessary to fulfill their specific responsibilities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.1 |
Label: | Implement Network Segmentation Based On Information Class |
Description: | Segment the network based on the label or classification level of the information stored on the servers. Locate all sensitive information on separated VLANS with firewall filtering to ensure that only authorized individuals are only able to communicate with systems necessary to fulfill their specific responsibilities. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines which registry paths will be accessible over the network, regardless of the users or groups listed in the access control list (ACL) of the winreg registry key.
Note: This setting does not exist in Windows XP. There was a setting with that name in Windows XP, but it is called "Network access: Remotely accessible registry paths and sub-paths" in Windows Server 2003, Windows Vista, and Windows Server 2008 (non-R2).
Note #2: When you configure this setting you specify a list of one or more objects. The delimiter used when entering the list is a line feed or carriage return, that is, type the first object on the list, press the Enter button, type the next object, press Enter again, etc. The setting value is stored as a comma-delimited list in group policy security templates. It is also rendered as a comma-delimited list in Group Policy Editor's display pane and the Resultant Set of Policy console. It is recorded in the registry as a line-feed delimited list in a REG_MULTI_SZ value.
The recommended state for this setting is:
System\CurrentControlSet\Control\ProductOptions
System\CurrentControlSet\Control\Server Applications
Software\Microsoft\Windows NT\CurrentVersion
The registry is a database that contains computer configuration information, and much of the information is sensitive. An attacker could use this information to facilitate unauthorized activities. To reduce the risk of such an attack, suitable ACLs are assigned throughout the registry to help protect it from access by unauthorized users.
To establish the recommended configuration via GP, set the following UI path to: System\CurrentControlSet\Control\ProductOptions System\CurrentControlSet\Control\Server Applications Software\Microsoft\Windows NT\CurrentVersion
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network access: Remotely accessible registry paths
Impact:
None - this is the default behavior. However, if you remove the default registry paths from the list of accessible ones, remote management tools such as the Microsoft Baseline Security Analyzer and Microsoft Systems Management Server could fail, as they require remote access to the registry to properly monitor and manage computers.
Note: If you want to allow remote access, you must also enable the Remote Registry service.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.8_L1_Configure_Network_access_Remotely_accessible_registry_paths" role="full" severity="unknown" time="2020-04-22T15:48:38.602-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14/subcontrol/6" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/9" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37194-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:38.602-05:00" start-time="2020-04-22T15:48:38.539-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Machine' is 'Windows: Registry Value' to 'System\CurrentControlSet\Control\ProductOptions,System\CurrentControlSet\Control\Server Applications,Software\Microsoft\Windows NT\CurrentVersion'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817291" result="true" testref="oval:org.cisecurity.benchmarks:tst:817291" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817291"> <cis:evidence_item itemref="1209"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedExactPaths"/> <cis:evidence_item_pk_field name="name" value="Machine"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_multi_sz" dt="string" ev="reg_multi_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="System\CurrentControlSet\Control\ProductOptions" dt="string" ev="^((System\\CurrentControlSet\\Control\\ProductOptions)|(System\\CurrentControlSet\\Control\\Server Applications)|(Software\\Microsoft\\Windows NT\\CurrentVersion))$" name="value" op="pattern match" result="true"/> <cis:evidence_field cv="System\CurrentControlSet\Control\Server Applications" dt="string" ev="^((System\\CurrentControlSet\\Control\\ProductOptions)|(System\\CurrentControlSet\\Control\\Server Applications)|(Software\\Microsoft\\Windows NT\\CurrentVersion))$" name="value" op="pattern match" result="true"/> <cis:evidence_field cv="Software\Microsoft\Windows NT\CurrentVersion" dt="string" ev="^((System\\CurrentControlSet\\Control\\ProductOptions)|(System\\CurrentControlSet\\Control\\Server Applications)|(Software\\Microsoft\\Windows NT\\CurrentVersion))$" name="value" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172911" value-id="xccdf_org.cisecurity.benchmarks_value_817291_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172912" value-id="xccdf_org.cisecurity.benchmarks_value_817291_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817291"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37194-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.9 |
Label: | Enforce Detail Logging for Access or Changes to Sensitive Data |
Description: | Enforce detailed audit logging for access to sensitive data or changes to sensitive data (utilizing tools such as File Integrity Monitoring or Security Information and Event Monitoring). |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.6 |
Label: | Enforce Detailed Audit Logging For Sensitive Information |
Description: | Enforce detailed audit logging for access to nonpublic data and special authentication for sensitive data. |
This policy setting determines which registry paths and sub-paths will be accessible over the network, regardless of the users or groups listed in the access control list (ACL) of the winreg registry key.
Note: In Windows XP this setting is called "Network access: Remotely accessible registry paths," the setting with that same name in Windows Vista, Windows Server 2008 (non-R2), and Windows Server 2003 does not exist in Windows XP.
Note #2: When you configure this setting you specify a list of one or more objects. The delimiter used when entering the list is a line feed or carriage return, that is, type the first object on the list, press the Enter button, type the next object, press Enter again, etc. The setting value is stored as a comma-delimited list in group policy security templates. It is also rendered as a comma-delimited list in Group Policy Editor's display pane and the Resultant Set of Policy console. It is recorded in the registry as a line-feed delimited list in a REG_MULTI_SZ value.
The recommended state for this setting is:
System\CurrentControlSet\Control\Print\Printers
System\CurrentControlSet\Services\Eventlog
Software\Microsoft\OLAP Server
Software\Microsoft\Windows NT\CurrentVersion\Print
Software\Microsoft\Windows NT\CurrentVersion\Windows
System\CurrentControlSet\Control\ContentIndex
System\CurrentControlSet\Control\Terminal Server
System\CurrentControlSet\Control\Terminal Server\UserConfig
System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration
Software\Microsoft\Windows NT\CurrentVersion\Perflib
System\CurrentControlSet\Services\SysmonLog
The recommended state for servers that hold the Active Directory Certificate Services Role with Certification Authority Role Service includes the above list and:
System\CurrentControlSet\Services\CertSvc
The recommended state for servers that have the WINS Server Feature installed includes the above list and:
System\CurrentControlSet\Services\WINS
The registry contains sensitive computer configuration information that could be used by an attacker to facilitate unauthorized activities. The fact that the default ACLs assigned throughout the registry are fairly restrictive and help to protect the registry from access by unauthorized users reduces the risk of such an attack.
To establish the recommended configuration via GP, set the following UI path to: System\CurrentControlSet\Control\Print\Printers System\CurrentControlSet\Services\Eventlog Software\Microsoft\OLAP Server Software\Microsoft\Windows NT\CurrentVersion\Print Software\Microsoft\Windows NT\CurrentVersion\Windows System\CurrentControlSet\Control\ContentIndex System\CurrentControlSet\Control\Terminal Server System\CurrentControlSet\Control\Terminal Server\UserConfig System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration Software\Microsoft\Windows NT\CurrentVersion\Perflib System\CurrentControlSet\Services\SysmonLog
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network access: Remotely accessible registry paths and sub-paths
When a server holds the Active Directory Certificate Services Role with Certification Authority Role Service, the above list should also include: System\CurrentControlSet\Services\CertSvc .
When a server has the WINS Server Feature installed, the above list should also include:
System\CurrentControlSet\Services\WINS
Impact:
None - this is the default behavior. However, if you remove the default registry paths from the list of accessible ones, remote management tools such as the Microsoft Baseline Security Analyzer and Microsoft Systems Management Server could fail, as they require remote access to the registry to properly monitor and manage computers.
Note: If you want to allow remote access, you must also enable the Remote Registry service.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.9_L1_Configure_Network_access_Remotely_accessible_registry_paths_and_sub-paths" role="full" severity="unknown" time="2020-04-22T15:48:38.680-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/9" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36347-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:38.680-05:00" start-time="2020-04-22T15:48:38.618-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Machine' is 'Windows: Registry Value' to 'System\CurrentControlSet\Control\Print\Printers,System\CurrentControlSet\Services\Eventlog,Software\Microsoft\OLAP Server,Software\Microsoft\Windows NT\CurrentVersion\Print,Software\Microsoft\Windows NT\Cu" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817307" result="true" testref="oval:org.cisecurity.benchmarks:tst:817307" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817307"> <cis:evidence_item itemref="1210"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedPaths"/> <cis:evidence_item_pk_field name="name" value="Machine"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_multi_sz" dt="string" ev="reg_multi_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="Software\Microsoft\Windows NT\CurrentVersion\Print" dt="string" ev="^((System\\CurrentControlSet\\Control\\Print\\Printers)|(System\\CurrentControlSet\\Services\\Eventlog)|(Software\\Microsoft\\OLAP Server)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Print)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Windows)|(System\\CurrentControlSet\\Control\\ContentIndex)|(System\\CurrentControlSet\\Control\\Terminal Server)|(System\\CurrentControlSet\\Control\\Terminal Server\\UserConfig)|(System\\CurrentControlSet\\Control\\Terminal Server\\DefaultUserConfiguration)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Perflib)|(System\\CurrentControlSet\\Services\\SysmonLog)|(System\\CurrentControlSet\\Services\\CertSvc)|(System\\CurrentControlSet\\Services\\WINS))$" name="value" op="pattern match" result="true"/> <cis:evidence_field cv="Software\Microsoft\Windows NT\CurrentVersion\Windows" dt="string" ev="^((System\\CurrentControlSet\\Control\\Print\\Printers)|(System\\CurrentControlSet\\Services\\Eventlog)|(Software\\Microsoft\\OLAP Server)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Print)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Windows)|(System\\CurrentControlSet\\Control\\ContentIndex)|(System\\CurrentControlSet\\Control\\Terminal Server)|(System\\CurrentControlSet\\Control\\Terminal Server\\UserConfig)|(System\\CurrentControlSet\\Control\\Terminal Server\\DefaultUserConfiguration)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Perflib)|(System\\CurrentControlSet\\Services\\SysmonLog)|(System\\CurrentControlSet\\Services\\CertSvc)|(System\\CurrentControlSet\\Services\\WINS))$" name="value" op="pattern match" result="true"/> <cis:evidence_field cv="System\CurrentControlSet\Control\Print\Printers" dt="string" ev="^((System\\CurrentControlSet\\Control\\Print\\Printers)|(System\\CurrentControlSet\\Services\\Eventlog)|(Software\\Microsoft\\OLAP Server)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Print)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Windows)|(System\\CurrentControlSet\\Control\\ContentIndex)|(System\\CurrentControlSet\\Control\\Terminal Server)|(System\\CurrentControlSet\\Control\\Terminal Server\\UserConfig)|(System\\CurrentControlSet\\Control\\Terminal Server\\DefaultUserConfiguration)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Perflib)|(System\\CurrentControlSet\\Services\\SysmonLog)|(System\\CurrentControlSet\\Services\\CertSvc)|(System\\CurrentControlSet\\Services\\WINS))$" name="value" op="pattern match" result="true"/> <cis:evidence_field cv="System\CurrentControlSet\Services\Eventlog" dt="string" ev="^((System\\CurrentControlSet\\Control\\Print\\Printers)|(System\\CurrentControlSet\\Services\\Eventlog)|(Software\\Microsoft\\OLAP Server)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Print)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Windows)|(System\\CurrentControlSet\\Control\\ContentIndex)|(System\\CurrentControlSet\\Control\\Terminal Server)|(System\\CurrentControlSet\\Control\\Terminal Server\\UserConfig)|(System\\CurrentControlSet\\Control\\Terminal Server\\DefaultUserConfiguration)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Perflib)|(System\\CurrentControlSet\\Services\\SysmonLog)|(System\\CurrentControlSet\\Services\\CertSvc)|(System\\CurrentControlSet\\Services\\WINS))$" name="value" op="pattern match" result="true"/> <cis:evidence_field cv="Software\Microsoft\OLAP Server" dt="string" ev="^((System\\CurrentControlSet\\Control\\Print\\Printers)|(System\\CurrentControlSet\\Services\\Eventlog)|(Software\\Microsoft\\OLAP Server)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Print)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Windows)|(System\\CurrentControlSet\\Control\\ContentIndex)|(System\\CurrentControlSet\\Control\\Terminal Server)|(System\\CurrentControlSet\\Control\\Terminal Server\\UserConfig)|(System\\CurrentControlSet\\Control\\Terminal Server\\DefaultUserConfiguration)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Perflib)|(System\\CurrentControlSet\\Services\\SysmonLog)|(System\\CurrentControlSet\\Services\\CertSvc)|(System\\CurrentControlSet\\Services\\WINS))$" name="value" op="pattern match" result="true"/> <cis:evidence_field cv="System\CurrentControlSet\Control\ContentIndex" dt="string" ev="^((System\\CurrentControlSet\\Control\\Print\\Printers)|(System\\CurrentControlSet\\Services\\Eventlog)|(Software\\Microsoft\\OLAP Server)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Print)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Windows)|(System\\CurrentControlSet\\Control\\ContentIndex)|(System\\CurrentControlSet\\Control\\Terminal Server)|(System\\CurrentControlSet\\Control\\Terminal Server\\UserConfig)|(System\\CurrentControlSet\\Control\\Terminal Server\\DefaultUserConfiguration)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Perflib)|(System\\CurrentControlSet\\Services\\SysmonLog)|(System\\CurrentControlSet\\Services\\CertSvc)|(System\\CurrentControlSet\\Services\\WINS))$" name="value" op="pattern match" result="true"/> <cis:evidence_field cv="System\CurrentControlSet\Control\Terminal Server" dt="string" ev="^((System\\CurrentControlSet\\Control\\Print\\Printers)|(System\\CurrentControlSet\\Services\\Eventlog)|(Software\\Microsoft\\OLAP Server)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Print)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Windows)|(System\\CurrentControlSet\\Control\\ContentIndex)|(System\\CurrentControlSet\\Control\\Terminal Server)|(System\\CurrentControlSet\\Control\\Terminal Server\\UserConfig)|(System\\CurrentControlSet\\Control\\Terminal Server\\DefaultUserConfiguration)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Perflib)|(System\\CurrentControlSet\\Services\\SysmonLog)|(System\\CurrentControlSet\\Services\\CertSvc)|(System\\CurrentControlSet\\Services\\WINS))$" name="value" op="pattern match" result="true"/> <cis:evidence_field cv="System\CurrentControlSet\Control\Terminal Server\UserConfig" dt="string" ev="^((System\\CurrentControlSet\\Control\\Print\\Printers)|(System\\CurrentControlSet\\Services\\Eventlog)|(Software\\Microsoft\\OLAP Server)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Print)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Windows)|(System\\CurrentControlSet\\Control\\ContentIndex)|(System\\CurrentControlSet\\Control\\Terminal Server)|(System\\CurrentControlSet\\Control\\Terminal Server\\UserConfig)|(System\\CurrentControlSet\\Control\\Terminal Server\\DefaultUserConfiguration)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Perflib)|(System\\CurrentControlSet\\Services\\SysmonLog)|(System\\CurrentControlSet\\Services\\CertSvc)|(System\\CurrentControlSet\\Services\\WINS))$" name="value" op="pattern match" result="true"/> <cis:evidence_field cv="System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration" dt="string" ev="^((System\\CurrentControlSet\\Control\\Print\\Printers)|(System\\CurrentControlSet\\Services\\Eventlog)|(Software\\Microsoft\\OLAP Server)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Print)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Windows)|(System\\CurrentControlSet\\Control\\ContentIndex)|(System\\CurrentControlSet\\Control\\Terminal Server)|(System\\CurrentControlSet\\Control\\Terminal Server\\UserConfig)|(System\\CurrentControlSet\\Control\\Terminal Server\\DefaultUserConfiguration)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Perflib)|(System\\CurrentControlSet\\Services\\SysmonLog)|(System\\CurrentControlSet\\Services\\CertSvc)|(System\\CurrentControlSet\\Services\\WINS))$" name="value" op="pattern match" result="true"/> <cis:evidence_field cv="Software\Microsoft\Windows NT\CurrentVersion\Perflib" dt="string" ev="^((System\\CurrentControlSet\\Control\\Print\\Printers)|(System\\CurrentControlSet\\Services\\Eventlog)|(Software\\Microsoft\\OLAP Server)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Print)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Windows)|(System\\CurrentControlSet\\Control\\ContentIndex)|(System\\CurrentControlSet\\Control\\Terminal Server)|(System\\CurrentControlSet\\Control\\Terminal Server\\UserConfig)|(System\\CurrentControlSet\\Control\\Terminal Server\\DefaultUserConfiguration)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Perflib)|(System\\CurrentControlSet\\Services\\SysmonLog)|(System\\CurrentControlSet\\Services\\CertSvc)|(System\\CurrentControlSet\\Services\\WINS))$" name="value" op="pattern match" result="true"/> <cis:evidence_field cv="System\CurrentControlSet\Services\SysmonLog" dt="string" ev="^((System\\CurrentControlSet\\Control\\Print\\Printers)|(System\\CurrentControlSet\\Services\\Eventlog)|(Software\\Microsoft\\OLAP Server)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Print)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Windows)|(System\\CurrentControlSet\\Control\\ContentIndex)|(System\\CurrentControlSet\\Control\\Terminal Server)|(System\\CurrentControlSet\\Control\\Terminal Server\\UserConfig)|(System\\CurrentControlSet\\Control\\Terminal Server\\DefaultUserConfiguration)|(Software\\Microsoft\\Windows NT\\CurrentVersion\\Perflib)|(System\\CurrentControlSet\\Services\\SysmonLog)|(System\\CurrentControlSet\\Services\\CertSvc)|(System\\CurrentControlSet\\Services\\WINS))$" name="value" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173071" value-id="xccdf_org.cisecurity.benchmarks_value_817307_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173072" value-id="xccdf_org.cisecurity.benchmarks_value_817307_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817307"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36347-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.6 |
Label: | Protect Information through Access Control Lists |
Description: | Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.9 |
Label: | Enforce Detail Logging for Access or Changes to Sensitive Data |
Description: | Enforce detailed audit logging for access to sensitive data or changes to sensitive data (utilizing tools such as File Integrity Monitoring or Security Information and Event Monitoring). |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
When enabled, this policy setting restricts anonymous access to only those shares and pipes that are named in the Network access: Named pipes that can be accessed anonymously and Network access: Shares that can be accessed anonymously settings. This policy setting controls null session access to shares on your computers by adding RestrictNullSessAccess with the value 1 in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters
registry key. This registry value toggles null session shares on or off to control whether the server service restricts unauthenticated clients' access to named resources.
The recommended state for this setting is: Enabled .
Null sessions are a weakness that can be exploited through shares (including the default shares) on computers in your environment.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network access: Restrict anonymous access to Named Pipes and Shares
Impact:
None - this is the default behavior. If you choose to enable this setting and are supporting Windows NT 4.0 domains, you should check if any of the named pipes are required to maintain trust relationships between the domains, and then add the pipe to the Network access: Named pipes that can be accessed anonymously list:
Previous to the release of Windows Server 2003 with Service Pack 1 (SP1) these named pipes were allowed anonymous access by default, but with the increased hardening in Windows Server 2003 with SP1 these pipes must be explicitly added if needed.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.10_L1_Ensure_Network_access_Restrict_anonymous_access_to_Named_Pipes_and_Shares_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:37.836-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36021-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:37.836-05:00" start-time="2020-04-22T15:48:37.774-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'RestrictNullSessAccess' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817323" result="true" testref="oval:org.cisecurity.benchmarks:tst:817323" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817323"> <cis:evidence_item itemref="1198"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SYSTEM\CurrentControlSet\Services\LanManServer\Parameters"/> <cis:evidence_item_pk_field name="name" value="RestrictNullSessAccess"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173231" value-id="xccdf_org.cisecurity.benchmarks_value_817323_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173232" value-id="xccdf_org.cisecurity.benchmarks_value_817323_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817323"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36021-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.6 |
Label: | Protect Information through Access Control Lists |
Description: | Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting allows you to restrict remote RPC connections to SAM.
The recommended state for this setting is: Administrators: Remote Access: Allow .
Note: A Windows 10 R1607, Server 2016 or newer OS is required to access and set this value in Group Policy.
To ensure that an unauthorized user cannot anonymously list local account names or groups and use the information to attempt to guess passwords or perform social engineering attacks. (Social engineering attacks try to deceive users in some way to obtain passwords or some form of security information.)
To establish the recommended configuration via GP, set the following UI path to Administrators: Remote Access: Allow :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network access: Restrict clients allowed to make remote calls to SAM
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.11_L1_Ensure_Network_access_Restrict_clients_allowed_to_make_remote_calls_to_SAM_is_set_to_Administrators_Remote_Access_Allow_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:37.930-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:37.930-05:00" start-time="2020-04-22T15:48:37.852-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'restrictremotesam' is 'Windows: Registry Value' to 'O:BAG:BAD:(A;;RC;;;BA)'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817372" result="false" testref="oval:org.cisecurity.benchmarks:tst:817372" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817372"> <cis:evidence_item itemref="1199"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SYSTEM\CurrentControlSet\Control\Lsa"/> <cis:evidence_item_pk_field name="name" value="restrictremotesam"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="O:BAG:BAD:(A" dt="string" ev="O:BAG:BAD:(A;;RC;;;BA)" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173721" value-id="xccdf_org.cisecurity.benchmarks_value_817372_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173722" value-id="xccdf_org.cisecurity.benchmarks_value_817372_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817372"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.1 |
Label: | Limit Open Ports, Protocols, and Services |
Description: | Ensure that only ports, protocols, and services with validated business needs are running on each system. |
This policy setting determines which network shares can be accessed by anonymous users. The default configuration for this policy setting has little effect because all users have to be authenticated before they can access shared resources on the server.
The recommended state for this setting is: <blank> (i.e. None).
It is very dangerous to allow any values in this setting. Any shares that are listed can be accessed by any network user, which could lead to the exposure or corruption of sensitive data.
To establish the recommended configuration via GP, set the following UI path to <blank> (i.e. None):
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network access: Shares that can be accessed anonymously
Impact:
None - this is the default behavior.
Any of the following tests or sub-groups may pass: | ||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.12_L1_Ensure_Network_access_Shares_that_can_be_accessed_anonymously_is_set_to_None" role="full" severity="unknown" time="2020-04-22T15:48:38.008-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38095-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:38.008-05:00" start-time="2020-04-22T15:48:37.930-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="none_exist" comment="Ensure 'NullSessionShares' is 'Existence Test' to 'none_exist'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817351" result="false" testref="oval:org.cisecurity.benchmarks:tst:817351" type="registry_test"> <cis:evidence_object> <cis:evidence_item itemref="1200"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\LanManServer\Parameters"/> <cis:evidence_item_pk_field name="name" value="NullSessionShares"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NullSessionShares' is 'Windows: Registry Value' to '^$'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817344" result="true" testref="oval:org.cisecurity.benchmarks:tst:817344" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817344"> <cis:evidence_item itemref="1201"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\LanManServer\Parameters"/> <cis:evidence_item_pk_field name="name" value="NullSessionShares"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_multi_sz" dt="string" ev="reg_multi_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="" dt="string" ev="^$" name="value" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173441" value-id="xccdf_org.cisecurity.benchmarks_value_817344_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173442" value-id="xccdf_org.cisecurity.benchmarks_value_817344_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817344"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817351"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38095-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.6 |
Label: | Protect Information through Access Control Lists |
Description: | Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting determines how network logons that use local accounts are authenticated. The Classic option allows precise control over access to resources, including the ability to assign different types of access to different users for the same resource. The Guest only option allows you to treat all users equally. In this context, all users authenticate as Guest only to receive the same access level to a given resource.
The recommended state for this setting is: Classic - local users authenticate as themselves .
Note: This setting does not affect interactive logons that are performed remotely by using such services as Telnet or Remote Desktop Services (formerly called Terminal Services).
With the Guest only model, any user who can authenticate to your computer over the network does so with guest privileges, which probably means that they will not have write access to shared resources on that computer. Although this restriction does increase security, it makes it more difficult for authorized users to access shared resources on those computers because ACLs on those resources must include access control entries (ACEs) for the Guest account. With the Classic model, local accounts should be password protected. Otherwise, if Guest access is enabled, anyone can use those user accounts to access shared system resources.
To establish the recommended configuration via GP, set the following UI path to Classic - local users authenticate as themselves :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network access: Sharing and security model for local accounts
Impact:
None - this is the default configuration for domain-joined computers.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.10.13_L1_Ensure_Network_access_Sharing_and_security_model_for_local_accounts_is_set_to_Classic_-_local_users_authenticate_as_themselves" role="full" severity="unknown" time="2020-04-22T15:48:38.086-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37623-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:38.086-05:00" start-time="2020-04-22T15:48:38.008-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ForceGuest' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817360" result="true" testref="oval:org.cisecurity.benchmarks:tst:817360" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817360"> <cis:evidence_item itemref="1202"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa"/> <cis:evidence_item_pk_field name="name" value="ForceGuest"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173601" value-id="xccdf_org.cisecurity.benchmarks_value_817360_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173602" value-id="xccdf_org.cisecurity.benchmarks_value_817360_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817360"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37623-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This section contains recommendations related to network security.
This policy setting determines whether Local System services that use Negotiate when reverting to NTLM authentication can use the computer identity. This policy is supported on at least Windows 7 or Windows Server 2008 R2.
The recommended state for this setting is: Enabled .
When connecting to computers running versions of Windows earlier than Windows Vista or Windows Server 2008 (non-R2), services running as Local System and using SPNEGO (Negotiate) that revert to NTLM use the computer identity. In Windows 7, if you are connecting to a computer running Windows Server 2008 or Windows Vista, then a system service uses either the computer identity or a NULL session. When connecting with a NULL session, a system-generated session key is created, which provides no protection but allows applications to sign and encrypt data without errors. When connecting with the computer identity, both signing and encryption is supported in order to provide data protection.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network security: Allow Local System to use computer identity for NTLM
Impact:
Services running as Local System that use Negotiate when reverting to NTLM authentication will use the computer identity. This might cause some authentication requests between Windows operating systems to fail and log an error.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.1_L1_Ensure_Network_security_Allow_Local_System_to_use_computer_identity_for_NTLM_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:38.805-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38341-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:38.805-05:00" start-time="2020-04-22T15:48:38.743-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'UseMachineId' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817207" result="true" testref="oval:org.cisecurity.benchmarks:tst:817207" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817207"> <cis:evidence_item itemref="1212"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa"/> <cis:evidence_item_pk_field name="name" value="UseMachineId"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172071" value-id="xccdf_org.cisecurity.benchmarks_value_817207_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172072" value-id="xccdf_org.cisecurity.benchmarks_value_817207_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817207"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38341-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
This policy setting determines whether NTLM is allowed to fall back to a NULL session when used with LocalSystem.
The recommended state for this setting is: Disabled .
NULL sessions are less secure because by definition they are unauthenticated.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network security: Allow LocalSystem NULL session fallback
Impact:
Any applications that require NULL sessions for LocalSystem will not work as designed.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.2_L1_Ensure_Network_security_Allow_LocalSystem_NULL_session_fallback_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:38.868-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37035-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:38.868-05:00" start-time="2020-04-22T15:48:38.805-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowNullSessionFallback' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817213" result="true" testref="oval:org.cisecurity.benchmarks:tst:817213" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817213"> <cis:evidence_item itemref="1213"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa\MSV1_0"/> <cis:evidence_item_pk_field name="name" value="AllowNullSessionFallback"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172131" value-id="xccdf_org.cisecurity.benchmarks_value_817213_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172132" value-id="xccdf_org.cisecurity.benchmarks_value_817213_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817213"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37035-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
This setting determines if online identities are able to authenticate to this computer.
The Public Key Cryptography Based User-to-User (PKU2U) protocol introduced in Windows 7 and Windows Server 2008 R2 is implemented as a security support provider (SSP). The SSP enables peer-to-peer authentication, particularly through the Windows 7 media and file sharing feature called HomeGroup, which permits sharing between computers that are not members of a domain.
With PKU2U, a new extension was introduced to the Negotiate authentication package, Spnego.dll . In previous versions of Windows, Negotiate decided whether to use Kerberos or NTLM for authentication. The extension SSP for Negotiate, Negoexts.dll , which is treated as an authentication protocol by Windows, supports Microsoft SSPs including PKU2U.
When computers are configured to accept authentication requests by using online IDs, Negoexts.dll calls the PKU2U SSP on the computer that is used to log on. The PKU2U SSP obtains a local certificate and exchanges the policy between the peer computers. When validated on the peer computer, the certificate within the metadata is sent to the logon peer for validation and associates the user's certificate to a security token and the logon process completes.
The recommended state for this setting is: Disabled .
The PKU2U protocol is a peer-to-peer authentication protocol - authentication should be managed centrally in most managed networks.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network Security: Allow PKU2U authentication requests to this computer to use online identities
Impact:
None - this is the default configuration for domain-joined computers.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.3_L1_Ensure_Network_Security_Allow_PKU2U_authentication_requests_to_this_computer_to_use_online_identities_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:38.930-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38047-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:38.930-05:00" start-time="2020-04-22T15:48:38.868-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowOnlineID' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817219" result="true" testref="oval:org.cisecurity.benchmarks:tst:817219" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817219"> <cis:evidence_item itemref="1214"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa\pku2u"/> <cis:evidence_item_pk_field name="name" value="AllowOnlineID"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172191" value-id="xccdf_org.cisecurity.benchmarks_value_817219_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172192" value-id="xccdf_org.cisecurity.benchmarks_value_817219_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817219"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38047-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.9 |
Label: | Configure Account Access Centrally |
Description: | Configure access for all accounts through a centralized point of authentication, for example Active Directory or LDAP. Configure network and security devices for centralized authentication as well. |
This policy setting allows you to set the encryption types that Kerberos is allowed to use.
The recommended state for this setting is: AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types .
The strength of each encryption algorithm varies from one to the next, choosing stronger algorithms will reduce the risk of compromise however doing so may cause issues when the computer attempts to authenticate with systems that do not support them.
To establish the recommended configuration via GP, set the following UI path to AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network security: Configure encryption types allowed for Kerberos
Impact:
If not selected, the encryption type will not be allowed. This setting may affect compatibility with client computers or services and applications. Multiple selections are permitted.
Note: Some legacy applications and OSes may require RC4_HMAC_MD5 - we recommend you test in your environment and verify whether you can safely remove it.
Note #2: Windows Server 2008 (non-R2) and below allow DES for Kerberos by default, but later OS versions do not.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.4_L1_Ensure_Network_security_Configure_encryption_types_allowed_for_Kerberos_is_set_to_AES128_HMAC_SHA1_AES256_HMAC_SHA1_Future_encryption_types" role="full" severity="unknown" time="2020-04-22T15:48:39.008-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37755-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817225" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'SupportedEncryptionTypes' is 'Windows: Registry Value' to '2147483640'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817225" result="true" testref="oval:org.cisecurity.benchmarks:tst:817225" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817225"> <cis:evidence_item itemref="1215"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters"/> <cis:evidence_item_pk_field name="name" value="SupportedEncryptionTypes"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="2147483640" dt="int" ev="2147483640" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172251" value-id="xccdf_org.cisecurity.benchmarks_value_817225_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172252" value-id="xccdf_org.cisecurity.benchmarks_value_817225_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817225"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37755-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Encrypt or Hash all Authentication Credentials |
Description: | Encrypt or hash with a salt all authentication credentials when stored. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.14 |
Label: | Encrypt/Hash All Authentication Files And Monitor Their Access |
Description: | Verify that all authentication files are encrypted or hashed and that these files cannot be accessed without root or administrator privileges. Audit all access to password files in the system. |
This policy setting determines whether the LAN Manager (LM) hash value for the new password is stored when the password is changed. The LM hash is relatively weak and prone to attack compared to the cryptographically stronger Microsoft Windows NT hash. Since LM hashes are stored on the local computer in the security database, passwords can then be easily compromised if the database is attacked.
Note: Older operating systems and some third-party applications may fail when this policy setting is enabled. Also, note that the password will need to be changed on all accounts after you enable this setting to gain the proper benefit.
The recommended state for this setting is: Enabled .
The SAM file can be targeted by attackers who seek access to username and password hashes. Such attacks use special tools to crack passwords, which can then be used to impersonate users and gain access to resources on your network. These types of attacks will not be prevented if you enable this policy setting, but it will be much more difficult for these types of attacks to succeed.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network security: Do not store LAN Manager hash value on next password change
Impact:
None - this is the default behavior. Earlier operating systems such as Windows 95, Windows 98, and Windows ME as well as some third-party applications will fail.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.5_L1_Ensure_Network_security_Do_not_store_LAN_Manager_hash_value_on_next_password_change_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:39.071-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36326-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.071-05:00" start-time="2020-04-22T15:48:39.008-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoLMHash' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817231" result="true" testref="oval:org.cisecurity.benchmarks:tst:817231" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817231"> <cis:evidence_item itemref="1216"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa"/> <cis:evidence_item_pk_field name="name" value="NoLMHash"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172311" value-id="xccdf_org.cisecurity.benchmarks_value_817231_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172312" value-id="xccdf_org.cisecurity.benchmarks_value_817231_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817231"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36326-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Encrypt or Hash all Authentication Credentials |
Description: | Encrypt or hash with a salt all authentication credentials when stored. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.14 |
Label: | Encrypt/Hash All Authentication Files And Monitor Their Access |
Description: | Verify that all authentication files are encrypted or hashed and that these files cannot be accessed without root or administrator privileges. Audit all access to password files in the system. |
LAN Manager (LM) was a family of early Microsoft client/server software (predating Windows NT) that allowed users to link personal computers together on a single network. LM network capabilities included transparent file and print sharing, user security features, and network administration tools. In Active Directory domains, the Kerberos protocol is the default authentication protocol. However, if the Kerberos protocol is not negotiated for some reason, Active Directory will use LM, NTLM, or NTLMv2. LAN Manager authentication includes the LM, NTLM, and NTLM version 2 (NTLMv2) variants, and is the protocol that is used to authenticate all Windows clients when they perform the following operations:
The Network security: LAN Manager authentication level setting determines which challenge/response authentication protocol is used for network logons. This choice affects the level of authentication protocol used by clients, the level of session security negotiated, and the level of authentication accepted by servers.
The recommended state for this setting is: Send NTLMv2 response only. Refuse LM & NTLM .
Windows 2000 and Windows XP clients were configured by default to send LM and NTLM authentication responses (Windows 95-based and Windows 98-based clients only send LM). The default settings in OSes predating Windows Vista / Windows Server 2008 (non-R2) allowed all clients to authenticate with servers and use their resources. However, this meant that LM responses - the weakest form of authentication response - were sent over the network, and it was potentially possible for attackers to sniff that traffic to more easily reproduce the user's password.
The Windows 95, Windows 98, and Windows NT operating systems cannot use the Kerberos version 5 protocol for authentication. For this reason, in a Windows Server 2003 domain, these computers authenticate by default with both the LM and NTLM protocols for network authentication. You can enforce a more secure authentication protocol for Windows 95, Windows 98, and Windows NT by using NTLMv2. For the logon process, NTLMv2 uses a secure channel to protect the authentication process. Even if you use NTLMv2 for older clients and servers, Windows-based clients and servers that are members of the domain will use the Kerberos authentication protocol to authenticate with Windows Server 2003 or newer Domain Controllers. For these reasons, it is strongly preferred to restrict the use of LM & NTLM (non-v2) as much as possible.
To establish the recommended configuration via GP, set the following UI path to: Send NTLMv2 response only. Refuse LM & NTLM :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LAN Manager authentication level
Impact:
Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it; Domain Controllers refuse LM and NTLM (accept only NTLMv2 authentication). Clients that do not support NTLMv2 authentication will not be able to authenticate in the domain and access domain resources by using LM and NTLM.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.7_L1_Ensure_Network_security_LAN_Manager_authentication_level_is_set_to_Send_NTLMv2_response_only._Refuse_LM__NTLM" role="full" severity="unknown" time="2020-04-22T15:48:39.133-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36173-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.133-05:00" start-time="2020-04-22T15:48:39.071-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LmCompatibilityLevel' is 'Windows: Registry Value' to '5'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817238" result="false" testref="oval:org.cisecurity.benchmarks:tst:817238" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817238"> <cis:evidence_item itemref="1217"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa"/> <cis:evidence_item_pk_field name="name" value="LmCompatibilityLevel"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="5" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172381" value-id="xccdf_org.cisecurity.benchmarks_value_817238_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172382" value-id="xccdf_org.cisecurity.benchmarks_value_817238_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817238"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36173-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting determines the level of data signing that is requested on behalf of clients that issue LDAP BIND requests.
Note: This policy setting does not have any impact on LDAP simple bind ( ldap_simple_bind ) or LDAP simple bind through SSL ( ldap_simple_bind_s ). No Microsoft LDAP clients that are included with Windows XP Professional use ldap_simple_bind or ldap_simple_bind_s to communicate with a Domain Controller.
The recommended state for this setting is: Negotiate signing . Configuring this setting to Require signing also conforms to the benchmark.
Unsigned network traffic is susceptible to man-in-the-middle attacks in which an intruder captures the packets between the client and server, modifies them, and then forwards them to the server. For an LDAP server, this susceptibility means that an attacker could cause a server to make decisions that are based on false or altered data from the LDAP queries. To lower this risk in your network, you can implement strong physical security measures to protect the network infrastructure. Also, you can make all types of man-in-the-middle attacks extremely difficult if you require digital signatures on all network packets by means of IPsec authentication headers.
To establish the recommended configuration via GP, set the following UI path to Negotiate signing (configuring to Require signing also conforms to the benchmark):
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LDAP client signing requirements
Impact:
None - this is the default behavior. However, if you choose instead to configure the server to require LDAP signatures then you must also configure the client. If you do not configure the client it will not be able to communicate with the server, which could cause many features to fail, including user authentication, Group Policy, and logon scripts, because the caller will be told that the LDAP BIND command request failed.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.8_L1_Ensure_Network_security_LDAP_client_signing_requirements_is_set_to_Negotiate_signing_or_higher" role="full" severity="unknown" time="2020-04-22T15:48:39.196-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36858-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.196-05:00" start-time="2020-04-22T15:48:39.133-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LDAPClientIntegrity' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817248" result="true" testref="oval:org.cisecurity.benchmarks:tst:817248" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817248"> <cis:evidence_item itemref="1218"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\LDAP"/> <cis:evidence_item_pk_field name="name" value="LDAPClientIntegrity"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172481" value-id="xccdf_org.cisecurity.benchmarks_value_817248_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172482" value-id="xccdf_org.cisecurity.benchmarks_value_817248_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817248"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36858-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting determines which behaviors are allowed by clients for applications using the NTLM Security Support Provider (SSP). The SSP Interface (SSPI) is used by applications that need authentication services. The setting does not modify how the authentication sequence works but instead require certain behaviors in applications that use the SSPI.
The recommended state for this setting is: Require NTLMv2 session security, Require 128-bit encryption .
Note: These values are dependent on the Network security: LAN Manager Authentication Level (Rule 2.3.11.7) security setting value.
You can enable both options for this policy setting to help protect network traffic that uses the NTLM Security Support Provider (NTLM SSP) from being exposed or tampered with by an attacker who has gained access to the same network. In other words, these options help protect against man-in-the-middle attacks.
To establish the recommended configuration via GP, set the following UI path to Require NTLMv2 session security, Require 128-bit encryption :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network security: Minimum session security for NTLM SSP based (including secure RPC) clients
Impact:
NTLM connections will fail if NTLMv2 protocol and strong encryption (128-bit) are not both negotiated. Client applications that are enforcing these settings will be unable to communicate with older servers that do not support them. This setting could impact Windows Clustering when applied to servers running Windows Server 2003, see Microsoft Knowledge Base article 890761: You receive an "Error 0x8007042b" error message when you add or join a node to a cluster if you use NTLM version 2 in Windows Server 2003 for more information on possible issues and how to resolve them.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.9_L1_Ensure_Network_security_Minimum_session_security_for_NTLM_SSP_based_including_secure_RPC_clients_is_set_to_Require_NTLMv2_session_security_Require_128-bit_encryption" role="full" severity="unknown" time="2020-04-22T15:48:39.274-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37553-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.274-05:00" start-time="2020-04-22T15:48:39.196-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NTLMMinClientSec' is 'Windows: Registry Value' to '537395200'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817254" result="true" testref="oval:org.cisecurity.benchmarks:tst:817254" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817254"> <cis:evidence_item itemref="1219"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa\MSV1_0"/> <cis:evidence_item_pk_field name="name" value="NTLMMinClientSec"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="537395200" dt="int" ev="537395200" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172541" value-id="xccdf_org.cisecurity.benchmarks_value_817254_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172542" value-id="xccdf_org.cisecurity.benchmarks_value_817254_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817254"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37553-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting determines which behaviors are allowed by servers for applications using the NTLM Security Support Provider (SSP). The SSP Interface (SSPI) is used by applications that need authentication services. The setting does not modify how the authentication sequence works but instead require certain behaviors in applications that use the SSPI.
The recommended state for this setting is: Require NTLMv2 session security, Require 128-bit encryption .
Note: These values are dependent on the Network security: LAN Manager Authentication Level (Rule 2.3.11.7) security setting value.
You can enable all of the options for this policy setting to help protect network traffic that uses the NTLM Security Support Provider (NTLM SSP) from being exposed or tampered with by an attacker who has gained access to the same network. That is, these options help protect against man-in-the-middle attacks.
To establish the recommended configuration via GP, set the following UI path to Require NTLMv2 session security, Require 128-bit encryption :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network security: Minimum session security for NTLM SSP based (including secure RPC) servers
Impact:
NTLM connections will fail if NTLMv2 protocol and strong encryption (128-bit) are not both negotiated. Server applications that are enforcing these settings will be unable to communicate with older servers that do not support them. This setting could impact Windows Clustering when applied to servers running Windows Server 2003, see Microsoft Knowledge Base article 890761: You receive an "Error 0x8007042b" error message when you add or join a node to a cluster if you use NTLM version 2 in Windows Server 2003 for more information on possible issues and how to resolve them.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.11.10_L1_Ensure_Network_security_Minimum_session_security_for_NTLM_SSP_based_including_secure_RPC_servers_is_set_to_Require_NTLMv2_session_security_Require_128-bit_encryption" role="full" severity="unknown" time="2020-04-22T15:48:38.743-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37835-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:38.743-05:00" start-time="2020-04-22T15:48:38.680-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NTLMMinServerSec' is 'Windows: Registry Value' to '537395200'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817259" result="true" testref="oval:org.cisecurity.benchmarks:tst:817259" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817259"> <cis:evidence_item itemref="1211"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Lsa\MSV1_0"/> <cis:evidence_item_pk_field name="name" value="NTLMMinServerSec"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="537395200" dt="int" ev="537395200" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172591" value-id="xccdf_org.cisecurity.benchmarks_value_817259_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172592" value-id="xccdf_org.cisecurity.benchmarks_value_817259_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817259"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37835-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section contains recommendations related to the Windows shutdown functionality.
This policy setting determines whether a computer can be shut down when a user is not logged on. If this policy setting is enabled, the shutdown command is available on the Windows logon screen. It is recommended to disable this policy setting to restrict the ability to shut down the computer to users with credentials on the system.
The recommended state for this setting is: Disabled .
Note: In Server 2008 R2 and older versions, this setting had no impact on Remote Desktop (RDP) / Terminal Services sessions - it only affected the local console. However, Microsoft changed the behavior in Windows Server 2012 (non-R2) and above, where if set to Enabled, RDP sessions are also allowed to shut down or restart the server.
Users who can access the console locally could shut down the computer. Attackers could also walk to the local console and restart the server, which would cause a temporary DoS condition. Attackers could also shut down the server and leave all of its applications and services unavailable. As noted in the Description above, the Denial of Service (DoS) risk of enabling this setting dramatically increases in Windows Server 2012 (non-R2) and above, as even remote users could then shut down or restart the server from the logon screen of an RDP session.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Shutdown: Allow system to be shut down without having to log on
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.13.1_L1_Ensure_Shutdown_Allow_system_to_be_shut_down_without_having_to_log_on_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:39.336-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36788-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.336-05:00" start-time="2020-04-22T15:48:39.274-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ShutdownWithoutLogon' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817220" result="true" testref="oval:org.cisecurity.benchmarks:tst:817220" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817220"> <cis:evidence_item itemref="1220"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="ShutdownWithoutLogon"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172201" value-id="xccdf_org.cisecurity.benchmarks_value_817220_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172202" value-id="xccdf_org.cisecurity.benchmarks_value_817220_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817220"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36788-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section contains recommendations related to system objects.
This policy setting determines whether case insensitivity is enforced for all subsystems. The Microsoft Win32 subsystem is case insensitive. However, the kernel supports case sensitivity for other subsystems, such as the Portable Operating System Interface for UNIX (POSIX). Because Windows is case insensitive (but the POSIX subsystem will support case sensitivity), failure to enforce this policy setting makes it possible for a user of the POSIX subsystem to create a file with the same name as another file by using mixed case to label it. Such a situation can block access to these files by another user who uses typical Win32 tools, because only one of the files will be available.
The recommended state for this setting is: Enabled .
Because Windows is case-insensitive but the POSIX subsystem will support case sensitivity, failure to enable this policy setting would make it possible for a user of that subsystem to create a file with the same name as another file but with a different mix of upper and lower case letters. Such a situation could potentially confuse users when they try to access such files from normal Win32 tools because only one of the files will be available.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\System objects: Require case insensitivity for non-Windows subsystems
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.15.1_L1_Ensure_System_objects_Require_case_insensitivity_for_non-Windows_subsystems_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:39.399-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37885-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.399-05:00" start-time="2020-04-22T15:48:39.336-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ObCaseInsensitive' is equal to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817221" result="true" testref="oval:org.cisecurity.benchmarks:tst:817221" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817221"> <cis:evidence_item itemref="1221"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Session Manager\Kernel"/> <cis:evidence_item_pk_field name="name" value="ObCaseInsensitive"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172211" value-id="xccdf_org.cisecurity.benchmarks_value_817221_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172212" value-id="xccdf_org.cisecurity.benchmarks_value_817221_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817221"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37885-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
This policy setting determines the strength of the default discretionary access control list (DACL) for objects. Active Directory maintains a global list of shared system resources, such as DOS device names, mutexes, and semaphores. In this way, objects can be located and shared among processes. Each type of object is created with a default DACL that specifies who can access the objects and what permissions are granted.
The recommended state for this setting is: Enabled .
This setting determines the strength of the default DACL for objects. Windows maintains a global list of shared computer resources so that objects can be located and shared among processes. Each type of object is created with a default DACL that specifies who can access the objects and with what permissions.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\System objects: Strengthen default permissions of internal system objects (e.g. Symbolic Links)
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.15.2_L1_Ensure_System_objects_Strengthen_default_permissions_of_internal_system_objects_e.g._Symbolic_Links_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:39.477-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37644-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.477-05:00" start-time="2020-04-22T15:48:39.399-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ProtectionMode' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817227" result="true" testref="oval:org.cisecurity.benchmarks:tst:817227" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817227"> <cis:evidence_item itemref="1222"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Control\Session Manager"/> <cis:evidence_item_pk_field name="name" value="ProtectionMode"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172271" value-id="xccdf_org.cisecurity.benchmarks_value_817227_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172272" value-id="xccdf_org.cisecurity.benchmarks_value_817227_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817227"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37644-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.6 |
Label: | Protect Information through Access Control Lists |
Description: | Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.4 |
Label: | Protect Information With Access Control Lists |
Description: | All information stored on systems shall be protected with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principal that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section contains recommendations related to User Account Control.
This policy setting controls the behavior of Admin Approval Mode for the built-in Administrator account.
The recommended state for this setting is: Enabled .
One of the risks that the User Account Control feature introduced with Windows Vista is trying to mitigate is that of malicious software running under elevated credentials without the user or administrator being aware of its activity. An attack vector for these programs was to discover the password of the account named "Administrator" because that user account was created for all installations of Windows. To address this risk, in Windows Vista and newer, the built-in Administrator account is now disabled by default. In a default installation of a new computer, accounts with administrative control over the computer are initially set up in one of two ways:
Once Windows is installed, the built-in Administrator account may be manually enabled, but we strongly recommend that this account remain disabled.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\User Account Control: Admin Approval Mode for the Built-in Administrator account
Impact:
The built-in Administrator account uses Admin Approval Mode. Users that log on using the local Administrator account will be prompted for consent whenever a program requests an elevation in privilege, just like any other user would.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.1_L1_Ensure_User_Account_Control_Admin_Approval_Mode_for_the_Built-in_Administrator_account_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:39.539-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36494-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.539-05:00" start-time="2020-04-22T15:48:39.477-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'FilterAdministratorToken' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817232" result="true" testref="oval:org.cisecurity.benchmarks:tst:817232" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817232"> <cis:evidence_item itemref="1223"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="FilterAdministratorToken"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172321" value-id="xccdf_org.cisecurity.benchmarks_value_817232_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172322" value-id="xccdf_org.cisecurity.benchmarks_value_817232_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817232"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36494-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting controls the behavior of the elevation prompt for administrators.
The recommended state for this setting is: Prompt for consent on the secure desktop .
One of the risks that the UAC feature introduced with Windows Vista is trying to mitigate is that of malicious software running under elevated credentials without the user or administrator being aware of its activity. This setting raises awareness to the administrator of elevated privilege operations and permits the administrator to prevent a malicious program from elevating its privilege when the program attempts to do so.
To establish the recommended configuration via GP, set the following UI path to Prompt for consent on the secure desktop :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode
Impact:
When an operation (including execution of a Windows binary) requires elevation of privilege, the user is prompted on the secure desktop to select either Permit or Deny. If the user selects Permit, the operation continues with the user's highest available privilege.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.2_L1_Ensure_User_Account_Control_Behavior_of_the_elevation_prompt_for_administrators_in_Admin_Approval_Mode_is_set_to_Prompt_for_consent_on_the_secure_desktop" role="full" severity="unknown" time="2020-04-22T15:48:39.618-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37029-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.618-05:00" start-time="2020-04-22T15:48:39.555-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ConsentPromptBehaviorAdmin' is 'Windows: Registry Value' to '2'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817242" result="true" testref="oval:org.cisecurity.benchmarks:tst:817242" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817242"> <cis:evidence_item itemref="1224"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="ConsentPromptBehaviorAdmin"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="2" dt="int" ev="2" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172421" value-id="xccdf_org.cisecurity.benchmarks_value_817242_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172422" value-id="xccdf_org.cisecurity.benchmarks_value_817242_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817242"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37029-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting controls the behavior of the elevation prompt for standard users.
The recommended state for this setting is: Automatically deny elevation requests .
One of the risks that the User Account Control feature introduced with Windows Vista is trying to mitigate is that of malicious programs running under elevated credentials without the user or administrator being aware of their activity. This setting raises awareness to the user that a program requires the use of elevated privilege operations and requires that the user be able to supply administrative credentials in order for the program to run.
To establish the recommended configuration via GP, set the following UI path to Automatically deny elevation requests:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\User Account Control: Behavior of the elevation prompt for standard users
Impact:
When an operation requires elevation of privilege, a configurable access denied error message is displayed. An enterprise that is running desktops as standard user may choose this setting to reduce help desk calls.
Note: With this setting configured as recommended, the default error message displayed when a user attempts to perform an operation or run a program requiring privilege elevation (without Administrator rights) is " This program will not run. This program is blocked by group policy. For more information, contact your system administrator. " Some users who are not used to seeing this message may believe that the operation or program they attempted to run is specifically blocked by group policy, as that is what the message seems to imply. This message may therefore result in user questions as to why that specific operation/program is blocked, when in fact, the problem is that they need to perform the operation or run the program with an Administrative account (or "Run as Administrator" if it is already an Administrator account), and they are not doing that.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.3_L1_Ensure_User_Account_Control_Behavior_of_the_elevation_prompt_for_standard_users_is_set_to_Automatically_deny_elevation_requests" role="full" severity="unknown" time="2020-04-22T15:48:39.680-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36864-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.680-05:00" start-time="2020-04-22T15:48:39.618-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ConsentPromptBehaviorUser' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817262" result="true" testref="oval:org.cisecurity.benchmarks:tst:817262" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817262"> <cis:evidence_item itemref="1225"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="ConsentPromptBehaviorUser"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172621" value-id="xccdf_org.cisecurity.benchmarks_value_817262_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172622" value-id="xccdf_org.cisecurity.benchmarks_value_817262_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817262"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36864-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting controls the behavior of application installation detection for the computer.
The recommended state for this setting is: Enabled .
Some malicious software will attempt to install itself after being given permission to run. For example, malicious software with a trusted application shell. The user may have given permission for the program to run because the program is trusted, but if they are then prompted for installation of an unknown component this provides another way of trapping the software before it can do damage
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\User Account Control: Detect application installations and prompt for elevation
Impact:
When an application installation package is detected that requires elevation of privilege, the user is prompted to enter an administrative user name and password. If the user enters valid credentials, the operation continues with the applicable privilege.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.4_L1_Ensure_User_Account_Control_Detect_application_installations_and_prompt_for_elevation_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:39.743-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/2/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/2/subcontrol/7" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36533-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.743-05:00" start-time="2020-04-22T15:48:39.680-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableInstallerDetection' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817278" result="true" testref="oval:org.cisecurity.benchmarks:tst:817278" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817278"> <cis:evidence_item itemref="1226"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="EnableInstallerDetection"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172781" value-id="xccdf_org.cisecurity.benchmarks_value_817278_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172782" value-id="xccdf_org.cisecurity.benchmarks_value_817278_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817278"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36533-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that all unauthorized and unmanaged software is found and prevented from installation or execution. |
Subcontrol: | 2.6 |
Label: | Address unapproved software |
Description: | Ensure that unauthorized software is either removed or the inventory is updated in a timely manner |
CIS Control Information | |
---|---|
Control: | Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that all unauthorized and unmanaged software is found and prevented from installation or execution. |
Subcontrol: | 2.7 |
Label: | Utilize Application Whitelisting |
Description: | Utilize application whitelisting technology on all assets to ensure that only authorized software executes and all unauthorized software is blocked from executing on assets. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting controls whether applications that request to run with a User Interface Accessibility (UIAccess) integrity level must reside in a secure location in the file system. Secure locations are limited to the following:
Note: Windows enforces a public key infrastructure (PKI) signature check on any interactive application that requests to run with a UIAccess integrity level regardless of the state of this security setting.
The recommended state for this setting is: Enabled .
UIAccess Integrity allows an application to bypass User Interface Privilege Isolation (UIPI) restrictions when an application is elevated in privilege from a standard user to an administrator. This is required to support accessibility features such as screen readers that are transmitting user interfaces to alternative forms. A process that is started with UIAccess rights has the following abilities:
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\User Account Control: Only elevate UIAccess applications that are installed in secure locations
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.5_L1_Ensure_User_Account_Control_Only_elevate_UIAccess_applications_that_are_installed_in_secure_locations_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:39.805-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37057-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.805-05:00" start-time="2020-04-22T15:48:39.743-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableSecureUIAPaths' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817292" result="true" testref="oval:org.cisecurity.benchmarks:tst:817292" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817292"> <cis:evidence_item itemref="1227"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="EnableSecureUIAPaths"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172921" value-id="xccdf_org.cisecurity.benchmarks_value_817292_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172922" value-id="xccdf_org.cisecurity.benchmarks_value_817292_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817292"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37057-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting controls the behavior of all User Account Control (UAC) policy settings for the computer. If you change this policy setting, you must restart your computer.
The recommended state for this setting is: Enabled .
Note: If this policy setting is disabled, the Security Center notifies you that the overall security of the operating system has been reduced.
This is the setting that turns on or off UAC. If this setting is disabled, UAC will not be used and any security benefits and risk mitigations that are dependent on UAC will not be present on the system.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\User Account Control: Run all administrators in Admin Approval Mode
Impact:
None - this is the default behavior. Users and administrators will need to learn to work with UAC prompts and adjust their work habits to use least privilege operations.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.6_L1_Ensure_User_Account_Control_Run_all_administrators_in_Admin_Approval_Mode_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:39.883-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36869-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.883-05:00" start-time="2020-04-22T15:48:39.805-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableLUA' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817303" result="true" testref="oval:org.cisecurity.benchmarks:tst:817303" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817303"> <cis:evidence_item itemref="1228"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="EnableLUA"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173031" value-id="xccdf_org.cisecurity.benchmarks_value_817303_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173032" value-id="xccdf_org.cisecurity.benchmarks_value_817303_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817303"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36869-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting controls whether the elevation request prompt is displayed on the interactive user's desktop or the secure desktop.
The recommended state for this setting is: Enabled .
Standard elevation prompt dialog boxes can be spoofed, which may cause users to disclose their passwords to malicious software. The secure desktop presents a very distinct appearance when prompting for elevation, where the user desktop dims, and the elevation prompt UI is more prominent. This increases the likelihood that users who become accustomed to the secure desktop will recognize a spoofed elevation prompt dialog box and not fall for the trick.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\User Account Control: Switch to the secure desktop when prompting for elevation
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.7_L1_Ensure_User_Account_Control_Switch_to_the_secure_desktop_when_prompting_for_elevation_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:39.946-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36866-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:39.946-05:00" start-time="2020-04-22T15:48:39.883-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'PromptOnSecureDesktop' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817317" result="true" testref="oval:org.cisecurity.benchmarks:tst:817317" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817317"> <cis:evidence_item itemref="1229"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="PromptOnSecureDesktop"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173171" value-id="xccdf_org.cisecurity.benchmarks_value_817317_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173172" value-id="xccdf_org.cisecurity.benchmarks_value_817317_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817317"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36866-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This policy setting controls whether application write failures are redirected to defined registry and file system locations. This policy setting mitigates applications that run as administrator and write run-time application data to:
The recommended state for this setting is: Enabled .
This setting reduces vulnerabilities by ensuring that legacy applications only write data to permitted locations.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\User Account Control: Virtualize file and registry write failures to per-user locations
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_2.3.17.8_L1_Ensure_User_Account_Control_Virtualize_file_and_registry_write_failures_to_per-user_locations_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:40.008-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37064-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:40.008-05:00" start-time="2020-04-22T15:48:39.946-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableVirtualization' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817333" result="true" testref="oval:org.cisecurity.benchmarks:tst:817333" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817333"> <cis:evidence_item itemref="1230"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="EnableVirtualization"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173331" value-id="xccdf_org.cisecurity.benchmarks_value_817333_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173332" value-id="xccdf_org.cisecurity.benchmarks_value_817333_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817333"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37064-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section contains recommendations for configuring the Windows Firewall.
This section contains recommendations for the Domain Profile of the Windows Firewall.
Select On (recommended) to have Windows Firewall with Advanced Security use the settings for this profile to filter network traffic. If you select Off, Windows Firewall with Advanced Security will not use any of the firewall rules or connection security rules for this profile.
The recommended state for this setting is: On (recommended) .
If the firewall is turned off all traffic will be able to access the system and an attacker may be more easily able to remotely exploit a weakness in a network service.
To establish the recommended configuration via GP, set the following UI path to On (recommended) :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile\Firewall state
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.1.1_L1_Ensure_Windows_Firewall_Domain_Firewall_state_is_set_to_On_recommended" role="full" severity="unknown" time="2020-04-22T15:48:41.883-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36062-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817055" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableFirewall' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817055" result="true" testref="oval:org.cisecurity.benchmarks:tst:817055" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817055"> <cis:evidence_item itemref="1260"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\DomainProfile"/> <cis:evidence_item_pk_field name="name" value="EnableFirewall"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170551" value-id="xccdf_org.cisecurity.benchmarks_value_817055_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170552" value-id="xccdf_org.cisecurity.benchmarks_value_817055_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817055"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36062-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.4 |
Label: | Apply Host-Based Firewalls or Port Filtering |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.1 |
Label: | Maintain Standard Security Configurations for Network Devices |
Description: | Maintain standard, documented security configuration standards for all authorized network devices. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Leverage Host-based Firewalls |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
This setting determines the behavior for inbound connections that do not match an inbound firewall rule.
The recommended state for this setting is: Block (default) .
If the firewall allows all traffic to access the system then an attacker may be more easily able to remotely exploit a weakness in a network service.
To establish the recommended configuration via GP, set the following UI path to Block (default) :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile\Inbound connections
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.1.2_L1_Ensure_Windows_Firewall_Domain_Inbound_connections_is_set_to_Block_default" role="full" severity="unknown" time="2020-04-22T15:48:41.961-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38117-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:41.961-05:00" start-time="2020-04-22T15:48:41.883-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DefaultInboundAction' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817060" result="false" testref="oval:org.cisecurity.benchmarks:tst:817060" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817060"> <cis:evidence_item itemref="1261"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\DomainProfile"/> <cis:evidence_item_pk_field name="name" value="DefaultInboundAction"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="1" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170601" value-id="xccdf_org.cisecurity.benchmarks_value_817060_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170602" value-id="xccdf_org.cisecurity.benchmarks_value_817060_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817060"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38117-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.4 |
Label: | Apply Host-Based Firewalls or Port Filtering |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Leverage Host-based Firewalls |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
This setting determines the behavior for outbound connections that do not match an outbound firewall rule.
The recommended state for this setting is: Allow (default) .
Some people believe that it is prudent to block all outbound connections except those specifically approved by the user or administrator. Microsoft disagrees with this opinion, blocking outbound connections by default will force users to deal with a large number of dialog boxes prompting them to authorize or block applications such as their web browser or instant messaging software. Additionally, blocking outbound traffic has little value because if an attacker has compromised the system they can reconfigure the firewall anyway.
To establish the recommended configuration via GP, set the following UI path to Allow (default) :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile\Outbound connections
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.1.3_L1_Ensure_Windows_Firewall_Domain_Outbound_connections_is_set_to_Allow_default" role="full" severity="unknown" time="2020-04-22T15:48:42.024-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36146-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.024-05:00" start-time="2020-04-22T15:48:41.961-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DefaultOutboundAction' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817068" result="true" testref="oval:org.cisecurity.benchmarks:tst:817068" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817068"> <cis:evidence_item itemref="1262"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\DomainProfile"/> <cis:evidence_item_pk_field name="name" value="DefaultOutboundAction"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170681" value-id="xccdf_org.cisecurity.benchmarks_value_817068_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170682" value-id="xccdf_org.cisecurity.benchmarks_value_817068_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817068"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36146-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.4 |
Label: | Apply Host-Based Firewalls or Port Filtering |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Leverage Host-based Firewalls |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
Select this option to have Windows Firewall with Advanced Security display notifications to the user when a program is blocked from receiving inbound connections.
The recommended state for this setting is: No .
Note: When the Apply local firewall rules setting is configured to No , it's recommended to also configure the Display a notification setting to No . Otherwise, users will continue to receive messages that ask if they want to unblock a restricted inbound connection, but the user's response will be ignored.
Firewall notifications can be complex and may confuse the end users, who would not be able to address the alert.
To establish the recommended configuration via GP, set the following UI path to No :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile\Settings Customize\Display a notification
Impact:
Windows Firewall will not display a notification when a program is blocked from receiving inbound connections.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.1.4_L1_Ensure_Windows_Firewall_Domain_Settings_Display_a_notification_is_set_to_No" role="full" severity="unknown" time="2020-04-22T15:48:42.086-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38041-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.086-05:00" start-time="2020-04-22T15:48:42.024-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableNotifications' is equal to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817079" result="true" testref="oval:org.cisecurity.benchmarks:tst:817079" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817079"> <cis:evidence_item itemref="1263"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\DomainProfile"/> <cis:evidence_item_pk_field name="name" value="DisableNotifications"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170791" value-id="xccdf_org.cisecurity.benchmarks_value_817079_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170792" value-id="xccdf_org.cisecurity.benchmarks_value_817079_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817079"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38041-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
Use this option to specify the path and name of the file in which Windows Firewall will write its log information.
The recommended state for this setting is: %SystemRoot%\System32\logfiles\firewall\domainfw.log .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to %SystemRoot%\System32\logfiles\firewall\domainfw.log :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile\Logging Customize\Name
Impact:
The log file will be stored in the specified file.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.1.5_L1_Ensure_Windows_Firewall_Domain_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewalldomainfw.log" role="full" severity="unknown" time="2020-04-22T15:48:42.149-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37482-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.149-05:00" start-time="2020-04-22T15:48:42.086-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LogFilePath' is 'Windows: Registry Value' to '%SystemRoot%\System32\logfiles\firewall\domainfw.log'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817090" result="false" testref="oval:org.cisecurity.benchmarks:tst:817090" type="registry_test"> <cis:evidence_object> <cis:evidence_item itemref="1264"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\DomainProfile\Logging"/> <cis:evidence_item_pk_field name="name" value="LogFilePath"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170901" value-id="xccdf_org.cisecurity.benchmarks_value_817090_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170902" value-id="xccdf_org.cisecurity.benchmarks_value_817090_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817090"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37482-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Activate audit logging |
Description: | Ensure that local logging has been enabled on all systems and networking devices. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Ensure Audit Log Settings Support Appropriate Log Entry Formating |
Description: | Validate audit log settings for each hardware device and the software installed on it, ensuring that logs include a date, timestamp, source addresses, destination addresses, and various other useful elements of each packet and/or transaction. Systems should record logs in a standardized format such as syslog entries or those outlined by the Common Event Expression initiative. If systems cannot generate logs in a standardized format, log normalization tools can be deployed to convert logs into such a format. |
Use this option to specify the size limit of the file in which Windows Firewall will write its log information.
The recommended state for this setting is: 16,384 KB or greater .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to 16,384 KB or greater :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile\Logging Customize\Size limit (KB)
Impact:
The log file size will be limited to the specified size, old events will be overwritten by newer ones when the limit is reached.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.1.6_L1_Ensure_Windows_Firewall_Domain_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" role="full" severity="unknown" time="2020-04-22T15:48:42.211-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36088-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.211-05:00" start-time="2020-04-22T15:48:42.149-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LogFileSize' is 'Windows: Registry Value' to '16384'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817101" result="true" testref="oval:org.cisecurity.benchmarks:tst:817101" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817101"> <cis:evidence_item itemref="1265"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\DomainProfile\Logging"/> <cis:evidence_item_pk_field name="name" value="LogFileSize"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="16384" dt="int" ev="16384" name="value" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171011" value-id="xccdf_org.cisecurity.benchmarks_value_817101_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171012" value-id="xccdf_org.cisecurity.benchmarks_value_817101_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817101"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36088-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Ensure Audit Logging Systems Are Not Subject To Loss (i.e. rotation/archive) |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated on a regular basis, so that log files will not fill up between log rotation intervals. The logs must be archived and digitally signed on a periodic basis. |
Use this option to log when Windows Firewall with Advanced Security discards an inbound packet for any reason. The log records why and when the packet was dropped. Look for entries with the word DROP in the action column of the log.
The recommended state for this setting is: Yes .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to Yes :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile\Logging Customize\Log dropped packets
Impact:
Information about dropped packets will be recorded in the firewall log file.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.1.7_L1_Ensure_Windows_Firewall_Domain_Logging_Log_dropped_packets_is_set_to_Yes" role="full" severity="unknown" time="2020-04-22T15:48:42.274-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37523-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.274-05:00" start-time="2020-04-22T15:48:42.211-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LogDroppedPackets' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817113" result="true" testref="oval:org.cisecurity.benchmarks:tst:817113" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817113"> <cis:evidence_item itemref="1266"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\DomainProfile\Logging"/> <cis:evidence_item_pk_field name="name" value="LogDroppedPackets"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171131" value-id="xccdf_org.cisecurity.benchmarks_value_817113_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171132" value-id="xccdf_org.cisecurity.benchmarks_value_817113_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817113"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37523-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Activate audit logging |
Description: | Ensure that local logging has been enabled on all systems and networking devices. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Ensure Audit Log Settings Support Appropriate Log Entry Formating |
Description: | Validate audit log settings for each hardware device and the software installed on it, ensuring that logs include a date, timestamp, source addresses, destination addresses, and various other useful elements of each packet and/or transaction. Systems should record logs in a standardized format such as syslog entries or those outlined by the Common Event Expression initiative. If systems cannot generate logs in a standardized format, log normalization tools can be deployed to convert logs into such a format. |
Use this option to log when Windows Firewall with Advanced Security allows an inbound connection. The log records why and when the connection was formed. Look for entries with the word ALLOW in the action column of the log.
The recommended state for this setting is: Yes .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to Yes :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Domain Profile\Logging Customize\Log successful connections
Impact:
Information about successful connections will be recorded in the firewall log file.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.1.8_L1_Ensure_Windows_Firewall_Domain_Logging_Log_successful_connections_is_set_to_Yes" role="full" severity="unknown" time="2020-04-22T15:48:42.336-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36393-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.352-05:00" start-time="2020-04-22T15:48:42.289-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LogSuccessfulConnections' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817125" result="true" testref="oval:org.cisecurity.benchmarks:tst:817125" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817125"> <cis:evidence_item itemref="1267"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\DomainProfile\Logging"/> <cis:evidence_item_pk_field name="name" value="LogSuccessfulConnections"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171251" value-id="xccdf_org.cisecurity.benchmarks_value_817125_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171252" value-id="xccdf_org.cisecurity.benchmarks_value_817125_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817125"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36393-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Activate audit logging |
Description: | Ensure that local logging has been enabled on all systems and networking devices. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Ensure Audit Log Settings Support Appropriate Log Entry Formating |
Description: | Validate audit log settings for each hardware device and the software installed on it, ensuring that logs include a date, timestamp, source addresses, destination addresses, and various other useful elements of each packet and/or transaction. Systems should record logs in a standardized format such as syslog entries or those outlined by the Common Event Expression initiative. If systems cannot generate logs in a standardized format, log normalization tools can be deployed to convert logs into such a format. |
This section contains recommendations for the Private Profile of the Windows Firewall.
Select On (recommended) to have Windows Firewall with Advanced Security use the settings for this profile to filter network traffic. If you select Off, Windows Firewall with Advanced Security will not use any of the firewall rules or connection security rules for this profile.
The recommended state for this setting is: On (recommended) .
If the firewall is turned off all traffic will be able to access the system and an attacker may be more easily able to remotely exploit a weakness in a network service.
To establish the recommended configuration via GP, set the following UI path to On (recommended) :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile\Firewall state
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.2.1_L1_Ensure_Windows_Firewall_Private_Firewall_state_is_set_to_On_recommended" role="full" severity="unknown" time="2020-04-22T15:48:42.414-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38239-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.414-05:00" start-time="2020-04-22T15:48:42.352-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableFirewall' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817058" result="true" testref="oval:org.cisecurity.benchmarks:tst:817058" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817058"> <cis:evidence_item itemref="1268"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PrivateProfile"/> <cis:evidence_item_pk_field name="name" value="EnableFirewall"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170581" value-id="xccdf_org.cisecurity.benchmarks_value_817058_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170582" value-id="xccdf_org.cisecurity.benchmarks_value_817058_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817058"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38239-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.4 |
Label: | Apply Host-Based Firewalls or Port Filtering |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Leverage Host-based Firewalls |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
This setting determines the behavior for inbound connections that do not match an inbound firewall rule.
The recommended state for this setting is: Block (default) .
If the firewall allows all traffic to access the system then an attacker may be more easily able to remotely exploit a weakness in a network service.
To establish the recommended configuration via GP, set the following UI path to Block (default) :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile\Inbound connections
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.2.2_L1_Ensure_Windows_Firewall_Private_Inbound_connections_is_set_to_Block_default" role="full" severity="unknown" time="2020-04-22T15:48:42.477-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38042-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.477-05:00" start-time="2020-04-22T15:48:42.414-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DefaultInboundAction' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817066" result="false" testref="oval:org.cisecurity.benchmarks:tst:817066" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817066"> <cis:evidence_item itemref="1269"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PrivateProfile"/> <cis:evidence_item_pk_field name="name" value="DefaultInboundAction"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="1" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170661" value-id="xccdf_org.cisecurity.benchmarks_value_817066_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170662" value-id="xccdf_org.cisecurity.benchmarks_value_817066_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817066"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38042-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.4 |
Label: | Apply Host-Based Firewalls or Port Filtering |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Leverage Host-based Firewalls |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
This setting determines the behavior for outbound connections that do not match an outbound firewall rule.
The recommended state for this setting is: Allow (default) .
Note: If you set Outbound connections to Block and then deploy the firewall policy by using a GPO, computers that receive the GPO settings cannot receive subsequent Group Policy updates unless you create and deploy an outbound rule that enables Group Policy to work. Predefined rules for Core Networking include outbound rules that enable Group Policy to work. Ensure that these outbound rules are active, and thoroughly test firewall profiles before deploying.
Some people believe that it is prudent to block all outbound connections except those specifically approved by the user or administrator. Microsoft disagrees with this opinion, blocking outbound connections by default will force users to deal with a large number of dialog boxes prompting them to authorize or block applications such as their web browser or instant messaging software. Additionally, blocking outbound traffic has little value because if an attacker has compromised the system they can reconfigure the firewall anyway.
To establish the recommended configuration via GP, set the following UI path to Allow (default) :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile\Outbound connections
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.2.3_L1_Ensure_Windows_Firewall_Private_Outbound_connections_is_set_to_Allow_default" role="full" severity="unknown" time="2020-04-22T15:48:42.539-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38332-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.539-05:00" start-time="2020-04-22T15:48:42.493-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DefaultOutboundAction' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817075" result="true" testref="oval:org.cisecurity.benchmarks:tst:817075" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817075"> <cis:evidence_item itemref="1270"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PrivateProfile"/> <cis:evidence_item_pk_field name="name" value="DefaultOutboundAction"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170751" value-id="xccdf_org.cisecurity.benchmarks_value_817075_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170752" value-id="xccdf_org.cisecurity.benchmarks_value_817075_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817075"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38332-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.4 |
Label: | Apply Host-Based Firewalls or Port Filtering |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Leverage Host-based Firewalls |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
Select this option to have Windows Firewall with Advanced Security display notifications to the user when a program is blocked from receiving inbound connections.
The recommended state for this setting is: No .
Note: When the Apply local firewall rules setting is configured to No , it's recommended to also configure the Display a notification setting to No . Otherwise, users will continue to receive messages that ask if they want to unblock a restricted inbound connection, but the user's response will be ignored.
Firewall notifications can be complex and may confuse the end users, who would not be able to address the alert.
To establish the recommended configuration via GP, set the following UI path to No :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile\Settings Customize\Display a notification
Impact:
Windows Firewall will not display a notification when a program is blocked from receiving inbound connections.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.2.4_L1_Ensure_Windows_Firewall_Private_Settings_Display_a_notification_is_set_to_No" role="full" severity="unknown" time="2020-04-22T15:48:42.618-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37621-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.618-05:00" start-time="2020-04-22T15:48:42.555-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableNotifications' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817088" result="true" testref="oval:org.cisecurity.benchmarks:tst:817088" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817088"> <cis:evidence_item itemref="1271"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PrivateProfile"/> <cis:evidence_item_pk_field name="name" value="DisableNotifications"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170881" value-id="xccdf_org.cisecurity.benchmarks_value_817088_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170882" value-id="xccdf_org.cisecurity.benchmarks_value_817088_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817088"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37621-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
Use this option to specify the path and name of the file in which Windows Firewall will write its log information.
The recommended state for this setting is: %SystemRoot%\System32\logfiles\firewall\privatefw.log .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to %SystemRoot%\System32\logfiles\firewall\privatefw.log :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile\Logging Customize\Name
Impact:
The log file will be stored in the specified file.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.2.5_L1_Ensure_Windows_Firewall_Private_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewallprivatefw.log" role="full" severity="unknown" time="2020-04-22T15:48:42.680-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37569-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.680-05:00" start-time="2020-04-22T15:48:42.618-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LogFilePath' is 'Windows: Registry Value' to '%SystemRoot%\System32\logfiles\firewall\privatefw.log'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817098" result="false" testref="oval:org.cisecurity.benchmarks:tst:817098" type="registry_test"> <cis:evidence_object> <cis:evidence_item itemref="1272"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PrivateProfile\Logging"/> <cis:evidence_item_pk_field name="name" value="LogFilePath"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170981" value-id="xccdf_org.cisecurity.benchmarks_value_817098_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170982" value-id="xccdf_org.cisecurity.benchmarks_value_817098_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817098"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37569-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Activate audit logging |
Description: | Ensure that local logging has been enabled on all systems and networking devices. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Ensure Audit Log Settings Support Appropriate Log Entry Formating |
Description: | Validate audit log settings for each hardware device and the software installed on it, ensuring that logs include a date, timestamp, source addresses, destination addresses, and various other useful elements of each packet and/or transaction. Systems should record logs in a standardized format such as syslog entries or those outlined by the Common Event Expression initiative. If systems cannot generate logs in a standardized format, log normalization tools can be deployed to convert logs into such a format. |
Use this option to specify the size limit of the file in which Windows Firewall will write its log information.
The recommended state for this setting is: 16,384 KB or greater .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to 16,384 KB or greater :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile\Logging Customize\Size limit (KB)
Impact:
The log file size will be limited to the specified size, old events will be overwritten by newer ones when the limit is reached.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.2.6_L1_Ensure_Windows_Firewall_Private_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" role="full" severity="unknown" time="2020-04-22T15:48:42.743-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38178-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.743-05:00" start-time="2020-04-22T15:48:42.680-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LogFileSize' is 'Windows: Registry Value' to '16384'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817107" result="true" testref="oval:org.cisecurity.benchmarks:tst:817107" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817107"> <cis:evidence_item itemref="1273"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PrivateProfile\Logging"/> <cis:evidence_item_pk_field name="name" value="LogFileSize"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="16384" dt="int" ev="16384" name="value" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171071" value-id="xccdf_org.cisecurity.benchmarks_value_817107_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171072" value-id="xccdf_org.cisecurity.benchmarks_value_817107_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817107"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38178-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Ensure Audit Logging Systems Are Not Subject To Loss (i.e. rotation/archive) |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated on a regular basis, so that log files will not fill up between log rotation intervals. The logs must be archived and digitally signed on a periodic basis. |
Use this option to log when Windows Firewall with Advanced Security discards an inbound packet for any reason. The log records why and when the packet was dropped. Look for entries with the word DROP in the action column of the log.
The recommended state for this setting is: Yes .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to Yes :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile\Logging Customize\Log dropped packets
Impact:
Information about dropped packets will be recorded in the firewall log file.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.2.7_L1_Ensure_Windows_Firewall_Private_Logging_Log_dropped_packets_is_set_to_Yes" role="full" severity="unknown" time="2020-04-22T15:48:42.805-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-35972-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.805-05:00" start-time="2020-04-22T15:48:42.743-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LogDroppedPackets' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817119" result="true" testref="oval:org.cisecurity.benchmarks:tst:817119" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817119"> <cis:evidence_item itemref="1274"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PrivateProfile\Logging"/> <cis:evidence_item_pk_field name="name" value="LogDroppedPackets"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171191" value-id="xccdf_org.cisecurity.benchmarks_value_817119_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171192" value-id="xccdf_org.cisecurity.benchmarks_value_817119_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817119"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-35972-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Activate audit logging |
Description: | Ensure that local logging has been enabled on all systems and networking devices. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Ensure Audit Log Settings Support Appropriate Log Entry Formating |
Description: | Validate audit log settings for each hardware device and the software installed on it, ensuring that logs include a date, timestamp, source addresses, destination addresses, and various other useful elements of each packet and/or transaction. Systems should record logs in a standardized format such as syslog entries or those outlined by the Common Event Expression initiative. If systems cannot generate logs in a standardized format, log normalization tools can be deployed to convert logs into such a format. |
Use this option to log when Windows Firewall with Advanced Security allows an inbound connection. The log records why and when the connection was formed. Look for entries with the word ALLOW in the action column of the log.
The recommended state for this setting is: Yes .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to Yes :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Private Profile\Logging Customize\Log successful connections
Impact:
Information about successful connections will be recorded in the firewall log file.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.2.8_L1_Ensure_Windows_Firewall_Private_Logging_Log_successful_connections_is_set_to_Yes" role="full" severity="unknown" time="2020-04-22T15:48:42.883-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37387-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.883-05:00" start-time="2020-04-22T15:48:42.805-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LogSuccessfulConnections' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817134" result="true" testref="oval:org.cisecurity.benchmarks:tst:817134" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817134"> <cis:evidence_item itemref="1275"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PrivateProfile\Logging"/> <cis:evidence_item_pk_field name="name" value="LogSuccessfulConnections"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171341" value-id="xccdf_org.cisecurity.benchmarks_value_817134_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171342" value-id="xccdf_org.cisecurity.benchmarks_value_817134_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817134"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37387-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Activate audit logging |
Description: | Ensure that local logging has been enabled on all systems and networking devices. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Ensure Audit Log Settings Support Appropriate Log Entry Formating |
Description: | Validate audit log settings for each hardware device and the software installed on it, ensuring that logs include a date, timestamp, source addresses, destination addresses, and various other useful elements of each packet and/or transaction. Systems should record logs in a standardized format such as syslog entries or those outlined by the Common Event Expression initiative. If systems cannot generate logs in a standardized format, log normalization tools can be deployed to convert logs into such a format. |
This section contains recommendations for the Public Profile of the Windows Firewall.
Select On (recommended) to have Windows Firewall with Advanced Security use the settings for this profile to filter network traffic. If you select Off, Windows Firewall with Advanced Security will not use any of the firewall rules or connection security rules for this profile.
The recommended state for this setting is: On (recommended) .
If the firewall is turned off all traffic will be able to access the system and an attacker may be more easily able to remotely exploit a weakness in a network service.
To establish the recommended configuration via GP, set the following UI path to On (recommended):
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile\Firewall state
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.3.1_L1_Ensure_Windows_Firewall_Public_Firewall_state_is_set_to_On_recommended" role="full" severity="unknown" time="2020-04-22T15:48:43.008-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37862-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:43.008-05:00" start-time="2020-04-22T15:48:42.946-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableFirewall' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817062" result="true" testref="oval:org.cisecurity.benchmarks:tst:817062" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817062"> <cis:evidence_item itemref="1277"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PublicProfile"/> <cis:evidence_item_pk_field name="name" value="EnableFirewall"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170621" value-id="xccdf_org.cisecurity.benchmarks_value_817062_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170622" value-id="xccdf_org.cisecurity.benchmarks_value_817062_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817062"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37862-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.4 |
Label: | Apply Host-Based Firewalls or Port Filtering |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Leverage Host-based Firewalls |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
This setting determines the behavior for inbound connections that do not match an inbound firewall rule.
The recommended state for this setting is: Block (default) .
If the firewall allows all traffic to access the system then an attacker may be more easily able to remotely exploit a weakness in a network service.
To establish the recommended configuration via GP, set the following UI path to Block (default) :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile\Inbound connections
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.3.2_L1_Ensure_Windows_Firewall_Public_Inbound_connections_is_set_to_Block_default" role="full" severity="unknown" time="2020-04-22T15:48:43.086-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36057-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:43.086-05:00" start-time="2020-04-22T15:48:43.008-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DefaultInboundAction' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817071" result="false" testref="oval:org.cisecurity.benchmarks:tst:817071" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817071"> <cis:evidence_item itemref="1278"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PublicProfile"/> <cis:evidence_item_pk_field name="name" value="DefaultInboundAction"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="1" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170711" value-id="xccdf_org.cisecurity.benchmarks_value_817071_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170712" value-id="xccdf_org.cisecurity.benchmarks_value_817071_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817071"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36057-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.4 |
Label: | Apply Host-Based Firewalls or Port Filtering |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Leverage Host-based Firewalls |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
This setting determines the behavior for outbound connections that do not match an outbound firewall rule.
The recommended state for this setting is: Allow (default) .
Note: If you set Outbound connections to Block and then deploy the firewall policy by using a GPO, computers that receive the GPO settings cannot receive subsequent Group Policy updates unless you create and deploy an outbound rule that enables Group Policy to work. Predefined rules for Core Networking include outbound rules that enable Group Policy to work. Ensure that these outbound rules are active, and thoroughly test firewall profiles before deploying.
Some people believe that it is prudent to block all outbound connections except those specifically approved by the user or administrator. Microsoft disagrees with this opinion, blocking outbound connections by default will force users to deal with a large number of dialog boxes prompting them to authorize or block applications such as their web browser or instant messaging software. Additionally, blocking outbound traffic has little value because if an attacker has compromised the system they can reconfigure the firewall anyway.
To establish the recommended configuration via GP, set the following UI path to Allow (default) :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile\Outbound connections
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.3.3_L1_Ensure_Windows_Firewall_Public_Outbound_connections_is_set_to_Allow_default" role="full" severity="unknown" time="2020-04-22T15:48:43.149-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37434-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:43.149-05:00" start-time="2020-04-22T15:48:43.086-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DefaultOutboundAction' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817082" result="true" testref="oval:org.cisecurity.benchmarks:tst:817082" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817082"> <cis:evidence_item itemref="1279"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PublicProfile"/> <cis:evidence_item_pk_field name="name" value="DefaultOutboundAction"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170821" value-id="xccdf_org.cisecurity.benchmarks_value_817082_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170822" value-id="xccdf_org.cisecurity.benchmarks_value_817082_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817082"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37434-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.4 |
Label: | Apply Host-Based Firewalls or Port Filtering |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Leverage Host-based Firewalls |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
Select this option to have Windows Firewall with Advanced Security display notifications to the user when a program is blocked from receiving inbound connections.
The recommended state for this setting is: No .
Some organizations may prefer to avoid alarming users when firewall rules block certain types of network activity. However, notifications can be helpful when troubleshooting network issues involving the firewall.
To establish the recommended configuration via GP, set the following UI path to 'No':
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile\Settings Customize\Display a notification
Impact:
Windows Firewall will not display a notification when a program is blocked from receiving inbound connections.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.3.4_L1_Ensure_Windows_Firewall_Public_Settings_Display_a_notification_is_set_to_No" role="full" severity="unknown" time="2020-04-22T15:48:43.211-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38043-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:43.211-05:00" start-time="2020-04-22T15:48:43.149-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableNotifications' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817093" result="true" testref="oval:org.cisecurity.benchmarks:tst:817093" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817093"> <cis:evidence_item itemref="1280"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PublicProfile"/> <cis:evidence_item_pk_field name="name" value="DisableNotifications"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170931" value-id="xccdf_org.cisecurity.benchmarks_value_817093_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8170932" value-id="xccdf_org.cisecurity.benchmarks_value_817093_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817093"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38043-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
This setting controls whether local administrators are allowed to create local firewall rules that apply together with firewall rules configured by Group Policy.
The recommended state for this setting is: No .
Note: When the Apply local firewall rules setting is configured to No , it's recommended to also configure the Display a notification setting to No . Otherwise, users will continue to receive messages that ask if they want to unblock a restricted inbound connection, but the user's response will be ignored.
When in the Public profile, there should be no special local firewall exceptions per computer. These settings should be managed by a centralized policy.
To establish the recommended configuration via GP, set the following UI path to No :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile\Settings Customize\Apply local firewall rules
Impact:
Administrators can still create firewall rules, but the rules will not be applied.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.3.5_L1_Ensure_Windows_Firewall_Public_Settings_Apply_local_firewall_rules_is_set_to_No" role="full" severity="unknown" time="2020-04-22T15:48:43.289-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37861-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:43.289-05:00" start-time="2020-04-22T15:48:43.211-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowLocalPolicyMerge' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817104" result="true" testref="oval:org.cisecurity.benchmarks:tst:817104" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817104"> <cis:evidence_item itemref="1281"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PublicProfile"/> <cis:evidence_item_pk_field name="name" value="AllowLocalPolicyMerge"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171041" value-id="xccdf_org.cisecurity.benchmarks_value_817104_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171042" value-id="xccdf_org.cisecurity.benchmarks_value_817104_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817104"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37861-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This setting controls whether local administrators are allowed to create connection security rules that apply together with connection security rules configured by Group Policy.
The recommended state for this setting is: No .
Users with administrative privileges might create firewall rules that expose the system to remote attack.
To establish the recommended configuration via GP, set the following UI path to No :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile\Settings Customize\Apply local connection security rules
Impact:
Administrators can still create local connection security rules, but the rules will not be applied.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.3.6_L1_Ensure_Windows_Firewall_Public_Settings_Apply_local_connection_security_rules_is_set_to_No" role="full" severity="unknown" time="2020-04-22T15:48:43.352-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/11/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36268-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:43.352-05:00" start-time="2020-04-22T15:48:43.289-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowLocalIPsecPolicyMerge' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817117" result="true" testref="oval:org.cisecurity.benchmarks:tst:817117" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817117"> <cis:evidence_item itemref="1282"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PublicProfile"/> <cis:evidence_item_pk_field name="name" value="AllowLocalIPsecPolicyMerge"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171171" value-id="xccdf_org.cisecurity.benchmarks_value_817117_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171172" value-id="xccdf_org.cisecurity.benchmarks_value_817117_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817117"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36268-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.2 |
Label: | Document Traffic Configuration Rules |
Description: | All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 11.3 |
Label: | Use Automated Tools to Verify Standard Device Configurations and Detect Changes |
Description: | Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
Use this option to specify the path and name of the file in which Windows Firewall will write its log information.
The recommended state for this setting is: %SystemRoot%\System32\logfiles\firewall\publicfw.log .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to %SystemRoot%\System32\logfiles\firewall\publicfw.log :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile\Logging Customize\Name
Impact:
The log file will be stored in the specified file.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.3.7_L1_Ensure_Windows_Firewall_Public_Logging_Name_is_set_to_SystemRootSystem32logfilesfirewallpublicfw.log" role="full" severity="unknown" time="2020-04-22T15:48:43.414-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37266-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:43.414-05:00" start-time="2020-04-22T15:48:43.352-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LogFilePath' is 'Windows: Registry Value' to '%SystemRoot%\System32\logfiles\firewall\publicfw.log'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817128" result="false" testref="oval:org.cisecurity.benchmarks:tst:817128" type="registry_test"> <cis:evidence_object> <cis:evidence_item itemref="1283"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PublicProfile\Logging"/> <cis:evidence_item_pk_field name="name" value="LogFilePath"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171281" value-id="xccdf_org.cisecurity.benchmarks_value_817128_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171282" value-id="xccdf_org.cisecurity.benchmarks_value_817128_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817128"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37266-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Activate audit logging |
Description: | Ensure that local logging has been enabled on all systems and networking devices. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Ensure Audit Log Settings Support Appropriate Log Entry Formating |
Description: | Validate audit log settings for each hardware device and the software installed on it, ensuring that logs include a date, timestamp, source addresses, destination addresses, and various other useful elements of each packet and/or transaction. Systems should record logs in a standardized format such as syslog entries or those outlined by the Common Event Expression initiative. If systems cannot generate logs in a standardized format, log normalization tools can be deployed to convert logs into such a format. |
Use this option to specify the size limit of the file in which Windows Firewall will write its log information.
The recommended state for this setting is: 16,384 KB or greater .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to 16,384 KB or greater :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile\Logging Customize\Size limit (KB)
Impact:
The log file size will be limited to the specified size, old events will be overwritten by newer ones when the limit is reached.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.3.8_L1_Ensure_Windows_Firewall_Public_Logging_Size_limit_KB_is_set_to_16384_KB_or_greater" role="full" severity="unknown" time="2020-04-22T15:48:43.477-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36395-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:43.477-05:00" start-time="2020-04-22T15:48:43.414-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LogFileSize' is 'Windows: Registry Value' to '16384'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817146" result="true" testref="oval:org.cisecurity.benchmarks:tst:817146" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817146"> <cis:evidence_item itemref="1284"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PublicProfile\Logging"/> <cis:evidence_item_pk_field name="name" value="LogFileSize"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="16384" dt="int" ev="16384" name="value" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171461" value-id="xccdf_org.cisecurity.benchmarks_value_817146_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171462" value-id="xccdf_org.cisecurity.benchmarks_value_817146_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817146"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36395-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Ensure Audit Logging Systems Are Not Subject To Loss (i.e. rotation/archive) |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated on a regular basis, so that log files will not fill up between log rotation intervals. The logs must be archived and digitally signed on a periodic basis. |
Use this option to log when Windows Firewall with Advanced Security discards an inbound packet for any reason. The log records why and when the packet was dropped. Look for entries with the word DROP in the action column of the log.
The recommended state for this setting is: Yes .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to Yes :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile\Logging Customize\Log dropped packets
Impact:
Information about dropped packets will be recorded in the firewall log file.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.3.9_L1_Ensure_Windows_Firewall_Public_Logging_Log_dropped_packets_is_set_to_Yes" role="full" severity="unknown" time="2020-04-22T15:48:43.555-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37265-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:43.555-05:00" start-time="2020-04-22T15:48:43.493-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LogDroppedPackets' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817157" result="true" testref="oval:org.cisecurity.benchmarks:tst:817157" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817157"> <cis:evidence_item itemref="1285"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PublicProfile\Logging"/> <cis:evidence_item_pk_field name="name" value="LogDroppedPackets"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171571" value-id="xccdf_org.cisecurity.benchmarks_value_817157_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171572" value-id="xccdf_org.cisecurity.benchmarks_value_817157_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817157"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37265-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Activate audit logging |
Description: | Ensure that local logging has been enabled on all systems and networking devices. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Ensure Audit Log Settings Support Appropriate Log Entry Formating |
Description: | Validate audit log settings for each hardware device and the software installed on it, ensuring that logs include a date, timestamp, source addresses, destination addresses, and various other useful elements of each packet and/or transaction. Systems should record logs in a standardized format such as syslog entries or those outlined by the Common Event Expression initiative. If systems cannot generate logs in a standardized format, log normalization tools can be deployed to convert logs into such a format. |
Use this option to log when Windows Firewall with Advanced Security allows an inbound connection. The log records why and when the connection was formed. Look for entries with the word ALLOW in the action column of the log.
The recommended state for this setting is: Yes .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to Yes :
Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security\Windows Firewall Properties\Public Profile\Logging Customize\Log successful connections
Impact:
Information about successful connections will be recorded in the firewall log file.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_9.3.10_L1_Ensure_Windows_Firewall_Public_Logging_Log_successful_connections_is_set_to_Yes" role="full" severity="unknown" time="2020-04-22T15:48:42.946-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36394-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:42.946-05:00" start-time="2020-04-22T15:48:42.883-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LogSuccessfulConnections' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817172" result="true" testref="oval:org.cisecurity.benchmarks:tst:817172" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817172"> <cis:evidence_item itemref="1276"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\WindowsFirewall\PublicProfile\Logging"/> <cis:evidence_item_pk_field name="name" value="LogSuccessfulConnections"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171721" value-id="xccdf_org.cisecurity.benchmarks_value_817172_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171722" value-id="xccdf_org.cisecurity.benchmarks_value_817172_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817172"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36394-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Activate audit logging |
Description: | Ensure that local logging has been enabled on all systems and networking devices. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Ensure Audit Log Settings Support Appropriate Log Entry Formating |
Description: | Validate audit log settings for each hardware device and the software installed on it, ensuring that logs include a date, timestamp, source addresses, destination addresses, and various other useful elements of each packet and/or transaction. Systems should record logs in a standardized format such as syslog entries or those outlined by the Common Event Expression initiative. If systems cannot generate logs in a standardized format, log normalization tools can be deployed to convert logs into such a format. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This section contains recommendations for configuring the Windows audit facilities.
This section contains recommendations for configuring the Account Logon audit policy.
This subcategory reports the results of validation tests on credentials submitted for a user account logon request. These events occur on the computer that is authoritative for the credentials. For domain accounts, the Domain Controller is authoritative, whereas for local accounts, the local computer is authoritative. In domain environments, most of the Account Logon events occur in the Security log of the Domain Controllers that are authoritative for the domain accounts. However, these events can occur on other computers in the organization when local accounts are used to log on. Events for this subcategory include:
The recommended state for this setting is: Success and Failure .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to Success and Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Logon\Audit Credential Validation
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.1.1_L1_Ensure_Audit_Credential_Validation_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.508-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/8" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/12" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/9" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/12" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/13" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37741-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.508-05:00" start-time="2020-04-22T15:48:23.321-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'credential_validation' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817061" result="false" testref="oval:org.cisecurity.benchmarks:tst:817061" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817061"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="credential_validation" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817061" value-id="xccdf_org.cisecurity.benchmarks_value_817061_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817061"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37741-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.12 |
Label: | Monitor Attempts to Access Deactivated Accounts |
Description: | Monitor attempts to access deactivated accounts through audit logging. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.9 |
Label: | Disable Dormant Accounts |
Description: | Automatically disable dormant accounts after a set period of inactivity. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.13 |
Label: | Alert on Account Login Behavior Deviation |
Description: | Alert when users deviate from normal login behavior, such as time-of-day, workstation location and duration. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Automatically Log Off Users After Standard Period Of Inactivity |
Description: | Regularly monitor the use of all accounts, automatically logging off users after a standard period of inactivity. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.8 |
Label: | Log Attempts To Access Deactivated Accounts |
Description: | Monitor attempts to access deactivated accounts through audit logging. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.12 |
Label: | Use Long Passwords For All User Accounts |
Description: | Where multi-factor authentication is not supported, user accounts shall be required to use long passwords on the system (longer than 14 characters). |
This section contains recommendations for configuring the Account Management audit policy.
This policy setting allows you to audit events generated by changes to application groups such as the following:
Application groups are utilized by Windows Authorization Manager, which is a flexible framework created by Microsoft for integrating role-based access control (RBAC) into applications. More information on Windows Authorization Manager is available at MSDN - Windows Authorization Manager .
The recommended state for this setting is: Success and Failure .
Auditing events in this category may be useful when investigating an incident.
To establish the recommended configuration via GP, set the following UI path to Success and Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Management\Audit Application Group Management
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.2.1_L1_Ensure_Audit_Application_Group_Management_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.524-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/9" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/12" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38329-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.524-05:00" start-time="2020-04-22T15:48:23.508-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'application_group_management' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817063" result="false" testref="oval:org.cisecurity.benchmarks:tst:817063" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817063"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="application_group_management" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817063" value-id="xccdf_org.cisecurity.benchmarks_value_817063_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817063"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38329-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.9 |
Label: | Disable Dormant Accounts |
Description: | Automatically disable dormant accounts after a set period of inactivity. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.12 |
Label: | Monitor Attempts to Access Deactivated Accounts |
Description: | Monitor attempts to access deactivated accounts through audit logging. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This subcategory reports each event of security group management, such as when a security group is created, changed, or deleted or when a member is added to or removed from a security group. If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of security group accounts. Events for this subcategory include:
The recommended state for this setting is to include: Success .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to include Success :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Management\Audit Security Group Management
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.2.5_L1_Ensure_Audit_Security_Group_Management_is_set_to_include_Success" role="full" severity="unknown" time="2020-04-22T15:48:23.524-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38034-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.524-05:00" start-time="2020-04-22T15:48:23.524-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'security_group_management' is 'Equals' to 'AUDIT_SUCCESS'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817091" result="false" testref="oval:org.cisecurity.benchmarks:tst:817091" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817091"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS" name="security_group_management" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'security_group_management' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817095" result="false" testref="oval:org.cisecurity.benchmarks:tst:817095" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817095"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="security_group_management" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817091" value-id="xccdf_org.cisecurity.benchmarks_value_817091_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817091"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817095" value-id="xccdf_org.cisecurity.benchmarks_value_817095_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817095"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38034-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.6 |
Label: | Maintain an Inventory of Accounts |
Description: | Maintain an inventory of all accounts organized by authentication system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This subcategory reports each event of user account management, such as when a user account is created, changed, or deleted; a user account is renamed, disabled, or enabled; or a password is set or changed. If you enable this Audit policy setting, administrators can track events to detect malicious, accidental, and authorized creation of user accounts. Events for this subcategory include:
The recommended state for this setting is: Success and Failure .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to Success and Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Account Management\Audit User Account Management
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.2.6_L1_Ensure_Audit_User_Account_Management_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.539-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37856-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.539-05:00" start-time="2020-04-22T15:48:23.539-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'user_account_management' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817099" result="false" testref="oval:org.cisecurity.benchmarks:tst:817099" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817099"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="user_account_management" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817099" value-id="xccdf_org.cisecurity.benchmarks_value_817099_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817099"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37856-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.6 |
Label: | Maintain an Inventory of Accounts |
Description: | Maintain an inventory of all accounts organized by authentication system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Automatically Log Off Users After Standard Period Of Inactivity |
Description: | Regularly monitor the use of all accounts, automatically logging off users after a standard period of inactivity. |
This section contains recommendations for configuring the Detailed Tracking audit policy.
This policy setting allows you to audit when plug and play detects an external device.
The recommended state for this setting is to include: Success .
Note: A Windows 10, Server 2016 or newer OS is required to access and set this value in Group Policy.
Enabling this setting will allow a user to audit events when a device is plugged into a system. This can help alert IT staff if unapproved devices are plugged in.
To establish the recommended configuration via GP, set the following UI path to include Success :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Detailed Tracking\Audit PNP Activity
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.3.1_L1_Ensure_Audit_PNP_Activity_is_set_to_include_Success" role="full" severity="unknown" time="2020-04-22T15:48:23.539-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/13/subcontrol/7" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.539-05:00" start-time="2020-04-22T15:48:23.539-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'pnp_activity' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817078" result="false" testref="oval:org.cisecurity.benchmarks:tst:817078" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817078"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="pnp_activity" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'pnp_activity' is 'Equals' to 'AUDIT_SUCCESS'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817074" result="false" testref="oval:org.cisecurity.benchmarks:tst:817074" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817074"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS" name="pnp_activity" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817074" value-id="xccdf_org.cisecurity.benchmarks_value_817074_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817074"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817078" value-id="xccdf_org.cisecurity.benchmarks_value_817078_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817078"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Configure Anti-Malware Scanning of Removable Devices |
Description: | Configure devices so that they automatically conduct an anti-malware scan of removable media when inserted or connected. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.5 |
Label: | Configure Devices Not To Auto-Run Content |
Description: | Configure devices to not auto-run content from removable media. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
Subcontrol: | 13.7 |
Label: | Manage USB Devices |
Description: | If USB storage devices are required, enterprise software should be used that can configure systems to allow the use of specific devices. An inventory of such devices should be maintained. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.3 |
Label: | Limit Use Of External Devices (i.e. USB) |
Description: | Limit use of external devices to those with an approved, documented business need. Monitor for use and attempted use of external devices. Configure laptops, workstations, and servers so that they will not auto-run content from removable media, like USB tokens (i.e., “thumb drives”), USB hard drives, CDs/DVDs, FireWire devices, external serial advanced technology attachment devices, and mounted network shares. Configure systems so that they automatically conduct an anti-malware scan of removable media when inserted. |
This subcategory reports the creation of a process and the name of the program or user that created it. Events for this subcategory include:
Refer to Microsoft Knowledge Base article 947226: Description of security events in Windows Vista and in Windows Server 2008 for the most recent information about this setting.
The recommended state for this setting is to include: Success .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to include Success :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Detailed Tracking\Audit Process Creation
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.3.2_L1_Ensure_Audit_Process_Creation_is_set_to_include_Success" role="full" severity="unknown" time="2020-04-22T15:48:23.555-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36059-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.555-05:00" start-time="2020-04-22T15:48:23.539-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'process_creation' is 'Equals' to 'AUDIT_SUCCESS'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817084" result="false" testref="oval:org.cisecurity.benchmarks:tst:817084" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817084"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS" name="process_creation" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'process_creation' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817087" result="false" testref="oval:org.cisecurity.benchmarks:tst:817087" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817087"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="process_creation" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817084" value-id="xccdf_org.cisecurity.benchmarks_value_817084_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817084"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817087" value-id="xccdf_org.cisecurity.benchmarks_value_817087_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817087"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36059-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
This section contains recommendations for configuring the Directory Services Access audit policy.
This section contains recommendations for configuring the Logon/Logoff audit policy.
This subcategory reports when a user's account is locked out as a result of too many failed logon attempts. Events for this subcategory include:
The recommended state for this setting is to include: Failure .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to include Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff\Audit Account Lockout
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.5.1_L1_Ensure_Audit_Account_Lockout_is_set_to_include_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.555-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37133-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.555-05:00" start-time="2020-04-22T15:48:23.555-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'account_lockout' is 'Equals' to 'AUDIT_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817094" result="false" testref="oval:org.cisecurity.benchmarks:tst:817094" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817094"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_FAILURE" name="account_lockout" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817094" value-id="xccdf_org.cisecurity.benchmarks_value_817094_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817094"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37133-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.6 |
Label: | Maintain an Inventory of Accounts |
Description: | Maintain an inventory of all accounts organized by authentication system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.7 |
Label: | Configure Account Lockouts |
Description: | Use and configure account lockouts such that after a set number of failed login attempts the account is locked for a standard period of time. |
This policy allows you to audit the group membership information in the user’s logon token. Events in this subcategory are generated on the computer on which a logon session is created. For an interactive logon, the security audit event is generated on the computer that the user logged on to. For a network logon, such as accessing a shared folder on the network, the security audit event is generated on the computer hosting the resource.
The recommended state for this setting is to include: Success .
Note: A Windows 10, Server 2016 or newer OS is required to access and set this value in Group Policy.
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to include Success :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff\Audit Group Membership
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.5.2_L1_Ensure_Audit_Group_Membership_is_set_to_include_Success" role="full" severity="unknown" time="2020-04-22T15:48:23.571-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/4/subcontrol/8" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.571-05:00" start-time="2020-04-22T15:48:23.571-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'group_membership' is 'Equals' to 'AUDIT_SUCCESS'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817103" result="false" testref="oval:org.cisecurity.benchmarks:tst:817103" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817103"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS" name="group_membership" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'group_membership' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817105" result="false" testref="oval:org.cisecurity.benchmarks:tst:817105" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817105"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="group_membership" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817103" value-id="xccdf_org.cisecurity.benchmarks_value_817103_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817103"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817105" value-id="xccdf_org.cisecurity.benchmarks_value_817105_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817105"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.6 |
Label: | Maintain an Inventory of Accounts |
Description: | Maintain an inventory of all accounts organized by authentication system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 4.8 |
Label: | Vulnerability Risk Rating Workflow |
Description: | Establish a process to risk-rate vulnerabilities based on the exploitability and potential impact of the vulnerability, and segmented by appropriate groups of assets (example, DMZ servers, internal network servers, desktops, laptops). Apply patches for the riskiest vulnerabilities first. A phased rollout can be used to minimize the impact to the organization. Establish expected patching timelines based on the risk rating level. |
This subcategory reports when a user logs off from the system. These events occur on the accessed computer. For interactive logons, the generation of these events occurs on the computer that is logged on to. If a network logon takes place to access a share, these events generate on the computer that hosts the accessed resource. If you configure this setting to No auditing, it is difficult or impossible to determine which user has accessed or attempted to access organization computers. Events for this subcategory include:
The recommended state for this setting is to include: Success .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to include Success :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff\Audit Logoff
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.5.3_L1_Ensure_Audit_Logoff_is_set_to_include_Success" role="full" severity="unknown" time="2020-04-22T15:48:23.571-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/10" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/13" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38237-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.571-05:00" start-time="2020-04-22T15:48:23.571-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'logoff' is 'Equals' to 'AUDIT_SUCCESS'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817112" result="false" testref="oval:org.cisecurity.benchmarks:tst:817112" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817112"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS" name="logoff" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'logoff' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817114" result="false" testref="oval:org.cisecurity.benchmarks:tst:817114" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817114"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="logoff" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817112" value-id="xccdf_org.cisecurity.benchmarks_value_817112_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817112"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817114" value-id="xccdf_org.cisecurity.benchmarks_value_817114_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817114"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38237-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.6 |
Label: | Maintain an Inventory of Accounts |
Description: | Maintain an inventory of all accounts organized by authentication system. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.13 |
Label: | Alert on Account Login Behavior Deviation |
Description: | Alert when users deviate from normal login behavior, such as time-of-day, workstation location and duration. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.10 |
Label: | Profile User Account Usage And Monitor For Anomalies |
Description: | Profile each user’s typical account usage by determining normal time-of-day access and access duration. Reports should be generated that indicate users who have logged in during unusual hours or have exceeded their normal login duration. This includes flagging the use of the user’s credentials from a computer other than computers on which the user generally works. |
This subcategory reports when a user attempts to log on to the system. These events occur on the accessed computer. For interactive logons, the generation of these events occurs on the computer that is logged on to. If a network logon takes place to access a share, these events generate on the computer that hosts the accessed resource. If you configure this setting to No auditing, it is difficult or impossible to determine which user has accessed or attempted to access organization computers. Events for this subcategory include:
The recommended state for this setting is: Success and Failure .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to Success and Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff\Audit Logon
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.5.4_L1_Ensure_Audit_Logon_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.586-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/10" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/13" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38036-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.586-05:00" start-time="2020-04-22T15:48:23.571-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'logon' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817121" result="false" testref="oval:org.cisecurity.benchmarks:tst:817121" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817121"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="logon" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817121" value-id="xccdf_org.cisecurity.benchmarks_value_817121_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817121"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38036-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.13 |
Label: | Alert on Account Login Behavior Deviation |
Description: | Alert when users deviate from normal login behavior, such as time-of-day, workstation location and duration. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.6 |
Label: | Maintain an Inventory of Accounts |
Description: | Maintain an inventory of all accounts organized by authentication system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.10 |
Label: | Profile User Account Usage And Monitor For Anomalies |
Description: | Profile each user’s typical account usage by determining normal time-of-day access and access duration. Reports should be generated that indicate users who have logged in during unusual hours or have exceeded their normal login duration. This includes flagging the use of the user’s credentials from a computer other than computers on which the user generally works. |
This subcategory reports other logon/logoff-related events, such as Remote Desktop Services session disconnects and reconnects, using RunAs to run processes under a different account, and locking and unlocking a workstation. Events for this subcategory include:
The recommended state for this setting is: Success and Failure .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to Success and Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff\Audit Other Logon/Logoff Events
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.5.5_L1_Ensure_Audit_Other_LogonLogoff_Events_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.602-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/10" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/13" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36322-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.602-05:00" start-time="2020-04-22T15:48:23.586-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'other_logon_logoff_events' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817124" result="false" testref="oval:org.cisecurity.benchmarks:tst:817124" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817124"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="other_logon_logoff_events" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817124" value-id="xccdf_org.cisecurity.benchmarks_value_817124_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817124"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36322-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.13 |
Label: | Alert on Account Login Behavior Deviation |
Description: | Alert when users deviate from normal login behavior, such as time-of-day, workstation location and duration. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.6 |
Label: | Maintain an Inventory of Accounts |
Description: | Maintain an inventory of all accounts organized by authentication system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.10 |
Label: | Profile User Account Usage And Monitor For Anomalies |
Description: | Profile each user’s typical account usage by determining normal time-of-day access and access duration. Reports should be generated that indicate users who have logged in during unusual hours or have exceeded their normal login duration. This includes flagging the use of the user’s credentials from a computer other than computers on which the user generally works. |
This subcategory reports when a special logon is used. A special logon is a logon that has administrator-equivalent privileges and can be used to elevate a process to a higher level. Events for this subcategory include:
The recommended state for this setting is to include: Success .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to include Success :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff\Audit Special Logon
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.5.6_L1_Ensure_Audit_Special_Logon_is_set_to_include_Success" role="full" severity="unknown" time="2020-04-22T15:48:23.602-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/8" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36266-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.602-05:00" start-time="2020-04-22T15:48:23.602-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'special_logon' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817132" result="false" testref="oval:org.cisecurity.benchmarks:tst:817132" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817132"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="special_logon" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'special_logon' is 'Equals' to 'AUDIT_SUCCESS'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817129" result="false" testref="oval:org.cisecurity.benchmarks:tst:817129" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817129"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS" name="special_logon" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817129" value-id="xccdf_org.cisecurity.benchmarks_value_817129_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817129"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817132" value-id="xccdf_org.cisecurity.benchmarks_value_817132_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817132"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36266-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.6 |
Label: | Maintain an Inventory of Accounts |
Description: | Maintain an inventory of all accounts organized by authentication system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.8 |
Label: | Administrators Should Not Directly Log In To A System (i.e. use RunAs/sudo) |
Description: | Administrators should be required to access a system using a fully logged and non-administrative account. Then, once logged on to the machine without administrative privileges, the administrator should transition to administrative privileges using tools such as Sudo on Linux/UNIX, RunAs on Windows, and other similar facilities for other types of systems. |
This section contains recommendations for configuring the Object Access audit policy.
This subcategory allows you to audit attempts to access files and folders on a shared folder. Events for this subcategory include:
The recommended state for this setting is to include: Failure
Auditing the Failures will log which unauthorized users attempted (and failed) to get access to a file or folder on a network share on this computer, which could possibly be an indication of malicious intent.
To establish the recommended configuration via GP, set the following UI path to include Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access\Audit Detailed File Share
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.6.1_L1_Ensure_Audit_Detailed_File_Share_is_set_to_include_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.618-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36878-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.618-05:00" start-time="2020-04-22T15:48:23.602-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'detailed_file_share' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817110" result="false" testref="oval:org.cisecurity.benchmarks:tst:817110" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817110"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="detailed_file_share" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'detailed_file_share' is 'Equals' to 'AUDIT_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817106" result="false" testref="oval:org.cisecurity.benchmarks:tst:817106" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817106"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_FAILURE" name="detailed_file_share" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817106" value-id="xccdf_org.cisecurity.benchmarks_value_817106_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817106"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817110" value-id="xccdf_org.cisecurity.benchmarks_value_817110_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817110"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36878-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.6 |
Label: | Protect Information through Access Control Lists |
Description: | Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
This policy setting allows you to audit attempts to access a shared folder.
The recommended state for this setting is: Success and Failure .
Note: There are no system access control lists (SACLs) for shared folders. If this policy setting is enabled, access to all shared folders on the system is audited.
In an enterprise managed environment, it's important to track deletion, creation, modification, and access events for network shares. Any unusual file sharing activity may be useful in an investigation of potentially malicious activity.
To establish the recommended configuration via GP, set the following UI path to Success and Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access\Audit File Share
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.6.2_L1_Ensure_Audit_File_Share_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.618-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37384-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817115" definition_negate="false"> <cis:and negated="false" result="false"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'file_share' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817115" result="false" testref="oval:org.cisecurity.benchmarks:tst:817115" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817115"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="file_share" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817115" value-id="xccdf_org.cisecurity.benchmarks_value_817115_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817115"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37384-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.6 |
Label: | Protect Information through Access Control Lists |
Description: | Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.4 |
Label: | Protect Information With Access Control Lists |
Description: | All information stored on systems shall be protected with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principal that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
This policy setting allows you to audit events generated by the management of task scheduler jobs or COM+ objects.
For scheduler jobs, the following are audited:
For COM+ objects, the following are audited:
The recommended state for this setting is: Success and Failure .
The unexpected creation of scheduled tasks and COM+ objects could potentially be an indication of malicious activity. Since these types of actions are generally low volume, it may be useful to capture them in the audit logs for use during an investigation.
To establish the recommended configuration via GP, set the following UI path to Success and Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access\Audit Other Object Access Events
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.6.3_L1_Ensure_Audit_Other_Object_Access_Events_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.618-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37620-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.618-05:00" start-time="2020-04-22T15:48:23.618-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'other_object_access_events' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817102" result="false" testref="oval:org.cisecurity.benchmarks:tst:817102" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817102"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="other_object_access_events" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817102" value-id="xccdf_org.cisecurity.benchmarks_value_817102_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817102"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37620-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.2 |
Label: | Ensure Audit Log Settings Support Appropriate Log Entry Formating |
Description: | Validate audit log settings for each hardware device and the software installed on it, ensuring that logs include a date, timestamp, source addresses, destination addresses, and various other useful elements of each packet and/or transaction. Systems should record logs in a standardized format such as syslog entries or those outlined by the Common Event Expression initiative. If systems cannot generate logs in a standardized format, log normalization tools can be deployed to convert logs into such a format. |
This policy setting allows you to audit user attempts to access file system objects on a removable storage device. A security audit event is generated only for all objects for all types of access requested. If you configure this policy setting, an audit event is generated each time an account accesses a file system object on a removable storage. Success audits record successful attempts and Failure audits record unsuccessful attempts. If you do not configure this policy setting, no audit event is generated when an account accesses a file system object on a removable storage.
The recommended state for this setting is: Success and Failure .
Note: A Windows 8.0, Server 2012 (non-R2) or newer OS is required to access and set this value in Group Policy.
Auditing removable storage may be useful when investigating an incident. For example, if an individual is suspected of copying sensitive information onto a USB drive.
To establish the recommended configuration via GP, set the following UI path to Success and Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Object Access\Audit Removable Storage
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.6.4_L1_Ensure_Audit_Removable_Storage_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.633-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/13/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37617-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.633-05:00" start-time="2020-04-22T15:48:23.618-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'removable_storage' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817096" result="false" testref="oval:org.cisecurity.benchmarks:tst:817096" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817096"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="removable_storage" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817096" value-id="xccdf_org.cisecurity.benchmarks_value_817096_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817096"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37617-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Configure Anti-Malware Scanning of Removable Devices |
Description: | Configure devices so that they automatically conduct an anti-malware scan of removable media when inserted or connected. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.5 |
Label: | Configure Devices Not To Auto-Run Content |
Description: | Configure devices to not auto-run content from removable media. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
Subcontrol: | 13.8 |
Label: | Manage System's External Removable Media's Read/Write Configurations |
Description: | Configure systems not to write data to external removable media, if there is no business need for supporting such devices. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.3 |
Label: | Limit Use Of External Devices (i.e. USB) |
Description: | Limit use of external devices to those with an approved, documented business need. Monitor for use and attempted use of external devices. Configure laptops, workstations, and servers so that they will not auto-run content from removable media, like USB tokens (i.e., “thumb drives”), USB hard drives, CDs/DVDs, FireWire devices, external serial advanced technology attachment devices, and mounted network shares. Configure systems so that they automatically conduct an anti-malware scan of removable media when inserted. |
This section contains recommendations for configuring the Policy Change audit policy.
This subcategory reports changes in audit policy including SACL changes. Events for this subcategory include:
The recommended state for this setting is include: Success .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to include Success :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Policy Change\Audit Audit Policy Change
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.7.1_L1_Ensure_Audit_Audit_Policy_Change_is_set_to_include_Success" role="full" severity="unknown" time="2020-04-22T15:48:23.633-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/9" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38028-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.633-05:00" start-time="2020-04-22T15:48:23.633-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'audit_policy_change' is 'Equals' to 'AUDIT_SUCCESS'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817108" result="false" testref="oval:org.cisecurity.benchmarks:tst:817108" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817108"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS" name="audit_policy_change" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'audit_policy_change' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817111" result="false" testref="oval:org.cisecurity.benchmarks:tst:817111" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817111"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="audit_policy_change" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817108" value-id="xccdf_org.cisecurity.benchmarks_value_817108_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817108"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817111" value-id="xccdf_org.cisecurity.benchmarks_value_817111_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817111"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38028-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.5 |
Label: | Implement Automated Configuration Monitoring Systems |
Description: | Utilize a Security Content Automation Protocol (SCAP) compliant configuration monitoring system to verify all security configuration elements, catalog approved exceptions, and alert when unauthorized changes occur. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.9 |
Label: | Enforce Detail Logging for Access or Changes to Sensitive Data |
Description: | Enforce detailed audit logging for access to sensitive data or changes to sensitive data (utilizing tools such as File Integrity Monitoring or Security Information and Event Monitoring). |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 3.5 |
Label: | Use File Integrity Tools For Critical System Files |
Description: | Use file integrity checking tools to ensure that critical system files (including sensitive system and application executables, libraries, and configurations) have not been altered. The reporting system should: have the ability to account for routine and expected changes; highlight and alert on unusual or unexpected alterations; show the history of configuration changes over time and identify who made the change (including the original logged-in account in the event of a user ID switch, such as with the su or sudo command). These integrity checks should identify suspicious system alterations such as: owner and permissions changes to files or directories; the use of alternate data streams which could be used to hide malicious activities; and the introduction of extra files into key system areas (which could indicate malicious payloads left by attackers or additional files inappropriately added during batch distribution processes). |
This subcategory reports changes in authentication policy. Events for this subcategory include:
The recommended state for this setting is to include: Success .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to include Success :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Policy Change\Audit Authentication Policy Change
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.7.2_L1_Ensure_Audit_Authentication_Policy_Change_is_set_to_include_Success" role="full" severity="unknown" time="2020-04-22T15:48:23.633-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/9" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38327-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.633-05:00" start-time="2020-04-22T15:48:23.633-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'authentication_policy_change' is 'Equals' to 'AUDIT_SUCCESS'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817116" result="false" testref="oval:org.cisecurity.benchmarks:tst:817116" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817116"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS" name="authentication_policy_change" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'authentication_policy_change' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817118" result="false" testref="oval:org.cisecurity.benchmarks:tst:817118" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817118"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="authentication_policy_change" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817116" value-id="xccdf_org.cisecurity.benchmarks_value_817116_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817116"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817118" value-id="xccdf_org.cisecurity.benchmarks_value_817118_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817118"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38327-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.5 |
Label: | Implement Automated Configuration Monitoring Systems |
Description: | Utilize a Security Content Automation Protocol (SCAP) compliant configuration monitoring system to verify all security configuration elements, catalog approved exceptions, and alert when unauthorized changes occur. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.9 |
Label: | Enforce Detail Logging for Access or Changes to Sensitive Data |
Description: | Enforce detailed audit logging for access to sensitive data or changes to sensitive data (utilizing tools such as File Integrity Monitoring or Security Information and Event Monitoring). |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 3.5 |
Label: | Use File Integrity Tools For Critical System Files |
Description: | Use file integrity checking tools to ensure that critical system files (including sensitive system and application executables, libraries, and configurations) have not been altered. The reporting system should: have the ability to account for routine and expected changes; highlight and alert on unusual or unexpected alterations; show the history of configuration changes over time and identify who made the change (including the original logged-in account in the event of a user ID switch, such as with the su or sudo command). These integrity checks should identify suspicious system alterations such as: owner and permissions changes to files or directories; the use of alternate data streams which could be used to hide malicious activities; and the introduction of extra files into key system areas (which could indicate malicious payloads left by attackers or additional files inappropriately added during batch distribution processes). |
This subcategory reports changes in authorization policy. Events for this subcategory include:
The recommended state for this setting is to include: Success .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to include Success :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Policy Change\Audit Authorization Policy Change
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.7.3_L1_Ensure_Audit_Authorization_Policy_Change_is_set_to_include_Success" role="full" severity="unknown" time="2020-04-22T15:48:23.649-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/9" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36320-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.649-05:00" start-time="2020-04-22T15:48:23.649-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'authorization_policy_change' is 'Equal' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817126" result="false" testref="oval:org.cisecurity.benchmarks:tst:817126" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817126"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="authorization_policy_change" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'authorization_policy_change' is 'Equal' to 'AUDIT_SUCCESS'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817123" result="false" testref="oval:org.cisecurity.benchmarks:tst:817123" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817123"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS" name="authorization_policy_change" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817123" value-id="xccdf_org.cisecurity.benchmarks_value_817123_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817123"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817126" value-id="xccdf_org.cisecurity.benchmarks_value_817126_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817126"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36320-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.5 |
Label: | Implement Automated Configuration Monitoring Systems |
Description: | Utilize a Security Content Automation Protocol (SCAP) compliant configuration monitoring system to verify all security configuration elements, catalog approved exceptions, and alert when unauthorized changes occur. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.9 |
Label: | Enforce Detail Logging for Access or Changes to Sensitive Data |
Description: | Enforce detailed audit logging for access to sensitive data or changes to sensitive data (utilizing tools such as File Integrity Monitoring or Security Information and Event Monitoring). |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 3.5 |
Label: | Use File Integrity Tools For Critical System Files |
Description: | Use file integrity checking tools to ensure that critical system files (including sensitive system and application executables, libraries, and configurations) have not been altered. The reporting system should: have the ability to account for routine and expected changes; highlight and alert on unusual or unexpected alterations; show the history of configuration changes over time and identify who made the change (including the original logged-in account in the event of a user ID switch, such as with the su or sudo command). These integrity checks should identify suspicious system alterations such as: owner and permissions changes to files or directories; the use of alternate data streams which could be used to hide malicious activities; and the introduction of extra files into key system areas (which could indicate malicious payloads left by attackers or additional files inappropriately added during batch distribution processes). |
This subcategory determines whether the operating system generates audit events when changes are made to policy rules for the Microsoft Protection Service (MPSSVC.exe). Events for this subcategory include:
4944: The following policy was active when the Windows Firewall started.
4945: A rule was listed when the Windows Firewall started.
4946: A change has been made to Windows Firewall exception list. A rule was added.
4947: A change has been made to Windows Firewall exception list. A rule was modified.
4948: A change has been made to Windows Firewall exception list. A rule was deleted.
4949: Windows Firewall settings were restored to the default values.
4950: A Windows Firewall setting has changed.
4951: A rule has been ignored because its major version number was not recognized by Windows Firewall.
4952: Parts of a rule have been ignored because its minor version number was not recognized by Windows Firewall. The other parts of the rule will be enforced.
4953: A rule has been ignored by Windows Firewall because it could not parse the rule.
4954: Windows Firewall Group Policy settings have changed. The new settings have been applied.
4956: Windows Firewall has changed the active profile.
4957: Windows Firewall did not apply the following rule.
4958: Windows Firewall did not apply the following rule because the rule referred to items not configured on this computer.
The recommended state for this setting is : Success and Failure
Changes to firewall rules are important for understanding the security state of the computer and how well it is protected against network attacks.
To establish the recommended configuration via GP, set the following UI path to Success and Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Policy Change\Audit MPSSVC Rule-Level Policy Change
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.7.4_L1_Ensure_Audit_MPSSVC_Rule-Level_Policy_Change_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.649-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37852-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817131" definition_negate="false"> <cis:and negated="false" result="false"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'mpssvc_rule_level_policy_change' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817131" result="false" testref="oval:org.cisecurity.benchmarks:tst:817131" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817131"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="mpssvc_rule_level_policy_change" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817131" value-id="xccdf_org.cisecurity.benchmarks_value_817131_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817131"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37852-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
This subcategory contains events about EFS Data Recovery Agent policy changes, changes in Windows Filtering Platform filter, status on Security policy settings updates for local Group Policy settings, Central Access Policy changes, and detailed troubleshooting events for Cryptographic Next Generation (CNG) operations.
5063: A cryptographic provider operation was attempted.
5064: A cryptographic context operation was attempted.
5065: A cryptographic context modification was attempted.
5066: A cryptographic function operation was attempted.
5067: A cryptographic function modification was attempted.
5068: A cryptographic function provider operation was attempted.
5069: A cryptographic function property operation was attempted.
5070: A cryptographic function property modification was attempted.
6145: One or more errors occurred while processing security policy in the group policy objects.
The recommended state for this setting is to include: Failure .
This setting can help detect errors in applied Security settings which came from Group Policy, and failure events related to Cryptographic Next Generation (CNG) functions.
To establish the recommended configuration via GP, set the following UI path to include Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Policy Change\Audit Other Policy Change Events
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.7.5_L1_Ensure_Audit_Other_Policy_Change_Events_is_set_to_include_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.664-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38029-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.664-05:00" start-time="2020-04-22T15:48:23.649-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'other_policy_change_events' is 'Equals' to 'AUDIT_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817135" result="false" testref="oval:org.cisecurity.benchmarks:tst:817135" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817135"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_FAILURE" name="other_policy_change_events" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'other_policy_change_events' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817136" result="false" testref="oval:org.cisecurity.benchmarks:tst:817136" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817136"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="other_policy_change_events" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817135" value-id="xccdf_org.cisecurity.benchmarks_value_817135_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817135"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817136" value-id="xccdf_org.cisecurity.benchmarks_value_817136_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817136"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38029-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
This section contains recommendations for configuring the Privilege Use audit policy.
This subcategory reports when a user account or service uses a sensitive privilege. A sensitive privilege includes the following user rights:
Auditing this subcategory will create a high volume of events. Events for this subcategory include:
The recommended state for this setting is: Success and Failure .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to Success and Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Privilege Use\Audit Sensitive Privilege Use
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.8.1_L1_Ensure_Audit_Sensitive_Privilege_Use_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.664-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36267-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.664-05:00" start-time="2020-04-22T15:48:23.664-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'sensitive_privilege_use' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817122" result="false" testref="oval:org.cisecurity.benchmarks:tst:817122" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817122"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="sensitive_privilege_use" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817122" value-id="xccdf_org.cisecurity.benchmarks_value_817122_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817122"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36267-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This section contains recommendations for configuring the System audit policy.
This subcategory reports on the activities of the Internet Protocol security (IPsec) driver. Events for this subcategory include:
The recommended state for this setting is: Success and Failure .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to Success and Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\System\Audit IPsec Driver
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.9.1_L1_Ensure_Audit_IPsec_Driver_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.664-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37853-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.664-05:00" start-time="2020-04-22T15:48:23.664-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ipsec_driver' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817127" result="false" testref="oval:org.cisecurity.benchmarks:tst:817127" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817127"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="ipsec_driver" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817127" value-id="xccdf_org.cisecurity.benchmarks_value_817127_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817127"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37853-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This subcategory reports on other system events. Events for this subcategory include:
The recommended state for this setting is: Success and Failure .
Capturing these audit events may be useful for identifying when the Windows Firewall is not performing as expected.
To establish the recommended configuration via GP, set the following UI path to Success and Failure :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\System\Audit Other System Events
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.9.2_L1_Ensure_Audit_Other_System_Events_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.664-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38030-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.664-05:00" start-time="2020-04-22T15:48:23.664-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'other_system_events' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817133" result="false" testref="oval:org.cisecurity.benchmarks:tst:817133" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817133"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="other_system_events" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817133" value-id="xccdf_org.cisecurity.benchmarks_value_817133_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817133"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38030-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.4 |
Label: | Apply Host-Based Firewalls or Port Filtering |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Leverage Host-based Firewalls |
Description: | Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed. |
This subcategory reports changes in security state of the system, such as when the security subsystem starts and stops. Events for this subcategory include:
The recommended state for this setting is to include: Success .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to include Success :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\System\Audit Security State Change
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.9.3_L1_Ensure_Audit_Security_State_Change_is_set_to_include_Success" role="full" severity="unknown" time="2020-04-22T15:48:23.680-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38114-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.680-05:00" start-time="2020-04-22T15:48:23.680-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'security_state_change' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817139" result="false" testref="oval:org.cisecurity.benchmarks:tst:817139" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817139"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="security_state_change" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'security_state_change' is 'Equals' to 'AUDIT_SUCCESS'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817137" result="false" testref="oval:org.cisecurity.benchmarks:tst:817137" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817137"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS" name="security_state_change" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817137" value-id="xccdf_org.cisecurity.benchmarks_value_817137_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817137"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817139" value-id="xccdf_org.cisecurity.benchmarks_value_817139_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817139"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38114-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
This subcategory reports the loading of extension code such as authentication packages by the security subsystem. Events for this subcategory include:
The recommended state for this setting is to include: Success .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to include Success :
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\System\Audit Security System Extension
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
Any of the following tests or sub-groups may pass: | ||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.9.4_L1_Ensure_Audit_Security_System_Extension_is_set_to_include_Success" role="full" severity="unknown" time="2020-04-22T15:48:23.680-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36144-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.680-05:00" start-time="2020-04-22T15:48:23.680-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'security_system_extension' is 'Equals' to 'AUDIT_SUCCESS'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817142" result="false" testref="oval:org.cisecurity.benchmarks:tst:817142" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817142"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS" name="security_system_extension" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'security_system_extension' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817144" result="false" testref="oval:org.cisecurity.benchmarks:tst:817144" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817144"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="security_system_extension" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817142" value-id="xccdf_org.cisecurity.benchmarks_value_817142_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817142"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817144" value-id="xccdf_org.cisecurity.benchmarks_value_817144_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817144"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36144-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
This subcategory reports on violations of integrity of the security subsystem. Events for this subcategory include:
The recommended state for this setting is: Success and Failure .
Auditing these events may be useful when investigating a security incident.
To establish the recommended configuration via GP, set the following UI path to Success and Failure:
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\System\Audit System Integrity
Impact:
If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_17.9.5_L1_Ensure_Audit_System_Integrity_is_set_to_Success_and_Failure" role="full" severity="unknown" time="2020-04-22T15:48:23.696-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37132-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.696-05:00" start-time="2020-04-22T15:48:23.680-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'system_integrity' is 'Equals' to 'AUDIT_SUCCESS_FAILURE'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817148" result="false" testref="oval:org.cisecurity.benchmarks:tst:817148" type="auditeventpolicysubcategories_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817148"> <cis:evidence_item itemref="900"> <cis:evidence_item_pk status="exists"/> <cis:evidence_field cv="AUDIT_NONE" dt="string" ev="AUDIT_SUCCESS_FAILURE" name="system_integrity" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:817148" value-id="xccdf_org.cisecurity.benchmarks_value_817148_var"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817148"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37132-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
This section contains computer-based recommendations from Group Policy Administrative Templates (ADMX).
This section contains recommendations for Control Panel settings.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for Control Panel personalization settings.
This Group Policy section is provided by the Group Policy template ControlPanelDisplay.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Disables the lock screen camera toggle switch in PC Settings and prevents a camera from being invoked on the lock screen.
The recommended state for this setting is: Enabled .
Disabling the lock screen camera extends the protection afforded by the lock screen to camera features.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Control Panel\Personalization\Prevent enabling lock screen camera
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template ControlPanelDisplay.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Impact:
If you enable this setting, users will no longer be able to enable or disable lock screen camera access in PC Settings, and the camera cannot be invoked on the lock screen.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.1.1.1_L1_Ensure_Prevent_enabling_lock_screen_camera_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:23.758-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38347-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.774-05:00" start-time="2020-04-22T15:48:23.696-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoLockScreenCamera' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817235" result="true" testref="oval:org.cisecurity.benchmarks:tst:817235" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817235"> <cis:evidence_item itemref="901"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\Personalization"/> <cis:evidence_item_pk_field name="name" value="NoLockScreenCamera"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172351" value-id="xccdf_org.cisecurity.benchmarks_value_817235_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172352" value-id="xccdf_org.cisecurity.benchmarks_value_817235_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817235"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38347-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
Disables the lock screen slide show settings in PC Settings and prevents a slide show from playing on the lock screen.
The recommended state for this setting is: Enabled .
Disabling the lock screen slide show extends the protection afforded by the lock screen to slide show contents.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Control Panel\Personalization\Prevent enabling lock screen slide show
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template ControlPanelDisplay.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Impact:
If you enable this setting, users will no longer be able to modify slide show settings in PC Settings, and no slide show will ever start.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.1.1.2_L1_Ensure_Prevent_enabling_lock_screen_slide_show_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:23.836-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38348-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.836-05:00" start-time="2020-04-22T15:48:23.774-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoLockScreenSlideshow' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817253" result="true" testref="oval:org.cisecurity.benchmarks:tst:817253" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817253"> <cis:evidence_item itemref="902"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\Personalization"/> <cis:evidence_item_pk_field name="name" value="NoLockScreenSlideshow"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172531" value-id="xccdf_org.cisecurity.benchmarks_value_817253_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172532" value-id="xccdf_org.cisecurity.benchmarks_value_817253_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817253"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38348-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
This section contains recommendation settings for Regional and Language Options.
This Group Policy section is provided by the Group Policy template Globalization.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Globalization.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This policy enables the automatic learning component of input personalization that includes speech, inking, and typing. Automatic learning enables the collection of speech and handwriting patterns, typing history, contacts, and recent calendar information. It is required for the use of Cortana. Some of this collected information may be stored on the user's OneDrive, in the case of inking and typing; some of the information will be uploaded to Microsoft to personalize speech.
The recommended state for this setting is: Disabled .
If this setting is Enabled sensitive information could be stored in the cloud or sent to Microsoft.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Control Panel\Regional and Language Options\Allow users to enable online speech recognition services
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template Globalization.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Allow input personalization , but it was renamed to Allow users to enable online speech recognition services starting with the Windows 10 R1809 & Server 2019 Administrative Templates.
Impact:
Automatic learning of speech, inking, and typing stops and users cannot change its value via PC Settings.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.1.2.2_L1_Ensure_Allow_users_to_enable_online_speech_recognition_services_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:23.899-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.899-05:00" start-time="2020-04-22T15:48:23.836-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowInputPersonalization' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817230" result="true" testref="oval:org.cisecurity.benchmarks:tst:817230" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817230"> <cis:evidence_item itemref="903"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\InputPersonalization"/> <cis:evidence_item_pk_field name="name" value="AllowInputPersonalization"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172301" value-id="xccdf_org.cisecurity.benchmarks_value_817230_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172302" value-id="xccdf_org.cisecurity.benchmarks_value_817230_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817230"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This section contains recommendations for configuring Microsoft Local Administrator Password Solution (LAPS).
This Group Policy section is provided by the Group Policy template AdmPwd.admx/adml that is included with LAPS.
In May 2015, Microsoft released the Local Administrator Password Solution (LAPS) tool, which is free and supported software that allows an organization to automatically set randomized and unique local Administrator account passwords on domain-attached workstations and Member Servers. The passwords are stored in a confidential attribute of the domain computer account and can be retrieved from Active Directory by approved Sysadmins when needed.
The LAPS tool requires a small Active Directory Schema update in order to implement, as well as installation of a Group Policy Client Side Extension (CSE) on targeted computers. Please see the LAPS documentation for details.
LAPS supports Windows Vista or newer workstation OSes, and Server 2003 or newer server OSes. LAPS does not support standalone computers - they must be joined to a domain.
Note: Organizations that utilize 3rd-party commercial software to manage unique & complex local Administrator passwords on domain members may opt to disregard these LAPS recommendations.
Note #2: LAPS is only designed to manage local Administrator passwords, and is therefore not recommended (or supported) for use directly on Domain Controllers, which do not have a traditional local Administrator account. We strongly encourage you to only deploy the LAPS CSE and LAPS GPO settings to member servers and workstations.
Due to the difficulty in managing local Administrator passwords, many organizations choose to use the same password on all workstations and/or Member Servers when deploying them. This creates a serious attack surface security risk because if an attacker manages to compromise one system and learn the password to its local Administrator account, then they can leverage that account to instantly gain access to all other computers that also use that password for their local Administrator account.
In order to utilize LAPS, a minor Active Directory Schema update is required, and a Group Policy Client Side Extension (CSE) must be installed on each managed computer. When LAPS is installed, the file AdmPwd.dll must be present in the following location and registered in Windows (the LAPS AdmPwd GPO Extension / CSE installation does this for you):
C:\Program Files\LAPS\CSE\AdmPwd.dll
Impact:
No impact. When installed and registered properly, AdmPwd.dll takes no action unless given appropriate GPO commands during Group Policy refresh. It is not a memory-resident agent or service.
In a disaster recovery scenario where Active Directory is not available, the local Administrator password will not be retrievable and a local password reset using a tool (such as Microsoft's Disaster and Recovery Toolset (DaRT) Recovery Image) may be necessary.
Any of the following tests or sub-groups may pass: | ||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.2.1_L1_Ensure_LAPS_AdmPwd_GPO_Extension__CSE_is_installed_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:23.977-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:23.977-05:00" start-time="2020-04-22T15:48:23.899-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DllName' is 'Windows: Registry Value' to 'C:\Program Files\LAPS\CSE\AdmPwd.dll'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817141" result="false" testref="oval:org.cisecurity.benchmarks:tst:817141" type="registry_test"> <cis:evidence_object> <cis:evidence_item itemref="904"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions\{D76B9641-3288-4f75-942D-087DE603E3EA}"/> <cis:evidence_item_pk_field name="name" value="DllName"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DllName' is 'Windows: Registry Value' to 'C:\Program Files\LAPS\CSE\AdmPwd.dll'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817147" result="false" testref="oval:org.cisecurity.benchmarks:tst:817147" type="registry_test"> <cis:evidence_object> <cis:evidence_item itemref="905"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions\{D76B9641-3288-4f75-942D-087DE603E3EA}"/> <cis:evidence_item_pk_field name="name" value="DllName"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171411" value-id="xccdf_org.cisecurity.benchmarks_value_817141_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171412" value-id="xccdf_org.cisecurity.benchmarks_value_817141_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817141"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171471" value-id="xccdf_org.cisecurity.benchmarks_value_817147_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171472" value-id="xccdf_org.cisecurity.benchmarks_value_817147_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817147"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.9 |
Label: | Configure Account Access Centrally |
Description: | Configure access for all accounts through a centralized point of authentication, for example Active Directory or LDAP. Configure network and security devices for centralized authentication as well. |
In May 2015, Microsoft released the Local Administrator Password Solution (LAPS) tool, which is free and supported software that allows an organization to automatically set randomized and unique local Administrator account passwords on domain-attached workstations and Member Servers. The passwords are stored in a confidential attribute of the domain computer account and can be retrieved from Active Directory by approved Sysadmins when needed.
The LAPS tool requires a small Active Directory Schema update in order to implement, as well as installation of a Group Policy Client Side Extension (CSE) on targeted computers. Please see the LAPS documentation for details.
LAPS supports Windows Vista or newer workstation OSes, and Server 2003 or newer server OSes. LAPS does not support standalone computers - they must be joined to a domain.
The recommended state for this setting is: Enabled .
Note: Organizations that utilize 3rd-party commercial software to manage unique & complex local Administrator passwords on domain members may opt to disregard these LAPS recommendations.
Note #2: LAPS is only designed to manage local Administrator passwords, and is therefore not recommended (or supported) for use directly on Domain Controllers, which do not have a traditional local Administrator account. We strongly encourage you to only deploy the LAPS CSE and LAPS GPO settings to member servers and workstations.
Note #2: LAPS is only designed to manage local Administrator passwords, and is therefore not recommended (or supported) for use directly on Domain Controllers, which do not have a traditional local Administrator account. We strongly encourage you to only deploy the LAPS CSE and LAPS GPO settings to member servers and workstations.
Due to the difficulty in managing local Administrator passwords, many organizations choose to use the same password on all workstations and/or Member Servers when deploying them. This creates a serious attack surface security risk because if an attacker manages to compromise one system and learn the password to its local Administrator account, then they can leverage that account to instantly gain access to all other computers that also use that password for their local Administrator account.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\LAPS\Do not allow password expiration time longer than required by policy
Note: This Group Policy path does not exist by default. An additional Group Policy template ( AdmPwd.admx/adml ) is required - it is included with Microsoft Local Administrator Password Solution (LAPS).
Impact:
Planned password expiration longer than password age dictated by "Password Settings" policy is NOT allowed.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.2.2_L1_Ensure_Do_not_allow_password_expiration_time_longer_than_required_by_policy_is_set_to_Enabled_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:24.055-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/10" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:24.055-05:00" start-time="2020-04-22T15:48:23.993-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'PwdExpirationProtectionEnabled' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817158" result="true" testref="oval:org.cisecurity.benchmarks:tst:817158" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817158"> <cis:evidence_item itemref="906"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft Services\AdmPwd"/> <cis:evidence_item_pk_field name="name" value="PwdExpirationProtectionEnabled"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171581" value-id="xccdf_org.cisecurity.benchmarks_value_817158_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171582" value-id="xccdf_org.cisecurity.benchmarks_value_817158_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817158"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.10 |
Label: | Ensure All Accounts Have An Expiration Date |
Description: | Ensure that all accounts have an expiration date that is monitored and enforced. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | All Accounts Have A Monitored Expiration Date |
Description: | Ensure that all accounts have an expiration date that is monitored and enforced. |
In May 2015, Microsoft released the Local Administrator Password Solution (LAPS) tool, which is free and supported software that allows an organization to automatically set randomized and unique local Administrator account passwords on domain-attached workstations and Member Servers. The passwords are stored in a confidential attribute of the domain computer account and can be retrieved from Active Directory by approved Sysadmins when needed.
The LAPS tool requires a small Active Directory Schema update in order to implement, as well as installation of a Group Policy Client Side Extension (CSE) on targeted computers. Please see the LAPS documentation for details.
LAPS supports Windows Vista or newer workstation OSes, and Server 2003 or newer server OSes. LAPS does not support standalone computers - they must be joined to a domain.
The recommended state for this setting is: Enabled .
Note: Organizations that utilize 3rd-party commercial software to manage unique & complex local Administrator passwords on domain members may opt to disregard these LAPS recommendations.
Note #2: LAPS is only designed to manage local Administrator passwords, and is therefore not recommended (or supported) for use directly on Domain Controllers, which do not have a traditional local Administrator account. We strongly encourage you to only deploy the LAPS CSE and LAPS GPO settings to member servers and workstations.
Due to the difficulty in managing local Administrator passwords, many organizations choose to use the same password on all workstations and/or Member Servers when deploying them. This creates a serious attack surface security risk because if an attacker manages to compromise one system and learn the password to its local Administrator account, then they can leverage that account to instantly gain access to all other computers that also use that password for their local Administrator account.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\LAPS\Enable Local Admin Password Management
Note: This Group Policy path does not exist by default. An additional Group Policy template ( AdmPwd.admx/adml ) is required - it is included with Microsoft Local Administrator Password Solution (LAPS).
Impact:
The local administrator password is managed (provided that the LAPS AdmPwd GPO Extension / CSE is installed on the target computer (see Rule 18.2.1), the Active Directory domain schema and account permissions have been properly configured on the domain).
In a disaster recovery scenario where Active Directory is not available, the local Administrator password will not be retrievable and a local password reset using a tool (such as Microsoft's Disaster and Recovery Toolset (DaRT) Recovery Image) may be necessary.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.2.3_L1_Ensure_Enable_Local_Admin_Password_Management_is_set_to_Enabled_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:24.133-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:24.133-05:00" start-time="2020-04-22T15:48:24.071-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AdmPwdEnabled' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817171" result="true" testref="oval:org.cisecurity.benchmarks:tst:817171" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817171"> <cis:evidence_item itemref="907"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft Services\AdmPwd"/> <cis:evidence_item_pk_field name="name" value="AdmPwdEnabled"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171711" value-id="xccdf_org.cisecurity.benchmarks_value_817171_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171712" value-id="xccdf_org.cisecurity.benchmarks_value_817171_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817171"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.4 |
Label: | Use Unique Passwords |
Description: | Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.9 |
Label: | Configure Account Access Centrally |
Description: | Configure access for all accounts through a centralized point of authentication, for example Active Directory or LDAP. Configure network and security devices for centralized authentication as well. |
In May 2015, Microsoft released the Local Administrator Password Solution (LAPS) tool, which is free and supported software that allows an organization to automatically set randomized and unique local Administrator account passwords on domain-attached workstations and Member Servers. The passwords are stored in a confidential attribute of the domain computer account and can be retrieved from Active Directory by approved Sysadmins when needed.
The LAPS tool requires a small Active Directory Schema update in order to implement, as well as installation of a Group Policy Client Side Extension (CSE) on targeted computers. Please see the LAPS documentation for details.
LAPS supports Windows Vista or newer workstation OSes, and Server 2003 or newer server OSes. LAPS does not support standalone computers - they must be joined to a domain.
The recommended state for this setting is: Enabled: Large letters + small letters + numbers + special characters .
Note: Organizations that utilize 3rd-party commercial software to manage unique & complex local Administrator passwords on domain members may opt to disregard these LAPS recommendations.
Note #2: LAPS is only designed to manage local Administrator passwords, and is therefore not recommended (or supported) for use directly on Domain Controllers, which do not have a traditional local Administrator account. We strongly encourage you to only deploy the LAPS CSE and LAPS GPO settings to member servers and workstations.
Due to the difficulty in managing local Administrator passwords, many organizations choose to use the same password on all workstations and/or Member Servers when deploying them. This creates a serious attack surface security risk because if an attacker manages to compromise one system and learn the password to its local Administrator account, then they can leverage that account to instantly gain access to all other computers that also use that password for their local Administrator account.
To establish the recommended configuration via GP, set the following UI path to Enabled , and configure the Password Complexity option to Large letters + small letters + numbers + special characters :
Computer Configuration\Policies\Administrative Templates\LAPS\Password Settings
Note: This Group Policy path does not exist by default. An additional Group Policy template ( AdmPwd.admx/adml ) is required - it is included with Microsoft Local Administrator Password Solution (LAPS).
Impact:
LAPS-generated passwords will be required to contain large letters + small letters + numbers + special characters.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.2.4_L1_Ensure_Password_Settings_Password_Complexity_is_set_to_Enabled_Large_letters__small_letters__numbers__special_characters_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:24.196-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:24.196-05:00" start-time="2020-04-22T15:48:24.133-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'PasswordComplexity' is 'Windows: Registry Value' to '4'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817184" result="true" testref="oval:org.cisecurity.benchmarks:tst:817184" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817184"> <cis:evidence_item itemref="908"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft Services\AdmPwd"/> <cis:evidence_item_pk_field name="name" value="PasswordComplexity"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="4" dt="int" ev="4" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171841" value-id="xccdf_org.cisecurity.benchmarks_value_817184_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171842" value-id="xccdf_org.cisecurity.benchmarks_value_817184_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817184"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.7 |
Label: | User Accounts Shall Use Long Passwords |
Description: | Where multi-factor authentication is not supported, user accounts shall be required to use long passwords on the system (longer than 14 characters). |
In May 2015, Microsoft released the Local Administrator Password Solution (LAPS) tool, which is free and supported software that allows an organization to automatically set randomized and unique local Administrator account passwords on domain-attached workstations and Member Servers. The passwords are stored in a confidential attribute of the domain computer account and can be retrieved from Active Directory by approved Sysadmins when needed.
The LAPS tool requires a small Active Directory Schema update in order to implement, as well as installation of a Group Policy Client Side Extension (CSE) on targeted computers. Please see the LAPS documentation for details.
LAPS supports Windows Vista or newer workstation OSes, and Server 2003 or newer server OSes. LAPS does not support standalone computers - they must be joined to a domain.
The recommended state for this setting is: Enabled: 15 or more .
Note: Organizations that utilize 3rd-party commercial software to manage unique & complex local Administrator passwords on domain members may opt to disregard these LAPS recommendations.
Note #2: LAPS is only designed to manage local Administrator passwords, and is therefore not recommended (or supported) for use directly on Domain Controllers, which do not have a traditional local Administrator account. We strongly encourage you to only deploy the LAPS CSE and LAPS GPO settings to member servers and workstations.
Due to the difficulty in managing local Administrator passwords, many organizations choose to use the same password on all workstations and/or Member Servers when deploying them. This creates a serious attack surface security risk because if an attacker manages to compromise one system and learn the password to its local Administrator account, then they can leverage that account to instantly gain access to all other computers that also use that password for their local Administrator account.
To establish the recommended configuration via GP, set the following UI path to Enabled , and configure the Password Length option to 15 or more :
Computer Configuration\Policies\Administrative Templates\LAPS\Password Settings
Note: This Group Policy path does not exist by default. An additional Group Policy template ( AdmPwd.admx/adml ) is required - it is included with Microsoft Local Administrator Password Solution (LAPS).
Impact:
LAPS-generated passwords will be required to have a length of 15 characters (or more, if selected).
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.2.5_L1_Ensure_Password_Settings_Password_Length_is_set_to_Enabled_15_or_more_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:24.258-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:24.258-05:00" start-time="2020-04-22T15:48:24.196-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'PasswordLength' is 'Windows: Registry Value' to '15'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817198" result="true" testref="oval:org.cisecurity.benchmarks:tst:817198" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817198"> <cis:evidence_item itemref="909"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft Services\AdmPwd"/> <cis:evidence_item_pk_field name="name" value="PasswordLength"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="15" dt="int" ev="15" name="value" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171981" value-id="xccdf_org.cisecurity.benchmarks_value_817198_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171982" value-id="xccdf_org.cisecurity.benchmarks_value_817198_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817198"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.7 |
Label: | User Accounts Shall Use Long Passwords |
Description: | Where multi-factor authentication is not supported, user accounts shall be required to use long passwords on the system (longer than 14 characters). |
In May 2015, Microsoft released the Local Administrator Password Solution (LAPS) tool, which is free and supported software that allows an organization to automatically set randomized and unique local Administrator account passwords on domain-attached workstations and Member Servers. The passwords are stored in a confidential attribute of the domain computer account and can be retrieved from Active Directory by approved Sysadmins when needed.
The LAPS tool requires a small Active Directory Schema update in order to implement, as well as installation of a Group Policy Client Side Extension (CSE) on targeted computers. Please see the LAPS documentation for details.
LAPS supports Windows Vista or newer workstation OSes, and Server 2003 or newer server OSes. LAPS does not support standalone computers - they must be joined to a domain.
The recommended state for this setting is: Enabled: 30 or fewer .
Note: Organizations that utilize 3rd-party commercial software to manage unique & complex local Administrator passwords on domain members may opt to disregard these LAPS recommendations.
Note #2: LAPS is only designed to manage local Administrator passwords, and is therefore not recommended (or supported) for use directly on Domain Controllers, which do not have a traditional local Administrator account. We strongly encourage you to only deploy the LAPS CSE and LAPS GPO settings to member servers and workstations.
Due to the difficulty in managing local Administrator passwords, many organizations choose to use the same password on all workstations and/or Member Servers when deploying them. This creates a serious attack surface security risk because if an attacker manages to compromise one system and learn the password to its local Administrator account, then they can leverage that account to instantly gain access to all other computers that also use that password for their local Administrator account.
To establish the recommended configuration via GP, set the following UI path to Enabled , and configure the Password Age (Days) option to 30 or fewer :
Computer Configuration\Policies\Administrative Templates\LAPS\Password Settings
Note: This Group Policy path does not exist by default. An additional Group Policy template ( AdmPwd.admx/adml ) is required - it is included with Microsoft Local Administrator Password Solution (LAPS).
Impact:
LAPS-generated passwords will be required to have a maximum age of 30 days (or fewer, if selected).
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.2.6_L1_Ensure_Password_Settings_Password_Age_Days_is_set_to_Enabled_30_or_fewer_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:24.336-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:24.336-05:00" start-time="2020-04-22T15:48:24.274-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'PasswordAgeDays' is 'Windows: Registry Value' to '30'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817209" result="true" testref="oval:org.cisecurity.benchmarks:tst:817209" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817209"> <cis:evidence_item itemref="910"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft Services\AdmPwd"/> <cis:evidence_item_pk_field name="name" value="PasswordAgeDays"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="30" dt="int" ev="30" name="value" op="less than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172091" value-id="xccdf_org.cisecurity.benchmarks_value_817209_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172092" value-id="xccdf_org.cisecurity.benchmarks_value_817209_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817209"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This section contains settings for configuring additional settings from the MS Security Guide.
This Group Policy section is provided by the Group Policy template SecGuide.admx/adml that is available from Microsoft at this link .
This setting controls whether local accounts can be used for remote administration via network logon (e.g., NET USE, connecting to C$, etc.). Local accounts are at high risk for credential theft when the same account and password is configured on multiple systems. Enabling this policy significantly reduces that risk.
Enabled: Applies UAC token-filtering to local accounts on network logons. Membership in powerful group such as Administrators is disabled and powerful privileges are removed from the resulting access token. This configures the LocalAccountTokenFilterPolicy registry value to 0 . This is the default behavior for Windows.
Disabled: Allows local accounts to have full administrative rights when authenticating via network logon, by configuring the LocalAccountTokenFilterPolicy registry value to 1 .
For more information about local accounts and credential theft, review the " Mitigating Pass-the-Hash (PtH) Attacks and Other Credential Theft Techniques " documents.
For more information about LocalAccountTokenFilterPolicy , see Microsoft Knowledge Base article 951016: Description of User Account Control and remote restrictions in Windows Vista .
The recommended state for this setting is: Enabled .
Local accounts are at high risk for credential theft when the same account and password is configured on multiple systems. Ensuring this policy is Enabled significantly reduces that risk.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\MS Security Guide\Apply UAC restrictions to local accounts on network logons
Note: This Group Policy path does not exist by default. An additional Group Policy template ( SecGuide.admx/adml ) is required - it is available from Microsoft at this link .
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.3.1_L1_Ensure_Apply_UAC_restrictions_to_local_accounts_on_network_logons_is_set_to_Enabled_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:24.414-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/8" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37069-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:24.414-05:00" start-time="2020-04-22T15:48:24.336-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LocalAccountTokenFilterPolicy' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817150" result="true" testref="oval:org.cisecurity.benchmarks:tst:817150" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817150"> <cis:evidence_item itemref="911"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="LocalAccountTokenFilterPolicy"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171501" value-id="xccdf_org.cisecurity.benchmarks_value_817150_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171502" value-id="xccdf_org.cisecurity.benchmarks_value_817150_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817150"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37069-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.8 |
Label: | Administrators Should Not Directly Log In To A System (i.e. use RunAs/sudo) |
Description: | Administrators should be required to access a system using a fully logged and non-administrative account. Then, once logged on to the machine without administrative privileges, the administrator should transition to administrative privileges using tools such as Sudo on Linux/UNIX, RunAs on Windows, and other similar facilities for other types of systems. |
This setting configures the start type for the Server Message Block version 1 (SMBv1) client driver service ( MRxSmb10 ), which is recommended to be disabled.
The recommended state for this setting is: Enabled: Disable driver (recommended) .
Note: Do not, under any circumstances , configure this overall setting as Disabled , as doing so will delete the underlying registry entry altogether, which will cause serious problems.
Since September 2016, Microsoft has strongly encouraged that SMBv1 be disabled and no longer used on modern networks, as it is a 30 year old design that is much more vulnerable to attacks then much newer designs such as SMBv2 and SMBv3.
More information on this can be found at the following links:
Stop using SMB1 | Storage at Microsoft
Disable SMB v1 in Managed Environments with Group Policy – "Stay Safe" Cyber Security Blog
Disabling SMBv1 through Group Policy – Microsoft Security Guidance blog
To establish the recommended configuration via GP, set the following UI path to Enabled: Disable driver (recommended) :
Computer Configuration\Policies\Administrative Templates\MS Security Guide\Configure SMB v1 client driver
Note: This Group Policy path does not exist by default. An additional Group Policy template ( SecGuide.admx/adml ) is required - it is available from Microsoft at this link .
Impact:
Some legacy OSes (e.g. Windows XP, Server 2003 or older), applications and appliances may no longer be able to communicate with the system once SMBv1 is disabled. We recommend careful testing be performed to determine the impact prior to configuring this as a widespread control, and where possible, remediate any incompatibilities found with the vendor of the incompatible system. Microsoft is also maintaining a thorough (although not comprehensive) list of known SMBv1 incompatibilities at this link: SMB1 Product Clearinghouse | Storage at Microsoft
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.3.2_L1_Ensure_Configure_SMB_v1_client_driver_is_set_to_Enabled_Disable_driver_recommended" role="full" severity="unknown" time="2020-04-22T15:48:24.477-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:24.477-05:00" start-time="2020-04-22T15:48:24.414-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Start' is 'Windows: Registry Value' to '4'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817173" result="true" testref="oval:org.cisecurity.benchmarks:tst:817173" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817173"> <cis:evidence_item itemref="912"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SYSTEM\CurrentControlSet\Services\mrxsmb10"/> <cis:evidence_item_pk_field name="name" value="Start"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="4" dt="int" ev="4" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171731" value-id="xccdf_org.cisecurity.benchmarks_value_817173_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171732" value-id="xccdf_org.cisecurity.benchmarks_value_817173_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817173"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.3 |
Label: | Perform Regular Automated Port Scans |
Description: | Perform automated port scans on a regular basis against all systems and alert if unauthorized ports are detected on a system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.1 |
Label: | Limit Open Ports, Protocols, and Services |
Description: | Ensure that only ports, protocols, and services with validated business needs are running on each system. |
This setting configures the server-side processing of the Server Message Block version 1 (SMBv1) protocol.
The recommended state for this setting is: Disabled .
Since September 2016, Microsoft has strongly encouraged that SMBv1 be disabled and no longer used on modern networks, as it is a 30 year old design that is much more vulnerable to attacks then much newer designs such as SMBv2 and SMBv3.
More information on this can be found at the following links:
Stop using SMB1 | Storage at Microsoft
Disable SMB v1 in Managed Environments with Group Policy – "Stay Safe" Cyber Security Blog
Disabling SMBv1 through Group Policy – Microsoft Security Guidance blog
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\MS Security Guide\Configure SMB v1 server
Note: This Group Policy path does not exist by default. An additional Group Policy template ( SecGuide.admx/adml ) is required - it is available from Microsoft at this link .
Impact:
Some legacy OSes (e.g. Windows XP, Server 2003 or older), applications and appliances may no longer be able to communicate with the system once SMBv1 is disabled. We recommend careful testing be performed to determine the impact prior to configuring this as a widespread control, and where possible, remediate any incompatibilities found with the vendor of the incompatible system. Microsoft is also maintaining a thorough (although not comprehensive) list of known SMBv1 incompatibilities at this link: SMB1 Product Clearinghouse | Storage at Microsoft
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.3.3_L1_Ensure_Configure_SMB_v1_server_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:24.555-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:24.555-05:00" start-time="2020-04-22T15:48:24.493-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'SMB1' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817167" result="true" testref="oval:org.cisecurity.benchmarks:tst:817167" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817167"> <cis:evidence_item itemref="913"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters"/> <cis:evidence_item_pk_field name="name" value="SMB1"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171671" value-id="xccdf_org.cisecurity.benchmarks_value_817167_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171672" value-id="xccdf_org.cisecurity.benchmarks_value_817167_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817167"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.3 |
Label: | Perform Regular Automated Port Scans |
Description: | Perform automated port scans on a regular basis against all systems and alert if unauthorized ports are detected on a system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.1 |
Label: | Limit Open Ports, Protocols, and Services |
Description: | Ensure that only ports, protocols, and services with validated business needs are running on each system. |
Windows includes support for Structured Exception Handling Overwrite Protection (SEHOP). We recommend enabling this feature to improve the security profile of the computer.
The recommended state for this setting is: Enabled .
This feature is designed to block exploits that use the Structured Exception Handler (SEH) overwrite technique. This protection mechanism is provided at run-time. Therefore, it helps protect applications regardless of whether they have been compiled with the latest improvements, such as the /SAFESEH option.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\MS Security Guide\Enable Structured Exception Handling Overwrite Protection (SEHOP)
Note: This Group Policy path does not exist by default. An additional Group Policy template ( SecGuide.admx/adml ) is required - it is available from Microsoft at this link .
More information is available at MSKB 956607: How to enable Structured Exception Handling Overwrite Protection (SEHOP) in Windows operating systems
Impact:
After you enable SEHOP, existing versions of Cygwin, Skype, and Armadillo-protected applications may not work correctly.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.3.4_L1_Ensure_Enable_Structured_Exception_Handling_Overwrite_Protection_SEHOP_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:24.649-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:24.649-05:00" start-time="2020-04-22T15:48:24.555-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableExceptionChainValidation' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817163" result="true" testref="oval:org.cisecurity.benchmarks:tst:817163" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817163"> <cis:evidence_item itemref="914"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SYSTEM\CurrentControlSet\Control\Session Manager\kernel"/> <cis:evidence_item_pk_field name="name" value="DisableExceptionChainValidation"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171631" value-id="xccdf_org.cisecurity.benchmarks_value_817163_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171632" value-id="xccdf_org.cisecurity.benchmarks_value_817163_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817163"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.3 |
Label: | Enable Operating System Anti-Exploitation Features/ Deploy Anti-Exploit Technologies |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP) or Address Space Layout Randomization (ASLR) that are available in an operating system or deploy appropriate toolkits that can be configured to apply protection to a broader set of applications and executables. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Enable Anti-exploitation Features (i.e. DEP, ASLR, EMET) |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), virtualization/containerization, etc. For increased protection, deploy capabilities such as Enhanced Mitigation Experience Toolkit (EMET) that can be configured to apply these protections to a broader set of applications and executables. |
This setting determines which method NetBIOS over TCP/IP (NetBT) uses to register and resolve names. The available methods are:
The recommended state for this setting is: Enabled: P-node (recommended) (point-to-point).
Note: Resolution through LMHOSTS or DNS follows these methods. If the NodeType registry value is present, it overrides any DhcpNodeType registry value. If neither NodeType nor DhcpNodeType is present, the computer uses B-node (broadcast) if there are no WINS servers configured for the network, or H-node (hybrid) if there is at least one WINS server configured.
In order to help mitigate the risk of NetBIOS Name Service (NBT-NS) poisoning attacks, setting the node type to P-node (point-to-point) will prevent the system from sending out NetBIOS broadcasts.
To establish the recommended configuration via GP, set the following UI path to Enabled: P-node (recommended) :
Computer Configuration\Policies\Administrative Templates\MS Security Guide\NetBT NodeType configuration
Note: This change does not take effect until the computer has been restarted.
Note #2: This Group Policy path does not exist by default. An additional Group Policy template ( SecGuide.admx/adml ) is required - it is available from Microsoft at this link . Please note that this setting is only available in the Security baseline (FINAL) for Windows 10 v1903 and Windows Server v1903 (or newer) release of SecGuide.admx/adml , so if you previously downloaded this template, you may need to update it from a newer Microsoft baseline to get this new NetBT NodeType configuration setting.
Impact:
NetBIOS name resolution queries will require a defined and available WINS server for external NetBIOS name resolution. If a WINS server is not defined or not reachable, and the desired hostname is not defined in the local cache, local LMHOSTS or HOSTS files, NetBIOS name resolution will fail.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.3.6_L1_Ensure_NetBT_NodeType_configuration_is_set_to_Enabled_P-node_recommended" role="full" severity="unknown" time="2020-04-22T15:48:24.711-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:24.711-05:00" start-time="2020-04-22T15:48:24.649-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NodeType' is 'Windows: Registry Value' to '2'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817156" result="true" testref="oval:org.cisecurity.benchmarks:tst:817156" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817156"> <cis:evidence_item itemref="915"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SYSTEM\CurrentControlSet\Services\NetBT\Parameters"/> <cis:evidence_item_pk_field name="name" value="NodeType"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="2" dt="int" ev="2" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171561" value-id="xccdf_org.cisecurity.benchmarks_value_817156_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171562" value-id="xccdf_org.cisecurity.benchmarks_value_817156_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817156"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.3 |
Label: | Perform Regular Automated Port Scans |
Description: | Perform automated port scans on a regular basis against all systems and alert if unauthorized ports are detected on a system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
When WDigest authentication is enabled, Lsass.exe retains a copy of the user's plaintext password in memory, where it can be at risk of theft. If this setting is not configured, WDigest authentication is disabled in Windows 8.1 and in Windows Server 2012 R2; it is enabled by default in earlier versions of Windows and Windows Server.
For more information about local accounts and credential theft, review the " Mitigating Pass-the-Hash (PtH) Attacks and Other Credential Theft Techniques " documents.
For more information about UseLogonCredential , see Microsoft Knowledge Base article 2871997: Microsoft Security Advisory Update to improve credentials protection and management May 13, 2014 .
The recommended state for this setting is: Disabled .
Preventing the plaintext storage of credentials in memory may reduce opportunity for credential theft.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\MS Security Guide\WDigest Authentication (disabling may require KB2871997)
Note: This Group Policy path does not exist by default. An additional Group Policy template ( SecGuide.admx/adml ) is required - it is available from Microsoft at this link .
Impact:
None - this is also the default configuration for Server 2012 R2 and newer.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.3.7_L1_Ensure_WDigest_Authentication_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:24.789-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38444-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:24.789-05:00" start-time="2020-04-22T15:48:24.711-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'UseLogonCredential' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817153" result="true" testref="oval:org.cisecurity.benchmarks:tst:817153" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817153"> <cis:evidence_item itemref="916"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest"/> <cis:evidence_item_pk_field name="name" value="UseLogonCredential"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171531" value-id="xccdf_org.cisecurity.benchmarks_value_817153_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171532" value-id="xccdf_org.cisecurity.benchmarks_value_817153_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817153"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38444-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Encrypt or Hash all Authentication Credentials |
Description: | Encrypt or hash with a salt all authentication credentials when stored. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.14 |
Label: | Encrypt/Hash All Authentication Files And Monitor Their Access |
Description: | Verify that all authentication files are encrypted or hashed and that these files cannot be accessed without root or administrator privileges. Audit all access to password files in the system. |
This section contains recommendations for the Microsoft Solutions for Security (MSS) settings.
This Group Policy section is provided by the Group Policy template MSS-legacy.admx/adml that is available from this TechNet blog post: The MSS settings – Microsoft Security Guidance blog
This setting is separate from the Welcome screen feature in Windows XP and Windows Vista; if that feature is disabled, this setting is not disabled. If you configure a computer for automatic logon, anyone who can physically gain access to the computer can also gain access to everything that is on the computer, including any network or networks to which the computer is connected. Also, if you enable automatic logon, the password is stored in the registry in plaintext, and the specific registry key that stores this value is remotely readable by the Authenticated Users group.
For additional information, see Microsoft Knowledge Base article 324737: How to turn on automatic logon in Windows .
The recommended state for this setting is: Disabled .
If you configure a computer for automatic logon, anyone who can physically gain access to the computer can also gain access to everything that is on the computer, including any network or networks that the computer is connected to. Also, if you enable automatic logon, the password is stored in the registry in plaintext. The specific registry key that stores this setting is remotely readable by the Authenticated Users group. As a result, this entry is appropriate only if the computer is physically secured and if you ensure that untrusted users cannot remotely see the registry.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\MSS (Legacy)\MSS: (AutoAdminLogon) Enable Automatic Logon (not recommended)
Note: This Group Policy path does not exist by default. An additional Group Policy template ( MSS-legacy.admx/adml ) is required - it is available from this TechNet blog post: The MSS settings – Microsoft Security Guidance blog
Impact:
None - this is the default behavior.
All of the following tests or sub-groups must pass: | ||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.4.1_L1_Ensure_MSS_AutoAdminLogon_Enable_Automatic_Logon_not_recommended_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:25.008-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37067-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.008-05:00" start-time="2020-04-22T15:48:24.868-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="none_exist" comment="Ensure 'DefaultPassword' is 'Existence Test' to 'none_exist'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817143" result="true" testref="oval:org.cisecurity.benchmarks:tst:817143" type="registry_test"> <cis:evidence_object> <cis:evidence_item itemref="918"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"/> <cis:evidence_item_pk_field name="name" value="DefaultPassword"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AutoAdminLogon' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817140" result="true" testref="oval:org.cisecurity.benchmarks:tst:817140" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817140"> <cis:evidence_item itemref="919"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"/> <cis:evidence_item_pk_field name="name" value="AutoAdminLogon"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="string" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171401" value-id="xccdf_org.cisecurity.benchmarks_value_817140_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171402" value-id="xccdf_org.cisecurity.benchmarks_value_817140_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817140"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817143"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37067-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
IP source routing is a mechanism that allows the sender to determine the IP route that a datagram should follow through the network.
The recommended state for this setting is: Enabled: Highest protection, source routing is completely disabled .
An attacker could use source routed packets to obscure their identity and location. Source routing allows a computer that sends a packet to specify the route that the packet takes.
To establish the recommended configuration via GP, set the following UI path to Enabled: Highest protection, source routing is completely disabled :
Computer Configuration\Policies\Administrative Templates\MSS (Legacy)\MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)
Note: This Group Policy path does not exist by default. An additional Group Policy template ( MSS-legacy.admx/adml ) is required - it is available from this TechNet blog post: The MSS settings – Microsoft Security Guidance blog
Impact:
All incoming source routed packets will be dropped.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.4.2_L1_Ensure_MSS_DisableIPSourceRouting_IPv6_IP_source_routing_protection_level_protects_against_packet_spoofing_is_set_to_Enabled_Highest_protection_source_routing_is_completely_disabled" role="full" severity="unknown" time="2020-04-22T15:48:25.071-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36871-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.071-05:00" start-time="2020-04-22T15:48:25.008-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableIPSourceRouting' is 'Windows: Registry Value' to '2'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817149" result="true" testref="oval:org.cisecurity.benchmarks:tst:817149" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817149"> <cis:evidence_item itemref="920"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\Tcpip6\Parameters"/> <cis:evidence_item_pk_field name="name" value="DisableIPSourceRouting"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="2" dt="int" ev="2" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171491" value-id="xccdf_org.cisecurity.benchmarks_value_817149_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171492" value-id="xccdf_org.cisecurity.benchmarks_value_817149_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817149"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36871-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.3 |
Label: | Perform Regular Automated Port Scans |
Description: | Perform automated port scans on a regular basis against all systems and alert if unauthorized ports are detected on a system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
IP source routing is a mechanism that allows the sender to determine the IP route that a datagram should take through the network. It is recommended to configure this setting to Not Defined for enterprise environments and to Highest Protection for high security environments to completely disable source routing.
The recommended state for this setting is: Enabled: Highest protection, source routing is completely disabled .
An attacker could use source routed packets to obscure their identity and location. Source routing allows a computer that sends a packet to specify the route that the packet takes.
To establish the recommended configuration via GP, set the following UI path to Enabled: Highest protection, source routing is completely disabled :
Computer Configuration\Policies\Administrative Templates\MSS (Legacy)\MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)
Note: This Group Policy path does not exist by default. An additional Group Policy template ( MSS-legacy.admx/adml ) is required - it is available from this TechNet blog post: The MSS settings – Microsoft Security Guidance blog
Impact:
All incoming source routed packets will be dropped.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.4.3_L1_Ensure_MSS_DisableIPSourceRouting_IP_source_routing_protection_level_protects_against_packet_spoofing_is_set_to_Enabled_Highest_protection_source_routing_is_completely_disabled" role="full" severity="unknown" time="2020-04-22T15:48:25.133-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36535-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.133-05:00" start-time="2020-04-22T15:48:25.071-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableIPSourceRouting' is 'Windows: Registry Value' to '2'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817151" result="true" testref="oval:org.cisecurity.benchmarks:tst:817151" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817151"> <cis:evidence_item itemref="921"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\Tcpip\Parameters"/> <cis:evidence_item_pk_field name="name" value="DisableIPSourceRouting"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="2" dt="int" ev="2" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171511" value-id="xccdf_org.cisecurity.benchmarks_value_817151_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171512" value-id="xccdf_org.cisecurity.benchmarks_value_817151_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817151"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36535-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.3 |
Label: | Perform Regular Automated Port Scans |
Description: | Perform automated port scans on a regular basis against all systems and alert if unauthorized ports are detected on a system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Internet Control Message Protocol (ICMP) redirects cause the IPv4 stack to plumb host routes. These routes override the Open Shortest Path First (OSPF) generated routes.
The recommended state for this setting is: Disabled .
This behavior is expected. The problem is that the 10 minute time-out period for the ICMP redirect-plumbed routes temporarily creates a network situation in which traffic will no longer be routed properly for the affected host. Ignoring such ICMP redirects will limit the system's exposure to attacks that will impact its ability to participate on the network.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\MSS (Legacy)\MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes
Note: This Group Policy path does not exist by default. An additional Group Policy template ( MSS-legacy.admx/adml ) is required - it is available from this TechNet blog post: The MSS settings – Microsoft Security Guidance blog
Impact:
When Routing and Remote Access Service (RRAS) is configured as an autonomous system boundary router (ASBR), it does not correctly import connected interface subnet routes. Instead, this router injects host routes into the OSPF routes. However, the OSPF router cannot be used as an ASBR router, and when connected interface subnet routes are imported into OSPF the result is confusing routing tables with strange routing paths.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.4.4_L1_Ensure_MSS_EnableICMPRedirect_Allow_ICMP_redirects_to_override_OSPF_generated_routes_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:25.196-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37988-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.196-05:00" start-time="2020-04-22T15:48:25.133-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableICMPRedirect' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817154" result="true" testref="oval:org.cisecurity.benchmarks:tst:817154" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817154"> <cis:evidence_item itemref="922"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\Tcpip\Parameters"/> <cis:evidence_item_pk_field name="name" value="EnableICMPRedirect"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171541" value-id="xccdf_org.cisecurity.benchmarks_value_817154_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171542" value-id="xccdf_org.cisecurity.benchmarks_value_817154_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817154"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37988-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.3 |
Label: | Perform Regular Automated Port Scans |
Description: | Perform automated port scans on a regular basis against all systems and alert if unauthorized ports are detected on a system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
NetBIOS over TCP/IP is a network protocol that among other things provides a way to easily resolve NetBIOS names that are registered on Windows-based systems to the IP addresses that are configured on those systems. This setting determines whether the computer releases its NetBIOS name when it receives a name-release request.
The recommended state for this setting is: Enabled .
The NetBT protocol is designed not to use authentication, and is therefore vulnerable to spoofing. Spoofing makes a transmission appear to come from a user other than the user who performed the action. A malicious user could exploit the unauthenticated nature of the protocol to send a name-conflict datagram to a target computer, which would cause the computer to relinquish its name and not respond to queries.
An attacker could send a request over the network and query a computer to release its NetBIOS name. As with any change that could affect applications, it is recommended that you test this change in a non-production environment before you change the production environment.
The result of such an attack could be to cause intermittent connectivity issues on the target computer, or even to prevent the use of Network Neighborhood, domain logons, the NET SEND command, or additional NetBIOS name resolution.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\MSS (Legacy)\MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers
Note: This Group Policy path does not exist by default. An additional Group Policy template ( MSS-legacy.admx/adml ) is required - it is available from this TechNet blog post: The MSS settings – Microsoft Security Guidance blog
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.4.6_L1_Ensure_MSS_NoNameReleaseOnDemand_Allow_the_computer_to_ignore_NetBIOS_name_release_requests_except_from_WINS_servers_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:25.258-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36879-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.258-05:00" start-time="2020-04-22T15:48:25.196-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'nonamereleaseondemand' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817165" result="true" testref="oval:org.cisecurity.benchmarks:tst:817165" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817165"> <cis:evidence_item itemref="923"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Services\NetBT\Parameters"/> <cis:evidence_item_pk_field name="name" value="nonamereleaseondemand"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171651" value-id="xccdf_org.cisecurity.benchmarks_value_817165_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171652" value-id="xccdf_org.cisecurity.benchmarks_value_817165_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817165"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36879-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.3 |
Label: | Perform Regular Automated Port Scans |
Description: | Perform automated port scans on a regular basis against all systems and alert if unauthorized ports are detected on a system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
The DLL search order can be configured to search for DLLs that are requested by running processes in one of two ways:
When enabled, the registry value is set to 1. With a setting of 1, the system first searches the folders that are specified in the system path and then searches the current working folder. When disabled the registry value is set to 0 and the system first searches the current working folder and then searches the folders that are specified in the system path.
Applications will be forced to search for DLLs in the system path first. For applications that require unique versions of these DLLs that are included with the application, this entry could cause performance or stability problems.
The recommended state for this setting is: Enabled .
Note: More information on how Safe DLL search mode works is available at this link: Dynamic-Link Library Search Order - Windows applications | Microsoft Docs
If a user unknowingly executes hostile code that was packaged with additional files that include modified versions of system DLLs, the hostile code could load its own versions of those DLLs and potentially increase the type and degree of damage the code can render.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\MSS (Legacy)\MSS: (SafeDllSearchMode) Enable Safe DLL search mode (recommended)
Note: This Group Policy path does not exist by default. An additional Group Policy template ( MSS-legacy.admx/adml ) is required - it is available from this TechNet blog post: The MSS settings – Microsoft Security Guidance blog
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.4.8_L1_Ensure_MSS_SafeDllSearchMode_Enable_Safe_DLL_search_mode_recommended_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:25.336-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36351-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.336-05:00" start-time="2020-04-22T15:48:25.274-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'SafeDllSearchMode' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817176" result="true" testref="oval:org.cisecurity.benchmarks:tst:817176" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817176"> <cis:evidence_item itemref="924"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SYSTEM\CurrentControlSet\Control\Session Manager"/> <cis:evidence_item_pk_field name="name" value="SafeDllSearchMode"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171761" value-id="xccdf_org.cisecurity.benchmarks_value_817176_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171762" value-id="xccdf_org.cisecurity.benchmarks_value_817176_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817176"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36351-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.1 |
Label: | Utilize Centrally Managed Anti-malware Software |
Description: | Utilize centrally managed anti-malware software to continuously monitor and defend each of the organization's workstations and servers. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.2 |
Label: | Ensure Anti-Malware Software and Signatures are Updated |
Description: | Ensure that the organization's anti-malware software updates its scanning engine and signature database on a regular basis. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Windows includes a grace period between when the screen saver is launched and when the console is actually locked automatically when screen saver locking is enabled.
The recommended state for this setting is: Enabled: 5 or fewer seconds .
The default grace period that is allowed for user movement before the screen saver lock takes effect is five seconds. If you leave the default grace period configuration, your computer is vulnerable to a potential attack from someone who could approach the console and attempt to log on to the computer before the lock takes effect. An entry to the registry can be made to adjust the length of the grace period.
To establish the recommended configuration via GP, set the following UI path to Enabled: 5 or fewer seconds :
Computer Configuration\Policies\Administrative Templates\MSS (Legacy)\MSS: (ScreenSaverGracePeriod) The time in seconds before the screen saver grace period expires (0 recommended)
Note: This Group Policy path does not exist by default. An additional Group Policy template ( MSS-legacy.admx/adml ) is required - it is available from this TechNet blog post: The MSS settings – Microsoft Security Guidance blog
Impact:
Users will have to enter their passwords to resume their console sessions as soon as the grace period ends after screen saver activation.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.4.9_L1_Ensure_MSS_ScreenSaverGracePeriod_The_time_in_seconds_before_the_screen_saver_grace_period_expires_0_recommended_is_set_to_Enabled_5_or_fewer_seconds" role="full" severity="unknown" time="2020-04-22T15:48:25.399-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37993-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.399-05:00" start-time="2020-04-22T15:48:25.336-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ScreenSaverGracePeriod' is 'Windows: Registry Value' to '5'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817181" result="true" testref="oval:org.cisecurity.benchmarks:tst:817181" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817181"> <cis:evidence_item itemref="925"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows NT\CurrentVersion\Winlogon"/> <cis:evidence_item_pk_field name="name" value="ScreenSaverGracePeriod"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="5" dt="int" ev="5" name="value" op="less than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171811" value-id="xccdf_org.cisecurity.benchmarks_value_817181_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171812" value-id="xccdf_org.cisecurity.benchmarks_value_817181_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817181"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37993-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This setting can generate a security audit in the Security event log when the log reaches a user-defined threshold.
The recommended state for this setting is: Enabled: 90% or less .
Note: If log settings are configured to Overwrite events as needed or Overwrite events older than x days, this event will not be generated.
If the Security log reaches 90 percent of its capacity and the computer has not been configured to overwrite events as needed, more recent events will not be written to the log. If the log reaches its capacity and the computer has been configured to shut down when it can no longer record events to the Security log, the computer will shut down and will no longer be available to provide network services.
To establish the recommended configuration via GP, set the following UI path to Enabled: 90% or less :
Computer Configuration\Policies\Administrative Templates\MSS (Legacy)\MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning
Note: This Group Policy path does not exist by default. An additional Group Policy template ( MSS-legacy.admx/adml ) is required - it is available from this TechNet blog post: The MSS settings – Microsoft Security Guidance blog
Impact:
An audit event will be generated when the Security log reaches the 90% percent full threshold (or whatever lower value may be set) unless the log is configured to overwrite events as needed.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.4.12_L1_Ensure_MSS_WarningLevel_Percentage_threshold_for_the_security_event_log_at_which_the_system_will_generate_a_warning_is_set_to_Enabled_90_or_less" role="full" severity="unknown" time="2020-04-22T15:48:24.868-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36880-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:24.868-05:00" start-time="2020-04-22T15:48:24.789-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'WarningLevel' is 'Windows: Registry Value' to '90'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817199" result="true" testref="oval:org.cisecurity.benchmarks:tst:817199" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817199"> <cis:evidence_item itemref="917"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SYSTEM\CurrentControlSet\Services\Eventlog\Security"/> <cis:evidence_item_pk_field name="name" value="WarningLevel"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="90" dt="int" ev="90" name="value" op="less than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171991" value-id="xccdf_org.cisecurity.benchmarks_value_817199_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8171992" value-id="xccdf_org.cisecurity.benchmarks_value_817199_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817199"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36880-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Enable Detailed Logging |
Description: | Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. |
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.5 |
Label: | Central Log Management |
Description: | Ensure that appropriate logs are being aggregated to a central log management system for analysis and review. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Ensure Audit Logging Systems Are Not Subject To Loss (i.e. rotation/archive) |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated on a regular basis, so that log files will not fill up between log rotation intervals. The logs must be archived and digitally signed on a periodic basis. |
This section contains recommendations for network settings.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Bits.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template PeerToPeerCaching.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template nca.admx/adml that is included with the Microsoft 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section contains recommendations related to DNS Client.
This Group Policy section is provided by the Group Policy template DnsClient.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
LLMNR is a secondary name resolution protocol. With LLMNR, queries are sent using multicast over a local network link on a single subnet from a client computer to another client computer on the same subnet that also has LLMNR enabled. LLMNR does not require a DNS server or DNS client configuration, and provides name resolution in scenarios in which conventional DNS name resolution is not possible.
The recommended state for this setting is: Enabled .
An attacker can listen on a network for these LLMNR (UDP/5355) or NBT-NS (UDP/137) broadcasts and respond to them, tricking the host into thinking that it knows the location of the requested system.
Note: To completely mitigate local name resolution poisoning, in addition to this setting, the properties of each installed NIC should also be set to Disable NetBIOS over TCP/IP (on the WINS tab in the NIC properties). Unfortunately, there is no global setting to achieve this that automatically applies to all NICs - it is a per-NIC setting that varies with different NIC hardware installations.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Network\DNS Client\Turn off multicast name resolution
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template DnsClient.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
In the event DNS is unavailable a system will be unable to request it from other systems on the same subnet.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.5.4.1_L1_Ensure_Turn_off_multicast_name_resolution_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:25.883-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37450-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.883-05:00" start-time="2020-04-22T15:48:25.805-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="any_exist" comment="Ensure 'EnableMulticast' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817236" result="true" testref="oval:org.cisecurity.benchmarks:tst:817236" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817236"> <cis:evidence_item itemref="932"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows NT\DNSClient"/> <cis:evidence_item_pk_field name="name" value="EnableMulticast"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172361" value-id="xccdf_org.cisecurity.benchmarks_value_817236_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172362" value-id="xccdf_org.cisecurity.benchmarks_value_817236_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817236"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37450-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.3 |
Label: | Perform Regular Automated Port Scans |
Description: | Perform automated port scans on a regular basis against all systems and alert if unauthorized ports are detected on a system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
This section contains recommendations related to Fonts.
This Group Policy section is provided by the Group Policy template GroupPolicy.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template hotspotauth.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template LanmanServer.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section contains recommendations related to Lanman Workstation.
This Group Policy section is provided by the Group Policy template LanmanWorkstation.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
This policy setting determines if the SMB client will allow insecure guest logons to an SMB server.
The recommended state for this setting is: Disabled .
Insecure guest logons are used by file servers to allow unauthenticated access to shared folders.
To establish the recommended configuration via GP, set the following UI path to Disabled:
Computer Configuration\Policies\Administrative Templates\Network\Lanman Workstation\Enable insecure guest logons
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template LanmanWorkstation.admx/adml that is included with the Microsoft Windows 10 Release 1511 Administrative Templates (or newer).
Impact:
The SMB client will reject insecure guest logons. This was not originally the default behavior in older versions of Windows, but Microsoft changed the default behavior starting with Windows Server 2016 R1709: Guest access in SMB2 disabled by default in Windows 10 and Windows Server 2016
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.5.8.1_L1_Ensure_Enable_insecure_guest_logons_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:25.946-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.946-05:00" start-time="2020-04-22T15:48:25.883-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowInsecureGuestAuth' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817246" result="true" testref="oval:org.cisecurity.benchmarks:tst:817246" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817246"> <cis:evidence_item itemref="933"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation"/> <cis:evidence_item_pk_field name="name" value="AllowInsecureGuestAuth"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172461" value-id="xccdf_org.cisecurity.benchmarks_value_817246_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172462" value-id="xccdf_org.cisecurity.benchmarks_value_817246_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817246"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.3 |
Label: | Perform Regular Automated Port Scans |
Description: | Perform automated port scans on a regular basis against all systems and alert if unauthorized ports are detected on a system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.1 |
Label: | Limit Open Ports, Protocols, and Services |
Description: | Ensure that only ports, protocols, and services with validated business needs are running on each system. |
This section contains recommendations for Link-Layer Topology Discovery settings.
This Group Policy section is provided by the Group Policy template LinkLayerTopologyDiscovery.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for Microsoft Peer-to-Peer Networking Services settings.
This Group Policy section is provided by the Group Policy template P2P-pnrp.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template P2P-pnrp.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for Network Connections settings.
This Group Policy section is provided by the Group Policy template NetworkConnections.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsFirewall.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note: This section was initially named Windows Firewall but was renamed by Microsoft to Windows Defender Firewall starting with the Microsoft Windows 10 Release 1709 Administrative Templates.
You can use this procedure to controls user's ability to install and configure a Network Bridge.
The recommended state for this setting is: Enabled .
The Network Bridge setting, if enabled, allows users to create a Layer 2 Media Access Control (MAC) bridge, enabling them to connect two or more physical network segments together. A Network Bridge thus allows a computer that has connections to two different networks to share data between those networks.
In an enterprise managed environment, where there is a need to control network traffic to only authorized paths, allowing users to create a Network Bridge increases the risk and attack surface from the bridged network.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Network\Network Connections\Prohibit installation and configuration of Network Bridge on your DNS domain network
Note: This Group Policy path is provided by the Group Policy template NetworkConnections.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
Users cannot create or configure a Network Bridge.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.2_L1_Ensure_Prohibit_installation_and_configuration_of_Network_Bridge_on_your_DNS_domain_network_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:25.461-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38002-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.461-05:00" start-time="2020-04-22T15:48:25.399-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NC_AllowNetBridge_NLA' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817244" result="true" testref="oval:org.cisecurity.benchmarks:tst:817244" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817244"> <cis:evidence_item itemref="926"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\Network Connections"/> <cis:evidence_item_pk_field name="name" value="NC_AllowNetBridge_NLA"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172441" value-id="xccdf_org.cisecurity.benchmarks_value_817244_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172442" value-id="xccdf_org.cisecurity.benchmarks_value_817244_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817244"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38002-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
Although this "legacy" setting traditionally applied to the use of Internet Connection Sharing (ICS) in Windows 2000, Windows XP & Server 2003, this setting now freshly applies to the Mobile Hotspot feature in Windows 10 & Server 2016.
The recommended state for this setting is: Enabled .
Non-administrators should not be able to turn on the Mobile Hotspot feature and open their Internet connectivity up to nearby mobile devices.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Network\Network Connections\Prohibit use of Internet Connection Sharing on your DNS domain network
Note: This Group Policy path is provided by the Group Policy template NetworkConnections.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
Mobile Hotspot cannot be enabled or configured by Administrators and non-Administrators alike.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.3_L1_Ensure_Prohibit_use_of_Internet_Connection_Sharing_on_your_DNS_domain_network_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:25.539-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.539-05:00" start-time="2020-04-22T15:48:25.477-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NC_ShowSharedAccessUI' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817257" result="true" testref="oval:org.cisecurity.benchmarks:tst:817257" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817257"> <cis:evidence_item itemref="927"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\Network Connections"/> <cis:evidence_item_pk_field name="name" value="NC_ShowSharedAccessUI"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172571" value-id="xccdf_org.cisecurity.benchmarks_value_817257_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172572" value-id="xccdf_org.cisecurity.benchmarks_value_817257_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817257"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.3 |
Label: | Perform Regular Automated Port Scans |
Description: | Perform automated port scans on a regular basis against all systems and alert if unauthorized ports are detected on a system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.1 |
Label: | Limit Open Ports, Protocols, and Services |
Description: | Ensure that only ports, protocols, and services with validated business needs are running on each system. |
This policy setting determines whether to require domain users to elevate when setting a network's location.
The recommended state for this setting is: Enabled .
Allowing regular users to set a network location increases the risk and attack surface.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Network\Network Connections\Require domain users to elevate when setting a network's location
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template NetworkConnections.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
Impact:
Domain users must elevate when setting a network's location.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.5.11.4_L1_Ensure_Require_domain_users_to_elevate_when_setting_a_networks_location_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:25.602-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38188-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.602-05:00" start-time="2020-04-22T15:48:25.539-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NC_StdDomainUserSetLocation' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817250" result="true" testref="oval:org.cisecurity.benchmarks:tst:817250" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817250"> <cis:evidence_item itemref="928"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\Network Connections"/> <cis:evidence_item_pk_field name="name" value="NC_StdDomainUserSetLocation"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172501" value-id="xccdf_org.cisecurity.benchmarks_value_817250_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172502" value-id="xccdf_org.cisecurity.benchmarks_value_817250_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817250"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38188-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template NCSI.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template NetworkIsolation.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section contains recommendations for Network Provider settings.
This Group Policy section is provided by the Group Policy template NetworkProvider.admx/adml that is included with the MS15-011 / MSKB 3000483 security update and the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
This policy setting configures secure access to UNC paths.
The recommended state for this setting is: Enabled, with "Require Mutual Authentication" and "Require Integrity" set for all NETLOGON and SYSVOL shares .
Note: If the environment exclusively contains Windows 8.0 / Server 2012 (non-R2) or newer systems, then the " Privacy " setting may (optionally) also be set to enable SMB encryption. However, using SMB encryption will render the targeted share paths completely inaccessible by older OSes, so only use this additional option with caution and thorough testing.
In February 2015, Microsoft released a new control mechanism to mitigate a security risk in Group Policy as part of the MS15-011 / MSKB 3000483 security update. This mechanism requires both the installation of the new security update and also the deployment of specific group policy settings to all computers on the domain from Windows Vista / Server 2008 (non-R2) or newer (the associated security patch to enable this feature was not released for Server 2003). A new group policy template ( NetworkProvider.admx/adml ) was also provided with the security update.
Once the new GPO template is in place, the following are the minimum requirements to remediate the Group Policy security risk:
\\*\NETLOGON RequireMutualAuthentication=1, RequireIntegrity=1
\\*\SYSVOL RequireMutualAuthentication=1, RequireIntegrity=1
Note: A reboot may be required after the setting is applied to a client machine to access the above paths.
Additional guidance on the deployment of this security setting is available from the Microsoft Premier Field Engineering (PFE) Platforms TechNet Blog here: Guidance on Deployment of MS15-011 and MS15-014 .
To establish the recommended configuration via GP, set the following UI path to Enabled with the following paths configured, at a minimum:
\\*\NETLOGON RequireMutualAuthentication=1, RequireIntegrity=1 \\*\SYSVOL RequireMutualAuthentication=1, RequireIntegrity=1
Computer Configuration\Policies\Administrative Templates\Network\Network Provider\Hardened UNC Paths
Note: This Group Policy path does not exist by default. An additional Group Policy template ( NetworkProvider.admx/adml ) is required - it is included with the MS15-011 / MSKB 3000483 security update or with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
Impact:
Windows only allows access to the specified UNC paths after fulfilling additional security requirements.
All of the following tests or sub-groups must pass: | ||||||||||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.5.14.1_L1_Ensure_Hardened_UNC_Paths_is_set_to_Enabled_with_Require_Mutual_Authentication_and_Require_Integrity_set_for_all_NETLOGON_and_SYSVOL_shares" role="full" severity="unknown" time="2020-04-22T15:48:25.743-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/3/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.743-05:00" start-time="2020-04-22T15:48:25.617-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '\\*\SYSVOL' is 'Windows: Registry Value' to '[Rr]equire([Mm]utual[Aa]uthentication|[Ii]ntegrity)=1.*[Rr]equire([Mm]utual[Aa]uthentication|[Ii]ntegrity)=1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817261" result="true" testref="oval:org.cisecurity.benchmarks:tst:817261" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817261"> <cis:evidence_item itemref="929"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths"/> <cis:evidence_item_pk_field name="name" value="\\*\SYSVOL"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="RequireMutualAuthentication=1, RequireIntegrity=1" dt="string" ev="[Rr]equire([Mm]utual[Aa]uthentication|[Ii]ntegrity)=1.*[Rr]equire([Mm]utual[Aa]uthentication|[Ii]ntegrity)=1" name="value" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '\\*\NETLOGON' is 'Windows: Registry Value' to '[Rr]equire([Mm]utual[Aa]uthentication|[Ii]ntegrity)=1.*[Rr]equire([Mm]utual[Aa]uthentication|[Ii]ntegrity)=1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817256" result="true" testref="oval:org.cisecurity.benchmarks:tst:817256" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817256"> <cis:evidence_item itemref="930"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths"/> <cis:evidence_item_pk_field name="name" value="\\*\NETLOGON"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="RequireMutualAuthentication=1, RequireIntegrity=1" dt="string" ev="[Rr]equire([Mm]utual[Aa]uthentication|[Ii]ntegrity)=1.*[Rr]equire([Mm]utual[Aa]uthentication|[Ii]ntegrity)=1" name="value" op="pattern match" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172561" value-id="xccdf_org.cisecurity.benchmarks_value_817256_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172562" value-id="xccdf_org.cisecurity.benchmarks_value_817256_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817256"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172611" value-id="xccdf_org.cisecurity.benchmarks_value_817261_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172612" value-id="xccdf_org.cisecurity.benchmarks_value_817261_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817261"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 3.1 |
Label: | Run Automated Vulnerability Scanning Tools |
Description: | Utilize an up-to-date SCAP-compliant vulnerability scanning tool to automatically scan all systems on the network on a weekly or more frequent basis to identify all potential vulnerabilities on the organization's systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template OfflineFiles.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template QOS.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Snmp.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template CipherSuiteOrder.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains TCP/IP configuration settings.
This Group Policy section is provided by the Group Policy template tcpip.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template tcpip.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section contains TCP/IP parameter configuration settings.
This Group Policy section is provided by the Group Policy template tcpip.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section contains recommendations for Windows Connect Now settings.
This Group Policy section is provided by the Group Policy template WindowsConnectNow.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for Windows Connection Manager settings.
This Group Policy section is provided by the Group Policy template WCM.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This policy setting prevents computers from establishing multiple simultaneous connections to either the Internet or to a Windows domain.
The recommended state for this setting is: Enabled: 3 = Prevent Wi-Fi when on Ethernet .
Preventing bridged network connections can help prevent a user unknowingly allowing traffic to route between internal and external networks, which risks exposure to sensitive internal data.
To establish the recommended configuration via GP, set the following UI path to Enabled: 3 = Prevent Wi-Fi when on Ethernet :
Computer Configuration\Policies\Administrative Templates\Network\Windows Connection Manager\Minimize the number of simultaneous connections to the Internet or a Windows Domain
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WCM.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates. It was updated with a new Minimize Policy Options sub-setting starting with the Windows 10 Release 1903 Administrative Templates.
Impact:
While connected to an Ethernet connection, Windows won't allow use of a WLAN (automatically or manually) until Ethernet is disconnected. However, if a cellular data connection is available, it will always stay connected for services that require it, but no Internet traffic will be routed over cellular if an Ethernet or WLAN connection is present.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.5.21.1_L1_Ensure_Minimize_the_number_of_simultaneous_connections_to_the_Internet_or_a_Windows_Domain_is_set_to_Enabled_3__Prevent_Wi-Fi_when_on_Ethernet" role="full" severity="unknown" time="2020-04-22T15:48:25.805-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/12" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/15/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38338-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:25.805-05:00" start-time="2020-04-22T15:48:25.743-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'fMinimizeConnections' is 'Windows: Registry Value' to '3'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817266" result="false" testref="oval:org.cisecurity.benchmarks:tst:817266" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817266"> <cis:evidence_item itemref="931"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\WcmSvc\GroupPolicy"/> <cis:evidence_item_pk_field name="name" value="fMinimizeConnections"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="3" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172661" value-id="xccdf_org.cisecurity.benchmarks_value_817266_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172662" value-id="xccdf_org.cisecurity.benchmarks_value_817266_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817266"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38338-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the security use of wireless local area networks (WLANs), access points, and wireless client systems. |
Subcontrol: | 15.5 |
Label: | Limit Wireless Access on Client Devices |
Description: | Configure wireless access on client machines that do have an essential wireless business purpose, to allow access only to authorized wireless networks and to restrict access to other wireless networks. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Detect/prevent/correct the flow of information transferring networks of different trust levels with a focus on security-damaging data. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for Start Menu and Taskbar.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This section contains recommendations for Start Menu and Taskbar Notifications.
This Group Policy section is provided by the Group Policy template WPN.admx/adml that is included with the Microsoft 10 Release 1803 Administrative Templates (or newer).
This section contains recommendations for System settings.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template srm-fci.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template appv.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This section contains settings related to auditing of process creation events.
This Group Policy section is provided by the Group Policy template AuditSettings.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This policy setting determines what information is logged in security audit events when a new process has been created.
The recommended state for this setting is: Disabled .
When this policy setting is enabled, any user who has read access to the security events can read the command-line arguments for any successfully created process. Command-line arguments may contain sensitive or private information such as passwords or user data.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\System\Audit Process Creation\Include command line in process creation events
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template AuditSettings.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.3.1_L1_Ensure_Include_command_line_in_process_creation_events_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:27.008-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36925-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:27.008-05:00" start-time="2020-04-22T15:48:26.930-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ProcessCreationIncludeCmdLine_Enabled' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817269" result="true" testref="oval:org.cisecurity.benchmarks:tst:817269" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817269"> <cis:evidence_item itemref="949"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit"/> <cis:evidence_item_pk_field name="name" value="ProcessCreationIncludeCmdLine_Enabled"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172691" value-id="xccdf_org.cisecurity.benchmarks_value_817269_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172692" value-id="xccdf_org.cisecurity.benchmarks_value_817269_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817269"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36925-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Encrypt or Hash all Authentication Credentials |
Description: | Encrypt or hash with a salt all authentication credentials when stored. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.14 |
Label: | Encrypt/Hash All Authentication Files And Monitor Their Access |
Description: | Verify that all authentication files are encrypted or hashed and that these files cannot be accessed without root or administrator privileges. Audit all access to password files in the system. |
This section contains settings related to Credential Delegation.
This Group Policy section is provided by the Group Policy template CredSsp.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Some versions of the CredSSP protocol that is used by some applications (such as Remote Desktop Connection) are vulnerable to an encryption oracle attack against the client. This policy controls compatibility with vulnerable clients and servers and allows you to set the level of protection desired for the encryption oracle vulnerability.
The recommended state for this setting is: Enabled: Force Updated Clients .
This setting is important to mitigate the CredSSP encryption oracle vulnerability, for which information was published by Microsoft on 03/13/2018 in CVE-2018-0886 | CredSSP Remote Code Execution Vulnerability . All versions of Windows Server from Server 2008 (non-R2) onwards are affected by this vulnerability, and will be compatible with this recommendation provided that they have been patched up through May 2018 (or later).
To establish the recommended configuration via GP, set the following UI path to Enabled: Force Updated Clients :
Computer Configuration\Policies\Administrative Templates\System\Credentials Delegation\Encryption Oracle Remediation
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template CredSsp.admx/adml that is included with the Microsoft Windows 10 Release 1803 Administrative Templates (or newer).
Impact:
Client applications which use CredSSP will not be able to fall back to the insecure versions and services using CredSSP will not accept unpatched clients. This setting should not be deployed until all remote hosts support the newest version, which is achieved by ensuring that all Microsoft security updates at least through May 2018 are installed.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.4.1_L1_Ensure_Encryption_Oracle_Remediation_is_set_to_Enabled_Force_Updated_Clients" role="full" severity="unknown" time="2020-04-22T15:48:27.430-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817275" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowEncryptionOracle' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817275" result="true" testref="oval:org.cisecurity.benchmarks:tst:817275" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817275"> <cis:evidence_item itemref="955"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters"/> <cis:evidence_item_pk_field name="name" value="AllowEncryptionOracle"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172751" value-id="xccdf_org.cisecurity.benchmarks_value_817275_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172752" value-id="xccdf_org.cisecurity.benchmarks_value_817275_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817275"/> </check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Encrypt or Hash all Authentication Credentials |
Description: | Encrypt or hash with a salt all authentication credentials when stored. |
Remote host allows delegation of non-exportable credentials. When using credential delegation, devices provide an exportable version of credentials to the remote host. This exposes users to the risk of credential theft from attackers on the remote host. The Restricted Admin Mode and Windows Defender Remote Credential Guard features are two options to help protect against this risk.
The recommended state for this setting is: Enabled .
Note: More detailed information on Windows Defender Remote Credential Guard and how it compares to Restricted Admin Mode can be found at this link: Protect Remote Desktop credentials with Windows Defender Remote Credential Guard (Windows 10) | Microsoft Docs
Restricted Admin Mode was designed to help protect administrator accounts by ensuring that reusable credentials are not stored in memory on remote devices that could potentially be compromised. Windows Defender Remote Credential Guard helps you protect your credentials over a Remote Desktop connection by redirecting Kerberos requests back to the device that is requesting the connection. Both features should be enabled and supported, as they reduce the chance of credential theft.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\System\Credentials Delegation\Remote host allows delegation of non-exportable credentials
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template CredSsp.admx/adml that is included with the Microsoft Windows 10 Release 1703 Administrative Templates (or newer).
Impact:
The host will support the Restricted Admin Mode and Windows Defender Remote Credential Guard features.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.4.2_L1_Ensure_Remote_host_allows_delegation_of_non-exportable_credentials_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:27.508-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:27.508-05:00" start-time="2020-04-22T15:48:27.430-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowProtectedCreds' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817270" result="true" testref="oval:org.cisecurity.benchmarks:tst:817270" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817270"> <cis:evidence_item itemref="956"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation"/> <cis:evidence_item_pk_field name="name" value="AllowProtectedCreds"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172701" value-id="xccdf_org.cisecurity.benchmarks_value_817270_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172702" value-id="xccdf_org.cisecurity.benchmarks_value_817270_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817270"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Encrypt or Hash all Authentication Credentials |
Description: | Encrypt or hash with a salt all authentication credentials when stored. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This section contains Device Guard settings.
This Group Policy section is provided by the Group Policy template DeviceGuard.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TPM.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
This section contains recommendations related to device installation.
This Group Policy section is provided by the Group Policy template DeviceInstallation.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DeviceInstallation.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DeviceRedirection.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DiskNVCache.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DiskQuota.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Display.admx/adml that is included with the Microsoft Windows 10 Release 1703 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DCOM.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DeviceInstallation.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for configuring boot-start driver initialization settings.
This Group Policy section is provided by the Group Policy template EarlyLaunchAM.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This policy setting allows you to specify which boot-start drivers are initialized based on a classification determined by an Early Launch Antimalware boot-start driver. The Early Launch Antimalware boot-start driver can return the following classifications for each boot-start driver:
If you enable this policy setting you will be able to choose which boot-start drivers to initialize the next time the computer is started.
If your malware detection application does not include an Early Launch Antimalware boot-start driver or if your Early Launch Antimalware boot-start driver has been disabled, this setting has no effect and all boot-start drivers are initialized.
The recommended state for this setting is: Enabled: Good, unknown and bad but critical .
This policy setting helps reduce the impact of malware that has already infected your system.
To establish the recommended configuration via GP, set the following UI path to Enabled: Good, unknown and bad but critical:
Computer Configuration\Policies\Administrative Templates\System\Early Launch Antimalware\Boot-Start Driver Initialization Policy
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template EarlyLaunchAM.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.14.1_L1_Ensure_Boot-Start_Driver_Initialization_Policy_is_set_to_Enabled_Good_unknown_and_bad_but_critical" role="full" severity="unknown" time="2020-04-22T15:48:26.008-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37912-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.008-05:00" start-time="2020-04-22T15:48:25.946-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DriverLoadPolicy' is 'Windows: Registry Value' to '3'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817283" result="true" testref="oval:org.cisecurity.benchmarks:tst:817283" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817283"> <cis:evidence_item itemref="934"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="System\CurrentControlSet\Policies\EarlyLaunch"/> <cis:evidence_item_pk_field name="name" value="DriverLoadPolicy"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="3" dt="int" ev="3" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172831" value-id="xccdf_org.cisecurity.benchmarks_value_817283_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172832" value-id="xccdf_org.cisecurity.benchmarks_value_817283_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817283"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37912-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.1 |
Label: | Utilize Centrally Managed Anti-malware Software |
Description: | Utilize centrally managed anti-malware software to continuously monitor and defend each of the organization's workstations and servers. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.2 |
Label: | Ensure Anti-Malware Software and Signatures are Updated |
Description: | Ensure that the organization's anti-malware software updates its scanning engine and signature database on a regular basis. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template EnhancedStorage.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template srm-fci.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template FileServerVSSAgent.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy templates FileServerVSSProvider.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template FileSys.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note: This section was initially named NTFS Filesystem but was renamed by Microsoft to Filesystem starting with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template FolderRedirection.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for configuring group policy-related settings.
This Group Policy section is provided by the Group Policy template GroupPolicy.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template GroupPolicyPreferences.admx/adml that is included with the Microsoft Windows Server 2008 (non-R2) Administrative Templates (or newer).
The "Do not apply during periodic background processing" option prevents the system from updating affected policies in the background while the computer is in use. When background updates are disabled, policy changes will not take effect until the next user logon or system restart.
The recommended state for this setting is: Enabled: FALSE (unchecked).
Setting this option to false (unchecked) will ensure that domain policy changes take effect more quickly, as compared to waiting until the next user logon or system restart.
To establish the recommended configuration via GP, set the following UI path to Enabled , then set the Do not apply during periodic background processing option to FALSE (unchecked):
Computer Configuration\Policies\Administrative Templates\System\Group Policy\Configure registry policy processing
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template GroupPolicy.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
Group Policies will be reapplied every time they are refreshed, which could have a slight impact on performance.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.2_L1_Ensure_Configure_registry_policy_processing_Do_not_apply_during_periodic_background_processing_is_set_to_Enabled_FALSE" role="full" severity="unknown" time="2020-04-22T15:48:26.071-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3/subcontrol/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36169-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.071-05:00" start-time="2020-04-22T15:48:26.008-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoBackgroundPolicy' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817285" result="true" testref="oval:org.cisecurity.benchmarks:tst:817285" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817285"> <cis:evidence_item itemref="935"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}"/> <cis:evidence_item_pk_field name="name" value="NoBackgroundPolicy"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172851" value-id="xccdf_org.cisecurity.benchmarks_value_817285_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172852" value-id="xccdf_org.cisecurity.benchmarks_value_817285_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817285"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36169-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.4 |
Label: | Deploy System Configuration Management Tools |
Description: | Deploy system configuration management tools that will automatically enforce and redeploy configuration settings to systems at regularly scheduled intervals. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.5 |
Label: | Implement Automated Configuration Monitoring Systems |
Description: | Utilize a Security Content Automation Protocol (SCAP) compliant configuration monitoring system to verify all security configuration elements, catalog approved exceptions, and alert when unauthorized changes occur. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 3.7 |
Label: | Deploy System Configuration Management Tools (i.e. Remediation Tools) |
Description: | Deploy system configuration management tools, such as Active Directory Group Policy Objects for Microsoft Windows systems or Puppet for UNIX systems that will automatically enforce and redeploy configuration settings to systems at regularly scheduled intervals. They should be capable of triggering redeployment of configuration settings on a scheduled, manual, or event-driven basis. |
The "Process even if the Group Policy objects have not changed" option updates and reapplies policies even if the policies have not changed.
The recommended state for this setting is: Enabled: TRUE (checked).
Setting this option to true (checked) will ensure unauthorized changes that might have been configured locally are forced to match the domain-based Group Policy settings again.
To establish the recommended configuration via GP, set the following UI path to Enabled , then set the Process even if the Group Policy objects have not changed option to TRUE (checked):
Computer Configuration\Policies\Administrative Templates\System\Group Policy\Configure registry policy processing
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template GroupPolicy.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
Group Policies will be reapplied even if they have not been changed, which could have a slight impact on performance.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.3_L1_Ensure_Configure_registry_policy_processing_Process_even_if_the_Group_Policy_objects_have_not_changed_is_set_to_Enabled_TRUE" role="full" severity="unknown" time="2020-04-22T15:48:26.149-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3/subcontrol/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36169-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.149-05:00" start-time="2020-04-22T15:48:26.071-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoGPOListChanges' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817293" result="true" testref="oval:org.cisecurity.benchmarks:tst:817293" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817293"> <cis:evidence_item itemref="936"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}"/> <cis:evidence_item_pk_field name="name" value="NoGPOListChanges"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172931" value-id="xccdf_org.cisecurity.benchmarks_value_817293_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172932" value-id="xccdf_org.cisecurity.benchmarks_value_817293_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817293"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36169-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.4 |
Label: | Deploy System Configuration Management Tools |
Description: | Deploy system configuration management tools that will automatically enforce and redeploy configuration settings to systems at regularly scheduled intervals. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.5 |
Label: | Implement Automated Configuration Monitoring Systems |
Description: | Utilize a Security Content Automation Protocol (SCAP) compliant configuration monitoring system to verify all security configuration elements, catalog approved exceptions, and alert when unauthorized changes occur. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 3.7 |
Label: | Deploy System Configuration Management Tools (i.e. Remediation Tools) |
Description: | Deploy system configuration management tools, such as Active Directory Group Policy Objects for Microsoft Windows systems or Puppet for UNIX systems that will automatically enforce and redeploy configuration settings to systems at regularly scheduled intervals. They should be capable of triggering redeployment of configuration settings on a scheduled, manual, or event-driven basis. |
This policy setting determines whether the Windows device is allowed to participate in cross-device experiences (continue experiences).
The recommended state for this setting is: Disabled .
A cross-device experience is when a system can access app and send messages to other devices. In an enterprise managed environment only trusted systems should be communicating within the network. Access to any other system should be prohibited.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\System\Group Policy\Continue experiences on this device
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template GroupPolicy.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
Impact:
The Windows device will not be discoverable by other devices, and cannot participate in cross-device experiences.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.4_L1_Ensure_Continue_experiences_on_this_device_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:26.211-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.211-05:00" start-time="2020-04-22T15:48:26.149-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableCdp' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817302" result="true" testref="oval:org.cisecurity.benchmarks:tst:817302" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817302"> <cis:evidence_item itemref="937"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\System"/> <cis:evidence_item_pk_field name="name" value="EnableCdp"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173021" value-id="xccdf_org.cisecurity.benchmarks_value_817302_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173022" value-id="xccdf_org.cisecurity.benchmarks_value_817302_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817302"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.1 |
Label: | Limit Open Ports, Protocols, and Services |
Description: | Ensure that only ports, protocols, and services with validated business needs are running on each system. |
This policy setting prevents Group Policy from being updated while the computer is in use. This policy setting applies to Group Policy for computers, users and Domain Controllers.
The recommended state for this setting is: Disabled .
This setting ensures that group policy changes take effect more quickly, as compared to waiting until the next user logon or system restart.
To establish the recommended configuration via GP, set the following UI path to Disabled:
Computer Configuration\Policies\Administrative Templates\System\Group Policy\Turn off background refresh of Group Policy
Note: This Group Policy path is provided by the Group Policy template GroupPolicy.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.21.5_L1_Ensure_Turn_off_background_refresh_of_Group_Policy_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:26.274-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3/subcontrol/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37712-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.274-05:00" start-time="2020-04-22T15:48:26.211-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="none_exist" comment="Ensure 'DisableBkGndGroupPolicy' is 'Existence Test' to 'none_exist'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817298" result="true" testref="oval:org.cisecurity.benchmarks:tst:817298" type="registry_test"> <cis:evidence_object> <cis:evidence_item itemref="938"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="DisableBkGndGroupPolicy"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817298"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37712-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.4 |
Label: | Deploy System Configuration Management Tools |
Description: | Deploy system configuration management tools that will automatically enforce and redeploy configuration settings to systems at regularly scheduled intervals. |
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.5 |
Label: | Implement Automated Configuration Monitoring Systems |
Description: | Utilize a Security Content Automation Protocol (SCAP) compliant configuration monitoring system to verify all security configuration elements, catalog approved exceptions, and alert when unauthorized changes occur. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 3.7 |
Label: | Deploy System Configuration Management Tools (i.e. Remediation Tools) |
Description: | Deploy system configuration management tools, such as Active Directory Group Policy Objects for Microsoft Windows systems or Puppet for UNIX systems that will automatically enforce and redeploy configuration settings to systems at regularly scheduled intervals. They should be capable of triggering redeployment of configuration settings on a scheduled, manual, or event-driven basis. |
This section contains recommendations related to Internet Communication Management.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Internet Communication settings.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting controls whether the computer can download print driver packages over HTTP. To set up HTTP printing, printer drivers that are not available in the standard operating system installation might need to be downloaded over HTTP.
The recommended state for this setting is: Enabled .
Users might download drivers that include malicious code.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\System\Internet Communication Management\Internet Communication settings\Turn off downloading of print drivers over HTTP
Note: This Group Policy path is provided by the Group Policy template ICM.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
Print drivers cannot be downloaded over HTTP.
Note: This policy setting does not prevent the client computer from printing to printers on the intranet or the Internet over HTTP. It only prohibits downloading drivers that are not already installed locally.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.1_L1_Ensure_Turn_off_downloading_of_print_drivers_over_HTTP_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:26.336-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/2/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/2/subcontrol/7" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36625-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.336-05:00" start-time="2020-04-22T15:48:26.274-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableWebPnPDownload' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817416" result="true" testref="oval:org.cisecurity.benchmarks:tst:817416" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817416"> <cis:evidence_item itemref="939"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows NT\Printers"/> <cis:evidence_item_pk_field name="name" value="DisableWebPnPDownload"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174161" value-id="xccdf_org.cisecurity.benchmarks_value_817416_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174162" value-id="xccdf_org.cisecurity.benchmarks_value_817416_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817416"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36625-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that all unauthorized and unmanaged software is found and prevented from installation or execution. |
Subcontrol: | 2.6 |
Label: | Address unapproved software |
Description: | Ensure that unauthorized software is either removed or the inventory is updated in a timely manner |
CIS Control Information | |
---|---|
Control: | Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that all unauthorized and unmanaged software is found and prevented from installation or execution. |
Subcontrol: | 2.7 |
Label: | Utilize Application Whitelisting |
Description: | Utilize application whitelisting technology on all assets to ensure that only authorized software executes and all unauthorized software is blocked from executing on assets. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that unauthorized and unmanaged software is found and prevented from installation or execution. |
This policy setting controls whether Windows will download a list of providers for the Web publishing and online ordering wizards.
The recommended state for this setting is: Enabled .
Although the risk is minimal, enabling this setting will reduce the possibility of a user unknowingly downloading malicious content through this feature.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\System\Internet Communication Management\Internet Communication settings\Turn off Internet download for Web publishing and online ordering wizards
Note: This Group Policy path is provided by the Group Policy template ICM.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
Windows is prevented from downloading providers; only the service providers cached in the local registry are displayed.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.22.1.5_L1_Ensure_Turn_off_Internet_download_for_Web_publishing_and_online_ordering_wizards_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:26.414-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/7/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36096-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.414-05:00" start-time="2020-04-22T15:48:26.336-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoWebServices' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817452" result="true" testref="oval:org.cisecurity.benchmarks:tst:817452" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817452"> <cis:evidence_item itemref="940"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\Explorer"/> <cis:evidence_item_pk_field name="name" value="NoWebServices"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174521" value-id="xccdf_org.cisecurity.benchmarks_value_817452_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174522" value-id="xccdf_org.cisecurity.benchmarks_value_817452_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817452"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36096-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior through their interaction with web browsers and email systems. |
Subcontrol: | 7.4 |
Label: | Maintain and Enforce Network-Based URL Filters |
Description: | Enforce network-based URL filters that limit a system's ability to connect to websites not approved by the organization. This filtering shall be enforced for each of the organization's systems, whether they are physically at an organization's facilities or not. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior though their interaction with web browsers and email systems. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template iSCSI.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template KDC.admx/adml that is included with the Microsoft Windows Server 2008 (non-R2) Administrative Templates (or newer).
This section contains recommendations for Kerberos settings.
This Group Policy section is provided by the Group Policy template Kerberos.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DmaGuard.admx/adml that is included with the Microsoft Windows 10 Release 1809 and Server 2019 Administrative Templates (or newer).
This policy is intended to provide additional security against external DMA-capable devices. It allows for more control over the enumeration of external DMA-capable devices that are not compatible with DMA Remapping/device memory isolation and sandboxing.
The recommended state for this setting is: Enabled: Block All .
Note : This policy does not apply to 1394, PCMCIA or ExpressCard devices. The protection also only applies to Windows 10 R1803 or higher, and also requires a UEFI BIOS to function.
Note #2 : More information on this feature is available at this link: Kernel DMA Protection for Thunderbolt™ 3 (Windows 10) | Microsoft Docs .
Device memory sandboxing allows the OS to leverage the I/O Memory Management Unit (IOMMU) of a device to block unpermitted I/O, or memory access, by the peripheral.
To establish the recommended configuration via GP, set the following UI path to Enabled: Block All :
Computer Configuration\Policies\Administrative Templates\System\Kernel DMA Protection\Enumeration policy for external devices incompatible with Kernel DMA Protection
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template DmaGuard.admx/adml that is included with the Microsoft Windows 10 Release 1809 & Server 2019 Administrative Templates (or newer).
Impact:
External devices that are not compatible with DMA-remapping will not be enumerated and will not function unless/until the user has logged in successfully and has an unlocked user session. Once enumerated, these devices will continue to function, regardless of the state of the session. Devices that are compatible with DMA-remapping will be enumerated immediately, with their device memory isolated.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.26.1_L1_Ensure_Enumeration_policy_for_external_devices_incompatible_with_Kernel_DMA_Protection_is_set_to_Enabled_Block_All" role="full" severity="unknown" time="2020-04-22T15:48:26.477-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817310" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DeviceEnumerationPolicy' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817310" result="true" testref="oval:org.cisecurity.benchmarks:tst:817310" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817310"> <cis:evidence_item itemref="941"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\Kernel DMA Protection"/> <cis:evidence_item_pk_field name="name" value="DeviceEnumerationPolicy"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173101" value-id="xccdf_org.cisecurity.benchmarks_value_817310_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173102" value-id="xccdf_org.cisecurity.benchmarks_value_817310_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817310"/> </check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
This section contains recommendations for Locale Services settings.
This Group Policy section is provided by the Group Policy template Globalization.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to the logon process and lock screen.
This Group Policy section is provided by the Group Policy template Logon.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy prevents the user from showing account details (email address or user name) on the sign-in screen.
The recommended state for this setting is: Enabled .
An attacker with access to the console (for example, someone with physical access or someone who is able to connect to the server through Remote Desktop Services) could view the name of the last user who logged on to the server. The attacker could then try to guess the password, use a dictionary, or use a brute-force attack to try and log on.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\System\Logon\Block user from showing account details on sign-in
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template Logon.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
Impact:
The user cannot choose to show account details on the sign-in screen.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.1_L1_Ensure_Block_user_from_showing_account_details_on_sign-in_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:26.539-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.539-05:00" start-time="2020-04-22T15:48:26.477-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'BlockUserFromShowingAccountDetailsOnSignin' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817321" result="true" testref="oval:org.cisecurity.benchmarks:tst:817321" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817321"> <cis:evidence_item itemref="942"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\System"/> <cis:evidence_item_pk_field name="name" value="BlockUserFromShowingAccountDetailsOnSignin"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173211" value-id="xccdf_org.cisecurity.benchmarks_value_817321_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173212" value-id="xccdf_org.cisecurity.benchmarks_value_817321_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817321"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This policy setting allows you to control whether anyone can interact with available networks UI on the logon screen.
The recommended state for this setting is: Enabled .
An unauthorized user could disconnect the PC from the network or can connect the PC to other available networks without signing into Windows.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\System\Logon\Do not display network selection UI
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template Logon.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Impact:
The PC's network connectivity state cannot be changed without signing into Windows.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.2_L1_Ensure_Do_not_display_network_selection_UI_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:26.602-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38353-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.602-05:00" start-time="2020-04-22T15:48:26.539-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DontDisplayNetworkSelectionUI' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817296" result="true" testref="oval:org.cisecurity.benchmarks:tst:817296" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817296"> <cis:evidence_item itemref="943"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\System"/> <cis:evidence_item_pk_field name="name" value="DontDisplayNetworkSelectionUI"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172961" value-id="xccdf_org.cisecurity.benchmarks_value_817296_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172962" value-id="xccdf_org.cisecurity.benchmarks_value_817296_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817296"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38353-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
This policy setting prevents connected users from being enumerated on domain-joined computers.
The recommended state for this setting is: Enabled .
A malicious user could use this feature to gather account names of other users, that information could then be used in conjunction with other types of attacks such as guessing passwords or social engineering. The value of this countermeasure is small because a user with domain credentials could gather the same account information using other methods.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\System\Logon\Do not enumerate connected users on domain-joined computers
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template Logon.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
The Logon UI will not enumerate any connected users on domain-joined computers.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.3_L1_Ensure_Do_not_enumerate_connected_users_on_domain-joined_computers_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:26.680-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37838-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.680-05:00" start-time="2020-04-22T15:48:26.602-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DontEnumerateConnectedUsers' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817300" result="true" testref="oval:org.cisecurity.benchmarks:tst:817300" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817300"> <cis:evidence_item itemref="944"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\System"/> <cis:evidence_item_pk_field name="name" value="DontEnumerateConnectedUsers"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173001" value-id="xccdf_org.cisecurity.benchmarks_value_817300_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173002" value-id="xccdf_org.cisecurity.benchmarks_value_817300_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817300"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37838-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.9 |
Label: | Configure Account Access Centrally |
Description: | Configure access for all accounts through a centralized point of authentication, for example Active Directory or LDAP. Configure network and security devices for centralized authentication as well. |
This policy setting allows local users to be enumerated on domain-joined computers.
The recommended state for this setting is: Disabled .
A malicious user could use this feature to gather account names of other users, that information could then be used in conjunction with other types of attacks such as guessing passwords or social engineering. The value of this countermeasure is small because a user with domain credentials could gather the same account information using other methods.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\System\Logon\Enumerate local users on domain-joined computers
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template Logon.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.4_L1_Ensure_Enumerate_local_users_on_domain-joined_computers_is_set_to_Disabled_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:26.743-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-35894-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.743-05:00" start-time="2020-04-22T15:48:26.680-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnumerateLocalUsers' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817306" result="true" testref="oval:org.cisecurity.benchmarks:tst:817306" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817306"> <cis:evidence_item itemref="945"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\System"/> <cis:evidence_item_pk_field name="name" value="EnumerateLocalUsers"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173061" value-id="xccdf_org.cisecurity.benchmarks_value_817306_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173062" value-id="xccdf_org.cisecurity.benchmarks_value_817306_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817306"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-35894-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.9 |
Label: | Configure Account Access Centrally |
Description: | Configure access for all accounts through a centralized point of authentication, for example Active Directory or LDAP. Configure network and security devices for centralized authentication as well. |
This policy setting allows you to prevent app notifications from appearing on the lock screen.
The recommended state for this setting is: Enabled .
App notifications might display sensitive business or personal data.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\System\Logon\Turn off app notifications on the lock screen
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template Logon.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
No app notifications are displayed on the lock screen.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.5_L1_Ensure_Turn_off_app_notifications_on_the_lock_screen_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:26.805-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-35893-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.805-05:00" start-time="2020-04-22T15:48:26.743-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableLockScreenAppNotifications' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817311" result="true" testref="oval:org.cisecurity.benchmarks:tst:817311" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817311"> <cis:evidence_item itemref="946"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\System"/> <cis:evidence_item_pk_field name="name" value="DisableLockScreenAppNotifications"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173111" value-id="xccdf_org.cisecurity.benchmarks_value_817311_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173112" value-id="xccdf_org.cisecurity.benchmarks_value_817311_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817311"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-35893-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This policy setting allows you to control whether a domain user can sign in using a picture password.
The recommended state for this setting is: Enabled .
Note: If the picture password feature is permitted, the user's domain password is cached in the system vault when using it.
Picture passwords bypass the requirement for a typed complex password. In a shared work environment, a simple shoulder surf where someone observed the on-screen gestures would allow that person to gain access to the system without the need to know the complex password. Vertical monitor screens with an image are much more visible at a distance than horizontal key strokes, increasing the likelihood of a successful observation of the mouse gestures.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\System\Logon\Turn off picture password sign-in
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template CredentialProviders.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
Users will not be able to set up or sign in with a picture password.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.6_L1_Ensure_Turn_off_picture_password_sign-in_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:26.868-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37830-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.868-05:00" start-time="2020-04-22T15:48:26.805-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'BlockDomainPicturePassword' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817327" result="true" testref="oval:org.cisecurity.benchmarks:tst:817327" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817327"> <cis:evidence_item itemref="947"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\System"/> <cis:evidence_item_pk_field name="name" value="BlockDomainPicturePassword"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173271" value-id="xccdf_org.cisecurity.benchmarks_value_817327_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173272" value-id="xccdf_org.cisecurity.benchmarks_value_817327_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817327"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37830-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This policy setting allows you to control whether a domain user can sign in using a convenience PIN. In Windows 10, convenience PIN was replaced with Passport, which has stronger security properties. To configure Passport for domain users, use the policies under Computer Configuration\Administrative Templates\Windows Components\Microsoft Passport for Work.
Note: The user's domain password will be cached in the system vault when using this feature.
The recommended state for this setting is: Disabled .
A PIN is created from a much smaller selection of characters than a password, so in most cases a PIN will be much less robust than a password.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\System\Logon\Turn on convenience PIN sign-in
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template CredentialProviders.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Turn on PIN sign-in , but it was renamed starting with the Windows 10 Release 1511 Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.28.7_L1_Ensure_Turn_on_convenience_PIN_sign-in_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:26.930-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37528-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:26.930-05:00" start-time="2020-04-22T15:48:26.868-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowDomainPINLogon' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817316" result="true" testref="oval:org.cisecurity.benchmarks:tst:817316" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817316"> <cis:evidence_item itemref="948"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\System"/> <cis:evidence_item_pk_field name="name" value="AllowDomainPINLogon"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173161" value-id="xccdf_org.cisecurity.benchmarks_value_817316_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173162" value-id="xccdf_org.cisecurity.benchmarks_value_817316_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817316"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37528-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template GroupPolicy.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Netlogon.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to OS Policies.
This Group Policy section is provided by the Group Policy template OSPolicy.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template PerfCenterCPL.admx/adml that is only included with the Microsoft Windows Vista through the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Passport.admx/adml that is included with the Microsoft Windows 10 Release 1703 Administrative Templates (or newer).
This section contains recommendations for Power Management settings.
This Group Policy section is provided by the Group Policy template Power.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Power.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Power.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Power.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Power.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Power.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
This section contains recommendations related to Power Management Sleep mode.
This Group Policy section is provided by the Group Policy template Power.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Specifies whether or not the user is prompted for a password when the system resumes from sleep.
The recommended state for this setting is: Enabled .
Enabling this setting ensures that anyone who wakes an unattended computer from sleep state will have to provide logon credentials before they can access the system.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\System\Power Management\Sleep Settings\Require a password when a computer wakes (on battery)
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template Power.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.3_L1_Ensure_Require_a_password_when_a_computer_wakes_on_battery_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:27.086-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36881-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:27.086-05:00" start-time="2020-04-22T15:48:27.024-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DCSettingIndex' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817419" result="true" testref="oval:org.cisecurity.benchmarks:tst:817419" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817419"> <cis:evidence_item itemref="950"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51"/> <cis:evidence_item_pk_field name="name" value="DCSettingIndex"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174191" value-id="xccdf_org.cisecurity.benchmarks_value_817419_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174192" value-id="xccdf_org.cisecurity.benchmarks_value_817419_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817419"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36881-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
Specifies whether or not the user is prompted for a password when the system resumes from sleep.
The recommended state for this setting is: Enabled .
Enabling this setting ensures that anyone who wakes an unattended computer from sleep state will have to provide logon credentials before they can access the system.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\System\Power Management\Sleep Settings\Require a password when a computer wakes (plugged in)
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template Power.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.34.6.4_L1_Ensure_Require_a_password_when_a_computer_wakes_plugged_in_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:27.164-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37066-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:27.164-05:00" start-time="2020-04-22T15:48:27.086-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ACSettingIndex' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817428" result="true" testref="oval:org.cisecurity.benchmarks:tst:817428" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817428"> <cis:evidence_item itemref="951"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51"/> <cis:evidence_item_pk_field name="name" value="ACSettingIndex"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174281" value-id="xccdf_org.cisecurity.benchmarks_value_817428_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174282" value-id="xccdf_org.cisecurity.benchmarks_value_817428_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817428"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37066-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template ReAgent.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section contains recommendations related to Remote Assistance.
This Group Policy section is provided by the Group Policy template RemoteAssistance.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting allows you to turn on or turn off Offer (Unsolicited) Remote Assistance on this computer.
Help desk and support personnel will not be able to proactively offer assistance, although they can still respond to user assistance requests.
The recommended state for this setting is: Disabled .
A user might be tricked and accept an unsolicited Remote Assistance offer from a malicious user.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\System\Remote Assistance\Configure Offer Remote Assistance
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template RemoteAssistance.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.36.1_L1_Ensure_Configure_Offer_Remote_Assistance_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:27.242-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36388-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:27.242-05:00" start-time="2020-04-22T15:48:27.164-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'fAllowUnsolicited' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817299" result="true" testref="oval:org.cisecurity.benchmarks:tst:817299" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817299"> <cis:evidence_item itemref="952"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\policies\Microsoft\Windows NT\Terminal Services"/> <cis:evidence_item_pk_field name="name" value="fAllowUnsolicited"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172991" value-id="xccdf_org.cisecurity.benchmarks_value_817299_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8172992" value-id="xccdf_org.cisecurity.benchmarks_value_817299_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817299"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36388-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.1 |
Label: | Limit Open Ports, Protocols, and Services |
Description: | Ensure that only ports, protocols, and services with validated business needs are running on each system. |
This policy setting allows you to turn on or turn off Solicited (Ask for) Remote Assistance on this computer.
The recommended state for this setting is: Disabled .
There is slight risk that a rogue administrator will gain access to another user's desktop session, however, they cannot connect to a user's computer unannounced or control it without permission from the user. When an expert tries to connect, the user can still choose to deny the connection or give the expert view-only privileges. The user must explicitly click the Yes button to allow the expert to remotely control the workstation.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\System\Remote Assistance\Configure Solicited Remote Assistance
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template RemoteAssistance.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
Users on this computer cannot use e-mail or file transfer to ask someone for help. Also, users cannot use instant messaging programs to allow connections to this computer.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.36.2_L1_Ensure_Configure_Solicited_Remote_Assistance_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:27.305-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37281-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:27.305-05:00" start-time="2020-04-22T15:48:27.242-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'fAllowToGetHelp' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817304" result="true" testref="oval:org.cisecurity.benchmarks:tst:817304" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817304"> <cis:evidence_item itemref="953"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\policies\Microsoft\Windows NT\Terminal Services"/> <cis:evidence_item_pk_field name="name" value="fAllowToGetHelp"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173041" value-id="xccdf_org.cisecurity.benchmarks_value_817304_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173042" value-id="xccdf_org.cisecurity.benchmarks_value_817304_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817304"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37281-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This section contains recommendations related to Remote Procedure Call.
This Group Policy section is provided by the Group Policy template RPC.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting controls whether RPC clients authenticate with the Endpoint Mapper Service when the call they are making contains authentication information. The Endpoint Mapper Service on computers running Windows NT4 (all service packs) cannot process authentication information supplied in this manner. This policy setting can cause a specific issue with 1-way forest trusts if it is applied to the trusting domain DCs (see Microsoft KB3073942 ), so we do not recommend applying it to Domain Controllers.
Note: This policy will not be in effect until the system is rebooted.
The recommended state for this setting is: Enabled .
Anonymous access to RPC services could result in accidental disclosure of information to unauthenticated users.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\System\Remote Procedure Call\Enable RPC Endpoint Mapper Client Authentication
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template RPC.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
RPC clients will authenticate to the Endpoint Mapper Service for calls that contain authentication information. Clients making such calls will not be able to communicate with the Windows NT4 Server Endpoint Mapper Service.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.8.37.1_L1_Ensure_Enable_RPC_Endpoint_Mapper_Client_Authentication_is_set_to_Enabled_MS_only" role="full" severity="unknown" time="2020-04-22T15:48:27.368-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/9/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37346-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:27.368-05:00" start-time="2020-04-22T15:48:27.305-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableAuthEpResolution' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817305" result="true" testref="oval:org.cisecurity.benchmarks:tst:817305" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817305"> <cis:evidence_item itemref="954"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows NT\Rpc"/> <cis:evidence_item_pk_field name="name" value="EnableAuthEpResolution"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173051" value-id="xccdf_org.cisecurity.benchmarks_value_817305_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173052" value-id="xccdf_org.cisecurity.benchmarks_value_817305_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817305"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37346-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.2 |
Label: | Ensure Only Approved Ports, Protocols and Services Are Running |
Description: | Ensure that only network ports, protocols, and services listening on a system with validated business needs are running on each system. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers. |
Subcontrol: | 9.1 |
Label: | Limit Open Ports, Protocols, and Services |
Description: | Ensure that only ports, protocols, and services with validated business needs are running on each system. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template RemovableStorage.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Scripts.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template ServerManager.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template ServiceControlManager.admx/adml that is included with the Microsoft Windows 10 Release 1903 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WinInit.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Winsrv.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template StorageHealth.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template StorageSense.admx/adml that is included with the Microsoft Windows 10 Release 1903 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template SystemRestore.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Troubleshooting and Diagnostics.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template pca.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template FileRecovery.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DiskDiagnostic.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template fthsvc.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section contains recommendations related to the Microsoft Support Diagnostic Tool.
This Group Policy section is provided by the Group Policy template MSDT.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Msi-FileRecovery.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template sdiagschd.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template sdiageng.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template PerformanceDiagnostics.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template LeakDiagnostic.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Windows Performance PerfTrack.
This Group Policy section is provided by the Group Policy template PerformancePerftrack.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TPM.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to User Profiles.
This Group Policy section is provided by the Group Policy template UserProfiles.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsFileProtection.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template HotStart.admx/adml that is only included with the Microsoft Windows Vista through the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
This section contains recommendations related to the Windows Time Service.
This Group Policy section is provided by the Group Policy template W32Time.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Time Providers.
This Group Policy section is provided by the Group Policy template W32Time.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for Windows Component settings.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template adfs.admx/adml that is only included with the Microsoft Windows Vista through the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template ActiveXInstallService.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsAnytimeUpgrade.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
Note: This section was initially named Windows Anytime Upgrade but was renamed by Microsoft to Add features to Windows x starting with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
This section contains recommendations for App Package Deployment settings.
This Group Policy section is provided by the Group Policy template AppxPackageManager.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template AppPrivacy.admx/adml that is included with the Microsoft Windows 10 Release 1511 Administrative Templates (or newer).
This section contains recommendations for App runtime settings.
This Group Policy section is provided by the Group Policy template AppXRuntime.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This policy setting lets you control whether Microsoft accounts are optional for Windows Store apps that require an account to sign in. This policy only affects Windows Store apps that support it.
The recommended state for this setting is: Enabled .
Enabling this setting allows an organization to use their enterprise user accounts instead of using their Microsoft accounts when accessing Windows store apps. This provides the organization with greater control over relevant credentials. Microsoft accounts cannot be centrally managed and as such enterprise credential security policies cannot be applied to them, which could put any information accessed by using Microsoft accounts at risk.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\App runtime\Allow Microsoft accounts to be optional
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template AppXRuntime.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Impact:
Windows Store apps that typically require a Microsoft account to sign in will allow users to sign in with an enterprise account instead.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.6.1_L1_Ensure_Allow_Microsoft_accounts_to_be_optional_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:30.430-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/9" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38354-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:30.430-05:00" start-time="2020-04-22T15:48:30.352-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'MSAOptional' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817318" result="true" testref="oval:org.cisecurity.benchmarks:tst:817318" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817318"> <cis:evidence_item itemref="999"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\System"/> <cis:evidence_item_pk_field name="name" value="MSAOptional"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173181" value-id="xccdf_org.cisecurity.benchmarks_value_817318_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173182" value-id="xccdf_org.cisecurity.benchmarks_value_817318_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817318"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38354-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.9 |
Label: | Configure Account Access Centrally |
Description: | Configure access for all accounts through a centralized point of authentication, for example Active Directory or LDAP. Configure network and security devices for centralized authentication as well. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template AppCompat.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for AutoPlay policies.
This Group Policy section is provided by the Group Policy template AutoPlay.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting disallows AutoPlay for MTP devices like cameras or phones.
The recommended state for this setting is: Enabled .
An attacker could use this feature to launch a program to damage a client computer or data on the computer.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\AutoPlay Policies\Disallow Autoplay for non-volume devices
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template AutoPlay.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
AutoPlay will not be allowed for MTP devices like cameras or phones.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.1_L1_Ensure_Disallow_Autoplay_for_non-volume_devices_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:31.868-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37636-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:31.868-05:00" start-time="2020-04-22T15:48:31.821-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoAutoplayfornonVolume' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817322" result="true" testref="oval:org.cisecurity.benchmarks:tst:817322" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817322"> <cis:evidence_item itemref="1021"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\Explorer"/> <cis:evidence_item_pk_field name="name" value="NoAutoplayfornonVolume"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173221" value-id="xccdf_org.cisecurity.benchmarks_value_817322_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173222" value-id="xccdf_org.cisecurity.benchmarks_value_817322_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817322"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37636-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Configure Anti-Malware Scanning of Removable Devices |
Description: | Configure devices so that they automatically conduct an anti-malware scan of removable media when inserted or connected. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.5 |
Label: | Configure Devices Not To Auto-Run Content |
Description: | Configure devices to not auto-run content from removable media. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.3 |
Label: | Limit Use Of External Devices (i.e. USB) |
Description: | Limit use of external devices to those with an approved, documented business need. Monitor for use and attempted use of external devices. Configure laptops, workstations, and servers so that they will not auto-run content from removable media, like USB tokens (i.e., “thumb drives”), USB hard drives, CDs/DVDs, FireWire devices, external serial advanced technology attachment devices, and mounted network shares. Configure systems so that they automatically conduct an anti-malware scan of removable media when inserted. |
This policy setting sets the default behavior for Autorun commands. Autorun commands are generally stored in autorun.inf files. They often launch the installation program or other routines.
The recommended state for this setting is: Enabled: Do not execute any autorun commands .
Prior to Windows Vista, when media containing an autorun command is inserted, the system will automatically execute the program without user intervention. This creates a major security concern as code may be executed without user's knowledge. The default behavior starting with Windows Vista is to prompt the user whether autorun command is to be run. The autorun command is represented as a handler in the Autoplay dialog.
To establish the recommended configuration via GP, set the following UI path to Enabled: Do not execute any autorun commands :
Computer Configuration\Policies\Administrative Templates\Windows Components\AutoPlay Policies\Set the default behavior for AutoRun
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template AutoPlay.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
AutoRun commands will be completely disabled.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.2_L1_Ensure_Set_the_default_behavior_for_AutoRun_is_set_to_Enabled_Do_not_execute_any_autorun_commands" role="full" severity="unknown" time="2020-04-22T15:48:31.946-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38217-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:31.946-05:00" start-time="2020-04-22T15:48:31.883-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoAutorun' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817328" result="true" testref="oval:org.cisecurity.benchmarks:tst:817328" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817328"> <cis:evidence_item itemref="1022"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer"/> <cis:evidence_item_pk_field name="name" value="NoAutorun"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173281" value-id="xccdf_org.cisecurity.benchmarks_value_817328_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173282" value-id="xccdf_org.cisecurity.benchmarks_value_817328_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817328"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38217-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Configure Anti-Malware Scanning of Removable Devices |
Description: | Configure devices so that they automatically conduct an anti-malware scan of removable media when inserted or connected. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.5 |
Label: | Configure Devices Not To Auto-Run Content |
Description: | Configure devices to not auto-run content from removable media. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.3 |
Label: | Limit Use Of External Devices (i.e. USB) |
Description: | Limit use of external devices to those with an approved, documented business need. Monitor for use and attempted use of external devices. Configure laptops, workstations, and servers so that they will not auto-run content from removable media, like USB tokens (i.e., “thumb drives”), USB hard drives, CDs/DVDs, FireWire devices, external serial advanced technology attachment devices, and mounted network shares. Configure systems so that they automatically conduct an anti-malware scan of removable media when inserted. |
Autoplay starts to read from a drive as soon as you insert media in the drive, which causes the setup file for programs or audio media to start immediately. An attacker could use this feature to launch a program to damage the computer or data on the computer. Autoplay is disabled by default on some removable drive types, such as floppy disk and network drives, but not on CD-ROM drives.
Note: You cannot use this policy setting to enable Autoplay on computer drives in which it is disabled by default, such as floppy disk and network drives.
The recommended state for this setting is: Enabled: All drives .
An attacker could use this feature to launch a program to damage a client computer or data on the computer.
To establish the recommended configuration via GP, set the following UI path to Enabled: All drives :
Computer Configuration\Policies\Administrative Templates\Windows Components\AutoPlay Policies\Turn off Autoplay
Note: This Group Policy path is provided by the Group Policy template AutoPlay.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
Autoplay will be disabled - users will have to manually launch setup or installation programs that are provided on removable media.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.8.3_L1_Ensure_Turn_off_Autoplay_is_set_to_Enabled_All_drives" role="full" severity="unknown" time="2020-04-22T15:48:32.024-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36875-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.024-05:00" start-time="2020-04-22T15:48:31.946-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoDriveTypeAutoRun' is 'Windows: Registry Value' to '255'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817334" result="true" testref="oval:org.cisecurity.benchmarks:tst:817334" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817334"> <cis:evidence_item itemref="1023"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\Explorer"/> <cis:evidence_item_pk_field name="name" value="NoDriveTypeAutoRun"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="255" dt="int" ev="255" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173341" value-id="xccdf_org.cisecurity.benchmarks_value_817334_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173342" value-id="xccdf_org.cisecurity.benchmarks_value_817334_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817334"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36875-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Configure Anti-Malware Scanning of Removable Devices |
Description: | Configure devices so that they automatically conduct an anti-malware scan of removable media when inserted or connected. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.5 |
Label: | Configure Devices Not To Auto-Run Content |
Description: | Configure devices to not auto-run content from removable media. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.3 |
Label: | Limit Use Of External Devices (i.e. USB) |
Description: | Limit use of external devices to those with an approved, documented business need. Monitor for use and attempted use of external devices. Configure laptops, workstations, and servers so that they will not auto-run content from removable media, like USB tokens (i.e., “thumb drives”), USB hard drives, CDs/DVDs, FireWire devices, external serial advanced technology attachment devices, and mounted network shares. Configure systems so that they automatically conduct an anti-malware scan of removable media when inserted. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template UserDataBackup.admx/adml that is only included with the Microsoft Windows Vista through the Windows 10 Release 1511 Administrative Templates (except for the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates).
This section contains recommendations related to Biometrics.
This Group Policy section is provided by the Group Policy template Biometrics.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section contains recommendations related to Facial Feature Biometrics.
This Group Policy section is provided by the Group Policy template Biometrics.admx/adml that is included with the Microsoft Windows 10 Release 1511 Administrative Templates (or newer).
This policy setting determines whether enhanced anti-spoofing is configured for devices which support it.
The recommended state for this setting is: Enabled .
Enterprise managed environments are now supporting a wider range of mobile devices, increasing the security on these devices will help protect against unauthorized access on your network.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Biometrics\Facial Features\Configure enhanced anti-spoofing
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template Biometrics.admx/adml that is included with the Microsoft Windows 10 Release 1511 Administrative Templates (or newer).
Note #2: In the Windows 10 Release 1511 and Windows 10 Release 1607 & Server 2016 Administrative Templates, this setting was initially named Use enhanced anti-spoofing when available . It was renamed to Configure enhanced anti-spoofing starting with the Windows 10 Release 1703 Administrative Templates.
Impact:
Windows will require all users on the device to use anti-spoofing for facial features, on devices which support it.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.10.1.1_L1_Ensure_Configure_enhanced_anti-spoofing_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:27.571-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:27.571-05:00" start-time="2020-04-22T15:48:27.508-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnhancedAntiSpoofing' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817443" result="true" testref="oval:org.cisecurity.benchmarks:tst:817443" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817443"> <cis:evidence_item itemref="957"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Biometrics\FacialFeatures"/> <cis:evidence_item_pk_field name="name" value="EnhancedAntiSpoofing"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174431" value-id="xccdf_org.cisecurity.benchmarks_value_817443_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174432" value-id="xccdf_org.cisecurity.benchmarks_value_817443_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817443"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.2 |
Label: | Configure Centralized Point of Authentication |
Description: | Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template VolumeEncryption.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Camera.
This Group Policy section is provided by the Group Policy template Camera.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This section contains recommendations related to Cloud Content.
This Group Policy section is provided by the Group Policy template CloudContent.admx/adml that is included with the Microsoft Windows 10 Release 1511 Administrative Templates (or newer).
This policy setting turns off experiences that help consumers make the most of their devices and Microsoft account.
The recommended state for this setting is: Enabled .
Note: Per Microsoft TechNet , this policy setting only applies to Windows 10 Enterprise and Windows 10 Education editions.
Having apps silently install in an enterprise managed environment is not good security practice - especially if the apps send data back to a 3rd party.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Cloud Content\Turn off Microsoft consumer experiences
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template CloudContent.admx/adml that is included with the Microsoft Windows 10 Release 1511 Administrative Templates (or newer).
Impact:
Users will no longer see personalized recommendations from Microsoft and notifications about their Microsoft account.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.13.1_L1_Ensure_Turn_off_Microsoft_consumer_experiences_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:28.383-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/13/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.383-05:00" start-time="2020-04-22T15:48:28.305-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableWindowsConsumerFeatures' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817329" result="true" testref="oval:org.cisecurity.benchmarks:tst:817329" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817329"> <cis:evidence_item itemref="968"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\CloudContent"/> <cis:evidence_item_pk_field name="name" value="DisableWindowsConsumerFeatures"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173291" value-id="xccdf_org.cisecurity.benchmarks_value_817329_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173292" value-id="xccdf_org.cisecurity.benchmarks_value_817329_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817329"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
Subcontrol: | 13.3 |
Label: | Monitor and Block Unauthorized Network Traffic |
Description: | Deploy an automated tool on network perimeters that monitors for unauthorized transfer of sensitive information and blocks such transfers while alerting information security professionals. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This section contains recommendations related to Connect.
This Group Policy section is provided by the Group Policy template WirelessDisplay.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This policy setting controls whether or not a PIN is required for pairing to a wireless display device.
The recommended state for this setting is: Enabled: First Time OR Enabled: Always .
If this setting is not configured or disabled then a PIN would not be required when pairing wireless display devices to the system, increasing the risk of unauthorized use.
To establish the recommended configuration via GP, set the following UI path to Enabled: First Time OR Enabled: Always :
Computer Configuration\Policies\Administrative Templates\Windows Components\Connect\Require pin for pairing
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WirelessDisplay.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
Impact:
The pairing ceremony for connecting to new wireless display devices will always require a PIN.
Any of the following tests or sub-groups may pass: | ||||||||||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.14.1_L1_Ensure_Require_pin_for_pairing_is_set_to_Enabled_First_Time_OR_Enabled_Always" role="full" severity="unknown" time="2020-04-22T15:48:28.461-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/15/subcontrol/8" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/15/subcontrol/9" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.461-05:00" start-time="2020-04-22T15:48:28.383-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'RequirePinForPairing' is 'Windows: Registry Value' to '2'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817348" result="false" testref="oval:org.cisecurity.benchmarks:tst:817348" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817348"> <cis:evidence_item itemref="969"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\Connect"/> <cis:evidence_item_pk_field name="name" value="RequirePinForPairing"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="2" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'RequirePinForPairing' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817339" result="true" testref="oval:org.cisecurity.benchmarks:tst:817339" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817339"> <cis:evidence_item itemref="970"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\Connect"/> <cis:evidence_item_pk_field name="name" value="RequirePinForPairing"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173391" value-id="xccdf_org.cisecurity.benchmarks_value_817339_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173392" value-id="xccdf_org.cisecurity.benchmarks_value_817339_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817339"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173481" value-id="xccdf_org.cisecurity.benchmarks_value_817348_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173482" value-id="xccdf_org.cisecurity.benchmarks_value_817348_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817348"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the security use of wireless local area networks (WLANs), access points, and wireless client systems. |
Subcontrol: | 15.9 |
Label: | Disable Wireless Peripheral Access of Devices |
Description: | Disable wireless peripheral access of devices (such as Bluetooth and NFC), unless such access is required for a business purpose. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the security use of wireless local area networks (LANS), access points, and wireless client systems. |
Subcontrol: | 15.8 |
Label: | Disable Wireless Peripheral Access (i.e. Bluetooth) Unless Required |
Description: | Disable wireless peripheral access of devices (such as Bluetooth), unless such access is required for a documented business need. |
This section contains recommendations related to the Credential User Interface.
This Group Policy section is provided by the Group Policy template CredUI.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting allows you to configure the display of the password reveal button in password entry user experiences.
The recommended state for this setting is: Enabled .
This is a useful feature when entering a long and complex password, especially when using a touchscreen. The potential risk is that someone else may see your password while surreptitiously observing your screen.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Credential User Interface\Do not display the password reveal button
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template CredUI.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
The password reveal button will not be displayed after a user types a password in the password entry text box.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.15.1_L1_Ensure_Do_not_display_the_password_reveal_button_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:28.539-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37534-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.539-05:00" start-time="2020-04-22T15:48:28.461-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisablePasswordReveal' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817332" result="true" testref="oval:org.cisecurity.benchmarks:tst:817332" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817332"> <cis:evidence_item itemref="971"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\CredUI"/> <cis:evidence_item_pk_field name="name" value="DisablePasswordReveal"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173321" value-id="xccdf_org.cisecurity.benchmarks_value_817332_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173322" value-id="xccdf_org.cisecurity.benchmarks_value_817332_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817332"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37534-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This policy setting controls whether administrator accounts are displayed when a user attempts to elevate a running application.
The recommended state for this setting is: Disabled .
Users could see the list of administrator accounts, making it slightly easier for a malicious user who has logged onto a console session to try to crack the passwords of those accounts.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Credential User Interface\Enumerate administrator accounts on elevation
Note: This Group Policy path is provided by the Group Policy template CredUI.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.15.2_L1_Ensure_Enumerate_administrator_accounts_on_elevation_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:28.618-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36512-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.618-05:00" start-time="2020-04-22T15:48:28.539-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnumerateAdministrators' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817337" result="true" testref="oval:org.cisecurity.benchmarks:tst:817337" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817337"> <cis:evidence_item itemref="972"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\CredUI"/> <cis:evidence_item_pk_field name="name" value="EnumerateAdministrators"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173371" value-id="xccdf_org.cisecurity.benchmarks_value_817337_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173372" value-id="xccdf_org.cisecurity.benchmarks_value_817337_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817337"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36512-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.5 |
Label: | Use Multifactor Authentication For All Administrative Access |
Description: | Use multi-factor authentication and encrypted channels for all administrative account access. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This section contains settings for Data Collection and Preview Builds.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
This policy setting determines the amount of diagnostic and usage data reported to Microsoft:
Windows 10 telemetry settings apply to the Windows operating system and some first party apps. This setting does not apply to third party apps running on Windows 10.
The recommended state for this setting is: Enabled: 0 - Security [Enterprise Only] or Enabled: 1 - Basic .
Note: If the Allow Telemetry setting is configured to 0 - Security [Enterprise Only] , then the options in Windows Update to defer upgrades and updates will have no effect.
Note #2: In the Microsoft Windows 10 RTM (Release 1507) Administrative Templates, the zero value was initially named 0 - Off [Enterprise Only] , but it was renamed to 0 - Security [Enterprise Only] starting with the Windows 10 Release 1511 Administrative Templates.
Sending any data to a 3rd party vendor is a security concern and should only be done on an as needed basis.
To establish the recommended configuration via GP, set the following UI path to Enabled: 0 - Security [Enterprise Only] or Enabled: 1 - Basic :
Computer Configuration\Policies\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template DataCollection.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
Impact:
Note that setting values of 0 or 1 will degrade certain experiences on the device.
Any of the following tests or sub-groups may pass: | ||||||||||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.1_L1_Ensure_Allow_Telemetry_is_set_to_Enabled_0_-_Security_Enterprise_Only_or_Enabled_1_-_Basic" role="full" severity="unknown" time="2020-04-22T15:48:28.680-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/13/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.680-05:00" start-time="2020-04-22T15:48:28.618-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowTelemetry' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817341" result="false" testref="oval:org.cisecurity.benchmarks:tst:817341" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817341"> <cis:evidence_item itemref="973"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\DataCollection"/> <cis:evidence_item_pk_field name="name" value="AllowTelemetry"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="1" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowTelemetry' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817336" result="true" testref="oval:org.cisecurity.benchmarks:tst:817336" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817336"> <cis:evidence_item itemref="974"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\DataCollection"/> <cis:evidence_item_pk_field name="name" value="AllowTelemetry"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173361" value-id="xccdf_org.cisecurity.benchmarks_value_817336_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173362" value-id="xccdf_org.cisecurity.benchmarks_value_817336_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817336"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173411" value-id="xccdf_org.cisecurity.benchmarks_value_817341_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173412" value-id="xccdf_org.cisecurity.benchmarks_value_817341_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817341"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
Subcontrol: | 13.3 |
Label: | Monitor and Block Unauthorized Network Traffic |
Description: | Deploy an automated tool on network perimeters that monitors for unauthorized transfer of sensitive information and blocks such transfers while alerting information security professionals. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting allows an organization to prevent its devices from showing feedback questions from Microsoft.
The recommended state for this setting is: Enabled .
Users should not be sending any feedback to 3rd party vendors in an enterprise managed environment.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Data Collection and Preview Builds\Do not show feedback notifications
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template FeedbackNotifications.admx/adml that is included with the Microsoft Windows 10 Release 1511 Administrative Templates (or newer).
Impact:
Users will no longer see feedback notifications through the Windows Feedback app.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.3_L1_Ensure_Do_not_show_feedback_notifications_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:28.758-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.758-05:00" start-time="2020-04-22T15:48:28.680-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DoNotShowFeedbackNotifications' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817345" result="true" testref="oval:org.cisecurity.benchmarks:tst:817345" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817345"> <cis:evidence_item itemref="975"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\DataCollection"/> <cis:evidence_item_pk_field name="name" value="DoNotShowFeedbackNotifications"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173451" value-id="xccdf_org.cisecurity.benchmarks_value_817345_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173452" value-id="xccdf_org.cisecurity.benchmarks_value_817345_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817345"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting determines whether users can access the Insider build controls in the Advanced Options for Windows Update. These controls are located under "Get Insider builds," and enable users to make their devices available for downloading and installing Windows preview software.
The recommended state for this setting is: Disabled .
Note: This policy setting applies only to devices running Windows Server 2016, up until Release 1703. For Release 1709 or newer, Microsoft encourages using the Manage preview builds setting (Rule 18.9.102.1.1). We have kept this setting in the benchmark to ensure that any older builds of Windows Server 2016 in the environment are still enforced.
It can be risky for experimental features to be allowed in an enterprise managed environment because this can introduce bugs and security holes into systems, making it easier for an attacker to gain access. It is generally preferred to only use production-ready builds.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Data Collection and Preview Builds\Toggle user control over Insider builds
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template AllowBuildPreview.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
Impact:
The item "Get Insider builds" will be unavailable.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.16.4_L1_Ensure_Toggle_user_control_over_Insider_builds_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:28.836-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3" system="http://cisecurity.org/20-cc/v6.1"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.836-05:00" start-time="2020-04-22T15:48:28.758-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowBuildPreview' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817350" result="true" testref="oval:org.cisecurity.benchmarks:tst:817350" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817350"> <cis:evidence_item itemref="976"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\PreviewBuilds"/> <cis:evidence_item_pk_field name="name" value="AllowBuildPreview"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173501" value-id="xccdf_org.cisecurity.benchmarks_value_817350_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173502" value-id="xccdf_org.cisecurity.benchmarks_value_817350_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817350"/> </check> </complex-check> </rule-result>
References:
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DeliveryOptimization.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Sidebar.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DWM.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DeviceCompat.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WorkplaceJoin.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Note: This section was initially named Workplace Join but was renamed by Microsoft to Device Registration starting with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DigitalLocker.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template EdgeUI.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template EMET.admx/adml that is included with Microsoft EMET.
EMET is free and supported security software developed by Microsoft that allows an enterprise to apply exploit mitigations to applications that run on Windows. Many of these mitigations were later coded directly into Windows 10 and Server 2016.
Note: Although EMET is quite effective at enhancing exploit protection on Windows server OSes prior to Server 2016, it is highly recommended that compatibility testing is done on typical server configurations (including all CIS-recommended EMET settings) before widespread deployment to your environment.
Note #2: EMET has been reported to be very problematic on 32-bit OSes - we only recommend using it with 64-bit OSes.
Note #3: Microsoft has announced that EMET will be End-Of-Life (EOL) on July 31, 2018. This does not mean the software will stop working, only that Microsoft will not update it any further past that date, nor troubleshoot new problems with it. They are instead recommending that servers be upgraded to Server 2016.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template EventForwarding.admx/adml that is included with the Microsoft Windows Server 2008 (non-R2) Administrative Templates (or newer).
This section contains recommendations for configuring the Event Log Service.
This Group Policy section is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for configuring the Application Event Log.
This Group Policy section is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting controls Event Log behavior when the log file reaches its maximum size.
The recommended state for this setting is: Disabled .
Note: Old events may or may not be retained according to the Backup log automatically when full policy setting.
If new events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Event Log Service\Application\Control Event Log behavior when the log file reaches its maximum size
Note: This Group Policy path is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Retain old events , but it was renamed starting with the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.1.1_L1_Ensure_Application_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:28.914-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37775-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.914-05:00" start-time="2020-04-22T15:48:28.836-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Retention' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817439" result="true" testref="oval:org.cisecurity.benchmarks:tst:817439" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817439"> <cis:evidence_item itemref="977"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\EventLog\Application"/> <cis:evidence_item_pk_field name="name" value="Retention"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="string" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174391" value-id="xccdf_org.cisecurity.benchmarks_value_817439_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174392" value-id="xccdf_org.cisecurity.benchmarks_value_817439_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817439"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37775-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Ensure Audit Logging Systems Are Not Subject To Loss (i.e. rotation/archive) |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated on a regular basis, so that log files will not fill up between log rotation intervals. The logs must be archived and digitally signed on a periodic basis. |
This policy setting specifies the maximum size of the log file in kilobytes. The maximum log file size can be configured between 1 megabyte (1,024 kilobytes) and 4 terabytes (4,194,240 kilobytes) in kilobyte increments.
The recommended state for this setting is: Enabled: 32,768 or greater .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to Enabled: 32,768 or greater :
Computer Configuration\Policies\Administrative Templates\Windows Components\Event Log Service\Application\Specify the maximum log file size (KB)
Note: This Group Policy path is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Maximum Log Size (KB) , but it was renamed starting with the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
Impact:
When event logs fill to capacity, they will stop recording information unless the retention method for each is set so that the computer will overwrite the oldest entries with the most recent ones. To mitigate the risk of loss of recent data, you can configure the retention method so that older events are overwritten as needed.
The consequence of this configuration is that older events will be removed from the logs. Attackers can take advantage of such a configuration, because they can generate a large number of extraneous events to overwrite any evidence of their attack. These risks can be somewhat reduced if you automate the archival and backup of event log data.
Ideally, all specifically monitored events should be sent to a server that uses Microsoft System Center Operations Manager (SCOM) or some other automated monitoring tool. Such a configuration is particularly important because an attacker who successfully compromises a server could clear the Security log. If all events are sent to a monitoring server, then you will be able to gather forensic information about the attacker's activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.1.2_L1_Ensure_Application_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" role="full" severity="unknown" time="2020-04-22T15:48:28.977-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37948-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.992-05:00" start-time="2020-04-22T15:48:28.914-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'MaxSize' is 'Windows: Registry Value' to '32768'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817449" result="true" testref="oval:org.cisecurity.benchmarks:tst:817449" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817449"> <cis:evidence_item itemref="978"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\EventLog\Application"/> <cis:evidence_item_pk_field name="name" value="MaxSize"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="32768" dt="int" ev="32768" name="value" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174491" value-id="xccdf_org.cisecurity.benchmarks_value_817449_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174492" value-id="xccdf_org.cisecurity.benchmarks_value_817449_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817449"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37948-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Ensure Audit Logging Systems Are Not Subject To Loss (i.e. rotation/archive) |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated on a regular basis, so that log files will not fill up between log rotation intervals. The logs must be archived and digitally signed on a periodic basis. |
This section contains recommendations for configuring the Security Event Log.
This Group Policy section is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting controls Event Log behavior when the log file reaches its maximum size.
The recommended state for this setting is: Disabled .
Note: Old events may or may not be retained according to the Backup log automatically when full policy setting.
If new events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Event Log Service\Security\Control Event Log behavior when the log file reaches its maximum size
Note: This Group Policy path is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Retain old events , but it was renamed starting with the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.2.1_L1_Ensure_Security_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:29.055-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37145-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.055-05:00" start-time="2020-04-22T15:48:28.992-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Retention' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817459" result="true" testref="oval:org.cisecurity.benchmarks:tst:817459" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817459"> <cis:evidence_item itemref="979"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\EventLog\Security"/> <cis:evidence_item_pk_field name="name" value="Retention"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="string" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174591" value-id="xccdf_org.cisecurity.benchmarks_value_817459_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174592" value-id="xccdf_org.cisecurity.benchmarks_value_817459_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817459"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37145-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Ensure Audit Logging Systems Are Not Subject To Loss (i.e. rotation/archive) |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated on a regular basis, so that log files will not fill up between log rotation intervals. The logs must be archived and digitally signed on a periodic basis. |
This policy setting specifies the maximum size of the log file in kilobytes. The maximum log file size can be configured between 1 megabyte (1,024 kilobytes) and 4 terabytes (4,194,240 kilobytes) in kilobyte increments.
The recommended state for this setting is: Enabled: 196,608 or greater .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to Enabled: 196,608 or greater :
Computer Configuration\Policies\Administrative Templates\Windows Components\Event Log Service\Security\Specify the maximum log file size (KB)
Note: This Group Policy path is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Maximum Log Size (KB) , but it was renamed starting with the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
Impact:
When event logs fill to capacity, they will stop recording information unless the retention method for each is set so that the computer will overwrite the oldest entries with the most recent ones. To mitigate the risk of loss of recent data, you can configure the retention method so that older events are overwritten as needed.
The consequence of this configuration is that older events will be removed from the logs. Attackers can take advantage of such a configuration, because they can generate a large number of extraneous events to overwrite any evidence of their attack. These risks can be somewhat reduced if you automate the archival and backup of event log data.
Ideally, all specifically monitored events should be sent to a server that uses Microsoft System Center Operations Manager (SCOM) or some other automated monitoring tool. Such a configuration is particularly important because an attacker who successfully compromises a server could clear the Security log. If all events are sent to a monitoring server, then you will be able to gather forensic information about the attacker's activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.2.2_L1_Ensure_Security_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_196608_or_greater" role="full" severity="unknown" time="2020-04-22T15:48:29.133-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37695-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.133-05:00" start-time="2020-04-22T15:48:29.055-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'MaxSize' is 'Windows: Registry Value' to '196608'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817479" result="true" testref="oval:org.cisecurity.benchmarks:tst:817479" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817479"> <cis:evidence_item itemref="980"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\EventLog\Security"/> <cis:evidence_item_pk_field name="name" value="MaxSize"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="196608" dt="int" ev="196608" name="value" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174791" value-id="xccdf_org.cisecurity.benchmarks_value_817479_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174792" value-id="xccdf_org.cisecurity.benchmarks_value_817479_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817479"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37695-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Ensure Audit Logging Systems Are Not Subject To Loss (i.e. rotation/archive) |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated on a regular basis, so that log files will not fill up between log rotation intervals. The logs must be archived and digitally signed on a periodic basis. |
This section contains recommendations for configuring the Setup Event Log.
This Group Policy section is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting controls Event Log behavior when the log file reaches its maximum size.
The recommended state for this setting is: Disabled .
Note: Old events may or may not be retained according to the Backup log automatically when full policy setting.
If new events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Event Log Service\Setup\Control Event Log behavior when the log file reaches its maximum size
Note: This Group Policy path is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Retain old events , but it was renamed starting with the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.3.1_L1_Ensure_Setup_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:29.196-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38276-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.211-05:00" start-time="2020-04-22T15:48:29.133-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Retention' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817456" result="true" testref="oval:org.cisecurity.benchmarks:tst:817456" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817456"> <cis:evidence_item itemref="981"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\EventLog\Setup"/> <cis:evidence_item_pk_field name="name" value="Retention"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="string" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174561" value-id="xccdf_org.cisecurity.benchmarks_value_817456_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174562" value-id="xccdf_org.cisecurity.benchmarks_value_817456_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817456"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38276-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Ensure Audit Logging Systems Are Not Subject To Loss (i.e. rotation/archive) |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated on a regular basis, so that log files will not fill up between log rotation intervals. The logs must be archived and digitally signed on a periodic basis. |
This policy setting specifies the maximum size of the log file in kilobytes. The maximum log file size can be configured between 1 megabyte (1,024 kilobytes) and 4 terabytes (4,194,240 kilobytes) in kilobyte increments.
The recommended state for this setting is: Enabled: 32,768 or greater .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users
To establish the recommended configuration via GP, set the following UI path to Enabled: 32,768 or greater :
Computer Configuration\Policies\Administrative Templates\Windows Components\Event Log Service\Setup\Specify the maximum log file size (KB)
Note: This Group Policy path is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Maximum Log Size (KB) , but it was renamed starting with the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
Impact:
When event logs fill to capacity, they will stop recording information unless the retention method for each is set so that the computer will overwrite the oldest entries with the most recent ones. To mitigate the risk of loss of recent data, you can configure the retention method so that older events are overwritten as needed.
The consequence of this configuration is that older events will be removed from the logs. Attackers can take advantage of such a configuration, because they can generate a large number of extraneous events to overwrite any evidence of their attack. These risks can be somewhat reduced if you automate the archival and backup of event log data.
Ideally, all specifically monitored events should be sent to a server that uses Microsoft System Center Operations Manager (SCOM) or some other automated monitoring tool. Such a configuration is particularly important because an attacker who successfully compromises a server could clear the Security log. If all events are sent to a monitoring server, then you will be able to gather forensic information about the attacker's activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.3.2_L1_Ensure_Setup_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" role="full" severity="unknown" time="2020-04-22T15:48:29.274-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37526-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.274-05:00" start-time="2020-04-22T15:48:29.211-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'MaxSize' is 'Windows: Registry Value' to '32768'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817481" result="true" testref="oval:org.cisecurity.benchmarks:tst:817481" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817481"> <cis:evidence_item itemref="982"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\EventLog\Setup"/> <cis:evidence_item_pk_field name="name" value="MaxSize"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="32768" dt="int" ev="32768" name="value" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174811" value-id="xccdf_org.cisecurity.benchmarks_value_817481_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174812" value-id="xccdf_org.cisecurity.benchmarks_value_817481_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817481"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37526-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Ensure Audit Logging Systems Are Not Subject To Loss (i.e. rotation/archive) |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated on a regular basis, so that log files will not fill up between log rotation intervals. The logs must be archived and digitally signed on a periodic basis. |
This section contains recommendations for configuring the System Event Log.
This Group Policy section is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting controls Event Log behavior when the log file reaches its maximum size.
The recommended state for this setting is: Disabled .
Note: Old events may or may not be retained according to the Backup log automatically when full policy setting.
If new events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Event Log Service\System\Control Event Log behavior when the log file reaches its maximum size
Note: This Group Policy path is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Retain old events , but it was renamed starting with the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.4.1_L1_Ensure_System_Control_Event_Log_behavior_when_the_log_file_reaches_its_maximum_size_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:29.336-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36160-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.336-05:00" start-time="2020-04-22T15:48:29.274-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'Retention' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817457" result="true" testref="oval:org.cisecurity.benchmarks:tst:817457" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817457"> <cis:evidence_item itemref="983"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\EventLog\System"/> <cis:evidence_item_pk_field name="name" value="Retention"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="string" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174571" value-id="xccdf_org.cisecurity.benchmarks_value_817457_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174572" value-id="xccdf_org.cisecurity.benchmarks_value_817457_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817457"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36160-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Ensure Audit Logging Systems Are Not Subject To Loss (i.e. rotation/archive) |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated on a regular basis, so that log files will not fill up between log rotation intervals. The logs must be archived and digitally signed on a periodic basis. |
This policy setting specifies the maximum size of the log file in kilobytes. The maximum log file size can be configured between 1 megabyte (1,024 kilobytes) and 4 terabytes (4,194,240 kilobytes) in kilobyte increments.
The recommended state for this setting is: Enabled: 32,768 or greater .
If events are not recorded it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users
To establish the recommended configuration via GP, set the following UI path to Enabled: 32,768 or greater :
Computer Configuration\Policies\Administrative Templates\Windows Components\Event Log Service\System\Specify the maximum log file size (KB)
Note: This Group Policy path is provided by the Group Policy template EventLog.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Maximum Log Size (KB) , but it was renamed starting with the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
Impact:
When event logs fill to capacity, they will stop recording information unless the retention method for each is set so that the computer will overwrite the oldest entries with the most recent ones. To mitigate the risk of loss of recent data, you can configure the retention method so that older events are overwritten as needed.
The consequence of this configuration is that older events will be removed from the logs. Attackers can take advantage of such a configuration, because they can generate a large number of extraneous events to overwrite any evidence of their attack. These risks can be somewhat reduced if you automate the archival and backup of event log data.
Ideally, all specifically monitored events should be sent to a server that uses Microsoft System Center Operations Manager (SCOM) or some other automated monitoring tool. Such a configuration is particularly important because an attacker who successfully compromises a server could clear the Security log. If all events are sent to a monitoring server, then you will be able to gather forensic information about the attacker's activities.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.26.4.2_L1_Ensure_System_Specify_the_maximum_log_file_size_KB_is_set_to_Enabled_32768_or_greater" role="full" severity="unknown" time="2020-04-22T15:48:29.414-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/6/subcontrol/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/6/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36092-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.414-05:00" start-time="2020-04-22T15:48:29.336-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'MaxSize' is 'Windows: Registry Value' to '32768'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817488" result="true" testref="oval:org.cisecurity.benchmarks:tst:817488" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817488"> <cis:evidence_item itemref="984"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\EventLog\System"/> <cis:evidence_item_pk_field name="name" value="MaxSize"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="32768" dt="int" ev="32768" name="value" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174881" value-id="xccdf_org.cisecurity.benchmarks_value_817488_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174882" value-id="xccdf_org.cisecurity.benchmarks_value_817488_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817488"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36092-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Collect, manage and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.4 |
Label: | Ensure adequate storage for logs |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack. |
Subcontrol: | 6.3 |
Label: | Ensure Audit Logging Systems Are Not Subject To Loss (i.e. rotation/archive) |
Description: | Ensure that all systems that store logs have adequate storage space for the logs generated on a regular basis, so that log files will not fill up between log rotation intervals. The logs must be archived and digitally signed on a periodic basis. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template EventLogging.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template EventViewer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template ParentalControls.admx/adml that is only included with the Microsoft Windows Vista through the Windows 10 RTM (Release 1507) Administrative Templates.
Note: This section was initially named Parental Controls but was renamed by Microsoft to Family Safety starting with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
This section contains recommendations to control the availability of options such as menu items and tabs in dialog boxes.
This Group Policy section is provided by the Group Policy template WindowsExplorer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note: This section was initially named Windows Explorer but was renamed by Microsoft to File Explorer starting with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template PreviousVersions.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Disabling Data Execution Prevention can allow certain legacy plug-in applications to function without terminating Explorer.
The recommended state for this setting is: Disabled .
Note: Some legacy plug-in applications and other software may not function with Data Execution Prevention and will require an exception to be defined for that specific plug-in/software.
Data Execution Prevention is an important security feature supported by Explorer that helps to limit the impact of certain types of malware.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\File Explorer\Turn off Data Execution Prevention for Explorer
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template Explorer.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.2_L1_Ensure_Turn_off_Data_Execution_Prevention_for_Explorer_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:29.477-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37809-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.477-05:00" start-time="2020-04-22T15:48:29.414-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoDataExecutionPrevention' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817370" result="true" testref="oval:org.cisecurity.benchmarks:tst:817370" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817370"> <cis:evidence_item itemref="985"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\Explorer"/> <cis:evidence_item_pk_field name="name" value="NoDataExecutionPrevention"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173701" value-id="xccdf_org.cisecurity.benchmarks_value_817370_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173702" value-id="xccdf_org.cisecurity.benchmarks_value_817370_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817370"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37809-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.3 |
Label: | Enable Operating System Anti-Exploitation Features/ Deploy Anti-Exploit Technologies |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP) or Address Space Layout Randomization (ASLR) that are available in an operating system or deploy appropriate toolkits that can be configured to apply protection to a broader set of applications and executables. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Enable Anti-exploitation Features (i.e. DEP, ASLR, EMET) |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), virtualization/containerization, etc. For increased protection, deploy capabilities such as Enhanced Mitigation Experience Toolkit (EMET) that can be configured to apply these protections to a broader set of applications and executables. |
Without heap termination on corruption, legacy plug-in applications may continue to function when a File Explorer session has become corrupt. Ensuring that heap termination on corruption is active will prevent this.
The recommended state for this setting is: Disabled .
Allowing an application to function after its session has become corrupt increases the risk posture to the system.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\File Explorer\Turn off heap termination on corruption
Note: This Group Policy path is provided by the Group Policy template Explorer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.3_L1_Ensure_Turn_off_heap_termination_on_corruption_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:29.555-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36660-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.555-05:00" start-time="2020-04-22T15:48:29.477-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoHeapTerminationOnCorruption' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817374" result="true" testref="oval:org.cisecurity.benchmarks:tst:817374" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817374"> <cis:evidence_item itemref="986"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\Explorer"/> <cis:evidence_item_pk_field name="name" value="NoHeapTerminationOnCorruption"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173741" value-id="xccdf_org.cisecurity.benchmarks_value_817374_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173742" value-id="xccdf_org.cisecurity.benchmarks_value_817374_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817374"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36660-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.3 |
Label: | Enable Operating System Anti-Exploitation Features/ Deploy Anti-Exploit Technologies |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP) or Address Space Layout Randomization (ASLR) that are available in an operating system or deploy appropriate toolkits that can be configured to apply protection to a broader set of applications and executables. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Enable Anti-exploitation Features (i.e. DEP, ASLR, EMET) |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), virtualization/containerization, etc. For increased protection, deploy capabilities such as Enhanced Mitigation Experience Toolkit (EMET) that can be configured to apply these protections to a broader set of applications and executables. |
This policy setting allows you to configure the amount of functionality that the shell protocol can have. When using the full functionality of this protocol, applications can open folders and launch files. The protected mode reduces the functionality of this protocol allowing applications to only open a limited set of folders. Applications are not able to open files with this protocol when it is in the protected mode. It is recommended to leave this protocol in the protected mode to increase the security of Windows.
The recommended state for this setting is: Disabled .
Limiting the opening of files and folders to a limited set reduces the attack surface of the system.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\File Explorer\Turn off shell protocol protected mode
Note: This Group Policy path is provided by the Group Policy template WindowsExplorer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.30.4_L1_Ensure_Turn_off_shell_protocol_protected_mode_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:29.618-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36809-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.618-05:00" start-time="2020-04-22T15:48:29.555-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'PreXPSP2ShellProtocolBehavior' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817377" result="true" testref="oval:org.cisecurity.benchmarks:tst:817377" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817377"> <cis:evidence_item itemref="987"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\Policies\Explorer"/> <cis:evidence_item_pk_field name="name" value="PreXPSP2ShellProtocolBehavior"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173771" value-id="xccdf_org.cisecurity.benchmarks_value_817377_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173772" value-id="xccdf_org.cisecurity.benchmarks_value_817377_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817377"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36809-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.3 |
Label: | Enable Operating System Anti-Exploitation Features/ Deploy Anti-Exploit Technologies |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP) or Address Space Layout Randomization (ASLR) that are available in an operating system or deploy appropriate toolkits that can be configured to apply protection to a broader set of applications and executables. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Enable Anti-exploitation Features (i.e. DEP, ASLR, EMET) |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), virtualization/containerization, etc. For increased protection, deploy capabilities such as Enhanced Mitigation Experience Toolkit (EMET) that can be configured to apply these protections to a broader set of applications and executables. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template FileHistory.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template FindMy.admx/adml that is included with the Microsoft Windows 10 Release 1703 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template GameExplorer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Handwriting.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Sharing.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template CaptureWizard.admx/adml that is only included with the Microsoft Windows Vista and Windows Server 2008 (non-R2) Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template InetRes.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template IIS.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains settings for Locations and Sensors.
This Group Policy section is provided by the Group Policy template Sensors.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template LocationProviderAdm.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template msched.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WinMaps.admx/adml that is included with the Microsoft Windows 10 Release 1511 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template MDM.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This section contains messaging settings.
This Group Policy section is provided by the Group Policy template Messaging.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
This section contains recommendations related to Microsoft Accounts.
This Group Policy section is provided by the Group Policy template MSAPolicy.admx/adml that is included with the Microsoft Windows 10 Release 1703 Administrative Templates (or newer).
This setting determines whether applications and services on the device can utilize new consumer Microsoft account authentication via the Windows OnlineID and WebAccountManager APIs.
The recommended state for this setting is: Enabled .
Organizations that want to effectively implement identity management policies and maintain firm control of what accounts are used on their computers will probably want to block Microsoft accounts. Organizations may also need to block Microsoft accounts in order to meet the requirements of compliance standards that apply to their information systems.
To establish the recommended configuration via GP, set the following UI path to Enabled:
Computer Configuration\Policies\Administrative Templates\Windows Components\Microsoft accounts\Block all consumer Microsoft account user authentication
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template MSAPolicy.admx/adml that is included with the Microsoft Windows 10 Release 1703 Administrative Templates (or newer).
Impact:
All applications and services on the device will be prevented from new authentications using consumer Microsoft accounts via the Windows OnlineID and WebAccountManager APIs. Authentications performed directly by the user in web browsers or in apps that use OAuth will remain unaffected.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.44.1_L1_Ensure_Block_all_consumer_Microsoft_account_user_authentication_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:29.696-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/8" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.696-05:00" start-time="2020-04-22T15:48:29.633-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableUserAuth' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817406" result="true" testref="oval:org.cisecurity.benchmarks:tst:817406" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817406"> <cis:evidence_item itemref="988"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\MicrosoftAccount"/> <cis:evidence_item_pk_field name="name" value="DisableUserAuth"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174061" value-id="xccdf_org.cisecurity.benchmarks_value_817406_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174062" value-id="xccdf_org.cisecurity.benchmarks_value_817406_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817406"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.8 |
Label: | Disable Any Unassociated Accounts |
Description: | Disable any account that cannot be associated with a business process or business owner. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template MicrosoftEdge.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template FidoAuth.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DeviceCredential.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template UserExperienceVirtualization.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Conf.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template NAPXPQec.admx/adml that is only included with the Microsoft Windows Server 2008 (non-R2) through the Windows 8.1 Update & Server 2012 R2 Update Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template NetworkProjection.admx/adml that is only included with the Microsoft Windows Vista through the Windows 8.1 Update & Server 2012 R2 Update Administrative Templates.
This section contains recommendations related to OneDrive.
The Group Policy settings contained within this section are provided by the Group Policy template SkyDrive.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Note: This section was initially named SkyDrive but was renamed by Microsoft to OneDrive starting with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates.
This policy setting lets you prevent apps and features from working with files on OneDrive using the Next Generation Sync Client.
The recommended state for this setting is: Enabled .
Enabling this setting prevents users from accidentally (or intentionally) uploading confidential or sensitive corporate information to the OneDrive cloud service using the Next Generation Sync Client.
Note: This security concern applies to any cloud-based file storage application installed on a server, not just the one supplied with Windows Server.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\OneDrive\Prevent the usage of OneDrive for file storage
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template SkyDrive.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer). However, we strongly recommend you only use the version included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer). Older versions of the templates had conflicting settings in different template files for both OneDrive & SkyDrive, until it was cleaned up properly in the above version.
Note #2: In older Microsoft Windows Administrative Templates, this setting was named Prevent the usage of SkyDrive for file storage , but it was renamed starting with the Windows 10 RTM (Release 1507) Administrative Templates.
Impact:
Users can't access OneDrive from the OneDrive app and file picker. Windows Store apps can't access OneDrive using the WinRT API. OneDrive doesn't appear in the navigation pane in File Explorer. OneDrive files aren't kept in sync with the cloud. Users can't automatically upload photos and videos from the camera roll folder.
Note: If your organization uses Office 365, be aware that this setting will prevent users from saving files to OneDrive/SkyDrive.
Note #2: If your organization has decided to implement OneDrive for Business and therefore needs to except itself from this recommendation, we highly suggest that you also obtain and utilize the OneDrive.admx/adml template that is bundled with the latest OneDrive client, as noted at this link (this template is not included with the Windows Administrative Templates). Two alternative OneDrive settings in particular from that template are worth your consideration:
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.52.1_L1_Ensure_Prevent_the_usage_of_OneDrive_for_file_storage_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:29.758-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/13/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36939-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.758-05:00" start-time="2020-04-22T15:48:29.696-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableFileSyncNGSC' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817399" result="true" testref="oval:org.cisecurity.benchmarks:tst:817399" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817399"> <cis:evidence_item itemref="989"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\OneDrive"/> <cis:evidence_item_pk_field name="name" value="DisableFileSyncNGSC"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173991" value-id="xccdf_org.cisecurity.benchmarks_value_817399_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173992" value-id="xccdf_org.cisecurity.benchmarks_value_817399_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817399"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36939-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
Subcontrol: | 13.4 |
Label: | Only Allow Access to Authorized Cloud Storage or Email Providers |
Description: | Only allow access to authorized cloud storage or email providers. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template HelpAndSupport.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template OOBE.admx/adml that is included with the Microsoft Windows 10 Release 1809 and Server 2019 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template PswdSync.admx/adml that is only included with the Microsoft Windows Vista through the Windows 8.1 Update & Server 2012 R2 Update Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template ExternalBoot.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template MobilePCPresentationSettings.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template PushToInstall.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
This section contains recommendations related to Remote Desktop Services.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note: This section was initially named Terminal Services but was renamed by Microsoft to Remote Desktop Services starting with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note: This section was initially named TS Licensing but was renamed by Microsoft to RD Licensing starting with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates.
This section contains recommendations for the Remote Desktop Connection Client.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This policy setting helps prevent Remote Desktop clients from saving passwords on a computer.
The recommended state for this setting is: Enabled .
Note: If this policy setting was previously configured as Disabled or Not configured, any previously saved passwords will be deleted the first time a Remote Desktop client disconnects from any server.
An attacker with physical access to the computer may be able to break the protection guarding saved passwords. An attacker who compromises a user's account and connects to their computer could use saved passwords to gain access to additional hosts.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Connection Client\Do not allow passwords to be saved
Note: This Group Policy path is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
The password saving checkbox will be disabled for Remote Desktop clients and users will not be able to save passwords.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.2.2_L1_Ensure_Do_not_allow_passwords_to_be_saved_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:29.821-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36223-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.821-05:00" start-time="2020-04-22T15:48:29.758-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisablePasswordSaving' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817453" result="true" testref="oval:org.cisecurity.benchmarks:tst:817453" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817453"> <cis:evidence_item itemref="990"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services"/> <cis:evidence_item_pk_field name="name" value="DisablePasswordSaving"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174531" value-id="xccdf_org.cisecurity.benchmarks_value_817453_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174532" value-id="xccdf_org.cisecurity.benchmarks_value_817453_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817453"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36223-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Automatically Log Off Users After Standard Period Of Inactivity |
Description: | Regularly monitor the use of all accounts, automatically logging off users after a standard period of inactivity. |
This section contains recommendations for the Remote Desktop Session Host.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note: This section was initially named Terminal Server but was renamed by Microsoft to Remote Desktop Session Host starting with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TerminalServer-Server.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section contains recommendations for Connections to the Remote Desktop Session Host.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Remote Desktop Session Host Device and Resource Redirection.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting prevents users from sharing the local drives on their client computers to Remote Desktop Servers that they access. Mapped drives appear in the session folder tree in Windows Explorer in the following format:
\\TSClient\<driveletter>$
If local drives are shared they are left vulnerable to intruders who want to exploit the data that is stored on them.
The recommended state for this setting is: Enabled .
Data could be forwarded from the user's Remote Desktop Services session to the user's local computer without any direct user interaction. Malicious software already present on a compromised server would have direct and stealthy disk access to the user's local computer during the Remote Desktop session.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection\Do not allow drive redirection
Note: This Group Policy path is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
Drive redirection will not be possible. In most situations, traditional network drive mapping to file shares (including administrative shares) performed manually by the connected user will serve as a capable substitute to still allow file transfers when needed.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.3.2_L1_Ensure_Do_not_allow_drive_redirection_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:30.024-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36509-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:30.024-05:00" start-time="2020-04-22T15:48:29.961-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'fDisableCdm' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817504" result="false" testref="oval:org.cisecurity.benchmarks:tst:817504" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817504"> <cis:evidence_item itemref="993"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services"/> <cis:evidence_item_pk_field name="name" value="fDisableCdm"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="1" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175041" value-id="xccdf_org.cisecurity.benchmarks_value_817504_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175042" value-id="xccdf_org.cisecurity.benchmarks_value_817504_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817504"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36509-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.6 |
Label: | Protect Information through Access Control Lists |
Description: | Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note: This section was initially named TS Connection Broker but was renamed by Microsoft to RD Connection Broker starting with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Remote Desktop Session Host Security.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting specifies whether Remote Desktop Services always prompts the client computer for a password upon connection. You can use this policy setting to enforce a password prompt for users who log on to Remote Desktop Services, even if they already provided the password in the Remote Desktop Connection client.
The recommended state for this setting is: Enabled .
Users have the option to store both their username and password when they create a new Remote Desktop Connection shortcut. If the server that runs Remote Desktop Services allows users who have used this feature to log on to the server but not enter their password, then it is possible that an attacker who has gained physical access to the user's computer could connect to a Remote Desktop Server through the Remote Desktop Connection shortcut, even though they may not know the user's password.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security\Always prompt for password upon connection
Note: This Group Policy path is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In the Microsoft Windows Vista Administrative Templates, this setting was named Always prompt client for password upon connection , but it was renamed starting with the Windows Server 2008 (non-R2) Administrative Templates.
Impact:
Users cannot automatically log on to Remote Desktop Services by supplying their passwords in the Remote Desktop Connection client. They will be prompted for a password to log on.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.1_L1_Ensure_Always_prompt_for_password_upon_connection_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:30.102-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/14" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37929-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:30.102-05:00" start-time="2020-04-22T15:48:30.039-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'fPromptForPassword' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817526" result="true" testref="oval:org.cisecurity.benchmarks:tst:817526" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817526"> <cis:evidence_item itemref="994"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services"/> <cis:evidence_item_pk_field name="name" value="fPromptForPassword"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175261" value-id="xccdf_org.cisecurity.benchmarks_value_817526_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175262" value-id="xccdf_org.cisecurity.benchmarks_value_817526_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817526"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37929-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Encrypt or Hash all Authentication Credentials |
Description: | Encrypt or hash with a salt all authentication credentials when stored. |
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.14 |
Label: | Encrypt/Hash All Authentication Files And Monitor Their Access |
Description: | Verify that all authentication files are encrypted or hashed and that these files cannot be accessed without root or administrator privileges. Audit all access to password files in the system. |
This policy setting allows you to specify whether Remote Desktop Services requires secure Remote Procedure Call (RPC) communication with all clients or allows unsecured communication.
You can use this policy setting to strengthen the security of RPC communication with clients by allowing only authenticated and encrypted requests.
The recommended state for this setting is: Enabled .
Allowing unsecure RPC communication can exposes the server to man in the middle attacks and data disclosure attacks.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security\Require secure RPC communication
Note: This Group Policy path is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
Remote Desktop Services accepts requests from RPC clients that support secure requests, and does not allow unsecured communication with untrusted clients.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.2_L1_Ensure_Require_secure_RPC_communication_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:30.164-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37567-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:30.164-05:00" start-time="2020-04-22T15:48:30.102-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'fEncryptRPCTraffic' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817539" result="true" testref="oval:org.cisecurity.benchmarks:tst:817539" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817539"> <cis:evidence_item itemref="995"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows NT\Terminal Services"/> <cis:evidence_item_pk_field name="name" value="fEncryptRPCTraffic"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175391" value-id="xccdf_org.cisecurity.benchmarks_value_817539_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175392" value-id="xccdf_org.cisecurity.benchmarks_value_817539_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817539"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37567-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.5 |
Label: | Use Multifactor Authentication For All Administrative Access |
Description: | Use multi-factor authentication and encrypted channels for all administrative account access. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 3.4 |
Label: | Use Only Secure Channels For Remote System Administration |
Description: | Perform all remote administration of servers, workstation, network devices, and similar equipment over secure channels. Protocols such as telnet, VNC, RDP, or others that do not actively support strong encryption should only be used if they are performed over a secondary encryption channel, such as SSL, TLS or IPSEC. |
This policy setting specifies whether to require the use of a specific security layer to secure communications between clients and RD Session Host servers during Remote Desktop Protocol (RDP) connections.
The recommended state for this setting is: Enabled: SSL .
Note: In spite of this setting being labelled SSL , it is actually enforcing Transport Layer Security (TLS) version 1.0, not the older (and less secure) SSL protocol.
The native Remote Desktop Protocol (RDP) encryption is now considered a weak protocol, so enforcing the use of stronger Transport Layer Security (TLS) encryption for all RDP communications between clients and RD Session Host servers is preferred.
To establish the recommended configuration via GP, set the following UI path to Enabled: SSL :
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security\Require use of specific security layer for remote (RDP) connections
Note: This Group Policy path is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
TLS 1.0 will be required to authenticate to the RD Session Host server. If TLS is not supported, the connection fails.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.3_L1_Ensure_Require_use_of_specific_security_layer_for_remote_RDP_connections_is_set_to_Enabled_SSL" role="full" severity="unknown" time="2020-04-22T15:48:30.227-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36598-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817552" definition_negate="false"> <cis:and negated="false" result="false"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'SecurityLayer' is 'Windows: Registry Value' to '2'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817552" result="false" testref="oval:org.cisecurity.benchmarks:tst:817552" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817552"> <cis:evidence_item itemref="996"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services"/> <cis:evidence_item_pk_field name="name" value="SecurityLayer"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="2" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175521" value-id="xccdf_org.cisecurity.benchmarks_value_817552_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175522" value-id="xccdf_org.cisecurity.benchmarks_value_817552_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817552"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36598-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.5 |
Label: | Use Multifactor Authentication For All Administrative Access |
Description: | Use multi-factor authentication and encrypted channels for all administrative account access. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 3.4 |
Label: | Use Only Secure Channels For Remote System Administration |
Description: | Perform all remote administration of servers, workstation, network devices, and similar equipment over secure channels. Protocols such as telnet, VNC, RDP, or others that do not actively support strong encryption should only be used if they are performed over a secondary encryption channel, such as SSL, TLS or IPSEC. |
This policy setting allows you to specify whether to require user authentication for remote connections to the RD Session Host server by using Network Level Authentication.
The recommended state for this setting is: Enabled .
Requiring that user authentication occur earlier in the remote connection process enhances security.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security\Require user authentication for remote connections by using Network Level Authentication
Note: This Group Policy path is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In the Microsoft Windows Vista Administrative Templates, this setting was initially named Require user authentication using RDP 6.0 for remote connections , but it was renamed starting with the Windows Server 2008 (non-R2) Administrative Templates.
Impact:
Only client computers that support Network Level Authentication can connect to the RD Session Host server.
Note: Some third party two-factor authentication solutions (e.g. RSA Authentication Agent) can be negatively affected by this setting, as Network Level Authentication will expect the user's Windows password, and once successfully authenticated, pass the credential along to the Windows session on the RDP host (to complete the login). If a two-factor agent is present and expecting a different credential at the RDP logon screen, this initial connection may result in a failed logon attempt.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.4_L1_Ensure_Require_user_authentication_for_remote_connections_by_using_Network_Level_Authentication_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:30.289-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37330-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817557" definition_negate="false"> <cis:and negated="false" result="false"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'UserAuthentication' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817557" result="false" testref="oval:org.cisecurity.benchmarks:tst:817557" type="registry_test"> <cis:evidence_object> <cis:evidence_item itemref="997"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services"/> <cis:evidence_item_pk_field name="name" value="UserAuthentication"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175571" value-id="xccdf_org.cisecurity.benchmarks_value_817557_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175572" value-id="xccdf_org.cisecurity.benchmarks_value_817557_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817557"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37330-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.5 |
Label: | Use Multifactor Authentication For All Administrative Access |
Description: | Use multi-factor authentication and encrypted channels for all administrative account access. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 3.4 |
Label: | Use Only Secure Channels For Remote System Administration |
Description: | Perform all remote administration of servers, workstation, network devices, and similar equipment over secure channels. Protocols such as telnet, VNC, RDP, or others that do not actively support strong encryption should only be used if they are performed over a secondary encryption channel, such as SSL, TLS or IPSEC. |
This policy setting specifies whether to require the use of a specific encryption level to secure communications between client computers and RD Session Host servers during Remote Desktop Protocol (RDP) connections. This policy only applies when you are using native RDP encryption. However, native RDP encryption (as opposed to SSL encryption) is not recommended. This policy does not apply to SSL encryption.
The recommended state for this setting is: Enabled: High Level .
If Remote Desktop client connections that use low level encryption are allowed, it is more likely that an attacker will be able to decrypt any captured Remote Desktop Services network traffic.
To establish the recommended configuration via GP, set the following UI path to Enabled: High Level :
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security\Set client connection encryption level
Note: This Group Policy path is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.9.5_L1_Ensure_Set_client_connection_encryption_level_is_set_to_Enabled_High_Level" role="full" severity="unknown" time="2020-04-22T15:48:30.352-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36627-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:30.352-05:00" start-time="2020-04-22T15:48:30.289-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'MinEncryptionLevel' is 'Windows: Registry Value' to '3'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817546" result="false" testref="oval:org.cisecurity.benchmarks:tst:817546" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817546"> <cis:evidence_item itemref="998"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services"/> <cis:evidence_item_pk_field name="name" value="MinEncryptionLevel"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="2" dt="int" ev="3" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175461" value-id="xccdf_org.cisecurity.benchmarks_value_817546_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175462" value-id="xccdf_org.cisecurity.benchmarks_value_817546_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817546"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36627-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.5 |
Label: | Use Multifactor Authentication For All Administrative Access |
Description: | Use multi-factor authentication and encrypted channels for all administrative account access. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 3.4 |
Label: | Use Only Secure Channels For Remote System Administration |
Description: | Perform all remote administration of servers, workstation, network devices, and similar equipment over secure channels. Protocols such as telnet, VNC, RDP, or others that do not actively support strong encryption should only be used if they are performed over a secondary encryption channel, such as SSL, TLS or IPSEC. |
This section contains recommendations related to Remote Desktop Session Host Session Time Limits.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Remote Desktop Session Host Session Temporary folders.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting specifies whether Remote Desktop Services retains a user's per-session temporary folders at logoff.
The recommended state for this setting is: Disabled .
Sensitive information could be contained inside the temporary folders and visible to other administrators that log into the system.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Temporary Folders\Do not delete temp folders upon exit
Note: This Group Policy path is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was named Do not delete temp folder upon exit , but it was renamed starting with the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.11.1_L1_Ensure_Do_not_delete_temp_folders_upon_exit_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:29.899-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37946-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.899-05:00" start-time="2020-04-22T15:48:29.836-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DeleteTempDirsOnExit' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817528" result="true" testref="oval:org.cisecurity.benchmarks:tst:817528" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817528"> <cis:evidence_item itemref="991"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services"/> <cis:evidence_item_pk_field name="name" value="DeleteTempDirsOnExit"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175281" value-id="xccdf_org.cisecurity.benchmarks_value_817528_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175282" value-id="xccdf_org.cisecurity.benchmarks_value_817528_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817528"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37946-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.6 |
Label: | Protect Information through Access Control Lists |
Description: | Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.4 |
Label: | Protect Information With Access Control Lists |
Description: | All information stored on systems shall be protected with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principal that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
By default, Remote Desktop Services creates a separate temporary folder on the RD Session Host server for each active session that a user maintains on the RD Session Host server. The temporary folder is created on the RD Session Host server in a Temp folder under the user's profile folder and is named with the sessionid . This temporary folder is used to store individual temporary files.
To reclaim disk space, the temporary folder is deleted when the user logs off from a session.
The recommended state for this setting is: Disabled .
Disabling this setting keeps the cached data independent for each session, both reducing the chance of problems from shared cached data between sessions, and keeping possibly sensitive data separate to each user session.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Temporary Folders\Do not use temporary folders per session
Note: This Group Policy path is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.59.3.11.2_L1_Ensure_Do_not_use_temporary_folders_per_session_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:29.961-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38180-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:29.961-05:00" start-time="2020-04-22T15:48:29.899-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'PerSessionTempDir' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817540" result="true" testref="oval:org.cisecurity.benchmarks:tst:817540" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817540"> <cis:evidence_item itemref="992"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows NT\Terminal Services"/> <cis:evidence_item_pk_field name="name" value="PerSessionTempDir"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175401" value-id="xccdf_org.cisecurity.benchmarks_value_817540_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175402" value-id="xccdf_org.cisecurity.benchmarks_value_817540_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817540"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38180-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.6 |
Label: | Protect Information through Access Control Lists |
Description: | Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.4 |
Label: | Protect Information With Access Control Lists |
Description: | All information stored on systems shall be protected with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principal that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
This section contains recommendations related to RSS feeds.
This Group Policy section is provided by the Group Policy template InetRes.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting prevents the user from having enclosures (file attachments) downloaded from an RSS feed to the user's computer.
The recommended state for this setting is: Enabled .
Allowing attachments to be downloaded through the RSS feed can introduce files that could have malicious intent.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\RSS Feeds\Prevent downloading of enclosures
Note: This Group Policy path is provided by the Group Policy template InetRes.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was named Turn off downloading of enclosures , but it was renamed starting with the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
Impact:
Users cannot set the Feed Sync Engine to download an enclosure through the Feed property page. Developers cannot change the download setting through feed APIs.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.60.1_L1_Ensure_Prevent_downloading_of_enclosures_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:30.493-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/7/subcontrol/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/7/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37126-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:30.493-05:00" start-time="2020-04-22T15:48:30.430-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableEnclosureDownload' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817378" result="true" testref="oval:org.cisecurity.benchmarks:tst:817378" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817378"> <cis:evidence_item itemref="1000"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds"/> <cis:evidence_item_pk_field name="name" value="DisableEnclosureDownload"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173781" value-id="xccdf_org.cisecurity.benchmarks_value_817378_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173782" value-id="xccdf_org.cisecurity.benchmarks_value_817378_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817378"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37126-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior through their interaction with web browsers and email systems. |
Subcontrol: | 7.2 |
Label: | Disable Unnecessary or Unauthorized Browser or Email Client Plugins |
Description: | Uninstall or disable any unauthorized browser or email client plugins or add-on applications. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior though their interaction with web browsers and email systems. |
Subcontrol: | 7.2 |
Label: | Uninstall/Disable Unnecessary or Unauthorized Browser Or Email Client Plugins |
Description: | Uninstall or disable any unnecessary or unauthorized browser or email client plugins or add-on applications. Each plugin shall utilize application / URL whitelisting and only allow the use of the application for pre-approved domains. |
This section contains recommendations for Search settings.
This Group Policy section is provided by the Group Policy template Search.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template SearchOCR.admx/adml that is only included with the Microsoft Windows 7 & Server 2008 R2 through the Windows 10 Release 1511 Administrative Templates.
This policy setting controls whether encrypted items are allowed to be indexed. When this setting is changed, the index is rebuilt completely. Full volume encryption (such as BitLocker Drive Encryption or a non-Microsoft solution) must be used for the location of the index to maintain security for encrypted files.
The recommended state for this setting is: Disabled .
Indexing and allowing users to search encrypted files could potentially reveal confidential data stored within the encrypted files.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Search\Allow indexing of encrypted files
Note: This Group Policy path is provided by the Group Policy template Search.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.61.3_L1_Ensure_Allow_indexing_of_encrypted_files_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:30.555-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/13/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38277-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:30.555-05:00" start-time="2020-04-22T15:48:30.493-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowIndexingEncryptedStoresOrItems' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817380" result="true" testref="oval:org.cisecurity.benchmarks:tst:817380" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817380"> <cis:evidence_item itemref="1001"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\Windows Search"/> <cis:evidence_item_pk_field name="name" value="AllowIndexingEncryptedStoresOrItems"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173801" value-id="xccdf_org.cisecurity.benchmarks_value_817380_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173802" value-id="xccdf_org.cisecurity.benchmarks_value_817380_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817380"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38277-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
Subcontrol: | 13.3 |
Label: | Monitor and Block Unauthorized Network Traffic |
Description: | Deploy an automated tool on network perimeters that monitors for unauthorized transfer of sensitive information and blocks such transfers while alerting information security professionals. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
Subcontrol: | 13.1 |
Label: | Assess Data To Identify Sensitive Information |
Description: | Perform an assessment of data to identify sensitive information that requires the application of encryption and integrity controls. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template SecurityCenter.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Snis.admx/adml that is only included with the Microsoft Windows Vista through the Windows 8.1 Update & Server 2012 R2 Update Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WinInit.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template SmartCard.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to the Software Protection Platform.
This Group Policy section is provided by the Group Policy template AVSValidationGP.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template SoundRec.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Speech.admx/adml that is included with the Microsoft Windows 10 Release 1703 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WinStoreUI.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates, or by the Group Policy template WindowsStore.admx/adml that is included with the Microsoft Windows 10 Release 1511 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template SettingSync.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TaskScheduler.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TextInput.admx/adml that is only included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates and Microsoft Windows 10 Release 1511 Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WinCal.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsColorSystem.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template CEIPEnable.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Windows Defender Antivirus.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note: This section was originally named Windows Defender but was renamed by Microsoft to Windows Defender Antivirus starting with the Microsoft Windows 10 Release 1703 Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This section contains recommendations related to Microsoft Active Protection Service (MAPS).
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This policy setting configures a local override for the configuration to join Microsoft Active Protection Service (MAPS), which Microsoft has now renamed to "Windows Defender Antivirus Cloud Protection Service". This setting can only be set by Group Policy.
The recommended state for this setting is: Disabled .
The decision on whether or not to participate in Microsoft MAPS / Windows Defender Antivirus Cloud Protection Service for malicious software reporting should be made centrally in an enterprise managed environment, so that all computers within it behave consistently in that regard. Configuring this setting to Disabled ensures that the decision remains centrally managed.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Defender Antivirus\MAPS\Configure local setting override for reporting to Microsoft MAPS
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.3.1_L1_Ensure_Configure_local_setting_override_for_reporting_to_Microsoft_MAPS_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:31.743-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/2/subcontrol/7" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36940-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:31.743-05:00" start-time="2020-04-22T15:48:31.680-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'LocalSettingOverrideSpynetReporting' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817470" result="true" testref="oval:org.cisecurity.benchmarks:tst:817470" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817470"> <cis:evidence_item itemref="1019"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Spynet"/> <cis:evidence_item_pk_field name="name" value="LocalSettingOverrideSpynetReporting"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174701" value-id="xccdf_org.cisecurity.benchmarks_value_817470_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174702" value-id="xccdf_org.cisecurity.benchmarks_value_817470_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817470"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36940-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that all unauthorized and unmanaged software is found and prevented from installation or execution. |
Subcontrol: | 2.7 |
Label: | Utilize Application Whitelisting |
Description: | Utilize application whitelisting technology on all assets to ensure that only authorized software executes and all unauthorized software is blocked from executing on assets. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.1 |
Label: | Utilize Centrally Managed Anti-malware Software |
Description: | Utilize centrally managed anti-malware software to continuously monitor and defend each of the organization's workstations and servers. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.2 |
Label: | Ensure Anti-Malware Software and Signatures are Updated |
Description: | Ensure that the organization's anti-malware software updates its scanning engine and signature database on a regular basis. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 10 Release 1703 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This section contains settings related to Real-time Protection.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This policy setting allows you to configure behavior monitoring for Windows Defender Antivirus.
The recommended state for this setting is: Enabled .
When running an antivirus solution such as Windows Defender Antivirus, it is important to ensure that it is configured to heuristically monitor in real-time for suspicious and known malicious activity.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Defender Antivirus\Real-Time Protection\Turn on behavior monitoring
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Impact:
None - this is the default configuration.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.7.1_L1_Ensure_Turn_on_behavior_monitoring_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:31.805-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38389-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:31.805-05:00" start-time="2020-04-22T15:48:31.758-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableBehaviorMonitoring' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817464" result="true" testref="oval:org.cisecurity.benchmarks:tst:817464" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817464"> <cis:evidence_item itemref="1020"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Real-Time Protection"/> <cis:evidence_item_pk_field name="name" value="DisableBehaviorMonitoring"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174641" value-id="xccdf_org.cisecurity.benchmarks_value_817464_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174642" value-id="xccdf_org.cisecurity.benchmarks_value_817464_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817464"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38389-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.1 |
Label: | Utilize Centrally Managed Anti-malware Software |
Description: | Utilize centrally managed anti-malware software to continuously monitor and defend each of the organization's workstations and servers. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.6 |
Label: | Centralize Anti-Malware Logging |
Description: | Send all malware detection events to enterprise anti-malware administration tools and event log servers for analysis and alerting. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.2 |
Label: | Ensure Anti-Malware Software and Signatures are Updated |
Description: | Ensure that the organization's anti-malware software updates its scanning engine and signature database on a regular basis. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.1 |
Label: | Deploy Automated Endpoint Protection Tools |
Description: | Employ automated tools to continuously monitor workstations, servers, and mobile devices with anti-virus, anti-spyware, personal firewalls, and host-based IPS functionality. All malware detection events should be sent to enterprise anti-malware administration tools and event log servers. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This section contains settings related to Windows Defender Reporting.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This section contains settings related to Windows Defender scanning.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This policy setting allows you to manage whether or not to scan for malicious software and unwanted software in the contents of removable drives, such as USB flash drives, when running a full scan.
The recommended state for this setting is: Enabled .
It is important to ensure that any present removable drives are always included in any type of scan, as removable drives are more likely to contain malicious software brought in to the enterprise managed environment from an external, unmanaged computer.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Defender Antivirus\Scan\Scan removable drives
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Impact:
Removable drives will be scanned during any type of scan by Windows Defender Antivirus.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.10.1_L1_Ensure_Scan_removable_drives_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:30.633-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38409-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:30.633-05:00" start-time="2020-04-22T15:48:30.571-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableRemovableDriveScanning' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817471" result="true" testref="oval:org.cisecurity.benchmarks:tst:817471" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817471"> <cis:evidence_item itemref="1002"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Scan"/> <cis:evidence_item_pk_field name="name" value="DisableRemovableDriveScanning"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174711" value-id="xccdf_org.cisecurity.benchmarks_value_817471_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174712" value-id="xccdf_org.cisecurity.benchmarks_value_817471_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817471"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38409-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Configure Anti-Malware Scanning of Removable Devices |
Description: | Configure devices so that they automatically conduct an anti-malware scan of removable media when inserted or connected. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting allows you to configure e-mail scanning. When e-mail scanning is enabled, the engine will parse the mailbox and mail files, according to their specific format, in order to analyze the mail bodies and attachments. Several e-mail formats are currently supported, for example: pst (Outlook), dbx, mbx, mime (Outlook Express), binhex (Mac).
The recommended state for this setting is: Enabled .
Incoming e-mails should be scanned by an antivirus solution such as Windows Defender Antivirus, as email attachments are a commonly used attack vector to infiltrate computers with malicious software.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Defender Antivirus\Scan\Turn on e-mail scanning
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Impact:
E-mail scanning by Windows Defender Antivirus will be enabled.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.10.2_L1_Ensure_Turn_on_e-mail_scanning_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:30.696-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36958-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:30.696-05:00" start-time="2020-04-22T15:48:30.633-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableEmailScanning' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817466" result="true" testref="oval:org.cisecurity.benchmarks:tst:817466" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817466"> <cis:evidence_item itemref="1003"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Scan"/> <cis:evidence_item_pk_field name="name" value="DisableEmailScanning"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174661" value-id="xccdf_org.cisecurity.benchmarks_value_817466_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174662" value-id="xccdf_org.cisecurity.benchmarks_value_817466_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817466"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36958-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.1 |
Label: | Utilize Centrally Managed Anti-malware Software |
Description: | Utilize centrally managed anti-malware software to continuously monitor and defend each of the organization's workstations and servers. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.2 |
Label: | Ensure Anti-Malware Software and Signatures are Updated |
Description: | Ensure that the organization's anti-malware software updates its scanning engine and signature database on a regular basis. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Note: This section was initially named Signature Updates but was renamed by Microsoft to Security Intelligence Updates starting with the Microsoft Windows 10 Release 1903 Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This section contains Windows Defender Exploit Guard settings.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
This section contains Attack Surface Reduction settings.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This policy setting controls the state for the Attack Surface Reduction (ASR) rules.
The recommended state for this setting is: Enabled .
Attack surface reduction helps prevent actions and apps that are typically used by exploit-seeking malware to infect machines.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Defender Antivirus\Windows Defender Exploit Guard\Attack Surface Reduction\Configure Attack Surface Reduction rules
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
Impact:
When a rule is triggered, a notification will be displayed from the Action Center.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.1.1_L1_Ensure_Configure_Attack_Surface_Reduction_rules_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:30.758-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817487" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ExploitGuard_ASR_Rules' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817487" result="true" testref="oval:org.cisecurity.benchmarks:tst:817487" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817487"> <cis:evidence_item itemref="1004"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\ASR"/> <cis:evidence_item_pk_field name="name" value="ExploitGuard_ASR_Rules"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174871" value-id="xccdf_org.cisecurity.benchmarks_value_817487_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174872" value-id="xccdf_org.cisecurity.benchmarks_value_817487_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817487"/> </check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.3 |
Label: | Enable Operating System Anti-Exploitation Features/ Deploy Anti-Exploit Technologies |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP) or Address Space Layout Randomization (ASLR) that are available in an operating system or deploy appropriate toolkits that can be configured to apply protection to a broader set of applications and executables. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Enable Anti-exploitation Features (i.e. DEP, ASLR, EMET) |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), virtualization/containerization, etc. For increased protection, deploy capabilities such as Enhanced Mitigation Experience Toolkit (EMET) that can be configured to apply these protections to a broader set of applications and executables. |
This policy setting sets the Attack Surface Reduction rules.
The recommended state for this setting is:
26190899-1602-49e8-8b27-eb1d0a1ce869 - 1 (Block Office communication application from creating child processes)
3b576869-a4ec-4529-8536-b80a7769e899 - 1 (Block Office applications from creating executable content)
5beb7efe-fd9a-4556-801d-275e5ffc04cc - 1 (Block execution of potentially obfuscated scripts)
75668c1f-73b5-4cf0-bb93-3ecf5cb7cc84 - 1 (Block Office applications from injecting code into other processes)
7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c - 1 (Block Adobe Reader from creating child processes)
92e97fa1-2edf-4476-bdd6-9dd0b4dddc7b - 1 (Block Win32 API calls from Office macro)
9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2 - 1 (Block credential stealing from the Windows local security authority subsystem (lsass.exe))
b2b3f03d-6a65-4f7b-a9c7-1c7ef74a9ba4 - 1 (Block untrusted and unsigned processes that run from USB)
be9ba2d9-53ea-4cdc-84e5-9b1eeee46550 - 1 (Block executable content from email client and webmail)
d3e037e1-3eb8-44c8-a917-57927947596d - 1 (Block JavaScript or VBScript from launching downloaded executable content)
d4f940ab-401b-4efc-aadc-ad5f3c50688a - 1 (Block Office applications from creating child processes)
Note: More information on ASR rules can be found at the following link: Use Attack surface reduction rules to prevent malware infection | Microsoft Docs
Attack surface reduction helps prevent actions and apps that are typically used by exploit-seeking malware to infect machines.
To establish the recommended configuration via GP, set the following UI path so that 26190899-1602-49e8-8b27-eb1d0a1ce869 , 3b576869-a4ec-4529-8536-b80a7769e899 , 5beb7efe-fd9a-4556-801d-275e5ffc04cc , 75668c1f-73b5-4cf0-bb93-3ecf5cb7cc84 , 7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c , 92e97fa1-2edf-4476-bdd6-9dd0b4dddc7b , 9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2 , b2b3f03d-6a65-4f7b-a9c7-1c7ef74a9ba4 , be9ba2d9-53ea-4cdc-84e5-9b1eeee46550 , d3e037e1-3eb8-44c8-a917-57927947596d and d4f940ab-401b-4efc-aadc-ad5f3c50688a are each set to a value of 1 :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Defender Antivirus\Windows Defender Exploit Guard\Attack Surface Reduction\Configure Attack Surface Reduction rules: Set the state for each ASR rule
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
Impact:
When a rule is triggered, a notification will be displayed from the Action Center.
All of the following tests or sub-groups must pass: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.1.2_L1_Ensure_Configure_Attack_Surface_Reduction_rules_Set_the_state_for_each_ASR_rule_is_configured" role="full" severity="unknown" time="2020-04-22T15:48:31.477-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:31.477-05:00" start-time="2020-04-22T15:48:30.758-05:00"> <cis:and> <cis:and> <cis:and> <cis:and> <cis:and> <cis:and> <cis:and> <cis:and> <cis:and> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '3b576869-a4ec-4529-8536-b80a7769e899' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817501" result="true" testref="oval:org.cisecurity.benchmarks:tst:817501" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817501"> <cis:evidence_item itemref="1005"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\ASR\Rules"/> <cis:evidence_item_pk_field name="name" value="3b576869-a4ec-4529-8536-b80a7769e899"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '26190899-1602-49e8-8b27-eb1d0a1ce869' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817495" result="true" testref="oval:org.cisecurity.benchmarks:tst:817495" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817495"> <cis:evidence_item itemref="1006"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\ASR\Rules"/> <cis:evidence_item_pk_field name="name" value="26190899-1602-49e8-8b27-eb1d0a1ce869"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '5beb7efe-fd9a-4556-801d-275e5ffc04cc' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817506" result="true" testref="oval:org.cisecurity.benchmarks:tst:817506" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817506"> <cis:evidence_item itemref="1007"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\ASR\Rules"/> <cis:evidence_item_pk_field name="name" value="5beb7efe-fd9a-4556-801d-275e5ffc04cc"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '75668c1f-73b5-4cf0-bb93-3ecf5cb7cc84' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817510" result="true" testref="oval:org.cisecurity.benchmarks:tst:817510" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817510"> <cis:evidence_item itemref="1008"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\ASR\Rules"/> <cis:evidence_item_pk_field name="name" value="75668c1f-73b5-4cf0-bb93-3ecf5cb7cc84"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817515" result="true" testref="oval:org.cisecurity.benchmarks:tst:817515" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817515"> <cis:evidence_item itemref="1009"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\ASR\Rules"/> <cis:evidence_item_pk_field name="name" value="7674ba52-37eb-4a4f-a9a1-f0f9a1619a2c"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '92e97fa1-2edf-4476-bdd6-9dd0b4dddc7b' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817520" result="true" testref="oval:org.cisecurity.benchmarks:tst:817520" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817520"> <cis:evidence_item itemref="1010"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\ASR\Rules"/> <cis:evidence_item_pk_field name="name" value="92e97fa1-2edf-4476-bdd6-9dd0b4dddc7b"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure '9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817527" result="true" testref="oval:org.cisecurity.benchmarks:tst:817527" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817527"> <cis:evidence_item itemref="1011"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\ASR\Rules"/> <cis:evidence_item_pk_field name="name" value="9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'b2b3f03d-6a65-4f7b-a9c7-1c7ef74a9ba4' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817533" result="true" testref="oval:org.cisecurity.benchmarks:tst:817533" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817533"> <cis:evidence_item itemref="1012"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\ASR\Rules"/> <cis:evidence_item_pk_field name="name" value="b2b3f03d-6a65-4f7b-a9c7-1c7ef74a9ba4"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'be9ba2d9-53ea-4cdc-84e5-9b1eeee46550' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817537" result="true" testref="oval:org.cisecurity.benchmarks:tst:817537" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817537"> <cis:evidence_item itemref="1013"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\ASR\Rules"/> <cis:evidence_item_pk_field name="name" value="be9ba2d9-53ea-4cdc-84e5-9b1eeee46550"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'd3e037e1-3eb8-44c8-a917-57927947596d' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817541" result="true" testref="oval:org.cisecurity.benchmarks:tst:817541" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817541"> <cis:evidence_item itemref="1014"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\ASR\Rules"/> <cis:evidence_item_pk_field name="name" value="d3e037e1-3eb8-44c8-a917-57927947596d"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'd4f940ab-401b-4efc-aadc-ad5f3c50688a' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817544" result="true" testref="oval:org.cisecurity.benchmarks:tst:817544" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817544"> <cis:evidence_item itemref="1015"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\ASR\Rules"/> <cis:evidence_item_pk_field name="name" value="d4f940ab-401b-4efc-aadc-ad5f3c50688a"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <xccdf:complex-check operator="AND"> <xccdf:complex-check operator="AND"> <xccdf:complex-check operator="AND"> <xccdf:complex-check operator="AND"> <xccdf:complex-check operator="AND"> <xccdf:complex-check operator="AND"> <xccdf:complex-check operator="AND"> <xccdf:complex-check operator="AND"> <xccdf:complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174951" value-id="xccdf_org.cisecurity.benchmarks_value_817495_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174952" value-id="xccdf_org.cisecurity.benchmarks_value_817495_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817495"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175011" value-id="xccdf_org.cisecurity.benchmarks_value_817501_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175012" value-id="xccdf_org.cisecurity.benchmarks_value_817501_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817501"/> </check> </xccdf:complex-check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175061" value-id="xccdf_org.cisecurity.benchmarks_value_817506_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175062" value-id="xccdf_org.cisecurity.benchmarks_value_817506_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817506"/> </check> </xccdf:complex-check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175101" value-id="xccdf_org.cisecurity.benchmarks_value_817510_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175102" value-id="xccdf_org.cisecurity.benchmarks_value_817510_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817510"/> </check> </xccdf:complex-check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175151" value-id="xccdf_org.cisecurity.benchmarks_value_817515_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175152" value-id="xccdf_org.cisecurity.benchmarks_value_817515_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817515"/> </check> </xccdf:complex-check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175201" value-id="xccdf_org.cisecurity.benchmarks_value_817520_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175202" value-id="xccdf_org.cisecurity.benchmarks_value_817520_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817520"/> </check> </xccdf:complex-check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175271" value-id="xccdf_org.cisecurity.benchmarks_value_817527_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175272" value-id="xccdf_org.cisecurity.benchmarks_value_817527_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817527"/> </check> </xccdf:complex-check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175331" value-id="xccdf_org.cisecurity.benchmarks_value_817533_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175332" value-id="xccdf_org.cisecurity.benchmarks_value_817533_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817533"/> </check> </xccdf:complex-check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175371" value-id="xccdf_org.cisecurity.benchmarks_value_817537_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175372" value-id="xccdf_org.cisecurity.benchmarks_value_817537_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817537"/> </check> </xccdf:complex-check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175411" value-id="xccdf_org.cisecurity.benchmarks_value_817541_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175412" value-id="xccdf_org.cisecurity.benchmarks_value_817541_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817541"/> </check> </xccdf:complex-check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175441" value-id="xccdf_org.cisecurity.benchmarks_value_817544_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175442" value-id="xccdf_org.cisecurity.benchmarks_value_817544_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817544"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.3 |
Label: | Enable Operating System Anti-Exploitation Features/ Deploy Anti-Exploit Technologies |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP) or Address Space Layout Randomization (ASLR) that are available in an operating system or deploy appropriate toolkits that can be configured to apply protection to a broader set of applications and executables. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Enable Anti-exploitation Features (i.e. DEP, ASLR, EMET) |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), virtualization/containerization, etc. For increased protection, deploy capabilities such as Enhanced Mitigation Experience Toolkit (EMET) that can be configured to apply these protections to a broader set of applications and executables. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This section contains Windows Network Protection settings.
This Group Policy section is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
This policy setting controls Windows Defender Exploit Guard network protection.
The recommended state for this setting is: Enabled: Block .
This setting can help prevent employees from using any application to access dangerous domains that may host phishing scams, exploit-hosting sites, and other malicious content on the Internet.
To establish the recommended configuration via GP, set the following UI path to Enabled: Block :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Defender Antivirus\Windows Defender Exploit Guard\Network Protection\Prevent users and apps from accessing dangerous websites
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
Impact:
Users and applications will not be able to access dangerous domains.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.13.3.1_L1_Ensure_Prevent_users_and_apps_from_accessing_dangerous_websites_is_set_to_Enabled_Block" role="full" severity="unknown" time="2020-04-22T15:48:31.555-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/7/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/7/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/7/subcontrol/7" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817500" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableNetworkProtection' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817500" result="true" testref="oval:org.cisecurity.benchmarks:tst:817500" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817500"> <cis:evidence_item itemref="1016"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\Network Protection"/> <cis:evidence_item_pk_field name="name" value="EnableNetworkProtection"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175001" value-id="xccdf_org.cisecurity.benchmarks_value_817500_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175002" value-id="xccdf_org.cisecurity.benchmarks_value_817500_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817500"/> </check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior through their interaction with web browsers and email systems. |
Subcontrol: | 7.4 |
Label: | Maintain and Enforce Network-Based URL Filters |
Description: | Enforce network-based URL filters that limit a system's ability to connect to websites not approved by the organization. This filtering shall be enforced for each of the organization's systems, whether they are physically at an organization's facilities or not. |
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior through their interaction with web browsers and email systems. |
Subcontrol: | 7.6 |
Label: | Log all URL Requests |
Description: | Log all URL requests from each of the organization's systems, whether on-site or a mobile device, in order to identify potentially malicious activity and assist incident handlers with identifying potentially compromised systems. |
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior through their interaction with web browsers and email systems. |
Subcontrol: | 7.7 |
Label: | Use of DNS Filtering Services |
Description: | Use DNS filtering services to help block access to known malicious domains. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior though their interaction with web browsers and email systems. |
This policy setting controls detection and action for Potentially Unwanted Applications (PUA), which are sneaky unwanted application bundlers or their bundled applications, that can deliver adware or malware.
The recommended state for this setting is: Enabled: Block .
For more information, see this link: Block potentially unwanted applications with Windows Defender Antivirus | Microsoft Docs
Potentially unwanted applications can increase the risk of your network being infected with malware, cause malware infections to be harder to identify, and can waste IT resources in cleaning up the applications. They should be blocked from installation.
To establish the recommended configuration via GP, set the following UI path to Enabled: Block :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Defender Antivirus\Configure detection for potentially unwanted applications
Note: This Group Policy path is provided by the Group Policy template WindowsDefender.admx/adml that is included with the Microsoft Windows 10 Release 1809 & Server 2019 Administrative Templates (or newer).
Impact:
Applications that are identified by Microsoft as PUA will be blocked at download and install time.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.14_L1_Ensure_Configure_detection_for_potentially_unwanted_applications_is_set_to_Enabled_Block" role="full" severity="unknown" time="2020-04-22T15:48:31.618-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/2/subcontrol/7" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817393" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'PUAProtection' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817393" result="true" testref="oval:org.cisecurity.benchmarks:tst:817393" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817393"> <cis:evidence_item itemref="1017"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender"/> <cis:evidence_item_pk_field name="name" value="PUAProtection"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173931" value-id="xccdf_org.cisecurity.benchmarks_value_817393_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173932" value-id="xccdf_org.cisecurity.benchmarks_value_817393_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817393"/> </check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.1 |
Label: | Utilize Centrally Managed Anti-malware Software |
Description: | Utilize centrally managed anti-malware software to continuously monitor and defend each of the organization's workstations and servers. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.2 |
Label: | Ensure Anti-Malware Software and Signatures are Updated |
Description: | Ensure that the organization's anti-malware software updates its scanning engine and signature database on a regular basis. |
CIS Control Information | |
---|---|
Control: | Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that all unauthorized and unmanaged software is found and prevented from installation or execution. |
Subcontrol: | 2.7 |
Label: | Utilize Application Whitelisting |
Description: | Utilize application whitelisting technology on all assets to ensure that only authorized software executes and all unauthorized software is blocked from executing on assets. |
This policy setting turns off Windows Defender Antivirus. If the setting is configured to Disabled, Windows Defender Antivirus runs and computers are scanned for malware and other potentially unwanted software.
The recommended state for this setting is: Disabled .
It is important to ensure a current, updated antivirus product is scanning each computer for malicious file activity. Microsoft provides a competent solution out of the box in Windows Defender Antivirus.
Organizations that choose to purchase a reputable 3rd-party antivirus solution may choose to exempt themselves from this recommendation in lieu of the commercial alternative.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Defender Antivirus\Turn off Windows Defender AntiVirus
Note: This Group Policy path is provided by the Group Policy template WindowsDefender.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Turn off Windows Defender , but it was renamed starting with the Windows 10 Release 1703 Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.77.15_L1_Ensure_Turn_off_Windows_Defender_AntiVirus_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:31.680-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36082-6</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:31.680-05:00" start-time="2020-04-22T15:48:31.618-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableAntiSpyware' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817386" result="true" testref="oval:org.cisecurity.benchmarks:tst:817386" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817386"> <cis:evidence_item itemref="1018"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender"/> <cis:evidence_item_pk_field name="name" value="DisableAntiSpyware"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173861" value-id="xccdf_org.cisecurity.benchmarks_value_817386_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173862" value-id="xccdf_org.cisecurity.benchmarks_value_817386_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817386"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36082-6 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.1 |
Label: | Utilize Centrally Managed Anti-malware Software |
Description: | Utilize centrally managed anti-malware software to continuously monitor and defend each of the organization's workstations and servers. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.2 |
Label: | Ensure Anti-Malware Software and Signatures are Updated |
Description: | Ensure that the organization's anti-malware software updates its scanning engine and signature database on a regular basis. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.1 |
Label: | Deploy Automated Endpoint Protection Tools |
Description: | Employ automated tools to continuously monitor workstations, servers, and mobile devices with anti-virus, anti-spyware, personal firewalls, and host-based IPS functionality. All malware detection events should be sent to enterprise anti-malware administration tools and event log servers. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template AppHVSI.admx/adml that is included with the Microsoft Windows 10 Release 1703 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template ExploitGuard.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
This section contains Windows Defender SmartScreen settings.
This Group Policy section is provided by the Group Policy template SmartScreen.admx/adml that is included with the Microsoft Windows 10 Release 1703 Administrative Templates (or newer).
This section contains recommendations for Explorer-related Windows Defender SmartScreen settings.
The Group Policy settings contained within this section are provided by the Group Policy template WindowsExplorer.admx/adml that is included with the Microsoft Windows 10 Release 1703 Administrative Templates (or newer).
This policy setting allows you to manage the behavior of Windows SmartScreen. Windows SmartScreen helps keep PCs safer by warning users before running unrecognized programs downloaded from the Internet. Some information is sent to Microsoft about files and programs run on PCs with this feature enabled.
The recommended state for this setting is: Enabled: Warn and prevent bypass .
Windows SmartScreen helps keep PCs safer by warning users before running unrecognized programs downloaded from the Internet. However, due to the fact that some information is sent to Microsoft about files and programs run on PCs some organizations may prefer to disable it.
To establish the recommended configuration via GP, set the following UI path to Enabled: Warn and prevent bypass :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Defender SmartScreen\Explorer\Configure Windows Defender SmartScreen
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsExplorer.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Configure Windows SmartScreen , but it was renamed starting with the Windows 10 Release 1703 Administrative Templates.
Impact:
Users will be warned before they are allowed to run unrecognized programs downloaded from the Internet.
All of the following tests or sub-groups must pass: | ||||||||||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.80.1.1_L1_Ensure_Configure_Windows_Defender_SmartScreen_is_set_to_Enabled_Warn_and_prevent_bypass" role="full" severity="unknown" time="2020-04-22T15:48:32.164-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/2" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/2/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/2/subcontrol/7" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/7/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/7/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-35859-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.164-05:00" start-time="2020-04-22T15:48:32.024-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableSmartScreen' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817476" result="true" testref="oval:org.cisecurity.benchmarks:tst:817476" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817476"> <cis:evidence_item itemref="1024"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\System"/> <cis:evidence_item_pk_field name="name" value="EnableSmartScreen"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ShellSmartScreenLevel' is 'Windows: Registry Value' to 'Block'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817480" result="true" testref="oval:org.cisecurity.benchmarks:tst:817480" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817480"> <cis:evidence_item itemref="1025"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\System"/> <cis:evidence_item_pk_field name="name" value="ShellSmartScreenLevel"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="Block" dt="string" ev="Block" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174801" value-id="xccdf_org.cisecurity.benchmarks_value_817480_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174802" value-id="xccdf_org.cisecurity.benchmarks_value_817480_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817480"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174761" value-id="xccdf_org.cisecurity.benchmarks_value_817476_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174762" value-id="xccdf_org.cisecurity.benchmarks_value_817476_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817476"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-35859-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that all unauthorized and unmanaged software is found and prevented from installation or execution. |
Subcontrol: | 2.6 |
Label: | Address unapproved software |
Description: | Ensure that unauthorized software is either removed or the inventory is updated in a timely manner |
CIS Control Information | |
---|---|
Control: | Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that all unauthorized and unmanaged software is found and prevented from installation or execution. |
Subcontrol: | 2.7 |
Label: | Utilize Application Whitelisting |
Description: | Utilize application whitelisting technology on all assets to ensure that only authorized software executes and all unauthorized software is blocked from executing on assets. |
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior through their interaction with web browsers and email systems. |
Subcontrol: | 7.2 |
Label: | Disable Unnecessary or Unauthorized Browser or Email Client Plugins |
Description: | Uninstall or disable any unauthorized browser or email client plugins or add-on applications. |
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior through their interaction with web browsers and email systems. |
Subcontrol: | 7.3 |
Label: | Limit Use of Scripting Languages in Web Browsers and Email Clients |
Description: | Ensure that only authorized scripting languages are able to run in all web browsers and email clients. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that unauthorized and unmanaged software is found and prevented from installation or execution. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template ErrorReporting.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template GameDVR.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Passport.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
Note: This section was initially named Microsoft Passport for Work but was renamed by Microsoft to Windows Hello for Business starting with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates.
This section contains recommendations related to the Windows Ink Workspace.
This Group Policy section is provided by the Group Policy template WindowsInkWorkspace.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This policy setting determines whether Windows Ink items are allowed above the lock screen.
The recommended state for this setting is: Enabled: On, but disallow access above lock OR Disabled .
Allowing any apps to be accessed while system is locked is not recommended. If this feature is permitted, it should only be accessible once a user authenticates with the proper credentials.
To establish the recommended configuration via GP, set the following UI path to Enabled: On, but disallow access above lock OR Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Ink Workspace\Allow Windows Ink Workspace
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsInkWorkspace.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
Impact:
Windows Ink Workspace will not be permitted above the lock screen.
Any of the following tests or sub-groups may pass: | ||||||||||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.84.2_L1_Ensure_Allow_Windows_Ink_Workspace_is_set_to_Enabled_On_but_disallow_access_above_lock_OR_Disabled_but_not_Enabled_On" role="full" severity="unknown" time="2020-04-22T15:48:32.242-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.242-05:00" start-time="2020-04-22T15:48:32.164-05:00"> <cis:or> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowWindowsInkWorkspace' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817391" result="true" testref="oval:org.cisecurity.benchmarks:tst:817391" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817391"> <cis:evidence_item itemref="1026"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\WindowsInkWorkspace"/> <cis:evidence_item_pk_field name="name" value="AllowWindowsInkWorkspace"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowWindowsInkWorkspace' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817387" result="false" testref="oval:org.cisecurity.benchmarks:tst:817387" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817387"> <cis:evidence_item itemref="1027"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\WindowsInkWorkspace"/> <cis:evidence_item_pk_field name="name" value="AllowWindowsInkWorkspace"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="1" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:or> </cis:evidence> </metadata> <complex-check operator="OR"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173871" value-id="xccdf_org.cisecurity.benchmarks_value_817387_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173872" value-id="xccdf_org.cisecurity.benchmarks_value_817387_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817387"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173911" value-id="xccdf_org.cisecurity.benchmarks_value_817391_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173912" value-id="xccdf_org.cisecurity.benchmarks_value_817391_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817391"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This section contains recommendations related to Windows Installer.
This Group Policy section is provided by the Group Policy template MSI.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This setting controls whether users are permitted to change installation options that typically are available only to system administrators. The security features of Windows Installer normally prevent users from changing installation options that are typically reserved for system administrators, such as specifying the directory to which files are installed. If Windows Installer detects that an installation package has permitted the user to change a protected option, it stops the installation and displays a message. These security features operate only when the installation program is running in a privileged security context in which it has access to directories denied to the user.
The recommended state for this setting is: Disabled .
In an enterprise managed environment, only IT staff with administrative rights should be installing or changing software on a system. Allowing users the ability to have any control over installs can risk unapproved software from being installed or removed from a system, which could cause the system to become vulnerable to compromise.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Installer\Allow user control over installs
Note: This Group Policy path is provided by the Group Policy template MSI.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was named Enable user control over installs , but it was renamed starting with the Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.85.1_L1_Ensure_Allow_user_control_over_installs_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:32.305-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36400-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.305-05:00" start-time="2020-04-22T15:48:32.242-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableUserControl' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817410" result="true" testref="oval:org.cisecurity.benchmarks:tst:817410" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817410"> <cis:evidence_item itemref="1028"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\Installer"/> <cis:evidence_item_pk_field name="name" value="EnableUserControl"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174101" value-id="xccdf_org.cisecurity.benchmarks_value_817410_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174102" value-id="xccdf_org.cisecurity.benchmarks_value_817410_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817410"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36400-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This setting controls whether or not Windows Installer should use system permissions when it installs any program on the system.
Note: This setting appears both in the Computer Configuration and User Configuration folders. To make this setting effective, you must enable the setting in both folders.
Caution: If enabled, skilled users can take advantage of the permissions this setting grants to change their privileges and gain permanent access to restricted files and folders. Note that the User Configuration version of this setting is not guaranteed to be secure.
The recommended state for this setting is: Disabled .
Users with limited privileges can exploit this feature by creating a Windows Installer installation package that creates a new local account that belongs to the local built-in Administrators group, adds their current account to the local built-in Administrators group, installs malicious software, or performs other unauthorized activities.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Installer\Always install with elevated privileges
Note: This Group Policy path is provided by the Group Policy template MSI.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.85.2_L1_Ensure_Always_install_with_elevated_privileges_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:32.383-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36919-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.383-05:00" start-time="2020-04-22T15:48:32.305-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AlwaysInstallElevated' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817421" result="true" testref="oval:org.cisecurity.benchmarks:tst:817421" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817421"> <cis:evidence_item itemref="1029"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\Installer"/> <cis:evidence_item_pk_field name="name" value="AlwaysInstallElevated"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174211" value-id="xccdf_org.cisecurity.benchmarks_value_817421_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174212" value-id="xccdf_org.cisecurity.benchmarks_value_817421_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817421"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36919-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This section contains recommendations related to Windows Logon Options.
This Group Policy section is provided by the Group Policy template WinLogon.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting controls whether a device will automatically sign-in the last interactive user after Windows Update restarts the system.
The recommended state for this setting is: Disabled .
Disabling this feature will prevent the caching of user's credentials and unauthorized use of the device, and also ensure the user is aware of the restart.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Logon Options\Sign-in and lock last interactive user automatically after a restart
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WinLogon.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Sign-in last interactive user automatically after a system-initiated restart , but it was renamed starting with the Windows 10 Release 1903 Administrative Templates.
Impact:
The device does not store the user's credentials for automatic sign-in after a Windows Update restart. The users' lock screen apps are not restarted after the system restarts. The user is required to present the logon credentials in order to proceed after restart.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.86.1_L1_Ensure_Sign-in_and_lock_last_interactive_user_automatically_after_a_restart_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:32.446-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36977-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.446-05:00" start-time="2020-04-22T15:48:32.383-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableAutomaticRestartSignOn' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817390" result="true" testref="oval:org.cisecurity.benchmarks:tst:817390" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817390"> <cis:evidence_item itemref="1030"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Microsoft\Windows\CurrentVersion\policies\system"/> <cis:evidence_item_pk_field name="name" value="DisableAutomaticRestartSignOn"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173901" value-id="xccdf_org.cisecurity.benchmarks_value_817390_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173902" value-id="xccdf_org.cisecurity.benchmarks_value_817390_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817390"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36977-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsMail.admx/adml that is only included with the Microsoft Windows Vista through the Windows 10 Release 1703 Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template MediaCenter.admx/adml that is only included with the Microsoft Windows Vista through Windows 10 Release 1511 Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsMediaDRM.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsMediaPlayer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsCollaboration.admx/adml that is only included with the Microsoft Windows Vista and Server 2008 (non-R2) Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsMessenger.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template MobilePCMobilityCenter.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template MovieMaker.admx/adml that is only included with the Microsoft Windows Vista and Server 2008 (non-R2) Administrative Templates.
This section contains recommendations related to Windows PowerShell.
This Group Policy section is provided by the Group Policy template PowerShellExecutionPolicy.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This policy setting enables logging of all PowerShell script input to the Microsoft-Windows-PowerShell/Operational event log.
The recommended state for this setting is: Disabled .
Note: In Microsoft's own hardening guidance, they recommend the opposite value, Enabled , because having this data logged improves investigations of PowerShell attack incidents. However, the default ACL on the PowerShell Operational log allows Interactive User (i.e. any logged on user) to read it, and therefore possibly expose passwords or other sensitive information to unauthorized users. If Microsoft locks down the default ACL on that log in the future (e.g. to restrict it only to Administrators), then we will revisit this recommendation in a future release.
There are potential risks of capturing passwords in the PowerShell logs. This setting should only be needed for debugging purposes, and not in normal operation, it is important to ensure this is set to Disabled .
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows PowerShell\Turn on PowerShell Script Block Logging
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template PowerShellExecutionPolicy.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
Impact:
Logging of PowerShell script input is disabled.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.95.1_L1_Ensure_Turn_on_PowerShell_Script_Block_Logging_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:32.524-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.524-05:00" start-time="2020-04-22T15:48:32.446-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableScriptBlockLogging' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817401" result="true" testref="oval:org.cisecurity.benchmarks:tst:817401" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817401"> <cis:evidence_item itemref="1031"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging"/> <cis:evidence_item_pk_field name="name" value="EnableScriptBlockLogging"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174011" value-id="xccdf_org.cisecurity.benchmarks_value_817401_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174012" value-id="xccdf_org.cisecurity.benchmarks_value_817401_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817401"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Automatically Log Off Users After Standard Period Of Inactivity |
Description: | Regularly monitor the use of all accounts, automatically logging off users after a standard period of inactivity. |
This Policy setting lets you capture the input and output of Windows PowerShell commands into text-based transcripts.
The recommended state for this setting is: Disabled .
If this setting is enabled there is a risk that passwords could get stored in plain text in the PowerShell_transcript output file.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows PowerShell\Turn on PowerShell Transcription
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template PowerShellExecutionPolicy.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.95.2_L1_Ensure_Turn_on_PowerShell_Transcription_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:32.602-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.602-05:00" start-time="2020-04-22T15:48:32.524-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'EnableTranscripting' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817408" result="true" testref="oval:org.cisecurity.benchmarks:tst:817408" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817408"> <cis:evidence_item itemref="1032"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\PowerShell\Transcription"/> <cis:evidence_item_pk_field name="name" value="EnableTranscripting"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174081" value-id="xccdf_org.cisecurity.benchmarks_value_817408_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174082" value-id="xccdf_org.cisecurity.benchmarks_value_817408_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817408"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Automatically Log Off Users After Standard Period Of Inactivity |
Description: | Regularly monitor the use of all accounts, automatically logging off users after a standard period of inactivity. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template RacWmiProv.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section contains recommendations related to Windows Remote Management (WinRM).
This Group Policy section is provided by the Group Policy template WindowsRemoteManagement.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to the Windows Remote Management (WinRM) client.
This Group Policy section is provided by the Group Policy template WindowsRemoteManagement.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting allows you to manage whether the Windows Remote Management (WinRM) client uses Basic authentication.
The recommended state for this setting is: Disabled .
Basic authentication is less robust than other authentication methods available in WinRM because credentials including passwords are transmitted in plain text. An attacker who is able to capture packets on the network where WinRM is running may be able to determine the credentials used for accessing remote hosts via WinRM.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Client\Allow Basic authentication
Note: This Group Policy path is provided by the Group Policy template WindowsRemoteManagement.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.1_L1_Ensure_Allow_Basic_authentication_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:32.664-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36310-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.664-05:00" start-time="2020-04-22T15:48:32.602-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowBasic' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817497" result="true" testref="oval:org.cisecurity.benchmarks:tst:817497" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817497"> <cis:evidence_item itemref="1033"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\WinRM\Client"/> <cis:evidence_item_pk_field name="name" value="AllowBasic"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174971" value-id="xccdf_org.cisecurity.benchmarks_value_817497_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174972" value-id="xccdf_org.cisecurity.benchmarks_value_817497_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817497"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36310-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.4 |
Label: | Encrypt All Sensitive Information in Transit |
Description: | Encrypt all sensitive information in transit. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.13 |
Label: | User/Account Authentication Must Be Performed Over Encrypted Channels |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
This policy setting allows you to manage whether the Windows Remote Management (WinRM) client sends and receives unencrypted messages over the network.
The recommended state for this setting is: Disabled .
Encrypting WinRM network traffic reduces the risk of an attacker viewing or modifying WinRM messages as they transit the network.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Client\Allow unencrypted traffic
Note: This Group Policy path is provided by the Group Policy template WindowsRemoteManagement.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.2_L1_Ensure_Allow_unencrypted_traffic_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:32.742-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37726-7</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.742-05:00" start-time="2020-04-22T15:48:32.680-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowUnencryptedTraffic' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817517" result="true" testref="oval:org.cisecurity.benchmarks:tst:817517" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817517"> <cis:evidence_item itemref="1034"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\WinRM\Client"/> <cis:evidence_item_pk_field name="name" value="AllowUnencryptedTraffic"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175171" value-id="xccdf_org.cisecurity.benchmarks_value_817517_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175172" value-id="xccdf_org.cisecurity.benchmarks_value_817517_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817517"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37726-7 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.4 |
Label: | Encrypt All Sensitive Information in Transit |
Description: | Encrypt all sensitive information in transit. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.13 |
Label: | User/Account Authentication Must Be Performed Over Encrypted Channels |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
This policy setting allows you to manage whether the Windows Remote Management (WinRM) client will not use Digest authentication.
The recommended state for this setting is: Enabled .
Digest authentication is less robust than other authentication methods available in WinRM, an attacker who is able to capture packets on the network where WinRM is running may be able to determine the credentials used for accessing remote hosts via WinRM.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Client\Disallow Digest authentication
Note: This Group Policy path is provided by the Group Policy template WindowsRemoteManagement.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
The WinRM client will not use Digest authentication.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.1.3_L1_Ensure_Disallow_Digest_authentication_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:32.805-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38318-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.805-05:00" start-time="2020-04-22T15:48:32.742-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowDigest' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817532" result="true" testref="oval:org.cisecurity.benchmarks:tst:817532" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817532"> <cis:evidence_item itemref="1035"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\WinRM\Client"/> <cis:evidence_item_pk_field name="name" value="AllowDigest"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175321" value-id="xccdf_org.cisecurity.benchmarks_value_817532_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175322" value-id="xccdf_org.cisecurity.benchmarks_value_817532_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817532"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38318-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.4 |
Label: | Encrypt All Sensitive Information in Transit |
Description: | Encrypt all sensitive information in transit. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.13 |
Label: | User/Account Authentication Must Be Performed Over Encrypted Channels |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
This section contains recommendations related to the Windows Remote Management (WinRM) service.
This Group Policy section is provided by the Group Policy template WindowsRemoteManagement.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting allows you to manage whether the Windows Remote Management (WinRM) service accepts Basic authentication from a remote client.
The recommended state for this setting is: Disabled .
Basic authentication is less robust than other authentication methods available in WinRM because credentials including passwords are transmitted in plain text. An attacker who is able to capture packets on the network where WinRM is running may be able to determine the credentials used for accessing remote hosts via WinRM.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Service\Allow Basic authentication
Note: This Group Policy path is provided by the Group Policy template WindowsRemoteManagement.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.1_L1_Ensure_Allow_Basic_authentication_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:32.883-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36254-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.883-05:00" start-time="2020-04-22T15:48:32.821-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowBasic' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817474" result="true" testref="oval:org.cisecurity.benchmarks:tst:817474" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817474"> <cis:evidence_item itemref="1036"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\WinRM\Service"/> <cis:evidence_item_pk_field name="name" value="AllowBasic"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174741" value-id="xccdf_org.cisecurity.benchmarks_value_817474_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174742" value-id="xccdf_org.cisecurity.benchmarks_value_817474_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817474"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36254-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.4 |
Label: | Encrypt All Sensitive Information in Transit |
Description: | Encrypt all sensitive information in transit. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.13 |
Label: | User/Account Authentication Must Be Performed Over Encrypted Channels |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
This policy setting allows you to manage whether the Windows Remote Management (WinRM) service sends and receives unencrypted messages over the network.
The recommended state for this setting is: Disabled .
Encrypting WinRM network traffic reduces the risk of an attacker viewing or modifying WinRM messages as they transit the network.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Service\Allow unencrypted traffic
Note: This Group Policy path is provided by the Group Policy template WindowsRemoteManagement.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.3_L1_Ensure_Allow_unencrypted_traffic_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:32.946-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38223-4</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:32.946-05:00" start-time="2020-04-22T15:48:32.883-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AllowUnencryptedTraffic' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817492" result="true" testref="oval:org.cisecurity.benchmarks:tst:817492" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817492"> <cis:evidence_item itemref="1037"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\WinRM\Service"/> <cis:evidence_item_pk_field name="name" value="AllowUnencryptedTraffic"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174921" value-id="xccdf_org.cisecurity.benchmarks_value_817492_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174922" value-id="xccdf_org.cisecurity.benchmarks_value_817492_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817492"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38223-4 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Encrypt Transmittal of Username and Authentication Credentials |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.4 |
Label: | Encrypt All Sensitive Information in Transit |
Description: | Encrypt all sensitive information in transit. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.13 |
Label: | User/Account Authentication Must Be Performed Over Encrypted Channels |
Description: | Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels. |
This policy setting allows you to manage whether the Windows Remote Management (WinRM) service will allow RunAs credentials to be stored for any plug-ins.
The recommended state for this setting is: Enabled .
Note: If you enable and then disable this policy setting, any values that were previously configured for RunAsPassword will need to be reset.
Although the ability to store RunAs credentials is a convenient feature it increases the risk of account compromise slightly. For example, if you forget to lock your desktop before leaving it unattended for a few minutes another person could access not only the desktop of your computer but also any hosts you manage via WinRM with cached RunAs credentials.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Service\Disallow WinRM from storing RunAs credentials
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsRemoteManagement.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
The WinRM service will not allow the RunAsUser or RunAsPassword configuration values to be set for any plug-ins. If a plug-in has already set the RunAsUser and RunAsPassword configuration values, the RunAsPassword configuration value will be erased from the credential store on the computer.
If this setting is later Disabled again, any values that were previously configured for RunAsPassword will need to be reset.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.97.2.4_L1_Ensure_Disallow_WinRM_from_storing_RunAs_credentials_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:33.024-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36000-8</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:33.024-05:00" start-time="2020-04-22T15:48:32.961-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableRunAs' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817503" result="true" testref="oval:org.cisecurity.benchmarks:tst:817503" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817503"> <cis:evidence_item itemref="1038"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\WinRM\Service"/> <cis:evidence_item_pk_field name="name" value="DisableRunAs"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175031" value-id="xccdf_org.cisecurity.benchmarks_value_817503_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175032" value-id="xccdf_org.cisecurity.benchmarks_value_817503_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817503"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36000-8 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.3 |
Label: | Disable Workstation to Workstation Communication |
Description: | Disable all workstation to workstation communication to limit an attacker's ability to move laterally and compromise neighboring systems, through technologies such as Private VLANs or microsegmentation. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.4 |
Label: | Automatically Log Off Users After Standard Period Of Inactivity |
Description: | Regularly monitor the use of all accounts, automatically logging off users after a standard period of inactivity. |
This section contains settings related to Windows Remote Shell (WinRS).
This Group Policy section is provided by the Group Policy template WindowsRemoteShell.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to the Windows Security Center console settings.
This Group Policy section is provided by the Group Policy template WindowsDefenderSecurityCenter.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
Note: This section was originally named Windows Defender Security Center but was renamed by Microsoft to Windows Security starting with the Microsoft Windows 10 Release 1809 & Server 2019 Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsDefenderSecurityCenter.admx/adml that is included with the Microsoft Windows 10 Release 1803 Administrative Templates (or newer).
This section contains App and browser protection settings.
This Group Policy section is provided by the Group Policy template WindowsDefenderSecurityCenter.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
This policy setting prevent users from making changes to the Exploit protection settings area in the Windows Security settings.
The recommended state for this setting is: Enabled .
Only authorized IT staff should be able to make changes to the exploit protection settings in order to ensure the organizations specific configuration is not modified.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Security\App and browser protection\Prevent users from modifying settings
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsDefenderSecurityCenter.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
Impact:
Local users cannot make changes in the Exploit protection settings area.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.99.2.1_L1_Ensure_Prevent_users_from_modifying_settings_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:33.086-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/8/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817475" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisallowExploitProtectionOverride' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817475" result="true" testref="oval:org.cisecurity.benchmarks:tst:817475" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817475"> <cis:evidence_item itemref="1039"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows Defender Security Center\App and Browser protection"/> <cis:evidence_item_pk_field name="name" value="DisallowExploitProtectionOverride"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174751" value-id="xccdf_org.cisecurity.benchmarks_value_817475_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174752" value-id="xccdf_org.cisecurity.benchmarks_value_817475_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817475"/> </check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.3 |
Label: | Enable Operating System Anti-Exploitation Features/ Deploy Anti-Exploit Technologies |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP) or Address Space Layout Randomization (ASLR) that are available in an operating system or deploy appropriate toolkits that can be configured to apply protection to a broader set of applications and executables. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.4 |
Label: | Enable Anti-exploitation Features (i.e. DEP, ASLR, EMET) |
Description: | Enable anti-exploitation features such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), virtualization/containerization, etc. For increased protection, deploy capabilities such as Enhanced Mitigation Experience Toolkit (EMET) that can be configured to apply these protections to a broader set of applications and executables. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template SideShow.admx/adml that is only included with the Microsoft Windows Vista Administrative Templates through Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template SystemResourceManager.admx/adml that is only included with the Microsoft Windows Vista through Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
This section contains recommendations related to Windows Update.
This Group Policy section is provided by the Group Policy template WindowsUpdate.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Windows Update for Business.
This Group Policy section is provided by the Group Policy template WindowsUpdate.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
Note: This section was initially named Defer Windows Updates but was renamed by Microsoft to Windows Update for Business starting with the Microsoft Windows 10 Release 1709 Administrative Templates.
This policy setting determines whether users can access the Windows Insider Program controls in Settings -> Update and Security. These controls enable users to make their devices available for downloading and installing preview (beta) builds of Windows software.
The recommended state for this setting is: Enabled: Disable preview builds .
It can be risky for experimental features to be allowed in an enterprise managed environment because this can introduce bugs and security holes into systems, making it easier for an attacker to gain access. It is generally preferred to only use production-ready builds.
To establish the recommended configuration via GP, set the following UI path to Enabled: Disable preview builds :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update\Windows Update for Business\Manage preview builds
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsUpdate.admx/adml that is included with the Microsoft Windows 10 Release 1709 Administrative Templates (or newer).
Impact:
Preview builds are prevented from installing on the device.
All of the following tests or sub-groups must pass: | ||||||||||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.1_L1_Ensure_Manage_preview_builds_is_set_to_Enabled_Disable_preview_builds" role="full" severity="unknown" time="2020-04-22T15:48:27.711-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/2/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/2/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:27.711-05:00" start-time="2020-04-22T15:48:27.571-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ManagePreviewBuilds' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817518" result="true" testref="oval:org.cisecurity.benchmarks:tst:817518" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817518"> <cis:evidence_item itemref="958"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate"/> <cis:evidence_item_pk_field name="name" value="ManagePreviewBuilds"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ManagePreviewBuildsPolicyValue' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817525" result="true" testref="oval:org.cisecurity.benchmarks:tst:817525" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817525"> <cis:evidence_item itemref="959"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate"/> <cis:evidence_item_pk_field name="name" value="ManagePreviewBuildsPolicyValue"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175181" value-id="xccdf_org.cisecurity.benchmarks_value_817518_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175182" value-id="xccdf_org.cisecurity.benchmarks_value_817518_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817518"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175251" value-id="xccdf_org.cisecurity.benchmarks_value_817525_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175252" value-id="xccdf_org.cisecurity.benchmarks_value_817525_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817525"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that all unauthorized and unmanaged software is found and prevented from installation or execution. |
Subcontrol: | 2.3 |
Label: | Utilize Software Inventory Tools |
Description: | Utilize software inventory tools throughout the organization to automate the documentation of all software on business systems. |
CIS Control Information | |
---|---|
Control: | Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that all unauthorized and unmanaged software is found and prevented from installation or execution. |
Subcontrol: | 2.6 |
Label: | Address unapproved software |
Description: | Ensure that unauthorized software is either removed or the inventory is updated in a timely manner |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
This policy setting determines the level of Preview Build or Feature Updates to receive, and when.
The Windows readiness level for each new Windows 10 Feature Update is classified in one of 5 categories, depending on your organizations level of comfort with receiving them:
Preview Build - Fast: Devices set to this level will be the first to receive new builds of Windows with features not yet available to the general public. Select Fast to participate in identifying and reporting issues to Microsoft, and provide suggestions on new functionality.
Preview Build - Slow: Devices set to this level receive new builds of Windows before they are available to the general public, but at a slower cadence than those set to Fast, and with changes and fixes identified in earlier builds.
Release Preview: Receive builds of Windows just before Microsoft releases them to the general public.
Semi-Annual Channel (Targeted): Receive feature updates when they are released to the general public.
Semi-Annual Channel: Feature updates will arrive when they are declared Semi-Annual Channel. This usually occurs about 4 months after Semi-Annual Channel (Targeted), indicating that Microsoft, Independent Software Vendors (ISVs), partners and customer believe that the release is ready for broad deployment.
The recommended state for this setting is: Enabled: Semi-Annual Channel, 180 or more days .
Note: If the "Allow Telemetry" policy is set to 0, this policy will have no effect.
Note #2: Starting with Windows Server 2016 RTM (Release 1607), Microsoft introduced a new Windows Update (WU) client behavior called Dual Scan , with an eye to cloud-based update management. In some cases, this Dual Scan feature can interfere with Windows Updates from Windows Server Update Services (WSUS) and/or manual WU updates. If you are using WSUS in your environment, you may need to set the above setting to Not Configured or configure the setting Do not allow update deferral policies to cause scans against Windows Update (added in the Windows 10 Release 1709 Administrative Templates) in order to prevent the Dual Scan feature from interfering. More information on Dual Scan is available at these links:
Note #3: Prior to Windows Server 2016 R1709, values above 180 days are not recognized by the OS. Starting with Windows Server 2016 R1709, the maximum number of days you can defer is 365 days.
Forcing new features without prior testing in your environment could cause software incompatibilities as well as introducing new bugs into the operating system. In an enterprise managed environment, it is generally preferred to delay Feature Updates until thorough testing and a deployment plan is in place. This recommendation delays the automatic installation of new features as long as possible.
To establish the recommended configuration via GP, set the following UI path to Enabled: Semi-Annual Channel, 180 or more days :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update\Windows Update for Business\Select when Preview Builds and Feature Updates are received
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WindowsUpdate.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named Select when Feature Updates are received , but it was renamed to Select when Preview Builds and Feature Updates are received starting with the Windows 10 Release 1709 Administrative Templates.
Impact:
Feature Updates will be delayed until 180 or more days after they are declared to have a Windows readiness level of "Semi-Annual Channel".
All of the following tests or sub-groups must pass: | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.2_L1_Ensure_Select_when_Preview_Builds_and_Feature_Updates_are_received_is_set_to_Enabled_Semi-Annual_Channel_180_or_more_days" role="full" severity="unknown" time="2020-04-22T15:48:27.946-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/3" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:27.946-05:00" start-time="2020-04-22T15:48:27.711-05:00"> <cis:and> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DeferFeatureUpdates' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817498" result="true" testref="oval:org.cisecurity.benchmarks:tst:817498" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817498"> <cis:evidence_item itemref="960"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate"/> <cis:evidence_item_pk_field name="name" value="DeferFeatureUpdates"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'BranchReadinessLevel' is 'Windows: Registry Value' to '32'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817509" result="true" testref="oval:org.cisecurity.benchmarks:tst:817509" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817509"> <cis:evidence_item itemref="961"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate"/> <cis:evidence_item_pk_field name="name" value="BranchReadinessLevel"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="32" dt="int" ev="32" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DeferFeatureUpdatesPeriodInDays' is 'Windows: Registry Value' to '180'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817505" result="true" testref="oval:org.cisecurity.benchmarks:tst:817505" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817505"> <cis:evidence_item itemref="962"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate"/> <cis:evidence_item_pk_field name="name" value="DeferFeatureUpdatesPeriodInDays"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="180" dt="int" ev="180" name="value" op="greater than or equal" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <xccdf:complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174981" value-id="xccdf_org.cisecurity.benchmarks_value_817498_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174982" value-id="xccdf_org.cisecurity.benchmarks_value_817498_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817498"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175091" value-id="xccdf_org.cisecurity.benchmarks_value_817509_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175092" value-id="xccdf_org.cisecurity.benchmarks_value_817509_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817509"/> </check> </xccdf:complex-check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175051" value-id="xccdf_org.cisecurity.benchmarks_value_817505_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8175052" value-id="xccdf_org.cisecurity.benchmarks_value_817505_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817505"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
This settings controls when Quality Updates are received.
The recommended state for this setting is: Enabled: 0 days .
Note: If the "Allow Telemetry" policy is set to 0, this policy will have no effect.
Note #2: Starting with Windows Server 2016 RTM (Release 1607), Microsoft introduced a new Windows Update (WU) client behavior called Dual Scan , with an eye to cloud-based update management. In some cases, this Dual Scan feature can interfere with Windows Updates from Windows Server Update Services (WSUS) and/or manual WU updates. If you are using WSUS in your environment, you may need to set the above setting to Not Configured or configure the setting Do not allow update deferral policies to cause scans against Windows Update (added in the Windows 10 Release 1709 Administrative Templates) in order to prevent the Dual Scan feature from interfering. More information on Dual Scan is available at these links:
Quality Updates can contain important bug fixes and/or security patches, and should be installed as soon as possible.
To establish the recommended configuration via GP, set the following UI path to Enabled:0 days :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update\Windows Update for Business\Select when Quality Updates are received
Note: This Group Policy path does not exist by default. An updated Group Policy template ( WindowsUpdate.admx/adml ) is required - it is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
Impact:
None - this is the default behavior.
All of the following tests or sub-groups must pass: | ||||||||||||||||||||||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.1.3_L1_Ensure_Select_when_Quality_Updates_are_received_is_set_to_Enabled_0_days" role="full" severity="unknown" time="2020-04-22T15:48:28.086-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/4/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/3/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/3/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.086-05:00" start-time="2020-04-22T15:48:27.946-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DeferQualityUpdatesPeriodInDays' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817490" result="true" testref="oval:org.cisecurity.benchmarks:tst:817490" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817490"> <cis:evidence_item itemref="963"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate"/> <cis:evidence_item_pk_field name="name" value="DeferQualityUpdatesPeriodInDays"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DeferQualityUpdates' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817485" result="true" testref="oval:org.cisecurity.benchmarks:tst:817485" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817485"> <cis:evidence_item itemref="964"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate"/> <cis:evidence_item_pk_field name="name" value="DeferQualityUpdates"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174851" value-id="xccdf_org.cisecurity.benchmarks_value_817485_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174852" value-id="xccdf_org.cisecurity.benchmarks_value_817485_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817485"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174901" value-id="xccdf_org.cisecurity.benchmarks_value_817490_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174902" value-id="xccdf_org.cisecurity.benchmarks_value_817490_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817490"/> </check> </complex-check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 3.4 |
Label: | Deploy Automated Operating System Patch Management Tools |
Description: | Deploy automated software update tools in order to ensure that the operating systems are running the most recent security updates provided by the software vendor. |
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 3.5 |
Label: | Deploy Automated Software Patch Management Tools |
Description: | Deploy automated software update tools in order to ensure that third-party software on all systems is running the most recent security updates provided by the software vendor. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 4.5 |
Label: | Use Automated Patch Management And Software Update Tools |
Description: | Deploy automated patch management tools and software update tools for operating system and software/applications on all systems for which such tools are available and safe. Patches should be applied to all systems, even systems that are properly air gapped. |
This policy setting specifies whether computers in your environment will receive security updates from Windows Update or WSUS. If you configure this policy setting to Enabled, the operating system will recognize when a network connection is available and then use the network connection to search Windows Update or your designated intranet site for updates that apply to them.
After you configure this policy setting to Enabled, select one of the following three options in the Configure Automatic Updates Properties dialog box to specify how the service will work:
The recommended state for this setting is: Enabled .
Note: The sub-setting " Configure automatic updating: " has 4 possible values – all of them are valid depending on specific organizational needs, however if feasible we suggest using a value of 4 - Auto download and schedule the install . This suggestion is not a scored requirement.
Note #2: Organizations that utilize a 3rd-party solution for patching may choose to exempt themselves from this recommendation, and instead configure it to Disabled so that the native Windows Update mechanism does not interfere with the 3rd-party patching process.
Although each version of Windows is thoroughly tested before release, it is possible that problems will be discovered after the products are shipped. The Configure Automatic Updates setting can help you ensure that the computers in your environment will always have the most recent critical operating system updates and service packs installed.
To establish the recommended configuration via GP, set the following UI path to Enabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update\Configure Automatic Updates
Note: This Group Policy path is provided by the Group Policy template WindowsUpdate.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
Critical operating system updates and service packs will be installed as necessary.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.2_L1_Ensure_Configure_Automatic_Updates_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:28.164-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/4/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/3/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/3/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36172-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.164-05:00" start-time="2020-04-22T15:48:28.086-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoAutoUpdate' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817405" result="true" testref="oval:org.cisecurity.benchmarks:tst:817405" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817405"> <cis:evidence_item itemref="965"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\WindowsUpdate\AU"/> <cis:evidence_item_pk_field name="name" value="NoAutoUpdate"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174051" value-id="xccdf_org.cisecurity.benchmarks_value_817405_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174052" value-id="xccdf_org.cisecurity.benchmarks_value_817405_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817405"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36172-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 3.4 |
Label: | Deploy Automated Operating System Patch Management Tools |
Description: | Deploy automated software update tools in order to ensure that the operating systems are running the most recent security updates provided by the software vendor. |
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 3.5 |
Label: | Deploy Automated Software Patch Management Tools |
Description: | Deploy automated software update tools in order to ensure that third-party software on all systems is running the most recent security updates provided by the software vendor. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 4.5 |
Label: | Use Automated Patch Management And Software Update Tools |
Description: | Deploy automated patch management tools and software update tools for operating system and software/applications on all systems for which such tools are available and safe. Patches should be applied to all systems, even systems that are properly air gapped. |
This policy setting specifies when computers in your environment will receive security updates from Windows Update or WSUS.
The recommended state for this setting is: 0 - Every day .
Note: This setting is only applicable if 4 - Auto download and schedule the install is selected in Rule 18.9.102.2. It will have no impact if any other option is selected.
Although each version of Windows is thoroughly tested before release, it is possible that problems will be discovered after the products are shipped. The Configure Automatic Updates setting can help you ensure that the computers in your environment will always have the most recent critical operating system updates and service packs installed.
To establish the recommended configuration via GP, set the following UI path to 0 - Every day :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update\Configure Automatic Updates: Scheduled install day
Note: This Group Policy path is provided by the Group Policy template WindowsUpdate.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
If 4 - Auto download and schedule the install is selected in Rule 18.9.102.2, critical operating system updates and service packs will automatically download every day (at 3:00 A.M., by default).
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.3_L1_Ensure_Configure_Automatic_Updates_Scheduled_install_day_is_set_to_0_-_Every_day" role="full" severity="unknown" time="2020-04-22T15:48:28.243-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/4/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/3/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/3/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36172-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.243-05:00" start-time="2020-04-22T15:48:28.164-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ScheduledInstallDay' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817411" result="false" testref="oval:org.cisecurity.benchmarks:tst:817411" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817411"> <cis:evidence_item itemref="966"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\WindowsUpdate\AU"/> <cis:evidence_item_pk_field name="name" value="ScheduledInstallDay"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="4" dt="int" ev="0" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174111" value-id="xccdf_org.cisecurity.benchmarks_value_817411_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174112" value-id="xccdf_org.cisecurity.benchmarks_value_817411_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817411"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36172-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 3.4 |
Label: | Deploy Automated Operating System Patch Management Tools |
Description: | Deploy automated software update tools in order to ensure that the operating systems are running the most recent security updates provided by the software vendor. |
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 3.5 |
Label: | Deploy Automated Software Patch Management Tools |
Description: | Deploy automated software update tools in order to ensure that third-party software on all systems is running the most recent security updates provided by the software vendor. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 4.5 |
Label: | Use Automated Patch Management And Software Update Tools |
Description: | Deploy automated patch management tools and software update tools for operating system and software/applications on all systems for which such tools are available and safe. Patches should be applied to all systems, even systems that are properly air gapped. |
This policy setting specifies that Automatic Updates will wait for computers to be restarted by the users who are logged on to them to complete a scheduled installation.
The recommended state for this setting is: Disabled .
Note: This setting applies only when you configure Automatic Updates to perform scheduled update installations. If you configure the Configure Automatic Updates setting to Disabled, this setting has no effect.
Some security updates require that the computer be restarted to complete an installation. If the computer cannot restart automatically, then the most recent update will not completely install and no new updates will download to the computer until it is restarted. Without the auto-restart functionality, users who are not security-conscious may choose to indefinitely delay the restart, therefore keeping the computer in a less secure state.
To establish the recommended configuration via GP, set the following UI path to Disabled :
Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update\No auto-restart with logged on users for scheduled automatic updates installations
Note: This Group Policy path is provided by the Group Policy template WindowsUpdate.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named No auto-restart for scheduled Automatic Updates installations , but it was renamed starting with the Windows 7 & Server 2008 R2 Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_18.9.102.4_L1_Ensure_No_auto-restart_with_logged_on_users_for_scheduled_automatic_updates_installations_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:28.305-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/4/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/3/subcontrol/4" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/3/subcontrol/5" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37027-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:28.305-05:00" start-time="2020-04-22T15:48:28.243-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoAutoRebootWithLoggedOnUsers' is 'Windows: Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817434" result="true" testref="oval:org.cisecurity.benchmarks:tst:817434" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817434"> <cis:evidence_item itemref="967"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_LOCAL_MACHINE"/> <cis:evidence_item_pk_field name="key" value="Software\Policies\Microsoft\Windows\WindowsUpdate\AU"/> <cis:evidence_item_pk_field name="name" value="NoAutoRebootWithLoggedOnUsers"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174341" value-id="xccdf_org.cisecurity.benchmarks_value_817434_var1"/> <check-export export-name="oval:org.cisecurity.benchmarks:var:8174342" value-id="xccdf_org.cisecurity.benchmarks_value_817434_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817434"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37027-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 3.4 |
Label: | Deploy Automated Operating System Patch Management Tools |
Description: | Deploy automated software update tools in order to ensure that the operating systems are running the most recent security updates provided by the software vendor. |
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 3.5 |
Label: | Deploy Automated Software Patch Management Tools |
Description: | Deploy automated software update tools in order to ensure that third-party software on all systems is running the most recent security updates provided by the software vendor. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers. |
Subcontrol: | 4.5 |
Label: | Use Automated Patch Management And Software Update Tools |
Description: | Deploy automated patch management tools and software update tools for operating system and software/applications on all systems for which such tools are available and safe. Patches should be applied to all systems, even systems that are properly air gapped. |
This section contains user-based recommendations from Group Policy Administrative Templates (ADMX).
This section contains recommendations for Control Panel settings.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template AddRemovePrograms.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template ControlPanelDisplay.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for personalization settings.
This Group Policy section is provided by the Group Policy template ControlPanelDisplay.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note: This section was initially named Desktop Themes but was renamed by Microsoft to Personalization starting with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates.
This policy setting enables/disables the use of desktop screen savers.
The recommended state for this setting is: Enabled .
If a user forgets to lock their computer when they walk away, it is possible that a passerby will hijack it. Configuring a timed screen saver with password lock will help to protect against these hijacks.
To establish the recommended configuration via GP, set the following UI path to Enabled :
User Configuration\Policies\Administrative Templates\Control Panel\Personalization\Enable screen saver
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template ControlPanelDisplay.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
Impact:
A screen saver runs, provided that the following two conditions hold: First, a valid screen saver on the client is specified through the Force specific screen saver setting (Rule 19.1.3.2) or through Control Panel on the client computer. Second, the Screen saver timeout setting (Rule 19.1.3.4) is set to a nonzero value through the setting or through Control Panel.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.1_L1_Ensure_Enable_screen_saver_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:33.774-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37970-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817320" definition_negate="false"> <cis:and negated="false" result="false"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ScreenSaveActive' is 'Windows: Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817320" result="false" testref="oval:org.cisecurity.benchmarks:tst:817320" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817320"> <cis:evidence_item itemref="1042"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_USERS"/> <cis:evidence_item_pk_field name="key" value="S-1-5-21-3050897948-969533551-3432263440-500\Software\Policies\Microsoft\Windows\Control Panel\Desktop"/> <cis:evidence_item_pk_field name="name" value="ScreenSaveActive"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="case insensitive equals" result="true"/> <cis:evidence_field cv="0" dt="string" ev="1" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173202" value-id="xccdf_org.cisecurity.benchmarks_value_817320_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817320"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37970-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This policy setting specifies the screen saver for the user's desktop.
The recommended state for this setting is: Enabled: scrnsave.scr .
Note: If the specified screen saver is not installed on a computer to which this setting applies, the setting is ignored.
If a user forgets to lock their computer when they walk away, it is possible that a passerby will hijack it. Configuring a timed screen saver with password lock will help to protect against these hijacks.
To establish the recommended configuration via GP, set the following UI path to Enabled: scrnsave.scr :
User Configuration\Policies\Administrative Templates\Control Panel\Personalization\Force specific screen saver
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template ControlPanelDisplay.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
Impact:
The system displays the specified screen saver on the user's desktop. The drop-down list of screen savers in the Screen Saver dialog in the Personalization or Display Control Panel will be disabled, preventing users from changing the screen saver.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.2_L1_Ensure_Force_specific_screen_saver_Screen_saver_executable_name_is_set_to_Enabled_scrnsave.scr" role="full" severity="unknown" time="2020-04-22T15:48:33.836-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37907-3</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817324" definition_negate="false"> <cis:and negated="false" result="false"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'SCRNSAVE.EXE' is 'Windows: User Registry Value' to 'scrnsave.scr'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817324" result="false" testref="oval:org.cisecurity.benchmarks:tst:817324" type="registry_test"> <cis:evidence_object> <cis:evidence_item itemref="1044"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="hive" value="HKEY_USERS"/> <cis:evidence_item_pk_field name="key" value="S-1-5-21-3050897948-969533551-3432263440-500\Software\Policies\Microsoft\Windows\Control Panel\Desktop"/> <cis:evidence_item_pk_field name="name" value="SCRNSAVE.EXE"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173242" value-id="xccdf_org.cisecurity.benchmarks_value_817324_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817324"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37907-3 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This setting determines whether screen savers used on the computer are password protected.
The recommended state for this setting is: Enabled .
If a user forgets to lock their computer when they walk away, it is possible that a passerby will hijack it. Configuring a timed screen saver with password lock will help to protect against these hijacks.
To establish the recommended configuration via GP, set the following UI path to Enabled :
User Configuration\Policies\Administrative Templates\Control Panel\Personalization\Password protect the screen saver
Note: This Group Policy path is provided by the Group Policy template ControlPanelDisplay.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
All screen savers are password protected. The "Password protected" checkbox on the Screen Saver dialog in the Personalization or Display Control Panel will be disabled, preventing users from changing the password protection setting.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.3_L1_Ensure_Password_protect_the_screen_saver_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:33.914-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37658-2</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817331" definition_negate="false"> <cis:and negated="false" result="false"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ScreenSaverIsSecure' is 'Windows:User Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817331" result="false" testref="oval:org.cisecurity.benchmarks:tst:817331" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817331"> <cis:evidence_item itemref="1046"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_USERS"/> <cis:evidence_item_pk_field name="key" value="S-1-5-21-3050897948-969533551-3432263440-500\Software\Policies\Microsoft\Windows\Control Panel\Desktop"/> <cis:evidence_item_pk_field name="name" value="ScreenSaverIsSecure"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_sz" dt="string" ev="reg_sz" name="type" op="equals" result="true"/> <cis:evidence_field cv="0" dt="string" ev="1" name="value" op="equals" result="false"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173312" value-id="xccdf_org.cisecurity.benchmarks_value_817331_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817331"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37658-2 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This setting specifies how much user idle time must elapse before the screen saver is launched.
The recommended state for this setting is: Enabled: 900 seconds or fewer, but not 0 .
Note: This setting has no effect under the following circumstances:
If a user forgets to lock their computer when they walk away, it is possible that a passerby will hijack it. Configuring a timed screen saver with password lock will help to protect against these hijacks.
To establish the recommended configuration via GP, set the following UI path to Enabled: 900 or fewer, but not 0 :
User Configuration\Policies\Administrative Templates\Control Panel\Personalization\Screen saver timeout
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template ControlPanelDisplay.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
Impact:
The screen saver will automatically activate when the computer has been left unattended for the amount of time specified, and the users will not be able to change the timeout value.
All of the following tests or sub-groups must pass: | ||||||||||||
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_19.1.3.4_L1_Ensure_Screen_saver_timeout_is_set_to_Enabled_900_seconds_or_fewer_but_not_0" role="full" severity="unknown" time="2020-04-22T15:48:33.977-05:00" version="1" weight="1.0"> <result>fail</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37908-1</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" end-time="2020-04-22T15:48:33.977-05:00" start-time="2020-04-22T15:48:33.914-05:00"> <cis:and> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ScreenSaveTimeOut' is 'Windows: User Registry Value' is less than or equal to '900'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817335" result="false" testref="oval:org.cisecurity.benchmarks:tst:817335" type="registry_test"> <cis:evidence_object> <cis:evidence_item itemref="1048"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="hive" value="HKEY_USERS"/> <cis:evidence_item_pk_field name="key" value="S-1-5-21-3050897948-969533551-3432263440-500\Software\Policies\Microsoft\Windows\Control Panel\Desktop"/> <cis:evidence_item_pk_field name="name" value="ScreenSaveTimeOut"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ScreenSaveTimeOut' is 'Windows: User Registry Value' not equal to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817338" result="false" testref="oval:org.cisecurity.benchmarks:tst:817338" type="registry_test"> <cis:evidence_object> <cis:evidence_item itemref="1050"> <cis:evidence_item_pk status="does not exist"> <cis:evidence_item_pk_field name="hive" value="HKEY_USERS"/> <cis:evidence_item_pk_field name="key" value="S-1-5-21-3050897948-969533551-3432263440-500\Software\Policies\Microsoft\Windows\Control Panel\Desktop"/> <cis:evidence_item_pk_field name="name" value="ScreenSaveTimeOut"/> </cis:evidence_item_pk> </cis:evidence_item> </cis:evidence_object> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <complex-check operator="AND"> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173352" value-id="xccdf_org.cisecurity.benchmarks_value_817335_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817335"/> </check> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173382" value-id="xccdf_org.cisecurity.benchmarks_value_817338_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817338"/> </check> </complex-check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37908-1 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template SharedFolders.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for Start Menu and Taskbar settings.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for Notification settings.
This Group Policy section is provided by the Group Policy template WPN.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This policy setting turns off toast notifications on the lock screen.
The recommended state for this setting is Enabled .
While this feature can be handy for users, applications that provide toast notifications might display sensitive personal or business data while the device is left unattended.
To establish the recommended configuration via GP, set the following UI path to Enabled :
User Configuration\Policies\Administrative Templates\Start Menu and Taskbar\Notifications\Turn off toast notifications on the lock screen
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template WPN.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
Impact:
Applications will not be able to raise toast notifications on the lock screen.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_19.5.1.1_L1_Ensure_Turn_off_toast_notifications_on_the_lock_screen_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:34.055-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/16/subcontrol/5" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/16/subcontrol/11" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36332-5</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817347" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoToastApplicationNotificationOnLockScreen' is 'Windows: User Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817347" result="true" testref="oval:org.cisecurity.benchmarks:tst:817347" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817347"> <cis:evidence_item itemref="1052"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_USERS"/> <cis:evidence_item_pk_field name="key" value="S-1-5-21-3050897948-969533551-3432263440-500\Software\Policies\Microsoft\Windows\CurrentVersion\PushNotifications"/> <cis:evidence_item_pk_field name="name" value="NoToastApplicationNotificationOnLockScreen"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="case insensitive equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173472" value-id="xccdf_org.cisecurity.benchmarks_value_817347_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817347"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36332-5 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.11 |
Label: | Lock Workstation Sessions After Inactivity |
Description: | Automatically lock workstation sessions after a standard period of inactivity. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Actively manage the life cycle of system and application accounts – their creation, use, dormancy, deletion – in order to minimize opportunities for attackers to leverage them. |
Subcontrol: | 16.5 |
Label: | Ensure Workstation Screen Locks Are Configured |
Description: | Configure screen locks on systems to limit access to unattended workstations. |
This section contains recommendations for System settings.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template CtrlAltDel.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Display.admx/adml that is included with the Microsoft Windows 10 Release 1803 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DeviceInstallation.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template FolderRedirection.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template GroupPolicy.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Internet Communication Management.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Internet Communication settings.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations for Windows Component settings.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsAnytimeUpgrade.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
Note: This section was initially named Windows Anytime Upgrade but was renamed by Microsoft to Add features to Windows x starting with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template AppXRuntime.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template AppCompat.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Attachment Manager.
This Group Policy section is provided by the Group Policy template AttachmentManager.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting allows you to manage whether Windows marks file attachments with information about their zone of origin (such as restricted, Internet, intranet, local). This requires NTFS in order to function correctly, and will fail without notice on FAT32. By not preserving the zone information, Windows cannot make proper risk assessments.
The recommended state for this setting is: Disabled .
Note: The Attachment Manager feature warns users when opening or executing files which are marked as being from an untrusted source, unless/until the file's zone information has been removed via the "Unblock" button on the file's properties or via a separate tool such as Microsoft Sysinternals Streams .
A file that is downloaded from a computer in the Internet or Restricted Sites zone may be moved to a location that makes it appear safe, like an intranet file share, and executed by an unsuspecting user. The Attachment Manager feature will warn users when opening or executing files which are marked as being from an untrusted source, unless/until the file's zone information has been removed.
To establish the recommended configuration via GP, set the following UI path to Disabled :
User Configuration\Policies\Administrative Templates\Windows Components\Attachment Manager\Do not preserve zone information in file attachments
Note: This Group Policy path is provided by the Group Policy template AttachmentManager.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_19.7.4.1_L1_Ensure_Do_not_preserve_zone_information_in_file_attachments_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:34.211-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/7" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/7/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37424-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817349" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'SaveZoneInformation' is 'Windows: User Registry Value' to '2'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817349" result="true" testref="oval:org.cisecurity.benchmarks:tst:817349" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817349"> <cis:evidence_item itemref="1056"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_USERS"/> <cis:evidence_item_pk_field name="key" value="S-1-5-21-3050897948-969533551-3432263440-500\Software\Microsoft\Windows\CurrentVersion\Policies\Attachments"/> <cis:evidence_item_pk_field name="name" value="SaveZoneInformation"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="case insensitive equals" result="true"/> <cis:evidence_field cv="2" dt="int" ev="2" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173492" value-id="xccdf_org.cisecurity.benchmarks_value_817349_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817349"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37424-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior through their interaction with web browsers and email systems. |
Subcontrol: | 7.1 |
Label: | Ensure Use of Only Fully Supported Browsers and Email Clients |
Description: | Ensure that only fully supported web browsers and email clients are allowed to execute in the organization, ideally only using the latest version of the browsers and email clients provided by the vendor. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior though their interaction with web browsers and email systems. |
This policy setting manages the behavior for notifying registered antivirus programs. If multiple programs are registered, they will all be notified.
The recommended state for this setting is: Enabled .
Note: An updated antivirus program must be installed for this policy setting to function properly.
Antivirus programs that do not perform on-access checks may not be able to scan downloaded files.
To establish the recommended configuration via GP, set the following UI path to Enabled :
User Configuration\Policies\Administrative Templates\Windows Components\Attachment Manager\Notify antivirus programs when opening attachments
Note: This Group Policy path is provided by the Group Policy template AttachmentManager.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
Windows tells the registered antivirus program(s) to scan the file when a user opens a file attachment. If the antivirus program fails, the attachment is blocked from being opened.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_19.7.4.2_L1_Ensure_Notify_antivirus_programs_when_opening_attachments_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:34.289-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/7/subcontrol/8" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/7/subcontrol/9" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/7/subcontrol/10" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/8/subcontrol/2" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-36622-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817354" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ScanWithAntiVirus' is 'Windows: User Registry Value' to '3'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817354" result="true" testref="oval:org.cisecurity.benchmarks:tst:817354" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817354"> <cis:evidence_item itemref="1058"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_USERS"/> <cis:evidence_item_pk_field name="key" value="S-1-5-21-3050897948-969533551-3432263440-500\Software\Microsoft\Windows\CurrentVersion\Policies\Attachments"/> <cis:evidence_item_pk_field name="name" value="ScanWithAntiVirus"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="case insensitive equals" result="true"/> <cis:evidence_field cv="3" dt="int" ev="3" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173542" value-id="xccdf_org.cisecurity.benchmarks_value_817354_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817354"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-36622-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior through their interaction with web browsers and email systems. |
Subcontrol: | 7.9 |
Label: | Block Unnecessary File Types |
Description: | Block all e-mail attachments entering the organization's email gateway if the file types are unnecessary for the organization's business. |
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior through their interaction with web browsers and email systems. |
Subcontrol: | 7.10 |
Label: | Sandbox All Email Attachments |
Description: | Use sandboxing to analyze and block inbound email attachments with malicious behavior. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.1 |
Label: | Utilize Centrally Managed Anti-malware Software |
Description: | Utilize centrally managed anti-malware software to continuously monitor and defend each of the organization's workstations and servers. |
CIS Control Information | |
---|---|
Control: | Control the installation, spread, and execution of malicious code at multiple points in the enterprise, while optimizing the use of automation to enable rapid updating of defense, data gathering, and corrective action. |
Subcontrol: | 8.2 |
Label: | Ensure Anti-Malware Software and Signatures are Updated |
Description: | Ensure that the organization's anti-malware software updates its scanning engine and signature database on a regular basis. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | Minimize the attack surface and the opportunities for attackers to manipulate human behavior though their interaction with web browsers and email systems. |
Subcontrol: | 7.8 |
Label: | Scan All Inbound E-mail Attachments For Malicious Code |
Description: | Scan and block all e-mail attachments entering the organization's e-mail gateway if they contain malicious code or file types that are unnecessary for the organization's business. This scanning should be done before the e-mail is placed in the user's inbox. This includes e-mail content filtering and web content filtering. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template AutoPlay.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template UserDataBackup.admx/adml that is included only with the Microsoft Windows Vista through Windows 8.0 & Server 2012 (non-R2) Administrative Templates, as well as the Microsoft Windows 10 RTM (Release 1507) and Windows 10 Release 1511 Administrative Templates.
This section contains recommendations for Cloud Content.
This Group Policy section is provided by the Group Policy template CloudContent.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This policy setting lets you configure Windows Spotlight on the lock screen.
The recommended state for this setting is: Disabled .
Note: Per Microsoft TechNet , this policy setting only applies to Windows 10 Enterprise and Windows 10 Education editions.
Enabling this setting will help ensure your data is not shared with any third party. The Windows Spotlight feature collects data and uses that data to display suggested apps as well as images from the internet.
To establish the recommended configuration via GP, set the following UI path to Disabled :
User Configuration\Policies\Administrative Templates\Windows Components\Cloud Content\Configure Windows spotlight on lock screen
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template CloudContent.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
Impact:
Windows Spotlight will be turned off and users will no longer be able to select it as their lock screen.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.1_L1_Ensure_Configure_Windows_spotlight_on_lock_screen_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:34.446-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817357" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'ConfigureWindowsSpotlight' is 'Windows: User Registry Value' to '2'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817357" result="true" testref="oval:org.cisecurity.benchmarks:tst:817357" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817357"> <cis:evidence_item itemref="1062"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_USERS"/> <cis:evidence_item_pk_field name="key" value="S-1-5-21-3050897948-969533551-3432263440-500\Software\Policies\Microsoft\Windows\CloudContent"/> <cis:evidence_item_pk_field name="name" value="ConfigureWindowsSpotlight"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="case insensitive equals" result="true"/> <cis:evidence_field cv="2" dt="int" ev="2" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173572" value-id="xccdf_org.cisecurity.benchmarks_value_817357_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817357"/> </check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This policy setting determines whether Windows will suggest apps and content from third-party software publishers.
The recommended state for this setting is: Enabled .
Enabling this setting will help ensure your data is not shared with any third party. The Windows Spotlight feature collects data and uses that data to display suggested apps as well as images from the internet.
To establish the recommended configuration via GP, set the following UI path to Enabled :
User Configuration\Policies\Administrative Templates\Windows Components\Cloud Content\Do not suggest third-party content in Windows spotlight
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template CloudContent.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
Impact:
Windows Spotlight on lock screen, Windows tips, Microsoft consumer features and other related features will no longer suggest apps and content from third-party software publishers. Users may still see suggestions and tips to make them more productive with Microsoft features and apps.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_19.7.7.2_L1_Ensure_Do_not_suggest_third-party_content_in_Windows_spotlight_is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:34.524-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/13" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v7.0"/> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817359" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'DisableThirdPartySuggestions' is 'Windows: User Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817359" result="true" testref="oval:org.cisecurity.benchmarks:tst:817359" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817359"> <cis:evidence_item itemref="1064"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_USERS"/> <cis:evidence_item_pk_field name="key" value="S-1-5-21-3050897948-969533551-3432263440-500\Software\Policies\Microsoft\Windows\CloudContent"/> <cis:evidence_item_pk_field name="name" value="DisableThirdPartySuggestions"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="case insensitive equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173592" value-id="xccdf_org.cisecurity.benchmarks_value_817359_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817359"/> </check> </rule-result>
References:
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings. |
Subcontrol: | 5.1 |
Label: | Establish Secure Configurations |
Description: | Maintain documented, standard security configuration standards for all authorized operating systems and software. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template CredUI.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DataCollection.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Sidebar.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DWM.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template DigitalLocker.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template EdgeUI.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note: This section was initially named Windows Explorer but was renamed by Microsoft to File Explorer starting with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template FileRevocation.admx/adml that is included with the Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template EAIME.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template CaptureWizard.admx/adml that is only included with the Microsoft Windows Vista and Windows Server 2008 (non-R2) Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WordWheel.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template InetRes.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Sensors.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template MicrosoftEdge.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template MMC.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template UserExperienceVirtualization.admx/adml that is included with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Conf.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template NetworkProjection.admx/adml that is only included with the Microsoft Windows Vista through the Windows 8.1 Update & Server 2012 R2 Update Administrative Templates.
This section contains recommendations related to Network Sharing.
This Group Policy section is provided by the Group Policy template Sharing.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This policy setting determines whether users can share files within their profile. By default, users are allowed to share files within their profile to other users on their network after an administrator opts in the computer. An administrator can opt in the computer by using the sharing wizard to share a file within their profile.
The recommended state for this setting is: Enabled .
If not properly configured, a user could accidentally share sensitive data with unauthorized users. In an enterprise managed environment, the company should provide a managed location for file sharing, such as a file server or SharePoint, instead of the user sharing files directly from their own user profile.
To establish the recommended configuration via GP, set the following UI path to Enabled:
User Configuration\Policies\Administrative Templates\Windows Components\Network Sharing\Prevent users from sharing files within their profile.
Note: This Group Policy path is provided by the Group Policy template Sharing.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
Users cannot share files within their profile using the sharing wizard. Also, the sharing wizard cannot create a share at %root%\Users and can only be used to create SMB shares on folders.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_19.7.26.1_L1_Ensure_Prevent_users_from_sharing_files_within_their_profile._is_set_to_Enabled" role="full" severity="unknown" time="2020-04-22T15:48:34.133-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/14/subcontrol/4" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/14/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-38070-9</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817362" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'NoInplaceSharing' is 'Windows: User Registry Value' to '1'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817362" result="true" testref="oval:org.cisecurity.benchmarks:tst:817362" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817362"> <cis:evidence_item itemref="1054"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_USERS"/> <cis:evidence_item_pk_field name="key" value="S-1-5-21-3050897948-969533551-3432263440-500\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer"/> <cis:evidence_item_pk_field name="name" value="NoInplaceSharing"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="case insensitive equals" result="true"/> <cis:evidence_field cv="1" dt="int" ev="1" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173622" value-id="xccdf_org.cisecurity.benchmarks_value_817362_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817362"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-38070-9 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.6 |
Label: | Protect Information through Access Control Lists |
Description: | Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classification. |
Subcontrol: | 14.4 |
Label: | Protect Information With Access Control Lists |
Description: | All information stored on systems shall be protected with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principal that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template OOBE.admx/adml that is included with the Microsoft Windows 10 Release 1809 and Server 2019 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template MobilePCPresentationSettings.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TerminalServer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Note: This section was initially named Terminal Services but was renamed by Microsoft to Remote Desktop Services starting with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template InetRes.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Search.admx/adml that is included with the Microsoft Windows 7 & Server 2008 R2 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template SoundRec.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WinStoreUI.admx/adml that is included with the Microsoft Windows 8.0 & Server 2012 (non-R2) Administrative Templates and Microsoft Windows 8.1 & Server 2012 R2 Administrative Templates, or by the Group Policy template WindowsStore.admx/adml that is included with the Microsoft Windows 10 Release 1511 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Windows.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template TaskScheduler.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WinCal.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsColorSystem.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template SmartScreen.admx/adml that is included with the Microsoft Windows 10 Release 1703 Administrative Templates (or newer).
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template ErrorReporting.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template Passport.admx/adml that is included with the Microsoft Windows 10 RTM (Release 1507) Administrative Templates (or newer).
Note: This section was initially named Microsoft Passport for Work but was renamed by Microsoft to Windows Hello for Business starting with the Microsoft Windows 10 Release 1607 & Server 2016 Administrative Templates.
This section contains recommendations related to Windows Installer.
This Group Policy section is provided by the Group Policy template MSI.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This setting controls whether or not Windows Installer should use system permissions when it installs any program on the system.
Note: This setting appears both in the Computer Configuration and User Configuration folders. To make this setting effective, you must enable the setting in both folders.
Caution: If enabled, skilled users can take advantage of the permissions this setting grants to change their privileges and gain permanent access to restricted files and folders. Note that the User Configuration version of this setting is not guaranteed to be secure.
The recommended state for this setting is: Disabled .
Users with limited privileges can exploit this feature by creating a Windows Installer installation package that creates a new local account that belongs to the local built-in Administrators group, adds their current account to the local built-in Administrators group, installs malicious software, or performs other unauthorized activities.
To establish the recommended configuration via GP, set the following UI path to Disabled :
User Configuration\Policies\Administrative Templates\Windows Components\Windows Installer\Always install with elevated privileges
Note: This Group Policy path is provided by the Group Policy template MSI.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
Impact:
None - this is the default behavior.
|
<rule-result xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:ae="http://benchmarks.cisecurity.org/ae/0.5" xmlns:cc6="http://cisecurity.org/20-cc/v6.1" xmlns:cc7="http://cisecurity.org/20-cc/v7.0" xmlns:ciscf="https://benchmarks.cisecurity.org/ciscf/1.0" xmlns:notes="http://benchmarks.cisecurity.org/notes" xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" idref="xccdf_org.cisecurity.benchmarks_rule_19.7.41.1_L1_Ensure_Always_install_with_elevated_privileges_is_set_to_Disabled" role="full" severity="unknown" time="2020-04-22T15:48:34.383-05:00" version="1" weight="1.0"> <result>pass</result> <ident cc6:controlURI="http://cisecurity.org/20-cc/v6.1/control/5/subcontrol/1" system="http://cisecurity.org/20-cc/v6.1"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/3" system="http://cisecurity.org/20-cc/v7.0"/> <ident cc7:controlURI="http://cisecurity.org/20-cc/v7.0/control/4/subcontrol/6" system="http://cisecurity.org/20-cc/v7.0"/> <ident system="http://cce.mitre.org">CCE-37490-0</ident> <metadata> <cis:evidence xmlns:cis="http://benchmarks.cisecurity.org/evidence/1.0" definition_id="oval:org.cisecurity.benchmarks:def:817367" definition_negate="false"> <cis:and negated="false" result="true"> <cis:evidence_test check="all" check_existence="at_least_one_exists" comment="Ensure 'AlwaysInstallElevated' is 'Windows: User Registry Value' to '0'" negated="false" ns="windows" objref="oval:org.cisecurity.benchmarks:obj:817367" result="true" testref="oval:org.cisecurity.benchmarks:tst:817367" type="registry_test"> <cis:evidence_state steref="oval:org.cisecurity.benchmarks:ste:817367"> <cis:evidence_item itemref="1060"> <cis:evidence_item_pk status="exists"> <cis:evidence_item_pk_field name="hive" value="HKEY_USERS"/> <cis:evidence_item_pk_field name="key" value="S-1-5-21-3050897948-969533551-3432263440-500\Software\Policies\Microsoft\Windows\Installer"/> <cis:evidence_item_pk_field name="name" value="AlwaysInstallElevated"/> </cis:evidence_item_pk> <cis:evidence_field cv="reg_dword" dt="string" ev="reg_dword" name="type" op="case insensitive equals" result="true"/> <cis:evidence_field cv="0" dt="int" ev="0" name="value" op="equals" result="true"/> </cis:evidence_item> </cis:evidence_state> </cis:evidence_test> </cis:and> </cis:evidence> </metadata> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-export export-name="oval:org.cisecurity.benchmarks:var:8173672" value-id="xccdf_org.cisecurity.benchmarks_value_817367_var2"/> <check-content-ref href="CIS_Microsoft_Windows_Server_2019_Benchmark_v1.1.0-oval.xml" name="oval:org.cisecurity.benchmarks:def:817367"/> </check> </rule-result>
References:
CCE Information | |
---|---|
CCE-IDv5: | CCE-37490-0 |
Published On: | |
Last Modified On: |
CIS Controls V7.0:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.3 |
Label: | Ensure the Use of Dedicated Administrative Accounts |
Description: | Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities. |
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 4.6 |
Label: | Use of Dedicated Machines For All Administrative Tasks |
Description: | Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or browsing the Internet. |
CIS Controls V6.1:
CIS Control Information | |
---|---|
Control: | The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications. |
Subcontrol: | 5.1 |
Label: | Minimize And Sparingly Use Administrative Privileges |
Description: | Minimize administrative privileges and only use administrative accounts when they are required. Implement focused auditing on the use of administrative privileged functions and monitor for anomalous behavior. |
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WinLogon.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsMail.admx/adml that is only included with the Microsoft Windows Vista through the Windows 10 Release 1703 Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template MediaCenter.admx/adml that is only included with the Microsoft Windows Vista through Windows 10 Release 1511 Administrative Templates.
This section contains recommendations related to Windows Media Player.
This Group Policy section is provided by the Group Policy template WindowsMediaPlayer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section is intentionally blank and exists to ensure the structure of Windows benchmarks is consistent.
This Group Policy section is provided by the Group Policy template WindowsMediaPlayer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.
This section contains recommendations related to Windows Media Player playback.
This Group Policy section is provided by the Group Policy template WindowsMediaPlayer.admx/adml that is included with all versions of the Microsoft Windows Administrative Templates.