United States (NIST); used internationally

NIST Cybersecurity Framework 1.1

136 controls. 1 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

136 controls 1 frameworks share controls with it United States (NIST); used internationally verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
DE.AEAnomalies and Events (DE.AE)0
DE.AE-1DE.AE-1: A baseline of network operations and expected data flows for users and systems is established and managed1
DE.AE-2DE.AE-2: Detected events are analyzed to understand attack targets and methods1
DE.AE-3DE.AE-3: Event data are collected and correlated from multiple sources and sensors1
DE.AE-4DE.AE-4: Impact of events is determined1
DE.AE-5DE.AE-5: Incident alert thresholds are established1
DE.CMSecurity Continuous Monitoring (DE.CM)0
DE.CM-1DE.CM-1: The network is monitored to detect potential cybersecurity events1
DE.CM-2DE.CM-2: The physical environment is monitored to detect potential cybersecurity events1
DE.CM-3DE.CM-3: Personnel activity is monitored to detect potential cybersecurity events1
DE.CM-4DE.CM-4: Malicious code is detected1
DE.CM-5DE.CM-5: Unauthorized mobile code is detected1
DE.CM-6DE.CM-6: External service provider activity is monitored to detect potential cybersecurity events1
DE.CM-7DE.CM-7: Monitoring for unauthorized personnel, connections, devices, and software is performed1
DE.CM-8DE.CM-8: Vulnerability scans are performed1
DE.DPDetection Processes (DE.DP)0
DE.DP-1DE.DP-1: Roles and responsibilities for detection are well defined to ensure accountability1
DE.DP-2DE.DP-2: Detection activities comply with all applicable requirements1
DE.DP-3DE.DP-3: Detection processes are tested1
DE.DP-4DE.DP-4: Event detection information is communicated1
DE.DP-5DE.DP-5: Detection processes are continuously improved1
ID.AMAsset Management (ID.AM)0
ID.AM-1ID.AM-1: Physical devices and systems within the organization are inventoried1
ID.AM-2ID.AM-2: Software platforms and applications within the organization are inventoried1
ID.AM-3ID.AM-3: Organizational communication and data flows are mapped1
ID.AM-4ID.AM-4: External information systems are catalogued1
ID.AM-5ID.AM-5: Resources (e.g., hardware, devices, data, time, personnel, and software) are prioritized based on their classification, criticality, and business value1
ID.AM-6ID.AM-6: Cybersecurity roles and responsibilities for the entire workforce and third-party stakeholders (e.g., suppliers, customers, partners) are established1
ID.BEBusiness Environment (ID.BE)0
ID.BE-1ID.BE-1: The organization's role in the supply chain is identified and communicated1
ID.BE-2ID.BE-2: The organization's place in critical infrastructure and its industry sector is identified and communicated1
ID.BE-3ID.BE-3: Priorities for organizational mission, objectives, and activities are established and communicated1
ID.BE-4ID.BE-4: Dependencies and critical functions for delivery of critical services are established1
ID.BE-5ID.BE-5: Resilience requirements to support delivery of critical services are established for all operating states (e.g. under duress/attack, during recovery, normal operations)1
ID.GVGovernance (ID.GV)0
ID.GV-1ID.GV-1: Organizational cybersecurity policy is established and communicated1
ID.GV-2ID.GV-2: Cybersecurity roles and responsibilities are coordinated and aligned with internal roles and external partners1
ID.GV-3ID.GV-3: Legal and regulatory requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed1
ID.GV-4ID.GV-4: Governance and risk management processes address cybersecurity risks1
ID.RARisk Assessment (ID.RA)0
ID.RA-1ID.RA-1: Asset vulnerabilities are identified and documented1
ID.RA-2ID.RA-2: Cyber threat intelligence is received from information sharing forums and sources1
ID.RA-3ID.RA-3: Threats, both internal and external, are identified and documented1
ID.RA-4ID.RA-4: Potential business impacts and likelihoods are identified1
ID.RA-5ID.RA-5: Threats, vulnerabilities, likelihoods, and impacts are used to determine risk1
ID.RA-6ID.RA-6: Risk responses are identified and prioritized1
ID.RMRisk Management Strategy (ID.RM)0
ID.RM-1ID.RM-1: Risk management processes are established, managed, and agreed to by organizational stakeholders1
ID.RM-2ID.RM-2: Organizational risk tolerance is determined and clearly expressed1
ID.RM-3ID.RM-3: The organization's determination of risk tolerance is informed by its role in critical infrastructure and sector specific risk analysis1
ID.SCSupply Chain Risk Management (ID.SC)0
ID.SC-1ID.SC-1: Cyber supply chain risk management processes are identified, established, assessed, managed, and agreed to by organizational stakeholders1
ID.SC-2ID.SC-2: Suppliers and third party partners of information systems, components, and services are identified, prioritized, and assessed using a cyber supply chain risk assessment pr1
ID.SC-3ID.SC-3: Contracts with suppliers and third-party partners are used to implement appropriate measures designed to meet the objectives of an organization's cybersecurity program and1
ID.SC-4ID.SC-4: Suppliers and third-party partners are routinely assessed using audits, test results, or other forms of evaluations to confirm they are meeting their contractual obligatio1
ID.SC-5ID.SC-5: Response and recovery planning and testing are conducted with suppliers and third-party providers1
PR.ACIdentity Management, Authentication and Access Control (PR.AC)0
PR.AC-1PR.AC-1: Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users and processes1
PR.AC-2PR.AC-2: Physical access to assets is managed and protected1
PR.AC-3PR.AC-3: Remote access is managed1
PR.AC-4PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties1
PR.AC-5PR.AC-5: Network integrity is protected (e.g., network segregation, network segmentation)1
PR.AC-6PR.AC-6: Identities are proofed and bound to credentials and asserted in interactions1
PR.AC-7PR.AC-7: Users, devices, and other assets are authenticated (e.g., single-factor, multi-factor) commensurate with the risk of the transaction (e.g., individuals' security and priva1
PR.ATAwareness and Training (PR.AT)0
PR.AT-1PR.AT-1: All users are informed and trained1
PR.AT-2PR.AT-2: Privileged users understand their roles and responsibilities1
PR.AT-3PR.AT-3: Third-party stakeholders (e.g., suppliers, customers, partners) understand their roles and responsibilities1
PR.AT-4PR.AT-4: Senior executives understand their roles and responsibilities1
PR.AT-5PR.AT-5: Physical and cybersecurity personnel understand their roles and responsibilities1
PR.DSData Security (PR.DS)0
PR.DS-1PR.DS-1: Data-at-rest is protected1
PR.DS-2PR.DS-2: Data-in-transit is protected1
PR.DS-3PR.DS-3: Assets are formally managed throughout removal, transfers, and disposition1
PR.DS-4PR.DS-4: Adequate capacity to ensure availability is maintained1
PR.DS-5PR.DS-5: Protections against data leaks are implemented1
PR.DS-6PR.DS-6: Integrity checking mechanisms are used to verify software, firmware, and information integrity1
PR.DS-7PR.DS-7: The development and testing environment(s) are separate from the production environment1
PR.DS-8PR.DS-8: Integrity checking mechanisms are used to verify hardware integrity1
PR.IPInformation Protection Processes and Procedures (PR.IP)0
PR.IP-1PR.IP-1: A baseline configuration of information technology/industrial control systems is created and maintained incorporating security principles (e.g. concept of least functional1
PR.IP-10PR.IP-10: Response and recovery plans are tested1
PR.IP-11PR.IP-11: Cybersecurity is included in human resources practices (e.g., deprovisioning, personnel screening)1
PR.IP-12PR.IP-12: A vulnerability management plan is developed and implemented1
PR.IP-2PR.IP-2: A System Development Life Cycle to manage systems is implemented1
PR.IP-3PR.IP-3: Configuration change control processes are in place1
PR.IP-4PR.IP-4: Backups of information are conducted, maintained, and tested1
PR.IP-5PR.IP-5: Policy and regulations regarding the physical operating environment for organizational assets are met1
PR.IP-6PR.IP-6: Data is destroyed according to policy1
PR.IP-7PR.IP-7: Protection processes are improved1
PR.IP-8PR.IP-8: Effectiveness of protection technologies is shared1
PR.IP-9PR.IP-9: Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed1
PR.MAMaintenance (PR.MA)0
PR.MA-1PR.MA-1: Maintenance and repair of organizational assets are performed and logged, with approved and controlled tools1
PR.MA-2PR.MA-2: Remote maintenance of organizational assets is approved, logged, and performed in a manner that prevents unauthorized access1
PR.PTProtective Technology (PR.PT)0
PR.PT-1PR.PT-1: Audit/log records are determined, documented, implemented, and reviewed in accordance with policy1
PR.PT-2PR.PT-2: Removable media is protected and its use restricted according to policy1
PR.PT-3PR.PT-3: The principle of least functionality is incorporated by configuring systems to provide only essential capabilities1
PR.PT-4PR.PT-4: Communications and control networks are protected1
PR.PT-5PR.PT-5: Mechanisms (e.g., failsafe, load balancing, hot swap) are implemented to achieve resilience requirements in normal and adverse situations1
RC.COCommunications (RC.CO)0
RC.CO-1RC.CO-1: Public relations are managed1
RC.CO-2RC.CO-2: Reputation is repaired after an incident1
RC.CO-3RC.CO-3: Recovery activities are communicated to internal and external stakeholders as well as executive and management teams1
RC.IMImprovements (RC.IM)0
RC.IM-1RC.IM-1: Recovery plans incorporate lessons learned1
RC.IM-2RC.IM-2: Recovery strategies are updated1
RC.RPRecovery Planning (RC.RP)0
RC.RP-1RC.RP-1: Recovery plan is executed during or after a cybersecurity incident1
RS.ANAnalysis (RS.AN)0
RS.AN-1RS.AN-1: Notifications from detection systems are investigated1
RS.AN-2RS.AN-2: The impact of the incident is understood1
RS.AN-3RS.AN-3: Forensics are performed1
RS.AN-4RS.AN-4: Incidents are categorized consistent with response plans1
RS.AN-5RS.AN-5: Processes are established to receive, analyze and respond to vulnerabilities disclosed to the organization from internal and external sources (e.g. internal testing, secur1
RS.COCommunications (RS.CO)0
RS.CO-1RS.CO-1: Personnel know their roles and order of operations when a response is needed1
RS.CO-2RS.CO-2: Incidents are reported consistent with established criteria1
RS.CO-3RS.CO-3: Information is shared consistent with response plans1
RS.CO-4RS.CO-4: Coordination with stakeholders occurs consistent with response plans1
RS.CO-5RS.CO-5: Voluntary information sharing occurs with external stakeholders to achieve broader cybersecurity situational awareness1
RS.IMImprovements (RS.IM)0
RS.IM-1RS.IM-1: Response plans incorporate lessons learned1
RS.IM-2RS.IM-2: Response strategies are updated1
RS.MIMitigation (RS.MI)0
RS.MI-1RS.MI-1: Incidents are contained1
RS.MI-2RS.MI-2: Incidents are mitigated1
RS.MI-3RS.MI-3: Newly identified vulnerabilities are mitigated or documented as accepted risks1
RS.RPResponse Planning (RS.RP)0
RS.RP-1RS.RP-1: Response plan is executed during or after an incident1
X.1The Framework and its three parts0
X.2Implementation Tiers0
X.3Profiles and the seven-step program0
X.4Changes from Version 1.00
X.5Supersession by CSF 2.00

Tell me when NIST Cybersecurity Framework 1.1 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for NIST Cybersecurity Framework 1.1, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition