框架
NIST Cybersecurity Framework 2.0
概述
这是NIST发布的一套自愿性网络安全成果框架,发布于2024年2月。它包含六项职能(治理、识别、保护、检测、响应、恢复)、22个类别和106个子类别。该框架说明的是要实现什么,而非如何实现:组织通过当前概况和目标概况来描述自身所处的位置以及希望达到的状态。
适用人群
适用于任何规模或行业的组织。美国联邦机构将其与NIST风险管理框架结合使用,许多监管机构和保险公司都会引用该框架,董事会也利用它来组织网络安全汇报。
评估方式
CSF没有官方认证或审计机制。组织可自行评估其概况,也可委托独立机构进行评估;声称自己“通过CSF认证”的说法并非NIST所为。
106
子类别
89
映射到其他框架
100%
已覆盖主题(50/50)
对比分析
NIST CSF 2.0 vs ISO 27001NIST CSF 2.0 vs CIS v8.1NIST CSF 2.0 vs SOC 2NIST CSF 2.0 vs 800-53NIST CSF 2.0 vs HIPAANIST CSF 2.0 vs NIS2NIST CSF 2.0 vs Essential Eight
要求
要求编号和标题均按各框架官方发布的英文原文显示。
| ID | 要求 | 主题 | 映射于 |
|---|---|---|---|
| Detect (DE) · 11 | |||
| DE.AE-02 | Potentially adverse events are analyzed to better understand associated activities | 入侵检测, 异常检测 | 10 / 13 |
| DE.AE-03 | Information is correlated from multiple sources | 日志与审计, SIEM / SOC | 10 / 13 |
| DE.AE-04 | The estimated impact and scope of adverse events are understood | 异常检测 | 9 / 13 |
| DE.AE-06 | Information on adverse events is provided to authorized staff and tools | SIEM / SOC | 10 / 13 |
| DE.AE-07 | Cyber threat intelligence and other contextual information are integrated into the analysis | 威胁情报 | 6 / 13 |
| DE.AE-08 | Incidents are declared when adverse events meet the defined incident criteria | SIEM / SOC | 10 / 13 |
| DE.CM-01 | Networks and network services are monitored to find potentially adverse events | DNS 安全, WAF, 持续监控, 入侵检测 | 11 / 13 |
| DE.CM-02 | The physical environment is monitored to find potentially adverse events | 物理安全 | 8 / 13 |
| DE.CM-03 | Personnel activity and technology usage are monitored to find potentially adverse events | 持续监控, 内部威胁 | 11 / 13 |
| DE.CM-06 | External service provider activities and services are monitored to find potentially adverse events | 供应商风险管理 | 10 / 13 |
| DE.CM-09 | Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events | 终端防护, 邮件安全, 持续监控, 异常检测 | 11 / 13 |
| Govern (GV) · 31 | |||
| GV.OC-01 | The organizational mission is understood and informs cybersecurity risk management | 业务环境 | 5 / 13 |
| GV.OC-02 | Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered | — | |
| GV.OC-03 | Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed | 合规 | 10 / 13 |
| GV.OC-04 | Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated | 业务环境, 业务连续性 | 8 / 13 |
| GV.OC-05 | Outcomes, capabilities, and services that the organization depends on are understood and communicated | 业务环境 | 5 / 13 |
| GV.OV-01 | Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction | — | |
| GV.OV-02 | The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks | — | |
| GV.OV-03 | Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed | 合规 | 10 / 13 |
| GV.PO-01 | Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced | 治理政策 | 9 / 13 |
| GV.PO-02 | Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission | 治理政策 | 9 / 13 |
| GV.RM-01 | Risk management objectives are established and agreed to by organizational stakeholders | 风险管理 | 10 / 13 |
| GV.RM-02 | Risk appetite and risk tolerance statements are established, communicated, and maintained | 风险管理 | 10 / 13 |
| GV.RM-03 | Cybersecurity risk management activities and outcomes are included in enterprise risk management processes | 风险管理 | 10 / 13 |
| GV.RM-04 | Strategic direction that describes appropriate risk response options is established and communicated | — | |
| GV.RM-05 | Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties | — | |
| GV.RM-06 | A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated | 风险管理 | 10 / 13 |
| GV.RM-07 | Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions | — | |
| GV.RR-01 | Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving | 角色与职责 | 9 / 13 |
| GV.RR-02 | Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced | 角色与职责 | 9 / 13 |
| GV.RR-03 | Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies | 角色与职责 | 9 / 13 |
| GV.RR-04 | Cybersecurity is included in human resources practices | 内部威胁 | 8 / 13 |
| GV.SC-01 | A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders | 供应链风险 | 9 / 13 |
| GV.SC-02 | Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally | — | |
| GV.SC-03 | Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes | 供应链风险 | 9 / 13 |
| GV.SC-04 | Suppliers are known and prioritized by criticality | 供应商风险管理 | 10 / 13 |
| GV.SC-05 | Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties | 供应链风险 | 9 / 13 |
| GV.SC-06 | Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships | 供应商风险管理 | 10 / 13 |
| GV.SC-07 | The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship | 供应商风险管理 | 10 / 13 |
| GV.SC-08 | Relevant suppliers and other third parties are included in incident planning, response, and recovery activities | — | |
| GV.SC-09 | Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle | 供应链风险 | 9 / 13 |
| GV.SC-10 | Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement | — | |
| Identify (ID) · 21 | |||
| ID.AM-01 | Inventories of hardware managed by the organization are maintained | 资产管理 | 13 / 13 |
| ID.AM-02 | Inventories of software, services, and systems managed by the organization are maintained | 资产管理 | 13 / 13 |
| ID.AM-03 | Representations of the organization's authorized network communication and internal and external network data flows are maintained | 防火墙 / 网络分段 | 9 / 13 |
| ID.AM-04 | Inventories of services provided by suppliers are maintained | 资产管理, 云安全 | 13 / 13 |
| ID.AM-05 | Assets are prioritized based on classification, criticality, resources, and impact on the mission | 数据分类 | 9 / 13 |
| ID.AM-07 | Inventories of data and corresponding metadata for designated data types are maintained | 数据分类 | 9 / 13 |
| ID.AM-08 | Systems, hardware, software, services, and data are managed throughout their life cycles | 资产管理 | 13 / 13 |
| ID.IM-01 | Improvements are identified from evaluations | — | |
| ID.IM-02 | Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties | — | |
| ID.IM-03 | Improvements are identified from execution of operational processes, procedures, and activities | 经验教训 | 9 / 13 |
| ID.IM-04 | Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved | 事件响应, 恢复规划 | 12 / 13 |
| ID.RA-01 | Vulnerabilities in assets are identified, validated, and recorded | 漏洞管理 | 13 / 13 |
| ID.RA-02 | Cyber threat intelligence is received from information sharing forums and sources | 威胁情报 | 6 / 13 |
| ID.RA-03 | Internal and external threats to the organization are identified and recorded | 风险评估, 威胁情报 | 10 / 13 |
| ID.RA-04 | Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded | 风险评估 | 10 / 13 |
| ID.RA-05 | Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization | 风险评估 | 10 / 13 |
| ID.RA-06 | Risk responses are chosen, prioritized, planned, tracked, and communicated | 风险评估 | 10 / 13 |
| ID.RA-07 | Changes and exceptions are managed, assessed for risk impact, recorded, and tracked | — | |
| ID.RA-08 | Processes for receiving, analyzing, and responding to vulnerability disclosures are established | 漏洞管理 | 13 / 13 |
| ID.RA-09 | The authenticity and integrity of hardware and software are assessed prior to acquisition and use | 供应链风险 | 9 / 13 |
| ID.RA-10 | Critical suppliers are assessed prior to acquisition | 供应商风险管理 | 10 / 13 |
| Protect (PR) · 22 | |||
| PR.AA-01 | Identities and credentials for authorized users, services, and hardware are managed by the organization | 访问控制 | 11 / 13 |
| PR.AA-02 | Identities are proofed and bound to credentials based on the context of interactions | — | |
| PR.AA-03 | Users, services, and hardware are authenticated | 多因素认证, 零信任, API 安全 | 10 / 13 |
| PR.AA-04 | Identity assertions are protected, conveyed, and verified | 零信任 | 7 / 13 |
| PR.AA-05 | Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties | 访问控制, 特权访问, 零信任, 移动安全 | 12 / 13 |
| PR.AA-06 | Physical access to assets is managed, monitored, and enforced commensurate with risk | 物理安全 | 8 / 13 |
| PR.AT-01 | Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind | 意识与培训 | 10 / 13 |
| PR.AT-02 | Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind | 意识与培训 | 10 / 13 |
| PR.DS-01 | The confidentiality, integrity, and availability of data-at-rest are protected | 加密, 数据保护, DLP | 11 / 13 |
| PR.DS-02 | The confidentiality, integrity, and availability of data-in-transit are protected | 加密, 数据保护, 邮件安全, DLP | 12 / 13 |
| PR.DS-10 | The confidentiality, integrity, and availability of data-in-use are protected | 数据保护, DLP | 11 / 13 |
| PR.DS-11 | Backups of data are created, protected, maintained, and tested | 备份与恢复 | 11 / 13 |
| PR.IR-01 | Networks and environments are protected from unauthorized logical access and usage | 防火墙 / 网络分段, Web 安全, 零信任, 云安全, DNS 安全, WAF, API 安全 | 11 / 13 |
| PR.IR-02 | The organization's technology assets are protected from environmental threats | 物理安全 | 8 / 13 |
| PR.IR-03 | Mechanisms are implemented to achieve resilience requirements in normal and adverse situations | 业务连续性, 灾难恢复 | 10 / 13 |
| PR.IR-04 | Adequate resource capacity to ensure availability is maintained | — | |
| PR.PS-01 | Configuration management practices are established and applied | 安全配置, 移动安全, 云安全 | 12 / 13 |
| PR.PS-02 | Software is maintained, replaced, and removed commensurate with risk | 补丁管理 | 10 / 13 |
| PR.PS-03 | Hardware is maintained, replaced, and removed commensurate with risk | — | |
| PR.PS-04 | Log records are generated and made available for continuous monitoring | 日志与审计 | 10 / 13 |
| PR.PS-05 | Installation and execution of unauthorized software are prevented | 终端防护 | 10 / 13 |
| PR.PS-06 | Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle | 安全开发, Web 安全, API 安全 | 8 / 13 |
| Recover (RC) · 8 | |||
| RC.CO-03 | Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders | 沟通与恢复 | 8 / 13 |
| RC.CO-04 | Public updates on incident recovery are shared using approved methods and messaging | 沟通与恢复 | 8 / 13 |
| RC.RP-01 | The recovery portion of the incident response plan is executed once initiated from the incident response process | 恢复规划 | 9 / 13 |
| RC.RP-02 | Recovery actions are selected, scoped, prioritized, and performed | 恢复规划, 灾难恢复 | 10 / 13 |
| RC.RP-03 | The integrity of backups and other restoration assets is verified before using them for restoration | 备份与恢复 | 11 / 13 |
| RC.RP-04 | Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms | 业务连续性 | 8 / 13 |
| RC.RP-05 | The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed | 沟通与恢复, 灾难恢复 | 11 / 13 |
| RC.RP-06 | The end of incident recovery is declared based on criteria, and incident-related documentation is completed | 经验教训 | 9 / 13 |
| Respond (RS) · 13 | |||
| RS.AN-03 | Analysis is performed to establish what has taken place during an incident and the root cause of the incident | 取证分析 | 7 / 13 |
| RS.AN-06 | Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved | 取证分析 | 7 / 13 |
| RS.AN-07 | Incident data and metadata are collected, and their integrity and provenance are preserved | 取证分析 | 7 / 13 |
| RS.AN-08 | An incident's magnitude is estimated and validated | — | |
| RS.CO-02 | Internal and external stakeholders are notified of incidents | 报告 | 12 / 13 |
| RS.CO-03 | Information is shared with designated internal and external stakeholders | 沟通 | 8 / 13 |
| RS.MA-01 | The incident response plan is executed in coordination with relevant third parties once an incident is declared | 事件响应 | 12 / 13 |
| RS.MA-02 | Incident reports are triaged and validated | 事件响应 | 12 / 13 |
| RS.MA-03 | Incidents are categorized and prioritized | 事件响应 | 12 / 13 |
| RS.MA-04 | Incidents are escalated or elevated as needed | 事件响应 | 12 / 13 |
| RS.MA-05 | The criteria for initiating incident recovery are applied | — | |
| RS.MI-01 | Incidents are contained | 缓解 | 8 / 13 |
| RS.MI-02 | Incidents are eradicated | 缓解 | 8 / 13 |
主题覆盖情况
已映射 NIST CSF 2.0 要求的主题(50):