
cis-controls
CIS Controls v8 baseline security with IG1/IG2/IG3 levels
- version
- 0.1.0
- GitHub stars
- 436
Install
/plugin install cis-controls@grc-engineering-suiteRun it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.
Contents
Discovered from sourceSkills 1
CIS Controls Expert
Deep expertise in CIS Controls v8, the baseline cybersecurity framework developed by the Center for Internet Security.
License notice. This skill incorporates content derived from CIS Controls v8, © Center for Internet Security, Inc., used under the Creative Commons Attribution-ShareAlike 4.0 International license. This file and other CIS-derived content in
plugins/frameworks/cis-controls/are licensed under CC BY-SA 4.0 (the rest of the repository is MIT). See LICENSE-CIS.md.
Expertise Areas
CIS Controls Overview
Purpose: Prioritized set of actions to defend against the most pervasive cyber threats Authority: Center for Internet Security (CIS) - global non-profit Current Version: CIS Controls v8 (May 2021) Adoption: Cross-industry standard, used globally by organizations of all sizes
Key Principles:
- Offense informs defense (based on real-world attack data)
- Prioritization (most impactful controls first)
- Measurements and metrics
- Continuous diagnostics and mitigation
- Automation where possible
Evolution from v7 to v8:
- Consolidated from 20 to 18 controls
- Better alignment with Implementation Groups
- Enhanced cloud and mobile coverage
- Stronger integration with NIST CSF
- More actionable safeguards (171 to 153 refined)
Implementation Groups (IG1, IG2, IG3)
The core innovation of CIS Controls: tailored security based on organizational maturity and risk.
IG1 - Essential Cyber Hygiene
Target Audience:
- Small to medium businesses (typically <100 employees)
- Limited IT security resources (1-2 generalist IT staff)
- Organizations with low attack surface
- Standard business risk profile
- Minimal regulatory requirements
Characteristics:
- Safeguards: 56 essential controls
- Resource Model: Part-time security focus, leveraging generalist IT
- Budget: $10,000 - $50,000 annually
- Expertise: Basic IT competency, limited specialized security knowledge
- Tools: Commercial off-the-shelf, small business focused
Attack Profile IG1 Defends Against:
- Opportunistic attacks (phishing, commodity ransomware)
- Automated vulnerability scanning and exploitation
- Drive-by malware downloads
- Script kiddies and unsophisticated actors
- Social engineering targeting general workforce
Example Organizations:
- Local retail stores
- Small healthcare practices (1-3 doctors)
- Professional services (law firms, accounting)
- Regional nonprofits
- K-12 schools (individual schools, not districts)
- Small manufacturers
Critical IG1 Safeguards:
- Asset and software inventory (1.1, 2.1)
- Secure configurations (4.1, 4.2)
- Account management (5.1, 5.3, 5.4)
- Automated patching (7.3, 7.4)
- Anti-malware (10.1, 10.2)
- Backups (11.2, 11.3)
- Security awareness (14.1)
IG2 - Enterprise Security
Target Audience:
- Medium to large organizations (100-1,000 employees)
- Dedicated IT team with security responsibilities
- Moderate risk environment
- Customer or patient data handling (PII, PHI)
- Regulatory compliance needs (HIPAA, PCI-DSS)
Characteristics:
- Safeguards: 128 total (56 from IG1 + 72 additional)
- Resource Model: 1-3 dedicated security FTEs, larger IT team
- Budget: $100,000 - $500,000 annually
- Expertise: Security specialists, some advanced training
- Tools: Enterprise-grade (SIEM, EDR, vulnerability management)
Attack Profile IG2 Defends Against:
- Targeted phishing and spear-phishing campaigns
- Ransomware-as-a-Service (RaaS) operators
- Financially motivated cybercriminal groups
- Business email compromise (BEC)
- Credential stuffing and password spraying
- Industrial espionage (mid-tier)
- Supply chain attacks (lower sophistication)
Example Organizations:
- Mid-sized healthcare systems (regional hospitals)
- Community banks and credit unions
- Manufacturing companies (100-500 employees)
- SaaS startups (Series B/C)
- School districts and community colleges
- MSPs and IT service providers
Critical IG2 Safeguards (beyond IG1):
- Multi-factor authentication (5.5)
- Encryption (3.6, 3.10, 3.11)
- Centralized logging and SIEM (8.9, 8.11)
- Vulnerability scanning (7.5, 7.6)
- Network segmentation (12.2)
- IDS/IPS (13.2, 13.3)
- Secure SDLC (16.1, 16.2)
- Penetration testing (18.1, 18.2)
IG3 - Advanced Security
Target Audience:
- Large enterprises (1,000+ employees)
- Critical infrastructure organizations
- High-value intellectual property
- Known targets of nation-state actors
- Stringent regulatory environments (CMMC Level 3, NERC CIP)
Characteristics:
- Safeguards: 153 total (128 from IG2 + 25 additional)
- Resource Model: Security Operations Center (SOC), 5+ security FTEs
- Budget: $1,000,000+ annually
- Expertise: Highly specialized (threat hunters, forensics, IR specialists)
- Tools: Advanced threat detection, threat intelligence, SOAR platforms
Attack Profile IG3 Defends Against:
- Advanced Persistent Threats (APTs)
- Nation-state sponsored cyber espionage
- Sophisticated ransomware groups (Conti, REvil successors)
- Zero-day exploit campaigns
- Insider threats (malicious and negligent)
- Supply chain compromise (SolarWinds-level)
- Living-off-the-land (LOTL) techniques
- Multi-stage attacks with custom malware
Example Organizations:
- Fortune 500 companies
- Defense industrial base contractors
- Major healthcare systems (multi-state)
- Large financial institutions (national/global banks)
- Energy sector (utilities, pipelines)
- Telecommunications providers
- Federal/state government agencies
- Universities with significant research programs
Critical IG3 Safeguards (beyond IG2):
- Behavioral anti-malware and EDR (10.7)
- Data loss prevention (3.13)
- Privileged access workstations (12.8)
- Application layer filtering / WAF (13.10)
- Alert tuning and threat hunting (13.11)
- Application penetration testing (16.13)
- Internal penetration testing (18.5)
- Post-incident reviews (17.8)
The 18 CIS Controls (Detailed)
Control 1: Inventory and Control of Enterprise Assets
Why It Matters: You can't protect what you don't know exists.
Asset Types:
- End-user devices (laptops, desktops, tablets, smartphones)
- Servers (physical, virtual, cloud instances)
- Network infrastructure (routers, switches, firewalls, wireless APs)
- Network-attached storage (NAS)
- IoT and OT devices (printers, cameras, industrial control systems)
Required Information:
- Hardware make/model, serial number
- Network address (IP, MAC)
- Purpose/function
- Owner/custodian
- Physical/logical location
- Software/OS version
- Support status (vendor-supported, EOL)
Implementation Approaches:
- Passive Discovery: DHCP logs, network flow analysis, SPAN port monitoring
- Active Scanning: Nmap, Qualys, Rapid7, Lansweeper
- Agent-Based: Endpoint agents reporting to CMDB
- Cloud: AWS Config, Azure Resource Graph, GCP Asset Inventory
- Manual: Spreadsheets (only for very small orgs, IG1)
Common Challenges:
- Shadow IT (unapproved devices)
- BYOD (personal devices accessing corporate resources)
- Transient devices (visitor laptops, contractors)
- IoT proliferation (smart TVs, voice assistants, smart building tech)
- Cloud resource sprawl (forgotten EC2 instances)
Control 2: Inventory and Control of Software Assets
Why It Matters: Unauthorized software = unpatched vulnerabilities and compliance gaps.
Software Categories:
- Operating systems and firmware
- Business applications (ERP, CRM, productivity suites)
- Development tools and runtime environments
- Security tools
- Third-party libraries and dependencies
- Browser extensions and plugins
Safeguard Highlights:
- 2.1: Software inventory (name, version, publisher, install date)
- 2.2: Ensure software is vendor-supported (no EOL software)
- 2.3: Address unauthorized software (removal or approval)
- 2.4: Automated inventory tools (SCCM, Jamf, Ivanti)
- 2.5 (IG2): Application allowlisting (only approved software runs)
- 2.6 (IG2): Library allowlisting (approved DLLs, shared libraries)
- 2.7 (IG3): Script allowlisting (PowerShell, Python, Bash restrictions)
Implementation Approaches:
- Endpoint agents: Report installed software to central repository
- Package managers: Track software deployment (SCCM, Ansible, Puppet)
- Application control: AppLocker, Windows Defender Application Control, macOS Gatekeeper
- Container registries: Docker Hub controls, approved base images
- SaaS discovery: Cloud Access Security Broker (CASB) for shadow SaaS
Common Challenges:
- Developer workstations (require flexibility for tools)
- Open-source software tracking
- Software sprawl (users installing unauthorized apps)
- Legacy software (unsupported but business-critical)
- Cloud applications (SaaS discovery and control)
Control 3: Data Protection
Why It Matters: Data is the crown jewels. Protect it or lose competitive advantage, customer trust, and regulatory compliance.
Data Lifecycle:
- Creation: How data enters the organization
- Storage: Where data resides (databases, file shares, cloud)
- Use: How data is accessed and processed
- Sharing: Internal and external data transmission
- Archive: Long-term retention
- Destruction: Secure disposal
Key Safeguards:
- 3.1: Data management process
- 3.2: Data inventory (what sensitive data exists, where)
- 3.3: Data access control lists (least privilege)
- 3.4: Data retention policy and enforcement
- 3.5: Secure data disposal (wiping, destruction)
- 3.6 (IG2): Encrypt data on end-user devices (full disk encryption)
- 3.7 (IG2): Data classification scheme (public, internal, confidential, restricted)
- 3.10 (IG2): Encrypt sensitive data in transit (TLS 1.2+)
- 3.11 (IG2): Encrypt sensitive data at rest (database encryption, file encryption)
- 3.12 (IG2): Segment data by sensitivity (network/storage isolation)
- 3.13 (IG3): Deploy DLP solution (prevent exfiltration)
- 3.14 (IG3): Log sensitive data access (who accessed what, when)
Data Classification Examples:
- Public: Marketing materials, public-facing website content
- Internal: Internal memos, policies, general business data
- Confidential: Customer PII, employee records, financial data
- Restricted: Trade secrets, M&A data, regulated data (HIPAA, ITAR)
Encryption Standards:
- At Rest: AES-256, database TDE (Transparent Data Encryption)
- In Transit: TLS 1.2+ (prefer TLS 1.3), VPN (IPsec, WireGuard)
- Email: S/MIME, PGP for highly sensitive
- Cloud: CSP-managed keys (AWS KMS, Azure Key Vault) or customer-managed (BYOK)
Data Disposal Methods:
- Physical media: Shredding (hard drives), degaussing, incineration
- Digital: Multi-pass overwrite (DoD 5220.22-M), cryptographic erasure
- Cloud: Delete + verify (ensure backups and snapshots deleted)
- Certificates of destruction: For regulated industries
Control 4: Secure Configuration of Enterprise Assets and Software
Why It Matters: Default configurations are insecure. Attackers exploit well-known weaknesses.
Configuration Management Principles:
- Least Functionality: Disable unnecessary services, features, protocols
- Secure Defaults: Harden before deployment (not after)
- Consistency: Standard baselines for asset types
- Automation: Configuration-as-code (Infrastructure as Code)
- Validation: Regular audits and drift detection
Key Safeguards:
- 4.1: Secure configuration process (baseline creation, approval, deployment)
- 4.2: Secure configuration baselines (documented standards)
- 4.3: Automatic session locking (screen lock after inactivity)
- 4.4: Implement and manage firewalls (host-based firewalls enabled)
- 4.5 (IG2): Implement DMZ (demilitarized zone for internet-facing systems)
- 4.7: Manage default accounts (disable or rename, change passwords)
- 4.8 (IG2): Uninstall or disable unnecessary services (reduce attack surface)
Hardening Resources:
- CIS Benchmarks: Free, consensus-developed standards (150+ benchmarks)
- Operating systems (Windows, Linux, macOS)
- Cloud platforms (AWS, Azure, GCP)
- Applications (web servers, databases, containers)
- Network devices (Cisco, Palo Alto)
- DISA STIGs: Security Technical Implementation Guides (DoD standard)
- Vendor Hardening Guides: Microsoft Security Baselines, Red Hat Security Guide
- NIST Guidelines: NIST 800-123 (general server security)
Configuration Management Tools:
- Assessment: CIS-CAT Pro, OpenSCAP, Nessus compliance checks
- Enforcement: Ansible, Puppet, Chef, SaltStack, PowerShell DSC
- Cloud: AWS Config, Azure Policy, GCP Security Command Center
- Containers: Docker Bench, Kubernetes CIS Benchmark
Common Hardening Actions:
- Disable unnecessary services (Telnet, FTP, SMBv1)
- Enable host firewall (Windows Firewall, iptables, pf)
- Configure session timeouts (15 minutes idle)
- Disable USB auto-run
- Set BIOS/UEFI passwords
- Enable Secure Boot
- Configure audit logging
- Disable guest accounts
- Rename or disable default admin accounts
Control 5: Account Management
Why It Matters: Accounts are the keys to the kingdom. Poor account hygiene = easy lateral movement for attackers.
Account Types:
- Standard User Accounts: Day-to-day work, limited privileges
- Privileged Accounts: Administrator, root, domain admin
- Service Accounts: Application/service authentication
- Shared Accounts: (Avoid! If necessary, tightly control and log)
- Emergency Access Accounts: Break-glass for emergencies
Key Safeguards:
- 5.1: Account inventory (all user, admin, service accounts)
- 5.2: Use unique passwords (no shared passwords)
- 5.3: Disable dormant accounts (inactive 45-90 days)
- 5.4: Restrict administrator privileges to dedicated accounts (separate admin and user accounts)
- 5.5 (IG2): Establish and maintain MFA (all users, especially admins)
- 5.6 (IG2): Centralize account management (SSO, directory services)
Privileged Account Best Practices:
- Separate Accounts: User account for email/browsing, admin account for administration
- Just-in-Time (JIT) Access: Temporary privilege elevation, time-boxed
- Privileged Access Workstations (PAWs): Dedicated hardened systems for admin tasks (IG3)
- Session Recording: Record admin sessions for audit
- Password Vaulting: Store privileged credentials in vault (CyberArk, HashiCorp Vault, Keeper)
Service Account Management:
- Least privilege (only permissions needed)
- Unique per service (not shared across apps)
- Strong, randomly generated passwords (32+ characters)
- Regular password rotation (90-180 days, or eliminate with Managed Service Identities)
- Avoid interactive login rights
Dormant Account Detection:
- Last login date tracking
- Automated alerts after 30 days inactive
- Disable after 45-60 days inactive
- Delete after 90-120 days (or per retention policy)
Multi-Factor Authentication (MFA):
- Something you know: Password, PIN
- Something you have: Hardware token (YubiKey, RSA SecurID), mobile app (Duo, Authenticator)
- Something you are: Biometrics (fingerprint, face, iris)
MFA Strength Hierarchy (strongest to weakest):
- FIDO2/WebAuthn (hardware security keys, phishing-resistant)
- Certificate-based authentication (PIV/CAC smart cards)
- Authenticator app with push notification (Duo, Microsoft Authenticator)
- Time-based one-time password (TOTP) (Google Authenticator, Authy)
- SMS/voice call (weak, susceptible to SIM swapping - avoid if possible)
Account Lifecycle:
- Provisioning: Manager request, HR approval, role-based access
- Modification: Role changes, promotions, transfers
- Review: Quarterly access reviews, recertification
- Deprovisioning: Immediate upon termination, documented process
Control 6: Access Control Management
Why It Matters: Principle of least privilege prevents lateral movement and limits blast radius.
Access Control Models:
- Role-Based Access Control (RBAC): Access based on job function
- Attribute-Based Access Control (ABAC): Access based on attributes (department, clearance, location)
- Mandatory Access Control (MAC): System-enforced, label-based (government/military)
- Discretionary Access Control (DAC): Owner controls access (traditional file permissions)
Key Safeguards:
- 6.1: Access granting process (documented, approved)
- 6.2: Access revoking process (terminations, role changes)
- 6.3: Require MFA for externally-exposed applications
- 6.4: Require MFA for remote access
- 6.5 (IG2): Require MFA for administrative access
- 6.7 (IG2): Centralize access control (single authoritative source)
- 6.8 (IG2): Define and maintain RBAC (standardized roles)
RBAC Implementation:
- Define roles based on job functions (not individuals)
- Group permissions into roles (Finance-User, HR-Admin, Developer)
- Assign users to roles (not direct permissions)
- Regular role reviews and updates
Least Privilege Principles:
- Default deny (no access unless explicitly granted)
- Need-to-know basis
- Time-limited access (expire elevated access)
- Minimal effective permissions
- Separation of duties (no single person has end-to-end control)
Remote Access Security:
- VPN required (no direct internet exposure of internal resources)
- MFA for VPN access
- Split-tunnel vs full-tunnel (consider data sensitivity)
- Device posture checking (Endpoint compliance before access)
- Zero Trust Network Access (ZTNA) for modern approach
Access Review Process:
- Quarterly manager reviews of team access
- Annual comprehensive access recertification
- Automated alerts for dormant permissions
- Immediate revocation upon termination
- Audit trail of access changes
Control 7: Continuous Vulnerability Management
Why It Matters: Unpatched vulnerabilities are the #1 attack vector. Speed matters.
Vulnerability Management Lifecycle:
- Discovery: Identify assets and vulnerabilities
- Prioritization: Risk-based ranking (not just CVSS)
- Remediation: Patch, mitigate, or accept risk
- Verification: Confirm vulnerability closed
- Reporting: Metrics and trends
Key Safeguards:
- 7.1: Vulnerability management process
- 7.2: Remediation process (SLAs by severity)
- 7.3: Automated OS patch management
- 7.4: Automated application patch management
- 7.5 (IG2): Automated vulnerability scans of internal assets
- 7.6 (IG2): Automated vulnerability scans of externally-facing assets
- 7.7 (IG3): Remediate detected vulnerabilities (risk-based SLAs)
Vulnerability Scanning:
- Frequency: Weekly internal, monthly external (minimum)
- Scope: All internet-facing, all critical internal assets
- Scan Types:
- Unauthenticated: External attacker perspective
- Authenticated/Credentialed: Deeper visibility, detect missing patches
- Agent-based: Continuous assessment
- Tools: Qualys VMDR, Tenable.io, Rapid7 InsightVM, Nessus
Patch Management:
- Critical Patches: 15 days (CISA: 15 days for KEV)
- High Patches: 30 days
- Medium Patches: 60-90 days
- Low Patches: Next maintenance window
- Exceptions: Document compensating controls, business justification, executive approval
Prioritization Factors (beyond CVSS):
- Exploit availability: Is there a public exploit? (CISA KEV, Metasploit)
- Asset criticality: Production vs dev, customer-facing vs internal
- Exposure: Internet-facing vs internal
- Compensating controls: Firewall rules, WAF, IPS signatures
- EPSS Score: Exploit Prediction Scoring System (probability of exploit)
Common Challenges:
- Legacy systems (can't patch without breaking)
- Change control bureaucracy
- Patching windows (maintenance downtime)
- Testing requirements (QA before production)
- Third-party/vendor software (delayed patches)
- Cloud and container patching (immutable infrastructure, redeploy)
Control 8: Audit Log Management
Why It Matters: Logs are the evidence. No logs = no incident detection, no forensics, no compliance.
What to Log:
- Authentication events: Successful/failed logins, logouts, privilege escalation
- Account changes: Creation, deletion, privilege modifications
- System changes: Configuration changes, software installation
- File access: Sensitive data access (read, write, delete)
- Network connections: Firewall logs, VPN, proxy
- Security events: AV detections, IDS/IPS alerts, DLP violations
Key Safeguards:
- 8.1: Audit log management process
- 8.2: Collect audit logs (all critical systems)
- 8.3: Ensure adequate log storage (capacity planning)
- 8.5 (IG2): Collect detailed audit logs (enable verbose logging)
- 8.6 (IG2): Collect DNS query logs (detect C2, exfiltration)
- 8.9 (IG2): Centralize audit logs (SIEM, log aggregator)
- 8.10 (IG2): Retain audit logs (minimum 90 days, prefer 1 year)
- 8.11 (IG2): Conduct audit log reviews (manual or automated)
- 8.12 (IG3): Collect service provider logs (SaaS, IaaS, PaaS)
Log Sources:
- Operating systems (Windows Event Log, syslog)
- Applications (web servers, databases, business apps)
- Security tools (firewall, IDS/IPS, AV, DLP)
- Network devices (routers, switches, wireless)
- Cloud platforms (AWS CloudTrail, Azure Monitor, GCP Cloud Logging)
- Identity providers (Active Directory, Okta, Azure AD)
Centralized Logging (SIEM):
- Purpose: Aggregate, correlate, alert, investigate
- Tools: Splunk, Elastic Stack (ELK), Microsoft Sentinel, IBM QRadar, Sumo Logic
- Benefits: Single pane of glass, correlation, long-term retention, compliance reporting
Log Retention Requirements:
- CIS Baseline: 90 days minimum (IG2), 1 year recommended
- PCI DSS: 1 year (3 months immediately available)
- HIPAA: 6 years
- SOX: 7 years
- State breach laws: Varies (typically 1-2 years)
Log Review:
- Automated Alerting: High-priority events trigger immediate alerts
- Daily Review: Security team reviews critical alerts
- Weekly Review: Trend analysis, anomaly detection
- Monthly Reports: Executive dashboards, compliance metrics
Common Log Analysis Use Cases:
- Failed login attempts (brute force detection)
- Privilege escalation
- After-hours access
- Geographically impossible travel
- Data exfiltration (large outbound transfers)
- Malware execution
- Policy violations
Control 9: Email and Web Browser Protections
Why It Matters: Email and web are the primary attack vectors (90%+ of breaches start with phishing).
Email Threats:
- Phishing (credential theft)
- Spear-phishing (targeted)
- Business email compromise (BEC)
- Malware attachments (ransomware, trojans)
- Link-based attacks (malicious URLs)
Web Threats:
- Drive-by downloads
- Malicious advertisements (malvertising)
- Exploit kits
- Watering hole attacks
- Compromised websites
Key Safeguards:
- 9.1: Ensure use of fully supported browsers and email clients (no EOL)
- 9.2: Use DNS filtering services (block malicious domains)
- 9.3: Maintain network-based URL filters (web proxy, secure web gateway)
- 9.4: Restrict unnecessary browser and email extensions
- 9.5 (IG2): Implement DMARC (email authentication)
- 9.6 (IG2): Block unnecessary file types (executables, scripts in email)
- 9.7 (IG2): Deploy email server anti-malware
Email Security Stack:
- Email Gateway: Mimecast, Proofpoint, Cisco ESA, Microsoft Defender for Office 365
- Anti-spam, anti-malware, anti-phishing
- URL rewriting (time-of-click protection)
- Attachment sandboxing
- DMARC/SPF/DKIM: Email authentication
- SPF: Sender Policy Framework (authorized sending IPs)
- DKIM: DomainKeys Identified Mail (cryptographic signing)
- DMARC: Domain-based Message Authentication, Reporting & Conformance (policy enforcement)
- User Reporting: Phish Alert Button (let users report suspicious emails)
- Email Encryption: S/MIME, PGP for sensitive communications
DMARC Implementation:
- Start with monitoring mode (p=none)
- Analyze reports, fix legitimate mail flows
- Move to quarantine (p=quarantine)
- Eventually reject (p=reject) unauthorized email
Web Filtering:
- DNS Filtering: Cisco Umbrella, Quad9, Cloudflare Gateway (lightweight)
- Secure Web Gateway (SWG): Zscaler, Palo Alto Prisma Access, Menlo Security (deep inspection)
- Categories to Block: Malware, phishing, adult content, gambling, anonymizers/proxies
Browser Security:
- Keep Updated: Auto-update enabled (Chrome, Edge, Firefox)
- Extension Control: Allowlist approved extensions, block others
- Isolation: Browser isolation for high-risk browsing (Menlo, Ericom)
- Configuration: Disable Java, Flash (deprecated), restrict file downloads
Control 10: Malware Defenses
Why It Matters: Malware is pervasive. Defense-in-depth is essential.
Malware Types:
- Ransomware: Encrypts data, demands payment (REvil, Conti, LockBit)
- Trojans: Masquerades as legitimate software (remote access trojans - RATs)
- Worms: Self-propagating (WannaCry, NotPetya)
- Spyware: Steals information (keyloggers, infostealers)
- Rootkits: Hides presence, maintains persistence
- Cryptominers: Uses resources to mine cryptocurrency
Key Safeguards:
- 10.1: Deploy anti-malware software (all endpoints)
- 10.2: Configure automatic signature updates (daily or more)
- 10.3: Disable autorun and autoplay (USB, CD/DVD)
- 10.4: Configure automatic anti-malware scanning (real-time + scheduled)
- 10.5 (IG2): Enable anti-exploitation features (DEP, ASLR, EMET)
- 10.6 (IG2): Centrally manage anti-malware (console, reporting)
- 10.7 (IG3): Use behavioral anti-malware (EDR, machine learning)
Endpoint Protection Evolution:
- Traditional Antivirus (AV): Signature-based detection (legacy)
- Anti-Malware: Enhanced AV with heuristics
- Endpoint Protection Platform (EPP): AV + firewall + device control
- Endpoint Detection and Response (EDR): Behavioral analysis, threat hunting, forensics
- Extended Detection and Response (XDR): EDR + network + email + cloud
Leading Solutions:
- Next-Gen AV/EDR: CrowdStrike Falcon, SentinelOne, Microsoft Defender for Endpoint, Carbon Black
- Traditional: Symantec Endpoint Protection, Trend Micro, Sophos
Detection Methods:
- Signature-based: Known malware patterns (fast, but misses new threats)
- Heuristic: Behavioral analysis (catches variants)
- Sandboxing: Execute in isolated environment, observe behavior
- Machine Learning: AI-based anomaly detection
- Indicators of Attack (IoA): Detect tactics, techniques, procedures (TTPs)
Anti-Exploitation Techniques:
- DEP (Data Execution Prevention): Prevent code execution in data regions
- ASLR (Address Space Layout Randomization): Randomize memory addresses
- Control Flow Guard (CFG): Validate indirect calls
- Application Guard: Isolate risky applications (Windows Defender Application Guard)
Malware Response:
- Isolate: Quarantine infected endpoint (network isolation)
- Investigate: Determine scope, root cause, lateral movement
- Eradicate: Remove malware, rebuild if necessary
- Recover: Restore from clean backup
- Lessons Learned: Update defenses, user training
Control 11: Data Recovery
Why It Matters: Ransomware, hardware failure, disasters happen. Backups are your insurance policy.
3-2-1 Backup Rule:
- 3 copies of data (primary + 2 backups)
- 2 different media types (disk + tape/cloud)
- 1 copy offsite (protect against local disaster)
Modern Update: 3-2-1-1-0:
- 3-2-1 (as above)
- 1 immutable/air-gapped copy (ransomware protection)
- 0 errors in backup validation (test restores)
Key Safeguards:
- 11.1: Data recovery process (documented procedures)
- 11.2: Perform automated backups (scheduled, no manual intervention)
- 11.3: Protect recovery data (encryption, access control, offsite)
- 11.4: Establish isolated instance of recovery data (air-gapped, immutable)
- 11.5 (IG2): Test data recovery (quarterly or semi-annual restore tests)
Backup Scope:
- Critical Systems: ERP, CRM, databases, file servers, email
- User Data: Home directories, shared drives
- System State: OS configurations, Active Directory, certificates
- Applications: Application data, configurations
Backup Types:
- Full: Complete copy of all data (slow, storage-intensive, but fastest restore)
- Incremental: Changes since last backup (fast, efficient, slower restore)
- Differential: Changes since last full backup (middle ground)
- Synthetic Full: Combines full + incrementals to create new full
Backup Frequency:
- Critical systems: Daily or continuous (CDP - Continuous Data Protection)
- User data: Daily
- Databases: Transaction log backups (every 15-60 minutes) + daily full
- Offsite sync: Daily or weekly
Backup Testing:
- Restore Drills: Quarterly test restore of random data sets
- Disaster Recovery Exercises: Annual full DR test
- Validation: Automated backup verification (integrity checks)
- Documentation: Maintain restore runbooks
Ransomware-Resilient Backups:
- Immutability: Write-once-read-many (WORM), object lock (S3 Object Lock)
- Air-Gap: Physically or logically isolated (tape in safe, offline disk)
- Separate Credentials: Different admin accounts for backup systems
- Network Segmentation: Backups on separate VLAN, restricted access
Backup Solutions:
- Traditional: Veeam, Commvault, Veritas NetBackup, IBM Spectrum Protect
- Cloud-Native: AWS Backup, Azure Backup, GCP Cloud Backup
- SaaS Backup: Spanning, Veeam for M365 (for Office 365, Google Workspace)
- Ransomware-Focused: Rubrik, Cohesity (immutable, zero-trust)
Control 12: Network Infrastructure Management (IG2)
Why It Matters: Network is the highway for data and attacks. Secure the roads.
Key Safeguards:
- 12.1: Ensure network infrastructure is up-to-date (patch routers, switches, firewalls)
- 12.2: Establish secure network architecture (segmentation, DMZ)
- 12.3: Securely manage network infrastructure (dedicated admin VLANs, out-of-band)
- 12.4: Maintain network architecture diagram (current topology)
- 12.6: Use secure network management protocols (SSH, SNMPv3, no Telnet)
- 12.7: Ensure remote devices use VPN (encrypt remote access)
- 12.8 (IG3): Dedicated computing resources for admins (jump boxes, PAWs)
Network Segmentation:
- Purpose: Limit lateral movement, isolate critical assets
- Approaches:
- VLANs: Virtual LANs (Layer 2 separation)
- Subnets: IP addressing (Layer 3 separation)
- Firewalls: Zone-based firewalls (enforce policy between segments)
- Micro-segmentation: Software-defined, workload-level (zero trust)
Network Zones:
- External/Internet: Untrusted
- DMZ (Perimeter Network): Internet-facing services (web servers, email gateways)
- Internal/Corporate: Workstations, internal applications
- Restricted/Secure: High-value assets (databases, HR systems)
- Management: Network and security device management (out-of-band)
DMZ Architecture:
- Purpose: Buffer between internet and internal network
- Placement: Dual firewall (external and internal) or screened subnet
- Assets: Web servers, mail relays, DNS, reverse proxies
- Rules: Strictly limited inbound, no direct access to internal
Secure Management:
- Protocols: SSH (not Telnet), HTTPS (not HTTP), SNMPv3 (not v1/v2c)
- Access: Management VLAN, out-of-band network, jump box
- Authentication: Strong passwords, MFA, certificate-based
- Monitoring: Log all admin access, session recording
Network Diagram:
- Information: Devices, IP addresses, VLANs, security zones, data flows
- Format: Visio, Draw.io, Lucidchart (keep current, version control)
- Frequency: Update quarterly or after major changes
Control 13: Network Monitoring and Defense (IG2)
Why It Matters: Visibility is security. You can't defend against what you can't see.
Key Safeguards:
- 13.1: Centralize security event alerting (SIEM)
- 13.2: Deploy network-based IDS (intrusion detection)
- 13.3: Deploy network-based IPS (intrusion prevention)
- 13.4: Perform traffic filtering (block known-bad IPs, domains)
- 13.6: Collect network traffic flow logs (NetFlow, IPFIX)
- 13.8: Deploy network-based anti-malware
- 13.10 (IG3): Perform application layer filtering (WAF)
- 13.11 (IG3): Tune security event alerting thresholds
IDS vs IPS:
- IDS (Intrusion Detection System): Passive monitoring, alerts on threats (Suricata, Snort, Zeek)
- IPS (Intrusion Prevention System): Active blocking, inline (Snort IPS, Palo Alto Threat Prevention)
Detection Methods:
- Signature-based: Match known attack patterns (Snort rules)
- Anomaly-based: Baseline normal traffic, alert on deviations
- Heuristic: Behavioral analysis
- Threat Intelligence: IP/domain reputation feeds
Network Traffic Analysis (NTA):
- Tools: Darktrace, ExtraHop, Vectra AI, Corelight (Zeek-based)
- Capabilities:
- Baseline normal network behavior
- Detect anomalies (data exfiltration, lateral movement, C2 beaconing)
- Machine learning-based detection
- East-west traffic visibility (internal lateral movement)
NetFlow/IPFIX:
- Purpose: Metadata about network traffic (who, what, when, how much)
- Data: Source/dest IP, ports, protocol, bytes transferred, timestamps
- Tools: SolarWinds NTA, Plixer Scrutinizer, ManageEngine NetFlow Analyzer
- Use Cases: Capacity planning, security investigation, compliance
Web Application Firewall (WAF):
- Purpose: Protect web applications from OWASP Top 10
- Placement: In front of web servers (cloud or on-prem)
- Detection: SQL injection, XSS, CSRF, file inclusion
- Solutions: F5 WAF, Imperva, Cloudflare WAF, AWS WAF, Azure WAF
Alert Tuning (IG3):
- Problem: Alert fatigue (too many false positives)
- Solution: Iterative tuning
- Baseline environment
- Disable low-value signatures
- Whitelist known-good traffic
- Adjust thresholds
- Prioritize critical alerts
- Goal: High-fidelity alerts that warrant investigation
Control 14: Security Awareness and Skills Training
Why It Matters: Users are the weakest link AND the strongest defense (if trained).
Key Safeguards:
- 14.1: Security awareness program (annual training, all workforce)
- 14.2: Train on secure authentication (password hygiene, MFA)
- 14.3: Train on data handling (classification, encryption, disposal)
- 14.4: Train on identifying social engineering (phishing, vishing, smishing)
- 14.5 (IG2): Train on authentication best practices (passphrase, password managers)
- 14.6 (IG2): Train on identifying and reporting incidents (when and how to report)
- 14.9 (IG3): Conduct role-specific training (developers, admins, executives)
Awareness Training Program:
- Frequency: Annual mandatory training, quarterly refreshers
- Topics:
- Phishing and social engineering
- Password security (unique, complex, MFA)
- Data classification and handling
- Physical security (tailgating, clean desk)
- Incident reporting
- Acceptable use policy
- Format: Online modules, videos, quizzes, in-person sessions
Phishing Simulation:
- Purpose: Test user awareness, identify high-risk users
- Frequency: Monthly or quarterly
- Escalation: Users who fail multiple times receive additional training
- Tools: KnowBe4, Proofpoint Security Awareness, Cofense PhishMe, SANS Securing The Human
Role-Specific Training (IG3):
- Developers: Secure coding (OWASP Top 10, input validation, authentication)
- System Administrators: Hardening, least privilege, secure remote access
- Executives: Business email compromise, social engineering targeting leadership
- HR/Finance: W-2 phishing, wire transfer fraud
- Security Team: Advanced training (SANS, Offensive Security, certifications)
Security Culture:
- Security Champions: Ambassadors in each department
- Gamification: Rewards for reporting phishing, security wins
- Communication: Regular security tips, newsletters, posters
- Executive Support: C-suite visibly supports security initiatives
Measurement:
- Phishing click rate (goal: <5%)
- Training completion rate (goal: 100%)
- Incident reporting rate (upward trend is good - users reporting more)
- Time to report phishing (faster is better)
Control 15: Service Provider Management
Why It Matters: Third-party risk is your risk. Supply chain attacks are on the rise.
Key Safeguards:
- 15.1: Inventory of service providers (cloud, SaaS, MSPs, vendors)
- 15.2: Service provider management policy (risk assessment, contracts)
- 15.3 (IG2): Classify service providers (by criticality, data access)
- 15.4 (IG2): Ensure contracts include security requirements (SLAs, audit rights)
- 15.5 (IG2): Assess service providers (questionnaires, certifications)
- 15.6 (IG2): Monitor service providers (ongoing, not just initial)
- 15.7 (IG3): Securely decommission service providers (data return, deletion)
Service Provider Types:
- Cloud IaaS: AWS, Azure, GCP (infrastructure)
- SaaS: Salesforce, Office 365, Workday (applications)
- Managed Services: MSP, MSSP, SOC-as-a-Service
- Professional Services: Consultants, auditors, pen testers
- Business Partners: Integrations, data sharing
Risk Classification:
- Critical: Access to sensitive data, single point of failure (e.g., email provider)
- High: Access to internal systems, PII (e.g., HR SaaS)
- Medium: Limited data access (e.g., marketing platform)
- Low: No data access (e.g., office supplies)
Vendor Assessment Methods:
- Security Questionnaires: SIG (Standard Information Gathering), CAIQ, custom
- Certifications: SOC 2, ISO 27001, HITRUST, PCI-DSS (request reports)
- Penetration Tests: Request recent pentest results (executive summary)
- On-Site Audits: For critical vendors (right-to-audit clause)
- Continuous Monitoring: SecurityScorecard, BitSight, UpGuard (external ratings)
Contract Security Clauses:
- Data protection: Encryption, access control, data location
- Incident notification: Timeframe (e.g., 24-72 hours)
- Right to audit: Annual or on-demand audits
- Data ownership: Customer owns data
- Data return/deletion: Upon termination, certificated deletion
- Subcontractor approval: Notify of subcontractor changes
- Insurance: Cyber liability insurance requirements
- Compliance: HIPAA BAA, GDPR DPA, etc.
Ongoing Monitoring:
- Quarterly reviews: Security posture, incidents, changes
- Annual recertification: Review SOC 2, ISO, pentest reports
- News monitoring: Breaches, M&A, financial stability
- Scorecard tracking: Trend analysis (improving or declining)
Offboarding:
- Data return: Request all data in usable format
- Data deletion: Certified destruction (certificate of deletion)
- Access revocation: Disable integrations, API keys, accounts
- Contractual obligations: Ensure terms survive termination (confidentiality)
Control 16: Application Software Security (IG2)
Why It Matters: Custom applications are unique attack surfaces. Secure code is foundational.
Key Safeguards:
- 16.1: Secure application development process (SDLC)
- 16.2: Secure software development practices (OWASP, standards)
- 16.3: Root cause analysis on security vulnerabilities
- 16.5: Use up-to-date and trusted third-party components
- 16.6: Establish and maintain SBOM (Software Bill of Materials)
- 16.7: Use standard hardening configuration templates
- 16.11 (IG3): Leverage vetted modules or services (proven libraries)
- 16.13 (IG3): Conduct application penetration testing
- 16.14 (IG3): Conduct threat modeling
Secure SDLC Phases:
- Requirements: Security requirements defined
- Design: Threat modeling, architecture review
- Development: Secure coding, code review, SAST
- Testing: DAST, penetration testing, security QA
- Deployment: Hardening, secure configuration
- Maintenance: Patch management, vulnerability monitoring
OWASP Top 10 (2021):
- Broken Access Control
- Cryptographic Failures
- Injection (SQL, OS, LDAP)
- Insecure Design
- Security Misconfiguration
- Vulnerable and Outdated Components
- Identification and Authentication Failures
- Software and Data Integrity Failures
- Security Logging and Monitoring Failures
- Server-Side Request Forgery (SSRF)
Application Security Testing:
- SAST (Static Application Security Testing): Source code analysis (Checkmarx, Veracode, SonarQube)
- DAST (Dynamic Application Security Testing): Running app testing (Burp Suite, OWASP ZAP, Acunetix)
- IAST (Interactive AST): Hybrid approach, runtime instrumentation
- SCA (Software Composition Analysis): Third-party library vulnerabilities (Snyk, WhiteSource, Black Duck)
- Penetration Testing: Manual testing by security experts
Software Bill of Materials (SBOM):
- Purpose: Inventory of application components (libraries, frameworks, dependencies)
- Format: SPDX, CycloneDX
- Use Cases: Vulnerability tracking (Log4Shell), license compliance, supply chain security
- Tools: Syft, Tern, SBOM generators in build pipelines
Secure Coding Practices:
- Input validation (whitelist, never trust user input)
- Output encoding (prevent XSS)
- Parameterized queries (prevent SQL injection)
- Least privilege (application runs with minimal permissions)
- Error handling (don't leak sensitive info in errors)
- Logging (security events, not sensitive data)
- Authentication and session management (secure cookies, timeouts)
Threat Modeling (IG3):
- Methodologies: STRIDE (Microsoft), PASTA, OCTAVE
- Process:
- Identify assets (data, systems)
- Create architecture diagram (data flows)
- Identify threats (STRIDE: Spoofing, Tampering, Repudiation, Info Disclosure, DoS, Elevation)
- Rank risks
- Mitigate (design changes, controls)
- When: Design phase (before coding)
Control 17: Incident Response Management
Why It Matters: Breaches happen. Preparation determines damage.
Key Safeguards:
- 17.1: Designate personnel to manage incident handling (CSIRT, SOC)
- 17.2: Establish and maintain contact information (24/7 escalation)
- 17.3: Establish enterprise process for reporting incidents (how users report)
- 17.4: Establish incident response process (documented plan)
- 17.5 (IG2): Assign key roles and responsibilities (incident commander, comms, legal)
- 17.6 (IG2): Define communication mechanisms (war room, Slack channel, bridge)
- 17.7 (IG2): Conduct routine incident response exercises (tabletops, simulations)
- 17.8 (IG3): Conduct post-incident reviews (lessons learned)
- 17.9 (IG3): Establish security incident thresholds (severity ratings, escalation)
Incident Response Lifecycle (NIST SP 800-61):
- Preparation: Plans, tools, training
- Detection and Analysis: Identify and scope incident
- Containment, Eradication, Recovery: Stop spread, remove threat, restore
- Post-Incident Activity: Lessons learned, improvements
Incident Response Team Roles:
- Incident Commander: Leads response, decision authority
- Technical Lead: Deep-dive analysis, forensics, remediation
- Communications: Internal and external communications, PR
- Legal: Legal implications, regulatory notification, law enforcement
- HR: Insider threats, employee notifications
- Executive Sponsor: C-suite oversight, resource allocation
Incident Severity Ratings:
- Critical/P1: Active breach, data exfiltration, ransomware, mission-critical system down
- High/P2: Confirmed compromise, malware detected, significant impact
- Medium/P3: Suspicious activity, potential compromise, limited impact
- Low/P4: Policy violations, informational alerts
Incident Response Playbooks:
- Ransomware: Isolation, backup recovery, decryption (if possible), law enforcement
- Phishing: Email recall, user notification, credential reset, malware scan
- Data Breach: Scope determination, notification (legal), forensics, remediation
- DDoS: Traffic filtering, CDN mitigation, ISP coordination
- Insider Threat: HR coordination, account disable, forensic imaging, investigation
Communication Plan:
- Internal: Incident status updates, executive briefings, workforce notifications
- External: Customers, partners, regulators, law enforcement, media (if necessary)
- Templates: Pre-drafted communications (reduce response time)
Tabletop Exercises:
- Frequency: Semi-annual or annual
- Scenarios: Ransomware, data breach, DDoS, insider threat
- Participants: IR team, executives, legal, HR, PR
- Objectives: Test plan, identify gaps, improve coordination
Post-Incident Review:
- What happened: Timeline of events
- What went well: Effective actions, successful containment
- What went poorly: Gaps, delays, miscommunications
- Action items: Process improvements, tool enhancements, training needs
- Documentation: Update runbooks, lessons learned database
Control 18: Penetration Testing (IG2)
Why It Matters: Validate defenses with real-world attack simulation.
Key Safeguards:
- 18.1: Penetration testing program (annual or after major changes)
- 18.2: Perform periodic external penetration tests (annual minimum)
- 18.3: Remediate penetration test findings (prioritized action plan)
- 18.4: Validate security measures (confirm controls effective)
- 18.5 (IG3): Perform periodic internal penetration tests (assume breach)
Penetration Testing Types:
- External: Internet-facing assets (websites, VPNs, email)
- Internal: Inside the network (lateral movement, privilege escalation)
- Web Application: OWASP Top 10, business logic flaws
- Wireless: WiFi security (WPA2/3, rogue APs)
- Physical: Facility access, tailgating, badge cloning
- Social Engineering: Phishing, vishing, pretexting
Testing Methodologies:
- Black Box: No prior knowledge (external attacker perspective)
- Gray Box: Partial knowledge (compromised user scenario)
- White Box: Full knowledge (comprehensive assessment)
Scope Considerations:
- In-Scope: Systems approved for testing (documented)
- Out-of-Scope: Production databases (read-only), third-party systems without approval
- Rules of Engagement: Testing hours, communication protocols, stop conditions
Testing Phases:
- Reconnaissance: Information gathering (passive and active)
- Scanning: Port scans, vulnerability scans, enumeration
- Exploitation: Gain access (proof-of-concept or full exploitation)
- Post-Exploitation: Lateral movement, privilege escalation, data exfiltration simulation
- Reporting: Findings, risk ratings, remediation recommendations
Deliverables:
- Executive Summary: Business-level overview, risk summary
- Technical Report: Detailed findings, step-by-step reproduction, evidence (screenshots)
- Remediation Guidance: Prioritized fixes, compensating controls
- Retest: Validate fixes after remediation
Purple Team Exercises (IG3):
- Concept: Red team (attackers) and Blue team (defenders) collaborate
- Goal: Improve detection and response (not just find vulnerabilities)
- Process: Red team executes TTPs, Blue team detects, both discuss gaps
- Outcome: Enhanced visibility, tuned alerts, improved runbooks
Red Team vs Penetration Test:
- Penetration Test: Find and report vulnerabilities, time-boxed (2-4 weeks)
- Red Team: Simulate APT, test detection/response, adversary emulation, longer duration (weeks to months)
Compliance Requirements:
- PCI DSS: Annual external pentest, internal if significant changes
- FedRAMP: Annual external, pre-authorization
- HIPAA: Not required but recommended (especially for BAs)
- CMMC: Level 2+ requires periodic assessments
Implementation Guidance
Starting Your CIS Controls Journey
Step 1: Assess Current State (Week 1-2)
- Determine which IG level is appropriate (IG1, IG2, IG3)
- Conduct gap assessment against target IG safeguards
- Identify existing controls and gaps
Step 2: Prioritize Quick Wins (Month 1-3)
- Focus on foundational IG1 safeguards:
- 1.1, 2.1: Asset and software inventory
- 10.1, 10.2: Anti-malware deployment
- 11.2, 11.3: Automated backups
- 7.3: Automated OS patching
- 14.1: Security awareness training
- These provide immediate risk reduction with moderate effort
Step 3: Build Foundation (Month 4-9)
- Implement remaining IG1 safeguards
- Establish governance (policies, procedures, roles)
- Deploy foundational tools (asset management, patch management, backup)
- Document configurations and processes
Step 4: Advance to IG2 (If applicable, Month 10-24)
- Implement IG2 safeguards:
- 5.5: Multi-factor authentication
- 8.9, 8.11: Centralized logging and SIEM
- 12.2: Network segmentation
- 13.2, 13.3: IDS/IPS
- 16.1, 16.2: Secure SDLC
- 18.1, 18.2: Penetration testing
- Focus on enterprise scalability and automation
Step 5: Mature to IG3 (If applicable, Year 2-3)
- Implement IG3 safeguards:
- 10.7: Behavioral anti-malware (EDR)
- 13.11: Alert tuning and threat hunting
- 16.13: Application penetration testing
- 18.5: Internal penetration testing
- Build advanced capabilities (SOC, threat intelligence, purple team)
Step 6: Continuous Improvement (Ongoing)
- Regular assessments (annual or semi-annual)
- Metrics and reporting (dashboard, KPIs)
- Adapt to new threats
- Stay current with CIS Controls updates
Measurement and Metrics
Control Implementation Metrics:
- Percentage of safeguards implemented (by IG level)
- Safeguards in progress vs completed
- Time to implement safeguards (track delays)
Operational Metrics:
- Control 1: % of assets in inventory (goal: >95%)
- Control 7: Mean time to patch (MTTP) - Critical: <15 days, High: <30 days
- Control 8: Log coverage (% of critical assets sending logs)
- Control 10: Malware detection rate, dwell time
- Control 11: Backup success rate (goal: >99%), restore test pass rate
- Control 14: Phishing click rate (goal: <5%), training completion (goal: 100%)
- Control 17: Mean time to detect (MTTD), mean time to respond (MTTR)
Risk Metrics:
- Open vulnerabilities by severity (trend down over time)
- Security incidents (volume, severity, trend)
- Compliance score (overall IG compliance %)
- Third-party risk score
Tools and Technology
Essential Tools for IG1:
- Asset Management: Lansweeper, Spiceworks (free tier)
- Endpoint Protection: Microsoft Defender, Sophos
- Backup: Veeam Community Edition, Windows Backup
- Patch Management: WSUS, SCCM, ManageEngine Patch Manager
- Awareness Training: KnowBe4 (small business tier)
Enterprise Tools for IG2:
- SIEM: Splunk, Elastic Stack, Microsoft Sentinel
- Vulnerability Management: Qualys, Tenable, Rapid7
- EDR: CrowdStrike, SentinelOne, Microsoft Defender for Endpoint
- IDS/IPS: Suricata, Snort, Palo Alto Threat Prevention
- SAST/DAST: Veracode, Checkmarx, OWASP ZAP
Advanced Tools for IG3:
- Threat Intelligence: Recorded Future, Anomali
- SOAR: Splunk Phantom, Palo Alto Cortex XSOAR
- NTA: Darktrace, ExtraHop, Vectra
- Deception: Attivo, TrapX
- Threat Hunting Platform: Sophos MDR, Red Canary
CIS Controls Alignment with Other Frameworks
NIST Cybersecurity Framework (CSF):
- CIS Controls map to all 5 CSF functions (Identify, Protect, Detect, Respond, Recover)
- CIS Controls are more prescriptive (how) vs NIST CSF (what)
NIST 800-53 / 800-171:
- Strong overlap with NIST security controls
- CIS Controls provide implementation guidance for NIST requirements
- IG2/IG3 aligns well with NIST 800-171 for CUI protection
ISO 27001/27002:
- CIS Controls can support ISO 27001 ISMS
- Many safeguards directly map to ISO 27002 controls
- More actionable than ISO (which is principle-based)
PCI DSS:
- CIS Controls IG2 covers most PCI DSS requirements
- Specific gaps: PCI DSS cardholder data environment (CDE) scoping
- CIS provides broader security beyond just payment data
CMMC:
- IG1 ≈ CMMC Level 1 (basic cyber hygiene)
- IG2 ≈ CMMC Level 2 (NIST 800-171, 110 practices)
- IG3 includes additional practices beyond CMMC
HIPAA Security Rule:
- CIS Controls IG2 addresses most HIPAA requirements
- Additional considerations: HIPAA-specific (BAAs, minimum necessary)
Capabilities
- CIS Controls v8 implementation planning and roadmapping
- Implementation Group selection (IG1, IG2, IG3) based on organizational profile
- Gap assessments and compliance scoring
- Safeguard-by-safeguard implementation guidance (all 153 safeguards)
- Control-level deep dives (all 18 controls)
- Tool selection and evaluation
- Metrics and measurement programs
- Framework alignment (NIST, ISO, PCI-DSS, CMMC, HIPAA)
- Continuous improvement and maturity advancement
- Executive reporting and risk communication
- Resource and budget planning
- Vendor and MSSP engagement support
Commands 5
CIS Controls v8 content used under CC BY-SA 4.0 from the Center for Internet Security. This command's CIS-derived content is CC BY-SA 4.0. See LICENSE-CIS.md.
CIS Controls Assessment
Evaluates organizational readiness for CIS Controls v8 baseline security framework.
Arguments
$1- Target Implementation Group (required: IG1, IG2, or IG3)$2- Assessment scope (optional: full, gap-analysis, specific-control)
CIS Controls v8 Implementation Groups
| Group | Target Organizations | Safeguards | Description |
|---|---|---|---|
| IG1 | Small/medium businesses, limited IT/cyber resources | 56 | Essential cyber hygiene, foundational controls |
| IG2 | Medium/large enterprises with IT staff | 128 | Adds enterprise-grade processes and tools |
| IG3 | Large enterprises, high-value assets, skilled adversaries | 153 | Advanced security practices, threat hunting |
IG1 - Essential Cyber Hygiene
- Target: Small to medium businesses
- Resources: Limited IT security expertise
- Focus: Foundational safeguards every organization should implement
- Safeguards: 56 basic security controls
- Examples: Inventory assets, control admin privileges, basic backups
IG2 - Enterprise Security
- Target: Medium to large organizations
- Resources: Dedicated IT security staff
- Focus: Scalable security operations and enterprise tools
- Safeguards: All IG1 + 72 additional (128 total)
- Examples: Centralized logging, automated vulnerability management, SIEM
IG3 - Advanced Security
- Target: Large organizations, critical infrastructure, high-value targets
- Resources: Specialized security teams (SOC, threat intel, IR)
- Focus: Advanced threat detection, response, and recovery
- Safeguards: All IG2 + 25 additional (153 total)
- Examples: Threat hunting, advanced incident response, security testing
18 CIS Controls
-
Inventory and Control of Enterprise Assets (IG1)
- Track all hardware devices
- Address unauthorized assets
-
Inventory and Control of Software Assets (IG1)
- Track authorized software
- Remove unauthorized software
-
Data Protection (IG1)
- Classify data
- Encrypt sensitive data
- Secure data destruction
-
Secure Configuration of Enterprise Assets and Software (IG1)
- Establish secure configurations
- Deploy system configuration management
-
Account Management (IG1)
- Centralized account management
- Strong authentication (MFA)
-
Access Control Management (IG1)
- Least privilege
- Automated access provisioning/deprovisioning
-
Continuous Vulnerability Management (IG1)
- Automated vulnerability scanning
- Remediation process
-
Audit Log Management (IG1)
- Collect audit logs
- Centralize and retain logs
-
Email and Web Browser Protections (IG1)
- Deploy anti-malware
- Web content filtering
-
Malware Defenses (IG1)
- Deploy signature-based detection
- Deploy behavioral-based detection
-
Data Recovery (IG1)
- Establish backup process
- Test data recovery
-
Network Infrastructure Management (IG2)
- Maintain network diagram
- Secure network boundaries
-
Network Monitoring and Defense (IG2)
- Deploy network IDS
- Monitor network traffic
-
Security Awareness and Skills Training (IG1)
- Security awareness training
- Role-based security training
-
Service Provider Management (IG1)
- Inventory service providers
- Manage third-party security
-
Application Software Security (IG2)
- Secure application development
- Vulnerability testing
-
Incident Response Management (IG1)
- Designate incident response team
- Test incident response plan
-
Penetration Testing (IG2)
- Establish penetration testing program
- Conduct regular tests
Assessment Output
- Readiness Score: Overall compliance percentage by IG level
- Control Gaps: Which of the 18 controls need implementation or improvement
- Safeguard Status: Per-safeguard implementation tracking
- IG1: 56 safeguards
- IG2: 128 safeguards (includes IG1)
- IG3: 153 safeguards (includes IG1 + IG2)
- Asset Security Functions: Coverage across 5 functions
- Identify: Asset and software inventory
- Protect: Configuration, access control, data protection
- Detect: Continuous monitoring, audit logs
- Respond: Incident response
- Recover: Data recovery, business continuity
- Implementation Priorities: Quick wins vs long-term projects
- Remediation Roadmap: Phased plan to achieve target IG level
Assessment Methodology
Data Collection:
- Configuration reviews
- Policy and procedure documentation
- Technical control testing
- Interviews with IT/security staff
- Network and system scans
Scoring:
- Per-safeguard implementation status (Not Implemented, Partially Implemented, Implemented)
- Control-level maturity (Ad hoc, Documented, Managed, Optimized)
- Overall IG compliance percentage
Gap Analysis:
- Missing safeguards by priority
- Incomplete implementations
- Documentation gaps
- Tool/technology deficiencies
Examples
# Full IG1 assessment for small business
/cis:assess IG1 full
# Gap analysis for IG2 compliance
/cis:assess IG2 gap-analysis
# Assess specific control implementation
/cis:assess IG2 "Account Management"
# Advanced security assessment for large enterprise
/cis:assess IG3 full
CIS Controls v8 content used under CC BY-SA 4.0 from the Center for Internet Security. This command's CIS-derived content is CC BY-SA 4.0. See LICENSE-CIS.md.
CIS Control Implementation Check
Provides detailed implementation guidance and verification for specific CIS Controls v8 controls.
Arguments
$1- Control number or name (required: 1-18 or control name)$2- Implementation Group level (optional: IG1, IG2, IG3)
The 18 CIS Controls
Control 1: Inventory and Control of Enterprise Assets
IG Level: IG1 | Safeguards: 5 (IG1: 5, IG2: 5, IG3: 5)
Purpose: Actively manage all enterprise assets connected to infrastructure
Key Safeguards:
- 1.1: Establish and maintain detailed enterprise asset inventory (IG1)
- 1.2: Address unauthorized assets (IG1)
- 1.3: Utilize asset management tool (IG1)
- 1.4: Use Dynamic Host Configuration Protocol (DHCP) logging (IG2)
- 1.5: Use Active Discovery Tools (IG3)
Implementation:
- Deploy asset discovery tools (CMDB, network scanner)
- Document all hardware (laptops, servers, network devices, IoT)
- Track location, owner, business purpose
- Automate unauthorized device detection
Common Tools: ServiceNow, Lansweeper, Qualys, Nessus
Control 2: Inventory and Control of Software Assets
IG Level: IG1 | Safeguards: 7 (IG1: 4, IG2: 6, IG3: 7)
Purpose: Actively manage all software on the network
Key Safeguards:
- 2.1: Establish and maintain software inventory (IG1)
- 2.2: Ensure authorized software is currently supported (IG1)
- 2.3: Address unauthorized software (IG1)
- 2.4: Utilize automated software inventory tools (IG1)
- 2.5: Allowlist authorized software (IG2)
- 2.6: Allowlist authorized libraries (IG2)
- 2.7: Allowlist authorized scripts (IG3)
Implementation:
- Software asset management (SAM) tool
- Application whitelisting/allowlisting
- Track version, vendor, support status
- Detect shadow IT
Common Tools: Microsoft Endpoint Manager, Flexera, Snow Software
Control 3: Data Protection
IG Level: IG1 | Safeguards: 14 (IG1: 3, IG2: 11, IG3: 14)
Purpose: Protect data at rest and in transit
Key Safeguards:
- 3.1: Establish and maintain data management process (IG1)
- 3.2: Establish and maintain data inventory (IG1)
- 3.3: Configure data access control lists (IG1)
- 3.4: Enforce data retention (IG1)
- 3.5: Securely dispose of data (IG1)
- 3.6: Encrypt data on end-user devices (IG2)
- 3.7: Establish and maintain data classification scheme (IG2)
- 3.10: Encrypt sensitive data in transit (IG2)
- 3.11: Encrypt sensitive data at rest (IG2)
- 3.12: Segment data processing and storage (IG2)
Implementation:
- Data classification policy
- Encryption (BitLocker, FileVault, TLS 1.2+)
- Data loss prevention (DLP)
- Secure deletion procedures
Common Tools: Microsoft Purview, Varonis, Symantec DLP
Control 4: Secure Configuration of Enterprise Assets and Software
IG Level: IG1 | Safeguards: 12 (IG1: 5, IG2: 10, IG3: 12)
Purpose: Establish and maintain secure configurations
Key Safeguards:
- 4.1: Establish and maintain secure configuration process (IG1)
- 4.2: Establish and maintain secure configuration baseline (IG1)
- 4.3: Configure automatic session locking (IG1)
- 4.4: Implement and manage firewall (IG1)
- 4.5: Implement and manage DMZ (IG2)
- 4.7: Manage default accounts (IG1)
- 4.8: Uninstall or disable unnecessary services (IG2)
Implementation:
- CIS Benchmarks, DISA STIGs
- Configuration management tools
- Hardening scripts
- Regular configuration audits
Common Tools: CIS-CAT Pro, Ansible, Puppet, Chef
Control 5: Account Management
IG Level: IG1 | Safeguards: 6 (IG1: 4, IG2: 6, IG3: 6)
Purpose: Manage lifecycle of system and application accounts
Key Safeguards:
- 5.1: Establish and maintain inventory of accounts (IG1)
- 5.2: Use unique passwords (IG1)
- 5.3: Disable dormant accounts (IG1)
- 5.4: Restrict administrator privileges (IG1)
- 5.5: Establish and maintain MFA (IG2)
- 5.6: Centralize account management (IG2)
Implementation:
- Identity and Access Management (IAM)
- Multi-factor authentication (MFA)
- Privileged Access Management (PAM)
- Regular access reviews
Common Tools: Active Directory, Okta, Duo, CyberArk
Control 6: Access Control Management
IG Level: IG1 | Safeguards: 8 (IG1: 3, IG2: 6, IG3: 8)
Purpose: Apply the principle of least privilege
Key Safeguards:
- 6.1: Establish access granting process (IG1)
- 6.2: Establish access revoking process (IG1)
- 6.3: Require MFA for externally-exposed applications (IG1)
- 6.4: Require MFA for remote access (IG1)
- 6.5: Require MFA for administrative access (IG2)
- 6.7: Centralize access control (IG2)
- 6.8: Define and maintain role-based access control (IG2)
Implementation:
- Role-based access control (RBAC)
- Just-in-time access
- Separation of duties
- Automated provisioning/deprovisioning
Common Tools: SailPoint, Saviynt, Azure AD
Control 7: Continuous Vulnerability Management
IG Level: IG1 | Safeguards: 7 (IG1: 3, IG2: 6, IG3: 7)
Purpose: Develop process to continuously identify and remediate vulnerabilities
Key Safeguards:
- 7.1: Establish and maintain vulnerability management process (IG1)
- 7.2: Establish and maintain remediation process (IG1)
- 7.3: Perform automated operating system patch management (IG1)
- 7.4: Perform automated application patch management (IG1)
- 7.5: Perform automated vulnerability scans (IG2)
- 7.6: Perform automated vulnerability scans of internal networks (IG2)
- 7.7: Remediate detected vulnerabilities (IG2)
Implementation:
- Vulnerability scanning (authenticated, unauthenticated)
- Patch management automation
- Risk-based prioritization
- SLA-based remediation
Common Tools: Qualys VMDR, Tenable.io, Rapid7 InsightVM
Control 8: Audit Log Management
IG Level: IG1 | Safeguards: 12 (IG1: 5, IG2: 10, IG3: 12)
Purpose: Collect, alert, review, and retain audit logs
Key Safeguards:
- 8.1: Establish and maintain audit log management process (IG1)
- 8.2: Collect audit logs (IG1)
- 8.3: Ensure adequate audit log storage (IG1)
- 8.5: Collect detailed audit logs (IG2)
- 8.6: Collect DNS query audit logs (IG2)
- 8.9: Centralize audit logs (IG2)
- 8.10: Retain audit logs (IG2)
- 8.11: Conduct audit log reviews (IG2)
Implementation:
- Centralized logging (SIEM)
- Log retention (1 year minimum)
- Automated alerting
- Regular log review
Common Tools: Splunk, Elastic Stack, Microsoft Sentinel
Control 9: Email and Web Browser Protections
IG Level: IG1 | Safeguards: 7 (IG1: 4, IG2: 6, IG3: 7)
Purpose: Protect against attacks via email and web browsers
Key Safeguards:
- 9.1: Ensure use of only fully supported browsers and email clients (IG1)
- 9.2: Use DNS filtering services (IG1)
- 9.3: Maintain and enforce network-based URL filters (IG1)
- 9.4: Restrict unnecessary browser and email client extensions (IG1)
- 9.5: Implement DMARC (IG2)
- 9.6: Block unnecessary file types (IG2)
- 9.7: Deploy and maintain email server anti-malware (IG2)
Implementation:
- Email security gateway
- Web content filtering
- DMARC, SPF, DKIM
- Browser isolation
Common Tools: Proofpoint, Mimecast, Cisco Umbrella, Zscaler
Control 10: Malware Defenses
IG Level: IG1 | Safeguards: 7 (IG1: 2, IG2: 5, IG3: 7)
Purpose: Prevent and control malware installation and execution
Key Safeguards:
- 10.1: Deploy and maintain anti-malware software (IG1)
- 10.2: Configure automatic anti-malware signature updates (IG1)
- 10.3: Disable autorun and autoplay (IG1)
- 10.4: Configure automatic anti-malware scanning (IG1)
- 10.5: Enable anti-exploitation features (IG2)
- 10.6: Centrally manage anti-malware software (IG2)
- 10.7: Use behavior-based anti-malware software (IG3)
Implementation:
- Endpoint protection platform (EPP)
- Endpoint detection and response (EDR)
- Application control
- Behavioral analysis
Common Tools: CrowdStrike Falcon, Microsoft Defender, SentinelOne
Control 11: Data Recovery
IG Level: IG1 | Safeguards: 5 (IG1: 4, IG2: 5, IG3: 5)
Purpose: Establish and maintain data recovery practices
Key Safeguards:
- 11.1: Establish and maintain data recovery process (IG1)
- 11.2: Perform automated backups (IG1)
- 11.3: Protect recovery data (IG1)
- 11.4: Establish and maintain isolated instance of recovery data (IG1)
- 11.5: Test data recovery (IG2)
Implementation:
- Automated backup solution (3-2-1 rule)
- Immutable/air-gapped backups
- Regular restore testing
- Ransomware-resilient backups
Common Tools: Veeam, Commvault, Rubrik, AWS Backup
Control 12: Network Infrastructure Management
IG Level: IG2 | Safeguards: 8 (IG1: 0, IG2: 6, IG3: 8)
Purpose: Establish, implement, and actively manage network devices
Key Safeguards:
- 12.1: Ensure network infrastructure is up-to-date (IG2)
- 12.2: Establish and maintain secure network architecture (IG2)
- 12.3: Securely manage network infrastructure (IG2)
- 12.4: Establish and maintain network architecture diagram (IG2)
- 12.6: Use secure network management protocols (IG2)
- 12.7: Ensure remote devices use VPN (IG2)
- 12.8: Establish and maintain dedicated computing for admin (IG3)
Implementation:
- Network segmentation (VLANs)
- Secure protocols (SSH, SNMPv3)
- Network diagram documentation
- Jump boxes for administration
Common Tools: Cisco ISE, Palo Alto Networks, Fortinet
Control 13: Network Monitoring and Defense
IG Level: IG2 | Safeguards: 11 (IG1: 0, IG2: 8, IG3: 11)
Purpose: Operate processes and tooling to detect and prevent network-based attacks
Key Safeguards:
- 13.1: Centralize security event alerting (IG2)
- 13.2: Deploy network-based IDS (IG2)
- 13.3: Deploy network-based IPS (IG2)
- 13.4: Perform traffic filtering (IG2)
- 13.6: Collect network traffic flow logs (IG2)
- 13.8: Deploy network-based anti-malware (IG2)
- 13.10: Perform application layer filtering (IG3)
- 13.11: Tune security event alerting thresholds (IG3)
Implementation:
- Intrusion detection/prevention (IDS/IPS)
- Network traffic analysis (NTA)
- Next-gen firewall (NGFW)
- Security orchestration (SOAR)
Common Tools: Darktrace, ExtraHop, Palo Alto NGFW
Control 14: Security Awareness and Skills Training
IG Level: IG1 | Safeguards: 9 (IG1: 3, IG2: 7, IG3: 9)
Purpose: Establish security awareness training program
Key Safeguards:
- 14.1: Establish and maintain security awareness program (IG1)
- 14.2: Train workforce members on secure authentication (IG1)
- 14.3: Train workforce on data handling (IG1)
- 14.4: Train workforce on identifying social engineering attacks (IG1)
- 14.5: Train workforce on authentication best practices (IG2)
- 14.6: Train workforce on identifying and reporting incidents (IG2)
- 14.9: Conduct role-specific security training (IG3)
Implementation:
- Annual security awareness training
- Phishing simulation campaigns
- Role-based training (developers, admins)
- Security champions program
Common Tools: KnowBe4, Proofpoint Security Awareness, SANS Securing The Human
Control 15: Service Provider Management
IG Level: IG1 | Safeguards: 7 (IG1: 2, IG2: 5, IG3: 7)
Purpose: Manage security risks from service providers
Key Safeguards:
- 15.1: Establish and maintain inventory of service providers (IG1)
- 15.2: Establish and maintain service provider management policy (IG1)
- 15.3: Classify service providers (IG2)
- 15.4: Ensure service provider contracts include security requirements (IG2)
- 15.5: Assess service providers (IG2)
- 15.6: Monitor service providers (IG2)
- 15.7: Securely decommission service providers (IG3)
Implementation:
- Vendor risk management program
- Security questionnaires
- Right-to-audit clauses
- Regular vendor assessments
Common Tools: OneTrust, ServiceNow VRM, BitSight, SecurityScorecard
Control 16: Application Software Security
IG Level: IG2 | Safeguards: 14 (IG1: 0, IG2: 10, IG3: 14)
Purpose: Manage security lifecycle of in-house developed and acquired software
Key Safeguards:
- 16.1: Establish and maintain secure application development process (IG2)
- 16.2: Establish and maintain secure software development practices (IG2)
- 16.3: Perform root cause analysis on security vulnerabilities (IG2)
- 16.5: Use up-to-date and trusted third-party components (IG2)
- 16.6: Establish and maintain SBOM (IG2)
- 16.7: Use standard hardening configuration templates (IG2)
- 16.11: Leverage vetted modules or services (IG3)
- 16.13: Conduct application penetration testing (IG3)
Implementation:
- Secure SDLC
- Static/dynamic application security testing (SAST/DAST)
- Software composition analysis (SCA)
- Code review and penetration testing
Common Tools: Veracode, Checkmarx, Snyk, OWASP ZAP
Control 17: Incident Response Management
IG Level: IG1 | Safeguards: 9 (IG1: 4, IG2: 7, IG3: 9)
Purpose: Establish process to detect and respond to cybersecurity incidents
Key Safeguards:
- 17.1: Designate personnel to manage incident handling (IG1)
- 17.2: Establish and maintain contact information (IG1)
- 17.3: Establish and maintain enterprise process for reporting incidents (IG1)
- 17.4: Establish and maintain incident response process (IG1)
- 17.5: Assign key roles and responsibilities (IG2)
- 17.6: Define mechanisms for communicating during incident response (IG2)
- 17.7: Conduct routine incident response exercises (IG2)
- 17.9: Establish and maintain security incident thresholds (IG3)
Implementation:
- Incident response plan
- IR team (CSIRT/SOC)
- Tabletop exercises
- Playbooks for common scenarios
Common Tools: TheHive, Cortex XSOAR, PagerDuty, Jira
Control 18: Penetration Testing
IG Level: IG2 | Safeguards: 5 (IG1: 0, IG2: 3, IG3: 5)
Purpose: Test security of enterprise assets through real-world attack techniques
Key Safeguards:
- 18.1: Establish and maintain penetration testing program (IG2)
- 18.2: Perform periodic external penetration tests (IG2)
- 18.3: Remediate penetration test findings (IG2)
- 18.4: Validate security measures (IG2)
- 18.5: Perform periodic internal penetration tests (IG3)
Implementation:
- Annual penetration testing (external/internal)
- Red team exercises
- Purple team exercises
- Remediation tracking
Common Tools: Metasploit, Cobalt Strike, Burp Suite, Core Impact
Verification Checklist
For each control, verify:
- Policy Documentation: Written policies and procedures exist
- Implementation: Technical controls are configured and operational
- Evidence: Artifacts demonstrate control effectiveness
- Testing: Controls are regularly validated
- Metrics: Measurement and reporting in place
Examples
# Check Account Management (Control 5) implementation
/cis:control-check 5
# Verify Data Protection (Control 3) for IG2
/cis:control-check "Data Protection" IG2
# Assess Incident Response Management
/cis:control-check 17 IG1
# Review all Malware Defenses safeguards
/cis:control-check "Malware Defenses" IG3
CIS Controls v8 Evidence Checklist
Generates comprehensive evidence collection checklists for CIS Controls v8 safeguards, organized by Implementation Group (IG1, IG2, IG3) with automated and manual collection guidance.
Never commit evidence artifacts to source control. The outputs below include real usernames, credential reports, MFA device states, and privileged-account inventories.
.gitignorecoversevidence/by default sogit add -Awill not sweep it up, but durable storage is your responsibility. Use an encrypted, access-controlled evidence locker (encrypted S3 with least-privilege IAM, a GRC platform, or a shared drive with full-disk encryption and MFA-gated access).
Usage
/cis-controls:evidence-checklist <safeguard-id> [--ig-level <1|2|3>] [--export <format>]
Arguments
<safeguard-id>: CIS safeguard (e.g., "1.1", "5.2", "8.3") or domain (e.g., "Asset Management", "Access Control")--ig-level: Filter by Implementation Group (1, 2, or 3). Default: all applicable--export: Export format (json,csv,markdown). Default:markdown
Example: Single Safeguard Evidence
/cis-controls:evidence-checklist 5.1 --ig-level 1
Output:
CIS Controls v8 Evidence Checklist
Safeguard: 5.1 - Establish and Maintain an Inventory of Accounts
Implementation Group: IG1 (Basic Cyber Hygiene)
Asset Type: Users
Security Function: Identify
## Control Description
Establish and maintain an inventory of all accounts managed in the enterprise. The inventory must include both user and administrator accounts. The inventory, at a minimum, should contain the person's name, username, start date, and end date.
## Evidence Requirements
### Required Documentation
□ Account Management Policy
- Document account lifecycle procedures
- Include approval processes
- Define account types (standard, privileged, service, shared)
- Update frequency: Annually or when procedures change
- Approver: IT Director or CISO
□ Account Inventory Procedures
- Step-by-step account creation process
- Step-by-step account modification process
- Step-by-step account deletion process
- Include screenshots or workflow diagrams
### Automated Evidence Collection
✓ **Complete Account Inventory (Primary Evidence)**
```bash
# AWS IAM Users
aws iam list-users --output json > evidence/cis-5.1-iam-users-$(date +%Y%m%d).json
aws iam get-credential-report > evidence/cis-5.1-credential-report-$(date +%Y%m%d).csv
# Azure AD Users
az ad user list --output json > evidence/cis-5.1-azure-users-$(date +%Y%m%d).json
# Google Workspace Users
gcloud identity groups memberships list --group-email=all-users@company.com \
--format=json > evidence/cis-5.1-gcp-users-$(date +%Y%m%d).json
# Linux/Unix Systems (if applicable)
sudo cat /etc/passwd | awk -F: '{print $1,$3,$5}' > evidence/cis-5.1-local-accounts-$(date +%Y%m%d).txt
# Windows Active Directory (if applicable)
Get-ADUser -Filter * -Properties DisplayName,SamAccountName,Created,LastLogonDate,Enabled |
Export-Csv evidence/cis-5.1-ad-users-$(date +%Y%m%d).csv -NoTypeInformation
Collection Frequency: Monthly snapshot Retention: 12 months minimum
✓ Privileged Account Inventory
# AWS Admin Accounts
aws iam list-users | jq '.Users[] | select(.PermissionsBoundary != null or .Tags[]? | select(.Key == "PrivilegedAccess"))' \
> evidence/cis-5.1-privileged-aws-$(date +%Y%m%d).json
# Azure Privileged Accounts
az ad user list --filter "userType eq 'Admin'" --output json \
> evidence/cis-5.1-privileged-azure-$(date +%Y%m%d).json
# List of users with sudo access (Linux)
sudo grep -r "^[^#]" /etc/sudoers /etc/sudoers.d/ > evidence/cis-5.1-sudo-users-$(date +%Y%m%d).txt
Collection Frequency: Weekly snapshot Retention: 12 months minimum
✓ Service Account Inventory
# AWS Service Accounts (IAM roles)
aws iam list-roles --output json > evidence/cis-5.1-service-roles-$(date +%Y%m%d).json
# Azure Service Principals
az ad sp list --all --output json > evidence/cis-5.1-service-principals-$(date +%Y%m%d).json
# GCP Service Accounts
gcloud iam service-accounts list --format=json \
> evidence/cis-5.1-gcp-service-accounts-$(date +%Y%m%d).json
Collection Frequency: Monthly snapshot Retention: 12 months minimum
✓ Account Creation/Modification Logs
# AWS CloudTrail for IAM events
aws cloudtrail lookup-events \
--lookup-attributes AttributeKey=EventName,AttributeValue=CreateUser \
--start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
--output json > evidence/cis-5.1-account-creation-$(date +%Y%m%d).json
aws cloudtrail lookup-events \
--lookup-attributes AttributeKey=EventName,AttributeValue=DeleteUser \
--start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
--output json > evidence/cis-5.1-account-deletion-$(date +%Y%m%d).json
# Azure AD Audit Logs
az monitor activity-log list \
--caller 'Microsoft.Authorization' \
--start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
--output json > evidence/cis-5.1-azure-audit-$(date +%Y%m%d).json
Collection Frequency: Monthly Retention: 12 months minimum
Manual Evidence Collection
□ Account Inventory Validation
- Review automated inventory exports
- Verify completeness (100% of accounts included)
- Check for orphaned/unknown accounts
- Document any discrepancies found
- Evidence: Validation report with sign-off
- Frequency: Quarterly
□ Account Creation Approvals (Sample)
- Sample size: 25 accounts created in last quarter
- Required elements:
- Original request ticket/email
- Manager approval
- IT approval (if separate)
- Account creation date matching approval date (+/- 5 days)
- Evidence: Folder of approval tickets/emails
- Frequency: Quarterly review
□ Account Termination Evidence (Sample)
- Sample size: All terminations in last quarter or 25 (whichever is less)
- Required elements:
- HR termination notice
- Account disabled/deleted within 24 hours of termination
- Access revocation confirmation
- Evidence: Folder of termination tickets + IAM deletion logs
- Frequency: Quarterly review
□ Orphaned Account Review
- Review accounts with no recent activity (>90 days)
- Document justification or schedule for deletion
- Evidence: Orphaned account report with disposition
- Frequency: Quarterly
Adequacy Criteria (Assessment Guidance)
IG1 Requirements (Scored)
✓ Account inventory exists and is documented ✓ Inventory includes at minimum:
- Full name
- Username/email
- Account creation date
- Account type (user/admin/service) ✓ Inventory updated at least quarterly ✓ Evidence retention: 12 months minimum
IG2 Additional Requirements
✓ Automated inventory collection (not manual spreadsheets) ✓ Privileged accounts identified separately ✓ Service accounts tracked separately ✓ Account creation/deletion audit trail ✓ Quarterly validation of inventory completeness
IG3 Additional Requirements
✓ Real-time or weekly inventory updates ✓ Automated orphaned account detection ✓ Integration with HR system for terminations ✓ Automated alerting for policy violations ✓ Continuous monitoring dashboard
Common Assessment Findings
Critical Findings
❌ No account inventory exists ❌ Inventory missing >25% of actual accounts ❌ No evidence of account deletion process ❌ Shared accounts not tracked or monitored
Moderate Findings
⚠️ Inventory incomplete (missing 10-25% of accounts) ⚠️ Manual inventory (spreadsheets) instead of automated ⚠️ Service accounts not inventoried separately ⚠️ Inventory not updated in >6 months
Minor Findings
⚠️ Inventory missing optional fields (last login, department) ⚠️ Orphaned account review not documented ⚠️ Evidence retention <12 months
Remediation Guidance
If No Inventory Exists
-
Immediate Actions (Week 1)
- Run automated collection scripts above
- Export all accounts from all systems
- Create initial inventory spreadsheet
-
Short-term (Weeks 2-4)
- Document account management procedures
- Establish quarterly review process
- Set up automated monthly snapshots
-
Long-term (Months 2-3)
- Implement automated inventory tools (AWS Config, Azure Policy, etc.)
- Integrate with HR system for auto-deprovisioning
- Build compliance dashboard
If Inventory Incomplete
- Identify missing systems/platforms
- Run discovery scans (Nmap, network inventory)
- Cross-reference with asset inventory (CIS 1.1)
- Update procedures to include all systems
Cross-References
Related CIS Safeguards
- 1.1 - Establish and Maintain Detailed Enterprise Asset Inventory
- 4.1 - Establish and Maintain a Secure Configuration Process
- 6.1 - Establish an Access Granting Process
- 6.2 - Establish an Access Revoking Process
- 6.8 - Define and Maintain Role-Based Access Control
Maps to Other Frameworks
- NIST 800-53: AC-2 (Account Management), IA-4 (Identifier Management)
- ISO 27001:2022: A.5.15 (Access control), A.5.18 (Access rights)
- SOC 2: CC6.1 (Logical and physical access controls)
- PCI-DSS v4: 8.2.1 (User identification management)
- CMMC 2.0: AC.L2-3.1.1 (Authorized access control)
Cost Estimates
IG1 Implementation
- Initial setup: 40 hours ($4,000 @ $100/hr)
- Quarterly maintenance: 8 hours/quarter ($800/quarter)
- Tools: AWS Config / Azure Policy (included) or open-source
IG2 Implementation
- Initial setup: 80 hours ($8,000 @ $100/hr)
- Monthly maintenance: 4 hours/month ($400/month)
- Tools: Identity governance platform ($5k-$15k/year for SMB)
IG3 Implementation
- Initial setup: 120 hours ($12,000 @ $100/hr)
- Continuous monitoring: 2 hours/week ($800/month)
- Tools: Enterprise IGA solution ($25k-$100k/year)
Evidence Package Structure
evidence/
└── cis-5.1-account-inventory/
├── 2025-01/
│ ├── automated/
│ │ ├── iam-users-20250115.json
│ │ ├── credential-report-20250115.csv
│ │ ├── privileged-accounts-20250115.json
│ │ └── cloudtrail-account-events-20250115.json
│ ├── manual/
│ │ ├── account-inventory-policy-v1.2.pdf
│ │ ├── account-procedures-2025.docx
│ │ ├── quarterly-validation-Q1-2025.pdf
│ │ └── approval-samples-Q1-2025/
│ │ ├── account-request-001.pdf
│ │ ├── account-request-002.pdf
│ │ └── ... (25 samples)
│ └── screenshots/
│ ├── aws-iam-console-20250115.png
│ └── access-analyzer-findings-20250115.png
└── README.md (evidence index)
Automation Script
#!/usr/bin/env python3
"""
CIS 5.1 Evidence Collection Automation
Collects account inventory evidence from AWS, Azure, GCP
"""
import boto3
import json
import subprocess
from datetime import datetime
import os
class CIS51EvidenceCollector:
def __init__(self, output_dir="evidence/cis-5.1"):
self.output_dir = output_dir
self.timestamp = datetime.now().strftime("%Y%m%d")
os.makedirs(f"{output_dir}/automated", exist_ok=True)
def collect_aws_accounts(self):
"""Collect AWS IAM user inventory"""
iam = boto3.client('iam')
# Get all users
users = iam.list_users()['Users']
output_file = f"{self.output_dir}/automated/aws-iam-users-{self.timestamp}.json"
with open(output_file, 'w') as f:
json.dump(users, f, indent=2, default=str)
print(f"✓ Collected {len(users)} AWS IAM users -> {output_file}")
# Get credential report
iam.generate_credential_report()
report = iam.get_credential_report()
report_file = f"{self.output_dir}/automated/aws-credential-report-{self.timestamp}.csv"
with open(report_file, 'wb') as f:
f.write(report['Content'])
print(f"✓ Generated AWS credential report -> {report_file}")
return len(users)
def collect_privileged_accounts(self):
"""Identify and collect privileged account inventory"""
iam = boto3.client('iam')
# Find users with admin policies
admin_users = []
for user in iam.list_users()['Users']:
username = user['UserName']
# Check attached policies
attached = iam.list_attached_user_policies(UserName=username)
for policy in attached['AttachedPolicies']:
if 'Admin' in policy['PolicyName']:
admin_users.append({
'username': username,
'policy': policy['PolicyName'],
'created': user['CreateDate']
})
output_file = f"{self.output_dir}/automated/privileged-accounts-{self.timestamp}.json"
with open(output_file, 'w') as f:
json.dump(admin_users, f, indent=2, default=str)
print(f"✓ Identified {len(admin_users)} privileged accounts -> {output_file}")
return len(admin_users)
def generate_evidence_report(self, total_users, privileged_count):
"""Generate summary evidence report"""
report = f"""
CIS Controls v8 - Safeguard 5.1 Evidence Report
Generated: {datetime.now().strftime("%Y-%m-%d %H:%M:%S")}
ACCOUNT INVENTORY SUMMARY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total Accounts: {total_users}
Privileged Accounts: {privileged_count} ({privileged_count/total_users*100:.1f}%)
Service Accounts: (manual review required)
EVIDENCE COLLECTED
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✓ Complete IAM user inventory
✓ Credential report with last login dates
✓ Privileged account identification
✓ CloudTrail account creation/deletion logs
COMPLIANCE STATUS: ✓ COMPLIANT (IG1)
NEXT ACTIONS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
□ Quarterly validation review (next due: {(datetime.now().replace(month=datetime.now().month+3)).strftime("%Y-%m-%d")})
□ Collect approval samples (25 accounts)
□ Review orphaned accounts (>90 days inactive)
□ Update account management policy (annual)
Evidence stored in: {self.output_dir}/
"""
report_file = f"{self.output_dir}/evidence-report-{self.timestamp}.txt"
with open(report_file, 'w') as f:
f.write(report)
print(f"\n{report}")
print(f"Full report: {report_file}")
if __name__ == "__main__":
collector = CIS51EvidenceCollector()
print("CIS 5.1 Evidence Collection Starting...")
print("=" * 50)
total = collector.collect_aws_accounts()
privileged = collector.collect_privileged_accounts()
collector.generate_evidence_report(total, privileged)
print("\n✓ Evidence collection complete!")
Quick Reference
| Evidence Type | Collection Method | Frequency | Retention |
|---|---|---|---|
| Account inventory | Automated (AWS CLI) | Monthly | 12 months |
| Privileged accounts | Automated (AWS CLI) | Weekly | 12 months |
| Service accounts | Automated (AWS CLI) | Monthly | 12 months |
| Account creation logs | CloudTrail | Monthly | 12 months |
| Account approvals (sample) | Manual (tickets) | Quarterly | 12 months |
| Termination evidence (sample) | Manual (HR + logs) | Quarterly | 12 months |
| Inventory validation | Manual (review) | Quarterly | 12 months |
| Policy documentation | Manual (document) | Annual | 3 years |
Implementation Priority: 🔴 CRITICAL (IG1 Requirement) Typical Assessment Weight: HIGH (Foundational control) Estimated Implementation Time: 2-6 weeks (depending on IG level)
CIS Controls v8 content used under CC BY-SA 4.0 from the Center for Internet Security. This command's CIS-derived content is CC BY-SA 4.0. See LICENSE-CIS.md.
CIS Controls IG Selection
Helps determine the appropriate Implementation Group (IG1, IG2, or IG3) for your organization based on size, resources, risk profile, and adversary sophistication.
Arguments
$1- Organization size (optional: small, medium, large)$2- Risk profile (optional: low, moderate, high, critical)
Implementation Group Decision Framework
IG1 - Essential Cyber Hygiene (56 Safeguards)
Recommended For:
- Small to medium businesses (<100 employees)
- Limited IT security resources (1-2 IT staff, no dedicated security team)
- Standard business risk profile
- Not targeted by advanced persistent threats
- Limited regulatory compliance requirements
Resource Requirements:
- Part-time security focus (can be handled by IT staff)
- Basic security tools (antivirus, firewall, backup)
- Budget: $10K-$50K annually
- Minimal specialized expertise needed
Threat Profile:
- Opportunistic attacks (phishing, ransomware)
- Automated scanning/exploitation
- Commodity malware
- Script kiddies, unsophisticated attackers
Example Organizations:
- Local retailers
- Professional services firms
- Small healthcare practices
- Regional nonprofits
- Educational institutions (K-12)
IG2 - Enterprise Security (128 Safeguards)
Recommended For:
- Medium to large organizations (100-1,000 employees)
- Dedicated IT team with security responsibilities
- Moderate regulatory requirements (HIPAA, PCI-DSS, etc.)
- Handle sensitive customer or business data
- Potential target for more sophisticated attacks
Resource Requirements:
- Dedicated security staff (1-3 FTEs)
- Enterprise security tools (SIEM, EDR, vulnerability scanner)
- Budget: $100K-$500K annually
- Some specialized security expertise
Threat Profile:
- Targeted phishing campaigns
- Financially motivated cybercriminals
- Ransomware groups
- Industrial espionage
- Nation-state actors (lower tier)
Example Organizations:
- Mid-sized healthcare systems
- Financial services companies
- Manufacturing firms
- Regional government agencies
- SaaS providers
IG3 - Advanced Security (153 Safeguards)
Recommended For:
- Large enterprises (1,000+ employees)
- Critical infrastructure organizations
- High-value assets or intellectual property
- Stringent regulatory requirements (CMMC L3, critical infrastructure)
- Known targets of sophisticated adversaries
Resource Requirements:
- Security Operations Center (SOC) team (5+ FTEs)
- Advanced security tools (threat intelligence, behavioral analysis, SOAR)
- Budget: $1M+ annually
- Highly specialized security expertise (threat hunters, forensics, IR)
Threat Profile:
- Advanced Persistent Threats (APTs)
- Nation-state actors
- Sophisticated cybercriminal organizations
- Insider threats
- Supply chain attacks
Example Organizations:
- Fortune 500 companies
- Defense contractors
- Major healthcare systems
- Critical infrastructure (energy, utilities, transportation)
- Large financial institutions
Selection Criteria Matrix
| Factor | IG1 | IG2 | IG3 |
|---|---|---|---|
| Employees | <100 | 100-1,000 | 1,000+ |
| IT Staff | 1-2 generalists | 3-10 with security focus | 10+ dedicated security |
| Annual Revenue | <$10M | $10M-$1B | $1B+ |
| Data Sensitivity | Basic business data | Customer PII, PHI | Trade secrets, critical infrastructure |
| Regulatory | Minimal | Moderate (HIPAA, SOX) | High (CMMC, NERC CIP) |
| Threat Level | Opportunistic | Targeted | Advanced/persistent |
| Security Budget | <$50K | $100K-$500K | $1M+ |
| Downtime Tolerance | Hours-days | Hours | Minutes |
Progressive Implementation Approach
Organizations should consider a phased approach:
Phase 1: Implement IG1 (Foundation)
- Timeline: 6-12 months
- Focus: Essential cyber hygiene
- Quick wins with high impact
Phase 2: Advance to IG2 (If needed)
- Timeline: 12-24 months
- Focus: Enterprise processes and automation
- Build on IG1 foundation
Phase 3: Advance to IG3 (If needed)
- Timeline: 24-36 months
- Focus: Advanced threat detection and response
- Mature security operations
Risk-Based Considerations
High-Risk Factors (may warrant higher IG):
- Handles sensitive data (PII, PHI, financial, IP)
- Critical infrastructure sector
- Known target of sophisticated threats
- High-profile or controversial organization
- Supply chain for critical industries
- Regulatory enforcement history
Offsetting Factors (may allow lower IG):
- Limited attack surface (air-gapped, isolated)
- Strong compensating controls
- Cyber insurance requirements met
- Managed security service provider (MSSP) support
- Cloud-native with strong CSP security
Industry Benchmarks
Healthcare:
- Small practices: IG1
- Mid-sized systems: IG2
- Large hospital networks: IG3
Financial Services:
- Credit unions: IG1-IG2
- Regional banks: IG2
- National banks: IG3
Manufacturing:
- Job shops: IG1
- Mid-market: IG2
- OEMs with IP: IG3
Technology:
- Startups: IG1
- Growth stage: IG2
- Enterprise SaaS: IG3
Output
- Recommended IG Level: IG1, IG2, or IG3
- Justification: Factors driving the recommendation
- Resource Requirements: Estimated staff, budget, tools needed
- Safeguard Count: How many controls to implement (56, 128, or 153)
- Implementation Timeline: Realistic timeframe to reach target IG
- Cost-Benefit Analysis: Security value vs implementation cost
- Progressive Path: If starting lower, roadmap to advance IG levels
Examples
# Determine IG for small healthcare practice
/cis:ig-select small moderate
# Assess IG needs for large financial institution
/cis:ig-select large critical
# Evaluate IG requirements for medium manufacturer
/cis:ig-select medium moderate
# General IG selection guidance
/cis:ig-select
CIS Controls v8 content used under CC BY-SA 4.0 from the Center for Internet Security. This command's CIS-derived content is CC BY-SA 4.0. See LICENSE-CIS.md.
CIS Controls Safeguard List
Provides comprehensive listing of CIS Controls v8 safeguards organized by Implementation Group (IG1, IG2, IG3).
Arguments
$1- Implementation Group (required: IG1, IG2, or IG3)$2- Control filter (optional: control number 1-18 or "all")
Safeguard Distribution
| Implementation Group | Total Safeguards | Incremental | Cumulative |
|---|---|---|---|
| IG1 | 56 | 56 new | 56 total |
| IG2 | 72 additional | 72 new | 128 total |
| IG3 | 25 additional | 25 new | 153 total |
IG1 - Essential Cyber Hygiene (56 Safeguards)
Foundational Controls
These 56 safeguards represent the minimum baseline for cybersecurity. All organizations should implement IG1 regardless of size or industry.
Controls Introduced at IG1:
- Control 1: Inventory and Control of Enterprise Assets (5 safeguards)
- Control 2: Inventory and Control of Software Assets (4 safeguards)
- Control 3: Data Protection (3 safeguards)
- Control 4: Secure Configuration (5 safeguards)
- Control 5: Account Management (4 safeguards)
- Control 6: Access Control Management (3 safeguards)
- Control 7: Continuous Vulnerability Management (3 safeguards)
- Control 8: Audit Log Management (5 safeguards)
- Control 9: Email and Web Browser Protections (4 safeguards)
- Control 10: Malware Defenses (2 safeguards)
- Control 11: Data Recovery (4 safeguards)
- Control 14: Security Awareness and Skills Training (3 safeguards)
- Control 15: Service Provider Management (2 safeguards)
- Control 17: Incident Response Management (4 safeguards)
Key IG1 Safeguards (High Priority):
1.1 - Establish and Maintain Detailed Enterprise Asset Inventory
- Track all hardware assets
- Include workstations, servers, network devices, IoT
- Document owner, location, function
2.1 - Establish and Maintain Software Inventory
- Track all authorized software
- Include applications, operating systems, firmware
- Version tracking and support status
3.1 - Establish and Maintain Data Management Process
- Data handling procedures
- Classification guidelines
- Retention and disposal
4.1 - Establish and Maintain Secure Configuration Process
- Configuration baselines
- Hardening standards (CIS Benchmarks)
- Change control
5.1 - Establish and Maintain Inventory of Accounts
- All user and service accounts
- Privileged account tracking
- Regular review process
5.3 - Disable Dormant Accounts
- Identify inactive accounts (45-90 days)
- Automated detection
- Disable or delete process
5.4 - Restrict Administrator Privileges to Dedicated Accounts
- Separate admin and user accounts
- Privileged access management
- Principle of least privilege
6.1 - Establish Access Granting Process
- Formal access request/approval
- Manager authorization
- Documentation
6.2 - Establish Access Revoking Process
- Termination procedures
- Role change procedures
- Regular access reviews
7.1 - Establish and Maintain Vulnerability Management Process
- Scanning schedule
- Prioritization criteria
- Remediation SLAs
7.3 - Perform Automated Operating System Patch Management
- Automated OS patching
- Critical patches within 30 days
- Regular patch cycles
8.2 - Collect Audit Logs
- System and application logs
- Authentication events
- Administrative actions
9.2 - Use DNS Filtering Services
- Block malicious domains
- Threat intelligence feeds
- Real-time protection
10.1 - Deploy and Maintain Anti-Malware Software
- All endpoints protected
- Real-time scanning
- Centrally managed
11.2 - Perform Automated Backups
- Automated backup schedule
- Critical data identified
- 3-2-1 backup rule
11.3 - Protect Recovery Data
- Backup encryption
- Access controls
- Offsite/offline storage
14.1 - Establish and Maintain Security Awareness Program
- Annual training
- Phishing awareness
- Policy acknowledgment
17.1 - Designate Personnel to Manage Incident Handling
- Incident response team
- Clear roles and responsibilities
- 24/7 contact information
IG2 - Enterprise Security (Additional 72 Safeguards, 128 Total)
Enterprise-Grade Controls
IG2 adds 72 safeguards for organizations with dedicated IT staff and moderate risk profiles.
New Controls at IG2:
- Control 12: Network Infrastructure Management (6 safeguards at IG2)
- Control 13: Network Monitoring and Defense (8 safeguards at IG2)
- Control 16: Application Software Security (10 safeguards at IG2)
- Control 18: Penetration Testing (3 safeguards at IG2)
Expanded Controls at IG2:
- Control 2: +2 safeguards (software allowlisting)
- Control 3: +8 safeguards (encryption, classification)
- Control 4: +5 safeguards (DMZ, hardening)
- Control 5: +2 safeguards (MFA, centralized management)
- Control 6: +3 safeguards (RBAC, centralized access)
- Control 7: +3 safeguards (automated scanning, remediation)
- Control 8: +5 safeguards (centralized logs, retention)
- Control 9: +2 safeguards (DMARC, file blocking)
- Control 10: +3 safeguards (centralized AV, anti-exploit)
- Control 11: +1 safeguard (backup testing)
- Control 14: +4 safeguards (advanced training)
- Control 15: +3 safeguards (vendor assessments)
- Control 17: +3 safeguards (IR exercises, playbooks)
Key IG2 Safeguards (High Value):
3.6 - Encrypt Data on End-User Devices
- Full disk encryption (BitLocker, FileVault)
- Mobile device encryption
- Encryption key management
3.10 - Encrypt Sensitive Data in Transit
- TLS 1.2+ for web traffic
- VPN for remote access
- Email encryption (S/MIME, PGP)
3.11 - Encrypt Sensitive Data at Rest
- Database encryption
- File/folder encryption
- Cloud storage encryption
5.5 - Establish and Maintain MFA
- MFA for all users (phishing-resistant preferred)
- Admin access requires MFA
- Remote access requires MFA
5.6 - Centralize Account Management
- Single sign-on (SSO)
- Identity provider (IdP)
- Directory services integration
7.5 - Perform Automated Vulnerability Scans of Internal Enterprise Assets
- Weekly authenticated scans
- Network and host-based
- Credentialed scanning
8.9 - Centralize Audit Logs
- SIEM or log aggregation
- Minimum 90-day retention
- Correlation and alerting
8.11 - Conduct Audit Log Reviews
- Regular log review (weekly/monthly)
- Anomaly detection
- Incident investigation
12.2 - Establish and Maintain Secure Network Architecture
- Network segmentation
- DMZ for internet-facing systems
- VLANs for asset separation
12.4 - Establish and Maintain Network Architecture Diagram
- Current network topology
- Security zones documented
- Data flows mapped
13.1 - Centralize Security Event Alerting
- SIEM alerting
- SOC or monitoring service
- Incident escalation
13.2 - Deploy Network-Based IDS
- Intrusion detection system
- Signature and anomaly-based
- Critical network segments
13.3 - Deploy Network-Based IPS
- Intrusion prevention system
- Inline blocking
- Tuned to environment
16.1 - Establish and Maintain Secure Application Development Process
- Secure SDLC
- Security requirements
- Code review process
16.2 - Establish and Maintain Secure Software Development Practices
- Secure coding standards (OWASP)
- Developer training
- Security testing integration
16.6 - Establish and Maintain SBOM
- Software bill of materials
- Dependency tracking
- Vulnerability monitoring
18.1 - Establish and Maintain Penetration Testing Program
- Annual external pentest
- Qualified testers
- Remediation tracking
18.2 - Perform Periodic External Penetration Tests
- Annual minimum
- Scope: internet-facing assets
- Realistic attack simulation
IG3 - Advanced Security (Additional 25 Safeguards, 153 Total)
Advanced Threat Defense
IG3 adds 25 safeguards for organizations facing sophisticated adversaries and managing high-value assets.
Expanded Controls at IG3:
- Control 1: +0 safeguards (same as IG2)
- Control 2: +1 safeguard (script allowlisting)
- Control 3: +3 safeguards (advanced data controls)
- Control 4: +2 safeguards (secure admin workstations)
- Control 7: +1 safeguard (advanced remediation)
- Control 8: +2 safeguards (advanced logging)
- Control 9: +1 safeguard (advanced email protection)
- Control 10: +2 safeguards (behavioral analysis)
- Control 12: +2 safeguards (dedicated admin systems)
- Control 13: +3 safeguards (advanced monitoring)
- Control 14: +2 safeguards (role-specific training)
- Control 15: +2 safeguards (vendor decommissioning)
- Control 16: +4 safeguards (advanced AppSec)
- Control 17: +2 safeguards (advanced IR)
- Control 18: +2 safeguards (internal pentesting)
Key IG3 Safeguards (Advanced Capabilities):
2.7 - Allowlist Authorized Scripts
- PowerShell, Python, Bash script control
- Code signing requirements
- Script execution policies
3.12 - Segment Data Processing and Storage Based on Sensitivity
- Data segmentation by classification
- Network isolation for sensitive data
- Access restrictions by segment
3.13 - Deploy a Data Loss Prevention Solution
- DLP for email, web, endpoints
- Data exfiltration prevention
- Policy-based blocking
3.14 - Log Sensitive Data Access
- Access logging for sensitive data
- User activity monitoring
- Privilege escalation detection
4.11 - Enforce Remote Access Using Multi-Factor Authentication
- Hardware tokens or biometrics
- FIDO2/WebAuthn preferred
- Phishing-resistant MFA
7.7 - Remediate Detected Vulnerabilities
- Risk-based prioritization (CVSS, EPSS)
- Critical: 15 days, High: 30 days
- Compensating controls documented
8.12 - Collect Service Provider Logs
- Cloud provider logs (AWS CloudTrail, Azure Monitor)
- SaaS application logs
- Integration with SIEM
10.7 - Use Behavior-Based Anti-Malware Software
- EDR with behavioral analysis
- Machine learning detection
- Automated response
12.8 - Establish and Maintain Dedicated Computing Resources for Admins
- Privileged Access Workstations (PAWs)
- Jump boxes for administration
- Isolated from general network
13.10 - Perform Application Layer Filtering
- Web application firewall (WAF)
- API gateway security
- OWASP Top 10 protection
13.11 - Tune Security Event Alerting Thresholds
- Alert tuning to reduce false positives
- Continuous improvement
- Threat hunting integration
14.9 - Conduct Role-Specific Security Training
- Developer secure coding
- Admin hardening training
- Executive awareness
16.11 - Leverage Vetted Modules or Services for Application Security
- Proven security libraries
- Vendor security assessments
- Supply chain security
16.13 - Conduct Application Penetration Testing
- Annual application pentesting
- Pre-production security testing
- Remediation before deployment
16.14 - Conduct Threat Modeling
- Architecture risk analysis
- Attack surface mapping
- Design phase security review
17.8 - Conduct Post-Incident Reviews
- Lessons learned sessions
- Root cause analysis
- Process improvements
17.9 - Establish and Maintain Security Incident Thresholds
- Incident severity ratings
- Escalation criteria
- Response time SLAs
18.4 - Validate Security Measures
- Adversary emulation
- Purple team exercises
- Control validation
18.5 - Perform Periodic Internal Penetration Tests
- Annual internal pentesting
- Assume breach scenarios
- Lateral movement testing
Safeguard Prioritization
Quick Wins (High Impact, Low Effort)
- 1.1: Asset inventory
- 2.1: Software inventory
- 5.3: Disable dormant accounts
- 7.3: Automated OS patching
- 10.1: Anti-malware deployment
- 14.1: Security awareness training
Foundational (Critical Infrastructure)
- 4.1: Secure configurations
- 5.1: Account inventory
- 6.1/6.2: Access processes
- 8.2: Audit logging
- 11.2/11.3: Backups and protection
- 17.1: Incident response team
Advanced (Risk Reduction)
- 5.5: Multi-factor authentication
- 7.5: Vulnerability scanning
- 8.9: Centralized logging
- 12.2: Network segmentation
- 13.2/13.3: IDS/IPS
- 16.1: Secure SDLC
Specialized (Threat Defense)
- 10.7: Behavioral anti-malware
- 13.11: Alert tuning
- 16.13: Application pentesting
- 18.5: Internal pentesting
Implementation Timeline by IG
IG1 Timeline (56 safeguards):
- Months 1-3: Inventory, backups, basic protections
- Months 4-6: Access controls, patching, awareness
- Months 7-9: Logging, configuration management
- Months 10-12: Refinement, documentation, testing
IG2 Timeline (additional 72 safeguards):
- Months 1-6: Encryption, MFA, centralized management
- Months 7-12: SIEM, IDS/IPS, network architecture
- Months 13-18: Vulnerability management, secure development
- Months 19-24: Penetration testing, continuous improvement
IG3 Timeline (additional 25 safeguards):
- Months 1-6: Behavioral detection, DLP, advanced monitoring
- Months 7-12: PAWs, advanced testing, threat modeling
- Months 13-18: Purple team, incident maturity
- Months 19-24+: Continuous optimization, threat hunting
Examples
# List all IG1 safeguards (56 total)
/cis:safeguard-list IG1
# Show IG2 safeguards for Control 8 (Audit Logs)
/cis:safeguard-list IG2 8
# Display all IG3 safeguards (153 total)
/cis:safeguard-list IG3 all
# Review IG2 safeguards for Account Management
/cis:safeguard-list IG2 5
Sponsors
Details
- Marketplace
- GRCEngClub/claude-grc-engineering
- Source
- plugins/frameworks/cis-controls
- Category
- Community
More from GRCEngClub/claude-grc-engineering
All 70- cmmcv0.1.0
- compliance-posture-dashboardv0.1.0
- crowdstrike-inspectorv0.1.0
- csa-ccmv0.1.0
- cyber-essentials-plusv0.1.0
- datadog-inspectorv0.1.0
- dorav0.1.0
- drata-inspectorv0.1.0
- essential8v0.1.0
- eu-nis2v0.1.0
- fedramp-20xv0.1.0
- fedramp-rev5v0.1.0
- fedramp-sspv0.1.0
- gcp-docsv0.1.0
- gcp-inspectorv0.1.0
- gcp-secret-metadatav0.1.0
- gdprv0.1.0
- github-inspectorv0.1.0
- glbav0.1.0
- grc-auditorv0.1.0
- grc-diagramsv0.1.0
- grc-engineerv0.1.0
- grc-internalv0.1.0
- grc-loopv0.1.0