Skip to content

Instantly share code, notes, and snippets.

@opexxx
Created September 6, 2022 21:54
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save opexxx/f381082bba87d0a59dd07e56397fc6f5 to your computer and use it in GitHub Desktop.
Save opexxx/f381082bba87d0a59dd07e56397fc6f5 to your computer and use it in GitHub Desktop.
NIST CSF
FID FUNCTION CID CATEGORY CATEGORY_DESCRIPTION SID SUBCATEGORY
ID IDENTIFY (ID) ID.AM Asset Management (ID.AM) Asset Management (ID.AM): The data, personnel, devices, systems, and facilities that enable the organization to achieve business purposes are identified and managed consistent with their relative importance to business objectives and the organization’s risk strategy. ID.AM-1 ID.AM-1: Physical devices and systems within the organization are inventoried
ID.AM-2 ID.AM-2: Software platforms and applications within the organization are inventoried
ID.AM-3 ID.AM-3: Organizational communication and data flows are mapped
ID.AM-4 ID.AM-4: External information systems are catalogued
ID.AM-5 ID.AM-5: Resources (e.g., hardware, devices, data, and software) are prioritized based on their classification, criticality, and business value
ID.AM-6 ID.AM-6: Cybersecurity roles and responsibilities for the entire workforce and third-party stakeholders (e.g., suppliers, customers, partners) are established
ID.BE Business Environment (ID.BE) Business Environment (ID.BE): The organization’s mission, objectives, stakeholders, and activities are understood and prioritized; this information is used to inform cybersecurity roles, responsibilities, and risk management decisions. ID.BE-1 ID.BE-1: The organization’s role in the supply chain is identified and communicated
ID.BE-2 ID.BE-2: The organization’s place in critical infrastructure and its industry sector is identified and communicated
ID.BE-3 ID.BE-3: Priorities for organizational mission, objectives, and activities are established and communicated
ID.BE-4 ID.BE-4: Dependencies and critical functions for delivery of critical services are established
ID.BE-5 ID.BE-5: Resilience requirements to support delivery of critical services are established
ID.GV Governance (ID.GV) Governance (ID.GV): The policies, procedures, and processes to manage and monitor the organization’s regulatory, legal, risk, environmental, and operational requirements are understood and inform the management of cybersecurity risk. ID.GV-1 ID.GV-1: Organizational information security policy is established
ID.GV-2 ID.GV-2: Information security roles & responsibilities are coordinated and aligned with internal roles and external partners
ID.GV-3 ID.GV-3: Legal and regulatory requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed
ID.GV-4 ID.GV-4: Governance and risk management processes address cybersecurity risks
ID.RA Risk Assessment (ID.RA) Risk Assessment (ID.RA): The organization understands the cybersecurity risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals. ID.RA-1 ID.RA-1: Asset vulnerabilities are identified and documented
ID.RA-2 ID.RA-2: Threat and vulnerability information is received from information sharing forums and sources
ID.RA-3 ID.RA-3: Threats, both internal and external, are identified and documented
ID.RA-4 ID.RA-4: Potential business impacts and likelihoods are identified
ID.RA-5 ID.RA-5: Threats, vulnerabilities, likelihoods, and impacts are used to determine risk
ID.RA-6 ID.RA-6: Risk responses are identified and prioritized
ID.RM Risk Management Strategy (ID.RM) Risk Management Strategy (ID.RM): The organization’s priorities, constraints, risk tolerances, and assumptions are established and used to support operational risk decisions. ID.RM-1 ID.RM-1: Risk management processes are established, managed, and agreed to by organizational stakeholders
ID.RM-2 ID.RM-2: Organizational risk tolerance is determined and clearly expressed
ID.RM-3 ID.RM-3: The organization’s determination of risk tolerance is informed by its role in critical infrastructure and sector specific risk analysis
PR PROTECT (PR) PR.AC Access Control (PR.AC) Access Control (PR.AC): Access to assets and associated facilities is limited to authorized users, processes, or devices, and to authorized activities and transactions. PR.AC-1 PR.AC-1: Identities and credentials are managed for authorized devices and users
PR.AC-2 PR.AC-2: Physical access to assets is managed and protected
PR.AC-3 PR.AC-3: Remote access is managed
PR.AC-4 PR.AC-4: Access permissions are managed, incorporating the principles of least privilege and separation of duties
PR.AC-5 PR.AC-5: Network integrity is protected, incorporating network segregation where appropriate
PR.AT Awareness and Training (PR.AT) Awareness and Training (PR.AT): The organization’s personnel and partners are provided cybersecurity awareness education and are adequately trained to perform their information security-related duties and responsibilities consistent with related policies, procedures, and agreements. PR.AT-1 PR.AT-1: All users are informed and trained
PR.AT-2 PR.AT-2: Privileged users understand roles & responsibilities
PR.AT-3 PR.AT-3: Third-party stakeholders (e.g., suppliers, customers, partners) understand roles & responsibilities
PR.AT-4 PR.AT-4: Senior executives understand roles & responsibilities
PR.AT-5 PR.AT-5: Physical and information security personnel understand roles & responsibilities
PR.DS Data Security (PR.DS) Data Security (PR.DS): Information and records (data) are managed consistent with the organization’s risk strategy to protect the confidentiality, integrity, and availability of information. PR.DS-1 PR.DS-1: Data-at-rest is protected
PR.DS-2 PR.DS-2: Data-in-transit is protected
PR.DS-3 PR.DS-3: Assets are formally managed throughout removal, transfers, and disposition
PR.DS-4 PR.DS-4: Adequate capacity to ensure availability is maintained
PR.DS-5 PR.DS-5: Protections against data leaks are implemented
PR.DS-6 PR.DS-6: Integrity checking mechanisms are used to verify software, firmware, and information integrity
PR.DS-7 PR.DS-7: The development and testing environment(s) are separate from the production environment
PR.IP Information Protection Processes and Procedures (PR.IP) Information Protection Processes and Procedures (PR.IP): Security policies (that address purpose, scope, roles, responsibilities, management commitment, and coordination among organizational entities), processes, and procedures are maintained and used to manage protection of information systems and assets. PR.IP-1 PR.IP-1: A baseline configuration of information technology/industrial control systems is created and maintained
PR.IP-2 PR.IP-2: A System Development Life Cycle to manage systems is implemented
PR.IP-3 PR.IP-3: Configuration change control processes are in place
PR.IP-4 PR.IP-4: Backups of information are conducted, maintained, and tested periodically
PR.IP-5 PR.IP-5: Policy and regulations regarding the physical operating environment for organizational assets are met
PR.IP-6 PR.IP-6: Data is destroyed according to policy
PR.IP-7 PR.IP-7: Protection processes are continuously improved
PR.IP-8 PR.IP-8: Effectiveness of protection technologies is shared with appropriate parties
PR.IP-9 PR.IP-9: Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed
PR.IP-10 PR.IP-10: Response and recovery plans are tested
PR.IP-11 PR.IP-11: Cybersecurity is included in human resources practices (e.g., deprovisioning, personnel screening)
PR.IP-12 PR.IP-12: A vulnerability management plan is developed and implemented
PR.MA Maintenance (PR.MA) Maintenance (PR.MA): Maintenance and repairs of industrial control and information system components is performed consistent with policies and procedures. PR.MA-1 PR.MA-1: Maintenance and repair of organizational assets is performed and logged in a timely manner, with approved and controlled tools
PR.MA-2 PR.MA-2: Remote maintenance of organizational assets is approved, logged, and performed in a manner that prevents unauthorized access
PR.PT Protective Technology (PR.PT) Protective Technology (PR.PT): Technical security solutions are managed to ensure the security and resilience of systems and assets, consistent with related policies, procedures, and agreements. PR.PT-1 PR.PT-1: Audit/log records are determined, documented, implemented, and reviewed in accordance with policy
PR.PT-2 PR.PT-2: Removable media is protected and its use restricted according to policy
PR.PT-3 PR.PT-3: Access to systems and assets is controlled, incorporating the principle of least functionality
PR.PT-4 PR.PT-4: Communications and control networks are protected
DE DETECT (DE) DE.AE Anomalies and Events (DE.AE) Anomalies and Events (DE.AE): Anomalous activity is detected in a timely manner and the potential impact of events is understood. DE.AE-1 DE.AE-1: A baseline of network operations and expected data flows for users and systems is established and managed
DE.AE-2 DE.AE-2: Detected events are analyzed to understand attack targets and methods
DE.AE-3 DE.AE-3: Event data are aggregated and correlated from multiple sources and sensors
DE.AE-4 DE.AE-4: Impact of events is determined
DE.AE-5 DE.AE-5: Incident alert thresholds are established
DE.CM Security Continuous Monitoring (DE.CM) Security Continuous Monitoring (DE.CM): The information system and assets are monitored at discrete intervals to identify cybersecurity events and verify the effectiveness of protective measures. DE.CM-1 DE.CM-1: The network is monitored to detect potential cybersecurity events
DE.CM-2 DE.CM-2: The physical environment is monitored to detect potential cybersecurity events
DE.CM-3 DE.CM-3: Personnel activity is monitored to detect potential cybersecurity events
DE.CM-4 DE.CM-4: Malicious code is detected
DE.CM-5 DE.CM-5: Unauthorized mobile code is detected
DE.CM-6 DE.CM-6: External service provider activity is monitored to detect potential cybersecurity events
DE.CM-7 DE.CM-7: Monitoring for unauthorized personnel, connections, devices, and software is performed
DE.CM-8 DE.CM-8: Vulnerability scans are performed
DE.DP Detection Processes (DE.DP) Detection Processes (DE.DP): Detection processes and procedures are maintained and tested to ensure timely and adequate awareness of anomalous events. DE.DP-1 DE.DP-1: Roles and responsibilities for detection are well defined to ensure accountability
DE.DP-2 DE.DP-2: Detection activities comply with all applicable requirements
DE.DP-3 DE.DP-3: Detection processes are tested
DE.DP-4 DE.DP-4: Event detection information is communicated to appropriate parties
DE.DP-5 DE.DP-5: Detection processes are continuously improved
RS RESPOND (RS) RS.RP Response Planning (RS.RP) Response Planning (RS.RP): Response processes and procedures are executed and maintained, to ensure timely response to detected cybersecurity events. RS.RP-1 RS.RP-1: Response plan is executed during or after an event
RS.CO Communications (RS.CO) Communications (RS.CO): Response activities are coordinated with internal and external stakeholders, as appropriate, to include external support from law enforcement agencies. RS.CO-1 RS.CO-1: Personnel know their roles and order of operations when a response is needed
RS.CO-2 RS.CO-2: Events are reported consistent with established criteria
RS.CO-3 RS.CO-3: Information is shared consistent with response plans
RS.CO-4 RS.CO-4: Coordination with stakeholders occurs consistent with response plans
RS.CO-5 RS.CO-5: Voluntary information sharing occurs with external stakeholders to achieve broader cybersecurity situational awareness
RS.AN Analysis (RS.AN) Analysis (RS.AN): Analysis is conducted to ensure adequate response and support recovery activities. RS.AN-1 RS.AN-1: Notifications from detection systems are investigated 
RS.AN-2 RS.AN-2: The impact of the incident is understood
RS.AN-3 RS.AN-3: Forensics are performed
RS.AN-4 RS.AN-4: Incidents are categorized consistent with response plans
RS.MI Mitigation (RS.MI) Mitigation (RS.MI): Activities are performed to prevent expansion of an event, mitigate its effects, and eradicate the incident. RS.MI-1 RS.MI-1: Incidents are contained
RS.MI-2 RS.MI-2: Incidents are mitigated
RS.MI-3 RS.MI-3: Newly identified vulnerabilities are mitigated or documented as accepted risks
RS.IM Improvements (RS.IM) Improvements (RS.IM): Organizational response activities are improved by incorporating lessons learned from current and previous detection/response activities. RS.IM-1 RS.IM-1: Response plans incorporate lessons learned
RS.IM-2 RS.IM-2: Response strategies are updated
RC RECOVER (RC) RC.RP Recovery Planning (RC.RP) Recovery Planning (RC.RP): Recovery processes and procedures are executed and maintained to ensure timely restoration of systems or assets affected by cybersecurity events. RC.RP-1 RC.RP-1: Recovery plan is executed during or after an event
RC.IM Improvements (RC.IM) Improvements (RC.IM): Recovery planning and processes are improved by incorporating lessons learned into future activities. RC.IM-1 RC.IM-1: Recovery plans incorporate lessons learned
RC.IM-2 RC.IM-2: Recovery strategies are updated
RC.CO Communications (RC.CO) Communications (RC.CO): Restoration activities are coordinated with internal and external parties, such as coordinating centers, Internet Service Providers, owners of attacking systems, victims, other CSIRTs, and vendors. RC.CO-1 RC.CO-1: Public relations are managed
RC.CO-2 RC.CO-2: Reputation after an event is repaired
RC.CO-3 RC.CO-3: Recovery activities are communicated to internal stakeholders and executive and management teams
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment