Cybersecurity Framework Security Policy Mapping Table



Similar documents
CRR-NIST CSF Crosswalk 1

Applying IBM Security solutions to the NIST Cybersecurity Framework

Improving Critical Infrastructure Cybersecurity Executive Order Preliminary Cybersecurity Framework

Automation Suite for NIST Cyber Security Framework

NIST CYBERSECURITY FRAMEWORK COMPLIANCE WITH OBSERVEIT

Happy First Anniversary NIST Cybersecurity Framework:

Critical Manufacturing Cybersecurity Framework Implementation Guidance

NIST Cybersecurity Framework & A Tale of Two Criticalities

Framework for Improving Critical Infrastructure Cybersecurity

Appendix B: Mapping Cybersecurity Assessment Tool to NIST

Framework for Improving Critical Infrastructure Cybersecurity

NIST Cybersecurity Framework Sean Sweeney, Information Security Officer 5/20/2015

Framework for Improving Critical Infrastructure Cybersecurity

Discussion Draft of the Preliminary Cybersecurity Framework

Framework for Improving Critical Infrastructure Cybersecurity

State Agency Cyber Security Survey v October State Agency Cybersecurity Survey v 3.4

Welcome! Designing and Building a Cybersecurity Program

IT ASSET MANAGEMENT Securing Assets for the Financial Services Sector

HITRUST Common Security Framework Summary of Changes

Weak (1.0) Limited (2.0) Effective (3.0) Strong (4.0) Very Strong (5.0)

Applying Framework to Mobile & BYOD

Building Security In:

Discussion Draft of the Preliminary Cybersecurity Framework Illustrative Examples

CRR Supplemental Resource Guide. Volume 5. Incident Management. Version 1.1

The NIST Framework for Improving Critical Infrastructure Cybersecurity - An Executive Guide

Attachment A. Identification of Risks/Cybersecurity Governance

ISO 27002:2013 Version Change Summary

The President issued an Executive Order Improving Critical Infrastructure Cybersecurity, on February 2013.

Framework for Improving Critical Infrastructure Cybersecurity

C Y B E R S E C U R I T Y INSIDER THREAT BEST PRACTICES GUIDE JULY 2014

HIPAA CRITICAL AREAS TECHNICAL SECURITY FOCUS FOR CLOUD DEPLOYMENT

Designing & Building a Cybersecurity Program. Based on the NIST Cybersecurity Framework (CSF)

IT AUDIT WHO WE ARE. Current Trends and Top Risks of /9/2015. Eric Vyverberg. Randy Armknecht. David Kupinski

Cybersecurity The role of Internal Audit

DATA INTEGRITY. Reducing the impact of an attack BUILDING BLOCK WHITE PAPER

Cybersecurity Framework: Current Status and Next Steps

¼ããÀ ããè¾ã ¹ãÆãä ã¼ãîãä ã ããõà ãäìããä ã½ã¾ã ºããñ à Securities and Exchange Board of India

Security Controls What Works. Southside Virginia Community College: Security Awareness

Executive Order 13636: The Healthcare Sector and the Cybersecurity Framework. September 23, 2014

ACCESS RIGHTS MANAGEMENT Securing Assets for the Financial Services Sector

University of Sunderland Business Assurance Information Security Policy

Cybersecurity in the Utilities Sector Best Practices and Implementation 2014 Canadian Utilities IT & Telecom Conference September 24, 2014

Data Breach Response Planning: Laying the Right Foundation

OCIE CYBERSECURITY INITIATIVE

The Cyber OODA Loop: How Your Attacker Should Help You Design Your Defense. Tony Sager The Center for Internet Security

ISO Controls and Objectives

INFORMATION SECURITY GOVERNANCE ASSESSMENT TOOL FOR HIGHER EDUCATION

LAMAR STATE COLLEGE - ORANGE INFORMATION RESOURCES SECURITY MANUAL. for INFORMATION RESOURCES

Into the cybersecurity breach

<Choose> Addendum Windows Azure Data Processing Agreement Amendment ID M129

Music Recording Studio Security Program Security Assessment Version 1.1

IT Best Practices Audit TCS offers a wide range of IT Best Practices Audit content covering 15 subjects and over 2200 topics, including:

Enrollment for Education Solutions Addendum Microsoft Online Services Agreement Amendment 10 EES

Information Shield Solution Matrix for CIP Security Standards

Microsoft s Compliance Framework for Online Services

Microsoft Online Subscription Agreement/Open Program License Amendment Microsoft Online Services Security Amendment Amendment ID MOS10

Using the HITRUST CSF to Assess Cybersecurity Preparedness 1 of 6

Acceptance Page 2. Revision History 3. Introduction 14. Control Categories 15. Scope 15. General Requirements 15

How To Write A Cybersecurity Framework

Earning Your Security Trustmark+

Creating an Integrated Business Continuity / Disaster Recovery (BC/DR) Program. A Hands on Workshop

Information Security Program CHARTER

Central Agency for Information Technology

REGULATIONS FOR THE SECURITY OF INTERNET BANKING

INFORMATION TECHNOLOGY SECURITY STANDARDS

Unified Security Anywhere HIPAA COMPLIANCE ACHIEVING HIPAA COMPLIANCE WITH MASERGY PROFESSIONAL SERVICES

Summary of CIP Version 5 Standards

Cybersecurity and internal audit. August 15, 2014

IBX Business Network Platform Information Security Controls Document Classification [Public]

Information Security Policy and Handbook Overview. ITSS Information Security June 2015

How To Manage Security On A Networked Computer System

Domain 1 The Process of Auditing Information Systems

Does it state the management commitment and set out the organizational approach to managing information security?

Logging In: Auditing Cybersecurity in an Unsecure World

Understanding changes to the Trust Services Principles for SOC 2 reporting

INFORMATION SYSTEMS. Revised: August 2013

Addressing Cloud Computing Security Considerations

SECURITY RISK MANAGEMENT

Office 365 Data Processing Agreement with Model Clauses

Your Agency Just Had a Privacy Breach Now What?

Cybersecurity Framework. Executive Order Improving Critical Infrastructure Cybersecurity

Security and Privacy Controls for Federal Information Systems and Organizations

VMware vcloud Air HIPAA Matrix

Anatomy of a Cloud Computing Data Breach

Compliance Guide ISO Compliance Guide. September Contents. Introduction 1. Detailed Controls Mapping 2.

NIST Cybersecurity Initiatives. ARC World Industry Forum 2014

Intel Security Professional Services Leveraging NIST Cybersecurity Framework (CSF): Complexity is the enemy of security

Information security controls. Briefing for clients on Experian information security controls

Working with the FBI

Business Continuity for Cyber Threat

Looking at the SANS 20 Critical Security Controls

FACT SHEET: Ransomware and HIPAA

security policy Purpose The purpose of this paper is to outline the steps required for developing and maintaining a corporate security policy.

Transcription:

Cybersecurity Framework Security Policy Mapping Table The following table illustrates how specific requirements of the US Cybersecurity Framework [1] are addressed by the ISO 27002 standard and covered by sample policy documents within Information Security Policies Made Easy (ISO 27002). In most cases, a single document covers more than a single subcategory requirement. Function Category Subcategory CPL Sample Policy IDENTIFY (ID) Asset Management (): The 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. Asset Management Policy ISO 27002-8.1. Responsibility for assets ID.-1: Physical devices and systems within the organization are inventoried ID.-2: Software platforms and applications within the organization are inventoried ID.-3: The organizational communication and data flow is mapped ID.-4: External information systems are mapped and catalogued ID.-5: Resources are prioritized based on the classification / criticality / business value of hardware, devices, data, and software ID.-6: Workforce roles and responsibilities for business functions, including cybersecurity, are established 8.1.1 Inventory of assets 8.1.1 Inventory of assets Information Classification Policy 8.2 Information classification Information Security Organization Policy 6.1.1 Information security roles and

responsibilities ID Business Environment (BE): The organization's mission, objectives, stakeholders, and activities are understood and prioritized, and inform cybersecurity roles, responsibilities, and risk decisions. Information Security Planning Policy ISO 27002-6.1 Internal organization BE BE BE ID.BE-1: The organization s role in the supply chain and is identified and communicated ID.BE-2: The organization s place in critical infrastructure and their industry ecosystem is identified and communicated ID.BE-3: Priorities for organizational mission, objectives, and activities are established 5.1 Management direction for information security ID BE BE ID.BE-4: Dependencies and critical functions for delivery of critical services are established ID.BE-5: Resilience requirements to support delivery of critical services are established Governance (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. 17.1.1 Planning information security continuity 17.2 Redundancies Information Security Program Policy ISO - 5.1. Management direction for information security ID.GV-1: Organizational information security policy is established ID.GV-2: Information security roles & responsibility are coordinated and aligned 5.1.1 Policies for information security Information Security Organization Policy 6.1.1 Information security roles and responsibilities ID.GV-3: Legal and regulatory requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed ID.GV-4: Governance and risk management processes address cybersecurity risks 18.1 Compliance with legal and contractual requirements IT Risk Management Policy

4 Risk Assessment ID Risk Assessment (RA): The organization understands the cybersecurity risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals. IT Risk Management Policy ISO 27002: 4.0 Risk Management ID PROTECT (PR) RA RA RA RA RA ID.RA-1: Asset vulnerabilities are identified and documented ID.RA-2: Threat and vulnerability information is received from information sharing forums and sources. ID.RA-3: Threats to organizational assets are identified and documented ID.RA-4: Potential impacts are analyzed ID.RA-5: Risk responses are identified. Risk Management Strategy (RM): The organization's priorities, constraints, risk tolerances, and assumptions are established and used to support operational risk decisions.. RM RM RM ID.RM-1: Risk management processes are managed and agreed to ID.RM-2: Organizational risk tolerance is determined and clearly expressed ID.RM-3: The organization s determination of risk tolerance is informed by their role in critical infrastructure and sector specific risk analysis Access Control (AC): Access to information resources and associated facilities are limited to authorized users, processes or devices (including other information systems), and to authorized activities and transactions. IT Risk Management Policy ISO 27002: 4.0 Risk Management Access Control Policy ISO 27002-9. Access control AC PR.AC-1: Identities and credentials are managed for authorized devices and users Account Management Policy 9.2 User access management AC PR.AC-2: Physical access to resources is managed and secured Physical Access Security Policy

11.1.2 Physical entry controls AC PR.AC-3: Remote access is managed Remote Access Security Policy 9.1.2 Access to networks and network services AC PR.AC-4: Access permissions are managed 9.2.2 User access provisioning AC PR.AC-5: Network integrity is protected Network Security Policy 9.1.2 Access to networks and network services Awareness and Training (AT): The organization's personnel and partners are adequately trained to perform their information security- related duties and responsibilities consistent with related policies, procedures, and agreements. Security Awareness and Training Policy ISO 27002: 7.2.2 - Information security awareness, education and training PR PR.AT-1: General users are informed and trained PR.AT-2: Privileged users understand roles & responsibilities PR.AT-3: Third-party stakeholders (suppliers, customers, partners) understand roles & responsibilities Third Party Security Management 15.1.1 Information security policy for supplier relationships PR PR.AT-4: Senior executives understand roles & responsibilities PR.AT-5: Physical and information security personnel understand roles & responsibilities Data Security (DS): Information and records (data) are managed consistent with the organization's risk strategy to protect the confidentiality, integrity, and availability of information. Information Protection Policy PR.DS-1: Data-at-rest is protected Information Protection Policy 8.2.3 Handling of assets PR.DS-2: Data-in-motion is secured Information Exchange Policy

8.3.3 Physical media transfer PR.DS-3: Assets are formally managed throughout removal, transfers, and disposition Asset Management Policy 8.2.3 Handling of assets PR.DS-4: Adequate capacity to ensure availability is maintained. Operational Security Policy 12.1.3 Capacity management PR.DS-5: There is protection against data leaks PR.DS-6: Intellectual property is protected 8.1.3 Acceptable use of assets Acceptable Use of Assets 18.1.2 Intellectual property Rights PR.DS-7: Unnecessary assets are eliminated PR.DS-8: Separate testing environments are used in system development Application Development Security Policy 14.3.1 Protection of test data PR.DS-9: Privacy of individuals and personally identifiable information (PII) is protected Data Privacy Policy 18.1.4 Privacy and protection of personally identifiable information PR Information Protection Processes and Procedures (IP): Security policy (that addresses 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 Information Security Program Policy ISO 27002 14. System acquisition, development and maintenance & ISO 27002: 12 Operations security PR.IP-1: A baseline configuration of information technology/operational technology systems is created PR.IP-2: A System Development Life Cycle to manage systems is implemented System Configuration Management Policy 14.2 Security in development and support processes System Configuration Management Policy 14.2.1 Secure development policy PR.IP-3: Configuration change control processes are in Change Control Policy

place 12.1.2 Change management PR.IP-4: Backups of information are managed Information Backup Policy 12.3.1 Information backup PR.IP-5: Policy and regulations regarding the physical operating environment for organizational assets are met. Physical Security Policy 11.2.1 Equipment siting and protection PR.IP-6: Information is destroyed according to policy and requirements Information Disposal Policy 8.3.2 Disposal of media PR.IP-7: Protection processes are continuously improved 18.2.3 Technical compliance review PR.IP-8: Information sharing occurs with appropriate parties PR.IP-9: Response plans (Business Continuity Plan(s), Disaster Recovery Plan(s), Incident Handling Plan(s)) are in place and managed PR.IP-10: Response plans are exercised Information Exchange Security Policy 13.2.2 Agreements on information transfer IT Continuity Security Policy 17.1 Information security continuity 17.1.3 Verify, review and evaluate information security continuity PR.IP-11: Cybersecurity is included in human resources practices (de-provisioning, personnel screening, etc.) Personnel Security Management Policy 7.1.1 Screening PR Maintenance (MA): Maintenance and repairs of operational and information system components is performed consistent with policies and procedures. Physical Security Policy ISO 27002-11.2.4 Equipment maintenance 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: Remote maintenance of organizational assets is approved, logged, and performed in a manner that prevents unauthorized access and supports availability 11.2.5 Removal of assets 11.2.6 Security of equipment and assets off premises

requirements for important operational and information systems. PR Protective Technology (PT): Technical security solutions are managed to ensure the security and resilience of systems and assets, consistent with related policies, procedures, and agreements. Log Management Security Policy 12.4 Logging and monitoring PR.PT-1: Audit and log records are stored in accordance with audit policy Log Management Security Policy 12.4 Logging and monitoring PR.PT-2: Removable media are protected according to a specified policy Removable Media Policy 8.3.1 Management of removable media PR.PT-3: Access to systems and assets is appropriately controlled Access Control Policy 9.1.2 Access to networks and network services PR.PT-4: Communications networks are secured Network Security Policy 13.1 Network security management DETECT (DE) PR.PT-5: Specialized systems are protected according to the risk analysis (SCADA, ICS, DLS) Anomalies and Events (AE): Anomalous activity is detected in a timely manner and the potential impact of events is understood.. DE.AE-1: A baseline of normal operations and procedures is identified and managed DE.AE-2: Detected events are analyzed to understand attack targets and methods DE.AE-3: Cybersecurity data are correlated from diverse information sources DE.AE-4: Impact of potential cybersecurity events is determined. System Monitoring Security Policy ISO 27002-12.4 Logging and monitoring 12.1.1 Documented operating procedures 16.1.2 Reporting information security events 16.1.2 Reporting information security events 16.1.4 Assessment of and decision on information security events

DE.AE-05: Incident alert thresholds are created 16.1.2 Reporting information security events DE Security Continuous Monitoring (CM): The information system and assets are monitored to identify cybersecurity events and verify the effectiveness of protective measures. DE.CM-2: The physical environment is monitored to detect potential cybersecurity events DE.CM-3: Personnel activity is monitored to detect potential cybersecurity events DE.CM-4: Malicious code is detected DE.CM-5: Unauthorized mobile code is detected DE.CM-6: External service providers are monitored System Monitoring Security Policy ISO 27002-12.4.1 Event logging Physical Security Policy 11.1.1 Physical security perimeter System Monitoring Security Policy 11.1.3 Securing offices, rooms and facilities Malicious Software Management Policy 12.2.1 Controls against mal-ware Malicious Software Management Policy 12.2.1 Controls against mal-ware Third Party Security Policy 15.2 Supplier service delivery management DE DE.CM-7: Unauthorized resources are monitored DE.CM-8: Vulnerability assessments are performed Detection Processes (DP): Detection processes and procedures are maintained and tested to ensure timely and adequate awareness of anomalous events. DE.DP-1: Roles and responsibilities for detection are well defined to ensure accountability DE.DP-2: Detection activities comply with all applicable requirements, including those related to privacy and civil liberties System Monitoring Security Policy 18.2.3 Technical compliance review Incident Management Security Policy ISO 27002: 16. Information security incident management 16.1.1 Responsibilities and Procedures 18.1.1 Identification of applicable legislation and contractual requirements

DE.DP-3: Detection processes are exercised to ensure readiness DE.DP-4: Event detection information is communicated to appropriate parties DE.DP-5: Detection processes are continuously improved 16.1.5 Response to information security incidents 6.1.3 Contact with authorities 16.1.6 Learning from information security incidents RESPOND (RS) Response Planning (RP): Response processes and procedures are maintained and tested to ensure timely response of detected cybersecurity events. Security Incident Management Policy ISO - 16. Information security incident management RS RS.PL-1: Response plan is implemented during or after an event. Communications (CO): Response activities are coordinated with internal and external stakeholders, as appropriate, to include external support from federal, state, and local law enforcement agencies. Security Incident Management Policy 16.1.1 Responsibilities and Procedures ISO - 6.1.3 Contact with authorities RS RS.CO-1: Personnel know their roles and order of operations when a response is needed RS.CO-2: Events are reported consistent with established criteria RS.CO-3: Detection/response information, such as breach reporting requirements, is shared consistent with response plans, including those related to privacy and civil liberties RS.CO-4: Coordination with stakeholders occurs consistent with response plans, including those related to privacy and civil liberties RS.CO-5: Voluntary coordination occurs with external stakeholders (ex, business partners, information sharing and analysis centers, customers) Analysis (AN): Analysis is conducted to ensure adequate response and support recovery activities. 16.1.1 Responsibilities and Procedures 16.1.2 Reporting information security events 16.1.5 Response to information security incidents 6.1.4 Contact with special interest groups 6.1.3 Contact with authorities Security Incident Management Policy ISO - 16.1.4 Assessment of and decision on

information security events. RS RS.AN-1: Notifications from the detection system are investigated RS.AN-2: Understand the impact of the incident RS.AN-3: Forensics are performed RS.AN-4: Incidents are classified consistent with response plans Mitigation (MI): Activities are performed to prevent expansion of an event, mitigate its effects, and eradicate the incident. Security Incident Management Policy ISO - 16.1.5 Response to information security incidents RS MI MI RS.MI-1: Incidents are contained RS.MI-2: Incidents are eradicated Improvements (IM): Organizational response activities are improved by incorporating lessons learned from current and previous detection/response activities. Security Incident Management Policy ISO - 16.1.6 Learning from information security incidents RECOVER (RC) IM IM RS.IM-1: Response plans incorporate lessons learned RS.IM-2: Response strategies are updated Recovery Planning (RP): Recovery processes and procedures are maintained and tested to ensure timely restoration of systems or assets affected by cybersecurity events. IT Continuity Security Policy ISO 27002: 17.1 Information security continuity RP RC.RP-1: Recovery plan is executed 17.1.2 Implementing information security continuity Improvements (IM): Recovery planning and processes are improved by incorporating lessons learned into future activities. IT Continuity Security Policy ISO 17.1.3 Verify, review and evaluate information security continuity IM RC.IM-1: Plans are updated with lessons learned

IM RC.IM-2: Recovery strategy is updated Communications (CO): Restoration activities are coordinated with internal and external parties, such as coordinating centers, Internet Service Providers, owners of attacking systems, victims, other IT Continuity Security Policy ISO - 16.1.5 Response to information security incidents ISO - 6.1.3 Contact with authorities CO RC.CO-1: Public Relations are managed 6.1.4 Contact with special interest groups CO RC.CO-2: Reputation after an event is repaired