CIS Controls, the practical security checklist
Eighteen prioritised actions that stop the most common attacks. Start small, then grow.
Official sources
Use these official places to read the text and find the latest version.
Official website
The Center for Internet Security publishes the controls, guides and benchmarks.
Visit cisecurity.org/controls ↗Get the document
The controls are free to download from CIS with a short registration.
Open the official page ↗What CIS Controls is
The CIS Controls are a short list of security actions, ordered by how much risk they remove. They were built from real attack data and written for practical use.
Three implementation groups help you pick a starting point based on your size and resources.
How CIS Controls got to where it is today
The milestones that changed what organisations have to do.
First list
Volunteer experts from US government and industry, convened through the SANS Institute, publish a prioritised list of defences.
Moves to CIS
The Center for Internet Security takes over maintenance.
Version 8
Reorganised into 18 controls to reflect cloud, remote work and mobile.
Dates are for orientation. The official website holds the authoritative record.
Do you need it?
If any of these sound familiar, probably yes.
You want a clear security to-do list without a heavy standard.
You are a small or mid-sized company with limited staff.
You need to show customers a recognised baseline.
You want a practical start before ISO 27001 or SOC 2.
What it asks of you
The requirements fall into six areas.
Know what you have
Inventory devices and software.
Secure configuration
Safe defaults and patching.
Control access
Accounts, least privilege, strong sign-in.
Protect data
Classify, encrypt, back up.
Detect and respond
Logs, alerts, incident plans.
People and vendors
Awareness and service provider checks.
The 18 controls and 153 safeguards, in 5 themes
Eighteen prioritised actions, each broken into safeguards you can tick off. Start with the basics, then work through the rest.
18 controls · 153 safeguards
GAKnow and harden what you haveInventory, configuration and patching of devices and software.4 controls · 31 safeguards
CIS1Control 1: Inventory and Control of Enterprise AssetsKnow every device that connects to your network so nothing unmanaged goes unnoticed.5 safeguards
- 1.1
Keep an accurate, detailed inventory of all enterprise devices, reviewed at least twice a year.
What you do
- Export devices from your MDM and network tools into one register and review it every six months
- 1.2
Have a process to deal with unauthorised assets weekly.
What you do
- Remove, quarantine or approve unknown devices found on the network each week
- 1.3
Use an active discovery tool to find assets on the network.
What you do
- Schedule a daily scan with a tool such as Nmap or your RMM discovery feature
- 1.4
Use DHCP logging to update the asset inventory.
What you do
- Enable DHCP logs and feed new leases into the inventory
- 1.5
Use a passive discovery tool to find assets.
What you do
- Turn on passive monitoring on a switch mirror port or in your NDR tool
Evidence to keep
- Asset inventory export
- Network discovery scan results
- Unauthorised device handling log
CIS2Control 2: Inventory and Control of Software AssetsKnow what software runs in your estate and block what is not approved.7 safeguards
- 2.1
Keep an inventory of all licensed software, reviewed at least twice a year.
What you do
- List installed applications with version and owner from your endpoint management tool
- 2.2
Make sure only currently supported software is authorised, with documented exceptions.
What you do
- Mark end-of-life software in the inventory and record a risk acceptance if it must stay
- 2.3
Deal with unauthorised software promptly.
What you do
- Uninstall or approve unlisted software found during the monthly review
- 2.4
Use automated tools to discover and update the software inventory.
What you do
- Run an agent-based software scan at least every two weeks
- 2.5
Use technical controls to allow only authorised software to run.
What you do
- Enable application control such as Windows AppLocker or macOS restrictions on key devices
- 2.6
Allow only authorised software libraries to load into processes.
What you do
- Restrict libraries to approved sources in build and endpoint configuration
- 2.7
Allow only authorised scripts to run, using signatures where possible.
What you do
- Set PowerShell execution policy to signed scripts only
Evidence to keep
- Software inventory
- Approved software list
- Allowlisting policy and exceptions
CIS4Control 4: Secure Configuration of Enterprise Assets and SoftwareSet devices and software up securely and keep them that way.12 safeguards
- 4.1
Have a secure configuration process for devices and software, reviewed yearly.
What you do
- Adopt a baseline such as a CIS Benchmark and record how it is applied
- 4.2
Have a secure configuration process for network devices.
What you do
- Apply a baseline to routers, switches and firewalls and back up configs
- 4.3
Lock sessions automatically after inactivity.
What you do
- Set screen lock to 15 minutes or less on all devices
- 4.4
Run a firewall on servers.
What you do
- Enable host firewalls with deny by default rules
- 4.5
Run a firewall on end-user devices.
What you do
- Enable the built-in firewall through policy
- 4.6
Manage assets and software using secure protocols.
What you do
- Use SSH and HTTPS for administration and disable Telnet
- 4.7
Manage default accounts.
What you do
- Disable or rename vendor default accounts and change default passwords
- 4.8
Uninstall or disable unnecessary services.
What you do
- Review running services and switch off what is not needed
- 4.9
Use trusted DNS servers.
What you do
- Point devices only at approved resolvers
- 4.10
Lock portable devices automatically after failed sign-in attempts.
What you do
- Set device lockout after a small number of failed attempts
- 4.11
Be able to remotely wipe lost enterprise devices.
What you do
- Enrol phones and laptops in MDM with remote wipe enabled
- 4.12
Keep separate work areas on mobile devices.
What you do
- Use work profiles or managed apps to split work and personal data
Evidence to keep
- Configuration baselines
- Hardening checklists
- Exception and change records
CIS7Control 7: Continuous Vulnerability ManagementFind and fix weaknesses before attackers use them.7 safeguards
- 7.1
Have a vulnerability management process, reviewed yearly.
What you do
- Write a short procedure covering scanning, ranking and fix timelines
- 7.2
Have a risk-based remediation process, reviewed monthly.
What you do
- Set fix deadlines by severity and track them
- 7.3
Patch operating systems automatically.
What you do
- Enable automatic updates through your endpoint tool
- 7.4
Patch applications automatically.
What you do
- Use automatic updates for browsers and common apps
- 7.5
Run automated vulnerability scans of internal assets quarterly.
What you do
- Schedule an authenticated internal scan every quarter
- 7.6
Run automated vulnerability scans of externally exposed assets monthly.
What you do
- Scan your public IPs and websites each month
- 7.7
Fix detected vulnerabilities in line with the process.
What you do
- Close findings and record exceptions with an owner and date
Evidence to keep
- Scan reports
- Patch status reports
- Remediation tracker
GBDesign and protect data and networksProtect data and build safe networks and applications.3 controls · 36 safeguards
CIS3Control 3: Data ProtectionKnow what data you hold, who can reach it, and protect it through its life.14 safeguards
- 3.1
Have a documented data management process, reviewed yearly.
What you do
- Write a short policy covering ownership, handling, retention and disposal
- 3.2
Keep an inventory of sensitive data.
What you do
- List systems and stores holding customer or personal data with an owner for each
- 3.3
Set access controls on data according to need to know.
What you do
- Limit file shares and cloud folders to named groups
- 3.4
Enforce data retention periods.
What you do
- Set automatic deletion rules in email, storage and backups
- 3.5
Dispose of data securely in line with its sensitivity.
What you do
- Use certified wiping or destruction and keep the certificates
- 3.6
Encrypt data on end-user devices.
What you do
- Turn on BitLocker or FileVault and report on coverage
- 3.7
Have a data classification scheme.
What you do
- Define three or four labels such as public, internal, confidential and restricted
- 3.8
Document data flows, including with service providers.
What you do
- Draw a simple diagram showing where sensitive data enters, moves and leaves
- 3.9
Encrypt data on removable media.
What you do
- Enforce encryption on USB drives or block them
- 3.10
Encrypt sensitive data in transit.
What you do
- Require TLS for web, email and API connections
- 3.11
Encrypt sensitive data at rest.
What you do
- Enable storage and database encryption with managed keys
- 3.12
Segment data processing and storage by sensitivity.
What you do
- Keep sensitive data in separate networks, accounts or tenants
- 3.13
Deploy a data loss prevention solution.
What you do
- Turn on built-in DLP rules in your email and cloud suite
- 3.14
Log access to sensitive data.
What you do
- Enable audit logging on sensitive stores and review alerts
Evidence to keep
- Data inventory and classification scheme
- Retention and disposal records
- Encryption configuration evidence
CIS12Control 12: Network Infrastructure ManagementKeep network equipment current and well designed.8 safeguards
- 12.1
Keep network infrastructure up to date.
What you do
- Update firmware and software on a regular schedule and replace end-of-life gear
- 12.2
Establish and maintain a secure network architecture.
What you do
- Segment user, server and guest networks
- 12.3
Manage network infrastructure securely.
What you do
- Use encrypted admin protocols and MFA for network admin
- 12.4
Establish and maintain architecture diagrams, reviewed yearly.
What you do
- Keep diagrams current and store them with the asset inventory
- 12.5
Centralise network authentication, authorisation and auditing.
What you do
- Use a central service for network device logins
- 12.6
Use secure network management and communication protocols.
What you do
- Use WPA2 Enterprise or WPA3 and 802.1X where possible
- 12.7
Make remote devices use a VPN and the enterprise security infrastructure.
What you do
- Require VPN or zero trust agent before access
- 12.8
Keep dedicated computing resources for all administrative work.
What you do
- Use a separate hardened admin workstation
Evidence to keep
- Network diagrams
- Firmware update records
- Network device configuration standards
CIS16Control 16: Application Software SecurityBuild and buy software that is secure by design.14 safeguards
- 16.1
Have a secure application development process.
What you do
- Define security steps in each stage of development
- 16.2
Have a process to accept and fix software vulnerability reports.
What you do
- Publish a security contact and track reports to closure
- 16.3
Perform root cause analysis on security vulnerabilities.
What you do
- Record why each serious flaw happened and how to prevent it
- 16.4
Keep an inventory of third-party software components.
What you do
- Generate a software bill of materials
- 16.5
Use up-to-date and trusted third-party components.
What you do
- Update dependencies regularly and use trusted sources
- 16.6
Establish a severity rating system for vulnerabilities.
What you do
- Adopt CVSS or similar and set fix times
- 16.7
Use standard hardening configuration templates for application infrastructure.
What you do
- Use approved templates for servers and containers
- 16.8
Separate production and non-production systems.
What you do
- Keep test and live environments apart
- 16.9
Train developers in secure coding.
What you do
- Provide yearly secure coding training
- 16.10
Apply secure design principles in application architectures.
What you do
- Use least privilege and input validation by design
- 16.11
Use vetted modules or services for application security components.
What you do
- Use established libraries for login and encryption
- 16.12
Implement code-level security checks.
What you do
- Add static analysis to the build pipeline
- 16.13
Conduct application penetration testing.
What you do
- Test critical applications before major releases
- 16.14
Conduct threat modelling.
What you do
- Review design risks for new features
Evidence to keep
- Secure development policy
- Code review and test records
- Component inventory
GCControl people and accessWho has access, how they prove it and how they are trained.3 controls · 23 safeguards
CIS5Control 5: Account ManagementKnow every account, remove what is not needed and tightly control admin accounts.6 safeguards
- 5.1
Keep an inventory of all accounts, reviewed at least twice a year.
What you do
- Export users from your directory and cloud services and check owners
- 5.2
Use unique, strong passwords.
What you do
- Set a password policy and provide a password manager
- 5.3
Disable dormant accounts after 45 days.
What you do
- Run a monthly report of inactive accounts and disable them
- 5.4
Restrict administrator privileges to dedicated admin accounts.
What you do
- Give admins separate accounts for daily work and for admin tasks
- 5.5
Keep an inventory of service accounts, reviewed at least twice a year.
What you do
- List service accounts with owner, purpose and last review date
- 5.6
Centralise account management through a directory or identity service.
What you do
- Connect apps to a single identity provider
Evidence to keep
- Account inventory
- Dormant account reviews
- Admin account list
CIS6Control 6: Access Control ManagementGive people only the access they need, and prove who they are with strong sign-in.8 safeguards
- 6.1
Have a process to grant access when someone joins or changes role.
What you do
- Use a request form with manager approval
- 6.2
Have a process to revoke access when someone leaves or changes role.
What you do
- Add account removal to the leaver checklist and check it is done the same day
- 6.3
Require MFA for externally exposed applications.
What you do
- Turn on MFA for email, VPN and cloud apps
- 6.4
Require MFA for remote network access.
What you do
- Enforce MFA on VPN and remote desktop
- 6.5
Require MFA for all administrative access.
What you do
- Enforce MFA on all admin portals and consoles
- 6.6
Keep an inventory of authentication and authorisation systems.
What you do
- List directories and identity providers in use
- 6.7
Centralise access control through a directory or SSO service.
What you do
- Use single sign-on for business applications
- 6.8
Define and maintain role-based access control.
What you do
- Document roles and the access each needs, and review yearly
Evidence to keep
- Joiner, mover, leaver records
- MFA enrolment reports
- Role definitions
CIS14Control 14: Security Awareness and Skills TrainingHelp people spot and avoid common attacks.9 safeguards
- 14.1
Have a security awareness programme.
What you do
- Run annual training at joining and each year after
- 14.2
Train staff to recognise social engineering.
What you do
- Cover phishing, phone scams and impersonation
- 14.3
Train staff on authentication best practices.
What you do
- Cover MFA, password managers and passphrases
- 14.4
Train staff on how to handle data safely.
What you do
- Cover classification, sharing and disposal
- 14.5
Train staff on causes of unintentional data exposure.
What you do
- Cover misdirected emails and public sharing links
- 14.6
Train staff to recognise and report incidents.
What you do
- Provide a simple report button or address
- 14.7
Train staff to spot and report missing security updates.
What you do
- Explain how to flag update prompts to IT
- 14.8
Train staff on the dangers of insecure networks.
What you do
- Cover public Wi-Fi and use of VPN
- 14.9
Provide role-specific security training.
What you do
- Give developers, admins and finance staff targeted modules
Evidence to keep
- Training content and schedule
- Completion records
- Phishing exercise results
GDDetect and prevent attacksSpot and block threats and keep logs.4 controls · 37 safeguards
CIS8Control 8: Audit Log ManagementCollect and keep logs so you can spot and investigate problems.12 safeguards
- 8.1
Have an audit log management process, reviewed yearly.
What you do
- Define what is logged, where it goes and how long it is kept
- 8.2
Collect audit logs from key systems.
What you do
- Switch on logging for servers, firewalls, identity and cloud
- 8.3
Make sure there is enough log storage.
What you do
- Size storage for your retention period and monitor it
- 8.4
Standardise time synchronisation.
What you do
- Point all systems at the same trusted time sources
- 8.5
Collect detailed audit logs for sensitive data and systems.
What you do
- Record who, what, when and where for sensitive access
- 8.6
Collect DNS query logs.
What you do
- Enable DNS logging on resolvers or the filtering service
- 8.7
Collect URL request logs.
What you do
- Log web proxy or filter requests
- 8.8
Collect command-line audit logs.
What you do
- Enable PowerShell and shell command logging
- 8.9
Centralise audit log collection.
What you do
- Send logs to a SIEM or log service
- 8.10
Retain audit logs for at least 90 days.
What you do
- Set retention to 90 days or longer
- 8.11
Review audit logs weekly to spot anomalies.
What you do
- Schedule a weekly review and note the outcome
- 8.12
Collect logs from service providers.
What you do
- Ask key suppliers for log access or reports
Evidence to keep
- Logging standard
- Log source list
- Log review records
CIS9Control 9: Email and Web Browser ProtectionsReduce risk from the two most common ways attackers get in.7 safeguards
- 9.1
Use only fully supported browsers and email clients.
What you do
- Keep clients updated and remove old versions
- 9.2
Use DNS filtering services.
What you do
- Turn on a filtering service for all devices
- 9.3
Maintain and enforce network-based URL filters.
What you do
- Block known malicious and risky site categories
- 9.4
Restrict unnecessary or unauthorised browser and email add-ons.
What you do
- Allow only approved extensions through policy
- 9.5
Implement DMARC.
What you do
- Publish SPF, DKIM and DMARC records and move to an enforcing policy
- 9.6
Block unnecessary file types at the mail gateway.
What you do
- Block executables and macro-enabled attachments from outside
- 9.7
Deploy email server anti-malware protections.
What you do
- Enable attachment sandboxing and scanning
Evidence to keep
- Email security configuration
- DMARC reports
- Web filtering policy
CIS10Control 10: Malware DefensesStop, detect and clean up malicious software.7 safeguards
- 10.1
Deploy and maintain anti-malware software on all assets.
What you do
- Install managed endpoint protection and report on coverage
- 10.2
Configure automatic anti-malware signature updates.
What you do
- Enable automatic updates in the console
- 10.3
Disable autorun and autoplay for removable media.
What you do
- Apply the policy through group policy or MDM
- 10.4
Configure automatic anti-malware scanning of removable media.
What you do
- Set endpoint tools to scan drives on insertion
- 10.5
Enable anti-exploitation features.
What you do
- Turn on built-in exploit protection in the OS and EDR
- 10.6
Centrally manage anti-malware software.
What you do
- Use one console for policy and alerts
- 10.7
Use behaviour-based anti-malware software.
What you do
- Choose endpoint tools with behavioural detection and enable it
Evidence to keep
- Anti-malware deployment report
- Update status
- Detection alerts
CIS13Control 13: Network Monitoring and DefenseDetect and respond to threats on the network.11 safeguards
- 13.1
Centralise security event alerting.
What you do
- Send alerts to a SIEM or managed service
- 13.2
Deploy a host-based intrusion detection solution.
What you do
- Enable EDR detection on endpoints and servers
- 13.3
Deploy a network intrusion detection solution.
What you do
- Use IDS on firewalls or network sensors
- 13.4
Perform traffic filtering between network segments.
What you do
- Set firewall rules between segments
- 13.5
Manage access control for remote assets.
What you do
- Check device health before allowing remote access
- 13.6
Collect network traffic flow logs.
What you do
- Enable NetFlow or equivalent logs
- 13.7
Deploy a host-based intrusion prevention solution.
What you do
- Use endpoint prevention features where supported
- 13.8
Deploy a network intrusion prevention solution.
What you do
- Enable IPS profiles on your firewall
- 13.9
Deploy port-level access control.
What you do
- Use 802.1X on wired ports
- 13.10
Perform application layer filtering.
What you do
- Use a web application firewall or proxy
- 13.11
Tune security event alerting thresholds.
What you do
- Review alert noise monthly and adjust rules
Evidence to keep
- Alert and monitoring configuration
- IDS or IPS reports
- Tuning records
GEPrepare, recover and testBe ready for incidents, recover, manage suppliers and test.4 controls · 26 safeguards
CIS11Control 11: Data RecoveryBe able to get your data back after loss, damage or ransomware.5 safeguards
- 11.1
Have a data recovery process, reviewed yearly.
What you do
- Document what is backed up, how often and who restores it
- 11.2
Perform automated backups of in-scope assets weekly or more often.
What you do
- Schedule automatic backups based on how fast data changes
- 11.3
Protect recovery data with controls equal to the original data.
What you do
- Encrypt backups and restrict access
- 11.4
Keep an isolated instance of recovery data.
What you do
- Keep an offline or immutable copy that ransomware cannot reach
- 11.5
Test data recovery quarterly.
What you do
- Restore a sample each quarter and record the time taken
Evidence to keep
- Backup schedule and logs
- Restore test records
- Recovery procedure
CIS15Control 15: Service Provider ManagementMake sure suppliers who touch your data protect it.7 safeguards
- 15.1
Keep an inventory of service providers.
What you do
- List suppliers with owner, data handled and contact
- 15.2
Have a service provider management policy, reviewed yearly.
What you do
- Set how suppliers are chosen, assessed and ended
- 15.3
Classify service providers.
What you do
- Rate suppliers by data sensitivity and criticality
- 15.4
Include security requirements in provider contracts.
What you do
- Add security, breach notice and audit clauses
- 15.5
Assess service providers.
What you do
- Review security reports or questionnaires for critical suppliers
- 15.6
Monitor service providers.
What you do
- Track changes in their security and service performance
- 15.7
Decommission service providers securely.
What you do
- Recover or delete data and revoke access at contract end
Evidence to keep
- Supplier inventory
- Supplier due diligence records
- Contract security clauses
CIS17Control 17: Incident Response ManagementBe ready to handle a security incident calmly and quickly.9 safeguards
- 17.1
Designate a person to manage incident handling.
What you do
- Name an incident lead and a deputy
- 17.2
Keep contact information for reporting security incidents.
What you do
- Maintain a list of internal, legal, insurer and regulator contacts
- 17.3
Have an enterprise process for reporting incidents.
What you do
- Tell staff how and when to report
- 17.4
Have an incident response process, reviewed yearly.
What you do
- Write a plan with roles and steps
- 17.5
Assign key roles and responsibilities.
What you do
- Define technical, legal, communication and management roles
- 17.6
Define mechanisms for communicating during incidents.
What you do
- Set backup channels in case email is down
- 17.7
Run routine incident response exercises.
What you do
- Hold a tabletop exercise at least once a year
- 17.8
Conduct post-incident reviews.
What you do
- Record lessons and actions after every incident
- 17.9
Establish and maintain security incident thresholds.
What you do
- Define what counts as minor, major or critical
Evidence to keep
- Incident response plan
- Contact lists
- Exercise and post-incident review records
CIS18Control 18: Penetration TestingTest your defences the way an attacker would.5 safeguards
- 18.1
Have a penetration testing programme.
What you do
- Set scope, frequency and rules for testing
- 18.2
Perform periodic external penetration tests.
What you do
- Commission an annual test from a qualified provider
- 18.3
Fix penetration testing findings.
What you do
- Track findings to closure with owners
- 18.4
Validate security measures.
What you do
- Test that controls work after changes
- 18.5
Perform periodic internal penetration tests.
What you do
- Test internal networks at least yearly
Evidence to keep
- Penetration test reports
- Remediation tracking
- Scope and rules of engagement
Nothing matches. Clear the search or pick another theme.
Outcomes and implementation examples are from CIS Critical Security Controls v8.1, published by NIST. Descriptions of what to do and the evidence lists are our own plain-English guidance. Check the official source for the authoritative text.
Your path to getting started
Five steps from first look to ready. Effort depends on your size and starting point.
- 1
Pick your group
IG1 is the starting point for most.
- 2
Assess today
Mark each safeguard met, partly met or not met.
- 3
Close the quick wins
Focus on high-impact safeguards.
- 4
Track progress
Review quarterly.
- 5
Move up a group
When ready.
How Optimus CyberX helps
Each area maps to a part of the platform, so the work and the evidence sit together.
| What it asks | What you do in Optimus CyberX |
|---|---|
| Know what you have | Asset inventory |
| Secure configuration | Configuration and patch records |
| Control access | Access reviews |
| Protect data | Data and backup records |
| Detect and respond | Monitoring and incident log |
| People and vendors | Training and vendor records |
Free CIS Controls readiness checklist
A one-page PDF you can print or share with your team. No sign-up needed.
Download the checklist (PDF)- IG1 checklist
- Asset inventory template
- Patch tracking sheet
- Quarterly review sheet
Share or cite this page
Writing about CIS Controls? You are welcome to link to this guide. Copy the link below.
<a href="/frameworks/cis-controls/">CIS Controls explained in plain English - Optimus CyberX</a>Common questions
Is it mandatory?
No. It is voluntary, though regulators and insurers often like to see it.
What is IG1?
The basic group of safeguards every organisation should have.
Can we get certified?
No. You can self-assess or ask a third party to review.
How does it map to ISO 27001?
CIS publishes mappings to other frameworks.
Related frameworks
See how ready you are for CIS Controls
Answer questions across every area. We email you a report showing where you comply and where you do not.