NIST Cybersecurity Framework 2.0

비교 자료

요구사항

요구사항 ID와 제목은 각 프레임워크가 발표한 그대로 영문으로 표시됩니다.

NIST Cybersecurity Framework 2.0 요구사항

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	—	0
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	—	0
GV.OV-02	The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks	—	0
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	—	0
GV.RM-05	Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties	—	0
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	—	0
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	—	0
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	—	0
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	—	0
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	—	0
ID.IM-02	Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties	—	0
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	—	0
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	—	0
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	방화벽 / 네트워크 분리, 웹 보안, 제로 트러스트, 클라우드 보안, 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	—	0
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	—	0
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	보안 개발, 웹 보안, 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	—	0
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	—	0
RS.MI-01	Incidents are contained	완화	8 / 13
RS.MI-02	Incidents are eradicated	완화	8 / 13

주제 커버리지

NIST CSF 2.0 요구사항과 매핑된 주제 (50개):