Hardens Windows endpoints using CIS (Center for Internet Security) Benchmark recommendations to reduce attack surface, enforce security baselines, and meet compliance requirements. Use when deploying new Windows workstations or servers, remediating audit findings, or establishing organization-wide security baselines. Activates for requests involving Windows hardening, CIS benchmarks, GPO security baselines, or endpoint configuration compliance.
Instrucciones de origen · Vista previa de solo lectura
name
hardening-windows-endpoint-with-cis-benchmark
description
Hardens Windows endpoints using CIS (Center for Internet Security) Benchmark recommendations to reduce attack surface, enforce security baselines, and meet compliance requirements. Use when deploying new Windows workstations or servers, remediating audit findings, or establishing organization-wide security baselines. Activates for requests involving Windows hardening, CIS benchmarks, GPO security baselines, or endpoint configuration compliance.
Deploying new Windows 10/11 or Server 2019/2022 endpoints that require security hardening
Establishing organization-wide security baselines using CIS Level 1 or Level 2 profiles
Remediating findings from compliance audits (PCI DSS, HIPAA, SOC 2) that reference CIS benchmarks
Validating existing endpoint configurations against current CIS benchmark versions
Do not use this skill for Linux endpoints (use hardening-linux-endpoint-with-cis-benchmark) or for cloud-native workloads that require CIS cloud benchmarks.
Common Misconfigurations & Verification
GPO linked but not applied: a linked CIS GPO means nothing until it reaches the host — confirm with gpresult /h report.html (or Get-GPResultantSetOfPolicy) that the baseline is under "Applied GPOs", not blocked by precedence, a WMI filter, or Block Inheritance on the OU.
Audit settings ineffective without the override: CIS 17.x advanced audit subcategories are ignored unless "Force audit policy subcategory settings to override" (SCENoApplyLegacyAuditPolicy) is Enabled. Validate on the host with auditpol /get /category:*, not the GPMC.
CIS-CAT score masks real gaps: a high Assessor-CLI score only covers Scored items and the profile you selected — running L1 hides missing L2 controls, and an outdated benchmark XML reports false passes. Match the benchmark version to the OS build.
Drift after baseline: local admins, app installers, or feature updates re-open settings (SMBv1, RDP, a firewall profile set Off). Schedule recurring CIS-CAT scans and feed results to the SIEM for drift detection rather than trusting a one-time pass.
Verify enforcement, not just policy: after applying, confirm a key control actually blocks — NTLMv2-only (2.3.11.7), Windows Firewall inbound Block per profile (9.x) — and run a 4688 / Atomic Red Team process-creation test to confirm Process Creation auditing (17.6.1) produces events that reach the SIEM.
Prerequisites
Windows 10/11 Enterprise or Windows Server 2019/2022 target endpoints
Active Directory Group Policy Management Console (GPMC) for enterprise deployment
CIS-CAT Pro Assessor or CIS-CAT Lite for automated benchmark assessment
Administrative access to target endpoints or domain controller
Current CIS Benchmark PDF for the target Windows version (download from cisecurity.org)
Workflow
Step 1: Select CIS Benchmark Profile Level
CIS provides two profile levels for Windows endpoints:
Level 1 (L1) - Corporate/Enterprise Environment:
Practical hardening settings that can be applied to most organizations
Minimal impact on functionality and user experience
Covers: password policy, audit policy, user rights, security options, Windows Firewall
Level 2 (L2) - High Security/Sensitive Data:
Includes all L1 settings plus additional restrictions
Audit Policy Configuration:
- Audit Credential Validation: Success and Failure (17.1.1)
- Audit Security Group Management: Success (17.2.5)
- Audit Logon: Success and Failure (17.5.1)
- Audit Process Creation: Success (17.6.1)
- Audit Removable Storage: Success and Failure (17.6.4)
Security Options (Section 2.3):
- Interactive logon: Do not display last user name: Enabled (2.3.7.1)
- Interactive logon: Machine inactivity limit: 900 seconds (2.3.7.3)
- Network access: Do not allow anonymous enumeration of SAM accounts: Enabled (2.3.10.2)
- Network security: LAN Manager authentication level: Send NTLMv2 response only (2.3.11.7)
- UAC: Run all administrators in Admin Approval Mode: Enabled (2.3.17.6)
Windows Firewall (Section 9):
- Domain Profile: Firewall state: On (9.1.1)
- Domain Profile: Inbound connections: Block (9.1.2)
- Private Profile: Firewall state: On (9.2.1)
- Public Profile: Firewall state: On (9.3.1)
- Public Profile: Inbound connections: Block (9.3.2)
Step 4: Validate with CIS-CAT Assessment
# Run CIS-CAT Pro Assessor against target endpoint
# CIS-CAT produces an HTML/XML report with pass/fail per recommendation
.\Assessor-CLI.bat `
-b "benchmarks\CIS_Microsoft_Windows_11_Enterprise_Benchmark_v3.0.0-xccdf.xml" `
-p "Level 1 (L1) - Corporate/Enterprise Environment" `
-rd "C:\CIS-Reports" `
-nts
# Review report for failed controls
# Score target: 95%+ for L1, 90%+ for L2 (due to operational exceptions)
Step 5: Document Exceptions and Compensating Controls
For each CIS recommendation that cannot be applied:
Document the specific recommendation ID and title
State the business justification for the exception
Define the compensating control that addresses the residual risk
Set a review date (quarterly) to reassess the exception
Obtain sign-off from the information security officer
Microsoft Security Compliance Toolkit (SCT): Microsoft's own GPO baselines (complementary to CIS)
Group Policy Management Console (GPMC): Enterprise GPO deployment and management
LGPO.exe: Microsoft tool for applying GPOs to standalone (non-domain) systems
Nessus/Tenable: Vulnerability scanner with CIS benchmark audit files
Common Pitfalls
Applying L2 to all endpoints: Level 2 restrictions (disabling Autoplay, restricting Remote Desktop) break workflows on standard workstations. Reserve L2 for endpoints handling sensitive data.
Not testing GPOs in pilot OU: Deploy CIS GPOs to a test OU with representative hardware/software before organization-wide rollout to avoid breaking line-of-business applications.
Ignoring CIS benchmark version updates: CIS benchmarks update with each Windows feature release. Running an outdated benchmark misses new security settings and generates false compliance reports.
Forgetting local admin accounts: CIS benchmarks assume domain-joined endpoints. Standalone systems require LGPO.exe or Microsoft Intune for baseline enforcement.
No exception process: Applying 100% of CIS recommendations is rarely feasible. Without a formal exception process, teams either ignore hardening or break applications.
