フレームワーク
NIST Cybersecurity Framework 2.0
概要
2024年2月に公表された、NISTによるサイバーセキュリティアウトカムの任意フレームワークです。6つの機能(統治、識別、防御、検知、対応、復旧)、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 とタイトルは、各フレームワークが公開している英語の表記のまま表示しています。
| ID | 要件 | トピック | マッピング先: |
|---|---|---|---|
| Detect (DE) · 11 | |||
| DE.AE-02 | Potentially adverse events are analyzed to better understand associated activities | 侵入検知, 異常検知 | 13 件中 10 件 |
| DE.AE-03 | Information is correlated from multiple sources | ログ記録と監査, SIEM / SOC | 13 件中 10 件 |
| DE.AE-04 | The estimated impact and scope of adverse events are understood | 異常検知 | 13 件中 9 件 |
| DE.AE-06 | Information on adverse events is provided to authorized staff and tools | SIEM / SOC | 13 件中 10 件 |
| DE.AE-07 | Cyber threat intelligence and other contextual information are integrated into the analysis | 脅威インテリジェンス | 13 件中 6 件 |
| DE.AE-08 | Incidents are declared when adverse events meet the defined incident criteria | SIEM / SOC | 13 件中 10 件 |
| DE.CM-01 | Networks and network services are monitored to find potentially adverse events | DNSセキュリティ, WAF, 継続的モニタリング, 侵入検知 | 13 件中 11 件 |
| DE.CM-02 | The physical environment is monitored to find potentially adverse events | 物理的セキュリティ | 13 件中 8 件 |
| DE.CM-03 | Personnel activity and technology usage are monitored to find potentially adverse events | 継続的モニタリング, 内部脅威 | 13 件中 11 件 |
| DE.CM-06 | External service provider activities and services are monitored to find potentially adverse events | ベンダーリスク管理 | 13 件中 10 件 |
| DE.CM-09 | Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events | エンドポイント保護, メールセキュリティ, 継続的モニタリング, 異常検知 | 13 件中 11 件 |
| Govern (GV) · 31 | |||
| GV.OC-01 | The organizational mission is understood and informs cybersecurity risk management | 事業環境 | 13 件中 5 件 |
| 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 | コンプライアンス | 13 件中 10 件 |
| GV.OC-04 | Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated | 事業環境, 事業継続 | 13 件中 8 件 |
| GV.OC-05 | Outcomes, capabilities, and services that the organization depends on are understood and communicated | 事業環境 | 13 件中 5 件 |
| 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 | コンプライアンス | 13 件中 10 件 |
| GV.PO-01 | Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced | ガバナンスポリシー | 13 件中 9 件 |
| GV.PO-02 | Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission | ガバナンスポリシー | 13 件中 9 件 |
| GV.RM-01 | Risk management objectives are established and agreed to by organizational stakeholders | リスクマネジメント | 13 件中 10 件 |
| GV.RM-02 | Risk appetite and risk tolerance statements are established, communicated, and maintained | リスクマネジメント | 13 件中 10 件 |
| GV.RM-03 | Cybersecurity risk management activities and outcomes are included in enterprise risk management processes | リスクマネジメント | 13 件中 10 件 |
| 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 | リスクマネジメント | 13 件中 10 件 |
| 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 | 役割と責任 | 13 件中 9 件 |
| GV.RR-02 | Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced | 役割と責任 | 13 件中 9 件 |
| GV.RR-03 | Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies | 役割と責任 | 13 件中 9 件 |
| GV.RR-04 | Cybersecurity is included in human resources practices | 内部脅威 | 13 件中 8 件 |
| GV.SC-01 | A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders | サプライチェーンリスク | 13 件中 9 件 |
| 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 | サプライチェーンリスク | 13 件中 9 件 |
| GV.SC-04 | Suppliers are known and prioritized by criticality | ベンダーリスク管理 | 13 件中 10 件 |
| 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 | サプライチェーンリスク | 13 件中 9 件 |
| GV.SC-06 | Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships | ベンダーリスク管理 | 13 件中 10 件 |
| 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 | ベンダーリスク管理 | 13 件中 10 件 |
| 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 | サプライチェーンリスク | 13 件中 9 件 |
| 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 | ファイアウォール / ネットワークセグメンテーション | 13 件中 9 件 |
| 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 | データ分類 | 13 件中 9 件 |
| ID.AM-07 | Inventories of data and corresponding metadata for designated data types are maintained | データ分類 | 13 件中 9 件 |
| 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 | 教訓の反映 | 13 件中 9 件 |
| ID.IM-04 | Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved | インシデント対応, 復旧計画 | 13 件中 12 件 |
| 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 | 脅威インテリジェンス | 13 件中 6 件 |
| ID.RA-03 | Internal and external threats to the organization are identified and recorded | リスクアセスメント, 脅威インテリジェンス | 13 件中 10 件 |
| ID.RA-04 | Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded | リスクアセスメント | 13 件中 10 件 |
| ID.RA-05 | Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization | リスクアセスメント | 13 件中 10 件 |
| ID.RA-06 | Risk responses are chosen, prioritized, planned, tracked, and communicated | リスクアセスメント | 13 件中 10 件 |
| 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 | サプライチェーンリスク | 13 件中 9 件 |
| ID.RA-10 | Critical suppliers are assessed prior to acquisition | ベンダーリスク管理 | 13 件中 10 件 |
| Protect (PR) · 22 | |||
| PR.AA-01 | Identities and credentials for authorized users, services, and hardware are managed by the organization | アクセス制御 | 13 件中 11 件 |
| 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 セキュリティ | 13 件中 10 件 |
| PR.AA-04 | Identity assertions are protected, conveyed, and verified | ゼロトラスト | 13 件中 7 件 |
| 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 | アクセス制御, 特権アクセス, ゼロトラスト, モバイルセキュリティ | 13 件中 12 件 |
| PR.AA-06 | Physical access to assets is managed, monitored, and enforced commensurate with risk | 物理的セキュリティ | 13 件中 8 件 |
| 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 | 意識向上とトレーニング | 13 件中 10 件 |
| 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 | 意識向上とトレーニング | 13 件中 10 件 |
| PR.DS-01 | The confidentiality, integrity, and availability of data-at-rest are protected | 暗号化, データ保護, DLP | 13 件中 11 件 |
| PR.DS-02 | The confidentiality, integrity, and availability of data-in-transit are protected | 暗号化, データ保護, メールセキュリティ, DLP | 13 件中 12 件 |
| PR.DS-10 | The confidentiality, integrity, and availability of data-in-use are protected | データ保護, DLP | 13 件中 11 件 |
| PR.DS-11 | Backups of data are created, protected, maintained, and tested | バックアップと復旧 | 13 件中 11 件 |
| PR.IR-01 | Networks and environments are protected from unauthorized logical access and usage | ファイアウォール / ネットワークセグメンテーション, Web セキュリティ, ゼロトラスト, クラウドセキュリティ, DNSセキュリティ, WAF, API セキュリティ | 13 件中 11 件 |
| PR.IR-02 | The organization's technology assets are protected from environmental threats | 物理的セキュリティ | 13 件中 8 件 |
| PR.IR-03 | Mechanisms are implemented to achieve resilience requirements in normal and adverse situations | 事業継続, ディザスタリカバリ | 13 件中 10 件 |
| PR.IR-04 | Adequate resource capacity to ensure availability is maintained | — | |
| PR.PS-01 | Configuration management practices are established and applied | 安全な構成, モバイルセキュリティ, クラウドセキュリティ | 13 件中 12 件 |
| PR.PS-02 | Software is maintained, replaced, and removed commensurate with risk | パッチ管理 | 13 件中 10 件 |
| 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 | ログ記録と監査 | 13 件中 10 件 |
| PR.PS-05 | Installation and execution of unauthorized software are prevented | エンドポイント保護 | 13 件中 10 件 |
| PR.PS-06 | Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle | セキュア開発, Web セキュリティ, API セキュリティ | 13 件中 8 件 |
| Recover (RC) · 8 | |||
| RC.CO-03 | Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders | 連絡と復旧 | 13 件中 8 件 |
| RC.CO-04 | Public updates on incident recovery are shared using approved methods and messaging | 連絡と復旧 | 13 件中 8 件 |
| RC.RP-01 | The recovery portion of the incident response plan is executed once initiated from the incident response process | 復旧計画 | 13 件中 9 件 |
| RC.RP-02 | Recovery actions are selected, scoped, prioritized, and performed | 復旧計画, ディザスタリカバリ | 13 件中 10 件 |
| RC.RP-03 | The integrity of backups and other restoration assets is verified before using them for restoration | バックアップと復旧 | 13 件中 11 件 |
| RC.RP-04 | Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms | 事業継続 | 13 件中 8 件 |
| RC.RP-05 | The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed | 連絡と復旧, ディザスタリカバリ | 13 件中 11 件 |
| RC.RP-06 | The end of incident recovery is declared based on criteria, and incident-related documentation is completed | 教訓の反映 | 13 件中 9 件 |
| 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 | フォレンジック | 13 件中 7 件 |
| RS.AN-06 | Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved | フォレンジック | 13 件中 7 件 |
| RS.AN-07 | Incident data and metadata are collected, and their integrity and provenance are preserved | フォレンジック | 13 件中 7 件 |
| RS.AN-08 | An incident's magnitude is estimated and validated | — | |
| RS.CO-02 | Internal and external stakeholders are notified of incidents | 報告 | 13 件中 12 件 |
| RS.CO-03 | Information is shared with designated internal and external stakeholders | コミュニケーション | 13 件中 8 件 |
| RS.MA-01 | The incident response plan is executed in coordination with relevant third parties once an incident is declared | インシデント対応 | 13 件中 12 件 |
| RS.MA-02 | Incident reports are triaged and validated | インシデント対応 | 13 件中 12 件 |
| RS.MA-03 | Incidents are categorized and prioritized | インシデント対応 | 13 件中 12 件 |
| RS.MA-04 | Incidents are escalated or elevated as needed | インシデント対応 | 13 件中 12 件 |
| RS.MA-05 | The criteria for initiating incident recovery are applied | — | |
| RS.MI-01 | Incidents are contained | 緩和策 | 13 件中 8 件 |
| RS.MI-02 | Incidents are eradicated | 緩和策 | 13 件中 8 件 |
トピックのカバレッジ
NIST CSF 2.0のマッピング済み要件を持つトピック(50件):
ガバナンスポリシー意識向上とトレーニングリスクマネジメントサプライチェーンリスク役割と責任コンプライアンス資産管理リスクアセスメント事業環境データ分類脆弱性管理脅威インテリジェンスアクセス制御多要素認証暗号化データ保護バックアップと復旧特権アクセスファイアウォール / ネットワークセグメンテーションエンドポイント保護パッチ管理安全な構成セキュア開発メールセキュリティWeb セキュリティゼロトラストモバイルセキュリティクラウドセキュリティDNSセキュリティWAFDLP継続的モニタリングログ記録と監査侵入検知異常検知SIEM / SOCインシデント対応フォレンジックコミュニケーション緩和策報告復旧計画事業継続教訓の反映連絡と復旧ディザスタリカバリAPI セキュリティ内部脅威ベンダーリスク管理物理的セキュリティ