ezesecops/rmf-ato-core huggingface dataset:
Security and Privacy Controls for Information Systems and Organizations
CP > CP-1 > Discussion

CP-1 Policy and Procedures - Discussion
Family: Contingency Planning (CP)

Contingency planning policy and procedures address the controls in the CP family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of contingency planning policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to contingency planning policy and procedures include assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2

CP-2 Contingency Plan
Family: Contingency Planning (CP)

a. Develop a contingency plan for the system that:
1. Identifies essential mission and business functions and associated contingency requirements;
2. Provides recovery objectives, restoration priorities, and metrics;
3. Addresses contingency roles, responsibilities, assigned individuals with contact information;
4. Addresses maintaining essential mission and business functions despite a system disruption, compromise, or failure;
5. Addresses eventual, full system restoration without deterioration of the controls originally planned and implemented;
6. Addresses the sharing of contingency information; and
7. Is reviewed and approved by [Assignment: organization-defined organization-defined personnel or roles];
b. Distribute copies of the contingency plan to [Assignment: organization-defined organization-defined key contingency personnel (identified by name and/or by role) and organizational elements];
c. Coordinate contingency planning activities with incident handling activities;
d. Review the contingency plan for the system [Assignment: organization-defined frequency];
e. Update the contingency plan to address changes to the organization, system, or environment of operation and problems encountered during contingency plan implementation, execution, or testing;
f. Communicate contingency plan changes to [Assignment: organization-defined organization-defined key contingency personnel (identified by name and/or by role) and organizational elements];
g. Incorporate lessons learned from contingency plan testing, training, or actual contingency activities into contingency testing and training; and
h. Protect the contingency plan from unauthorized disclosure and modification.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > Discussion

CP-2 Contingency Plan - Discussion
Family: Contingency Planning (CP)

Contingency planning for systems is part of an overall program for achieving continuity of operations for organizational mission and business functions. Contingency planning addresses system restoration and implementation of alternative mission or business processes when systems are compromised or breached. Contingency planning is considered throughout the system development life cycle and is a fundamental part of the system design. Systems can be designed for redundancy, to provide backup capabilities, and for resilience. Contingency plans reflect the degree of restoration required for organizational systems since not all systems need to fully recover to achieve the level of continuity of operations desired. System recovery objectives reflect applicable laws, executive orders, directives, regulations, policies, standards, guidelines, organizational risk tolerance, and system impact level.

Actions addressed in contingency plans include orderly system degradation, system shutdown, fallback to a manual mode, alternate information flows, and operating in modes reserved for when systems are under attack. By coordinating contingency planning with incident handling activities, organizations ensure that the necessary planning activities are in place and activated in the event of an incident. Organizations consider whether continuity of operations during an incident conflicts with the capability to automatically disable the system, as specified in [IR-4(5)](#ir-4.5) . Incident response planning is part of contingency planning for organizations and is addressed in the [IR](#ir) (Incident Response) family.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(1) > Discussion

CP-2(1) Coordinate with Related Plans - Discussion
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Plans that are related to contingency plans include Business Continuity Plans, Disaster Recovery Plans, Critical Infrastructure Plans, Continuity of Operations Plans, Crisis Communications Plans, Insider Threat Implementation Plans, Data Breach Response Plans, Cyber Incident Response Plans, Breach Response Plans, and Occupant Emergency Plans.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(1)

CP-2(1) Contingency Plan | Coordinate with Related Plans
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Coordinate contingency plan development with organizational elements responsible for related plans.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(2) > Discussion

CP-2(2) Capacity Planning - Discussion
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Capacity planning is needed because different threats can result in a reduction of the available processing, telecommunications, and support services intended to support essential mission and business functions. Organizations anticipate degraded operations during contingency operations and factor the degradation into capacity planning. For capacity planning, environmental support refers to any environmental factor for which the organization determines that it needs to provide support in a contingency situation, even if in a degraded state. Such determinations are based on an organizational assessment of risk, system categorization (impact level), and organizational risk tolerance.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(2)

CP-2(2) Contingency Plan | Capacity Planning
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Conduct capacity planning so that necessary capacity for information processing, telecommunications, and environmental support exists during contingency operations.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(3) > Discussion

CP-2(3) Resume Mission and Business Functions - Discussion
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Organizations may choose to conduct contingency planning activities to resume mission and business functions as part of business continuity planning or as part of business impact analyses. Organizations prioritize the resumption of mission and business functions. The time period for resuming mission and business functions may be dependent on the severity and extent of the disruptions to the system and its supporting infrastructure.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(3)

CP-2(3) Contingency Plan | Resume Mission and Business Functions
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Plan for the resumption of [Selection: all; essential] mission and business functions within [Assignment: organization-defined time period] of contingency plan activation.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(5) > Discussion

CP-2(5) Continue Mission and Business Functions - Discussion
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Organizations may choose to conduct the contingency planning activities to continue mission and business functions as part of business continuity planning or business impact analyses. Primary processing and/or storage sites defined by organizations as part of contingency planning may change depending on the circumstances associated with the contingency.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(5)

CP-2(5) Contingency Plan | Continue Mission and Business Functions
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Plan for the continuance of [Selection: all; essential] mission and business functions with minimal or no loss of operational continuity and sustains that continuity until full system restoration at primary processing and/or storage sites.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(6) > Discussion

CP-2(6) Alternate Processing and Storage Sites - Discussion
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Organizations may choose to conduct contingency planning activities for alternate processing and storage sites as part of business continuity planning or business impact analyses. Primary processing and/or storage sites defined by organizations as part of contingency planning may change depending on the circumstances associated with the contingency.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(6)

CP-2(6) Contingency Plan | Alternate Processing and Storage Sites
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Plan for the transfer of [Selection: all; essential] mission and business functions to alternate processing and/or storage sites with minimal or no loss of operational continuity and sustain that continuity through system restoration to primary processing and/or storage sites.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(7) > Discussion

CP-2(7) Coordinate with External Service Providers - Discussion
Family: Contingency Planning (CP) > CP-2 Contingency Plan

When the capability of an organization to carry out its mission and business functions is dependent on external service providers, developing a comprehensive and timely contingency plan may become more challenging. When mission and business functions are dependent on external service providers, organizations coordinate contingency planning activities with the external entities to ensure that the individual plans reflect the overall contingency needs of the organization.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(7)

CP-2(7) Contingency Plan | Coordinate with External Service Providers
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Coordinate the contingency plan with the contingency plans of external service providers to ensure that contingency requirements can be satisfied.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(8) > Discussion

CP-2(8) Identify Critical Assets - Discussion
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Organizations may choose to identify critical assets as part of criticality analysis, business continuity planning, or business impact analyses. Organizations identify critical system assets so that additional controls can be employed (beyond the controls routinely implemented) to help ensure that organizational mission and business functions can continue to be conducted during contingency operations. The identification of critical information assets also facilitates the prioritization of organizational resources. Critical system assets include technical and operational aspects. Technical aspects include system components, information technology services, information technology products, and mechanisms. Operational aspects include procedures (i.e., manually executed operations) and personnel (i.e., individuals operating technical controls and/or executing manual procedures). Organizational program protection plans can assist in identifying critical assets. If critical assets are resident within or supported by external service providers, organizations consider implementing [CP-2(7)](#cp-2.7) as a control enhancement.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-2 > CP-2(8)

CP-2(8) Contingency Plan | Identify Critical Assets
Family: Contingency Planning (CP) > CP-2 Contingency Plan

Identify critical system assets supporting [Selection: all; essential] mission and business functions.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-3

CP-3 Contingency Training
Family: Contingency Planning (CP)

a. Provide contingency training to system users consistent with assigned roles and responsibilities:
1. Within [Assignment: organization-defined time period] of assuming a contingency role or responsibility;
2. When required by system changes; and
3. [Assignment: organization-defined frequency] thereafter; and
b. Review and update contingency training content [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
Security and Privacy Controls for Information Systems and Organizations
CP > CP-3 > Discussion

CP-3 Contingency Training - Discussion
Family: Contingency Planning (CP)

Contingency training provided by organizations is linked to the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail is included in such training. For example, some individuals may only need to know when and where to report for duty during contingency operations and if normal duties are affected; system administrators may require additional training on how to establish systems at alternate processing and storage sites; and organizational officials may receive more specific training on how to conduct mission-essential functions in designated off-site locations and how to establish communications with other governmental entities for purposes of coordination on contingency-related activities. Training for contingency roles or responsibilities reflects the specific continuity requirements in the contingency plan. Events that may precipitate an update to contingency training content include, but are not limited to, contingency plan testing or an actual contingency (lessons learned), assessment or audit findings, security incidents or breaches, or changes in laws, executive orders, directives, regulations, policies, standards, and guidelines. At the discretion of the organization, participation in a contingency plan test or exercise, including lessons learned sessions subsequent to the test or exercise, may satisfy contingency plan training requirements.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-3 > CP-3(1) > Discussion

CP-3(1) Simulated Events - Discussion
Family: Contingency Planning (CP) > CP-3 Contingency Training

The use of simulated events creates an environment for personnel to experience actual threat events, including cyber-attacks that disable websites, ransomware attacks that encrypt organizational data on servers, hurricanes that damage or destroy organizational facilities, or hardware or software failures.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-3 > CP-3(1)

CP-3(1) Contingency Training | Simulated Events
Family: Contingency Planning (CP) > CP-3 Contingency Training

Incorporate simulated events into contingency training to facilitate effective response by personnel in crisis situations.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-3 > CP-3(2) > Discussion

CP-3(2) Mechanisms Used in Training Environments - Discussion
Family: Contingency Planning (CP) > CP-3 Contingency Training

Operational mechanisms refer to processes that have been established to accomplish an organizational goal or a system that supports a particular organizational mission or business objective. Actual mission and business processes, systems, and/or facilities may be used to generate simulated events and enhance the realism of simulated events during contingency training.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-3 > CP-3(2)

CP-3(2) Contingency Training | Mechanisms Used in Training Environments
Family: Contingency Planning (CP) > CP-3 Contingency Training

Employ mechanisms used in operations to provide a more thorough and realistic contingency training environment.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-4

CP-4 Contingency Plan Testing
Family: Contingency Planning (CP)

a. Test the contingency plan for the system [Assignment: organization-defined frequency] using the following tests to determine the effectiveness of the plan and the readiness to execute the plan: [Assignment: organization-defined organization-defined tests].
b. Review the contingency plan test results; and
c. Initiate corrective actions, if needed.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-4 > Discussion

CP-4 Contingency Plan Testing - Discussion
Family: Contingency Planning (CP)

Methods for testing contingency plans to determine the effectiveness of the plans and identify potential weaknesses include checklists, walk-through and tabletop exercises, simulations (parallel or full interrupt), and comprehensive exercises. Organizations conduct testing based on the requirements in contingency plans and include a determination of the effects on organizational operations, assets, and individuals due to contingency operations. Organizations have flexibility and discretion in the breadth, depth, and timelines of corrective actions.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-4 > CP-4(1) > Discussion

CP-4(1) Coordinate with Related Plans - Discussion
Family: Contingency Planning (CP) > CP-4 Contingency Plan Testing

Plans related to contingency planning for organizational systems include Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, and Occupant Emergency Plans. Coordination of contingency plan testing does not require organizations to create organizational elements to handle related plans or to align such elements with specific plans. However, it does require that if such organizational elements are responsible for related plans, organizations coordinate with those elements.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-4 > CP-4(1)

CP-4(1) Contingency Plan Testing | Coordinate with Related Plans
Family: Contingency Planning (CP) > CP-4 Contingency Plan Testing

Coordinate contingency plan testing with organizational elements responsible for related plans.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-4 > CP-4(2) > Discussion

CP-4(2) Alternate Processing Site - Discussion
Family: Contingency Planning (CP) > CP-4 Contingency Plan Testing

Conditions at the alternate processing site may be significantly different than the conditions at the primary site. Having the opportunity to visit the alternate site and experience the actual capabilities available at the site can provide valuable information on potential vulnerabilities that could affect essential organizational mission and business functions. The on-site visit can also provide an opportunity to refine the contingency plan to address the vulnerabilities discovered during testing.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-4 > CP-4(2)

CP-4(2) Contingency Plan Testing | Alternate Processing Site
Family: Contingency Planning (CP) > CP-4 Contingency Plan Testing

Test the contingency plan at the alternate processing site:
(a) To familiarize contingency personnel with the facility and available resources; and
(b) To evaluate the capabilities of the alternate processing site to support contingency operations.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-4 > CP-4(3) > Discussion

CP-4(3) Automated Testing - Discussion
Family: Contingency Planning (CP) > CP-4 Contingency Plan Testing

Automated mechanisms facilitate thorough and effective testing of contingency plans by providing more complete coverage of contingency issues, selecting more realistic test scenarios and environments, and effectively stressing the system and supported mission and business functions.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-4 > CP-4(3)

CP-4(3) Contingency Plan Testing | Automated Testing
Family: Contingency Planning (CP) > CP-4 Contingency Plan Testing

Test the contingency plan using [Assignment: organization-defined automated mechanisms].
Security and Privacy Controls for Information Systems and Organizations
CP > CP-4 > CP-4(4) > Discussion

CP-4(4) Full Recovery and Reconstitution - Discussion
Family: Contingency Planning (CP) > CP-4 Contingency Plan Testing

Recovery is executing contingency plan activities to restore organizational mission and business functions. Reconstitution takes place following recovery and includes activities for returning systems to fully operational states. Organizations establish a known state for systems that includes system state information for hardware, software programs, and data. Preserving system state information facilitates system restart and return to the operational mode of organizations with less disruption of mission and business processes.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-4 > CP-4(4)

CP-4(4) Contingency Plan Testing | Full Recovery and Reconstitution
Family: Contingency Planning (CP) > CP-4 Contingency Plan Testing

Include a full recovery and reconstitution of the system to a known state as part of contingency plan testing.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-4 > CP-4(5) > Discussion

CP-4(5) Self-challenge - Discussion
Family: Contingency Planning (CP) > CP-4 Contingency Plan Testing

Often, the best method of assessing system resilience is to disrupt the system in some manner. The mechanisms used by the organization could disrupt system functions or system services in many ways, including terminating or disabling critical system components, changing the configuration of system components, degrading critical functionality (e.g., restricting network bandwidth), or altering privileges. Automated, on-going, and simulated cyber-attacks and service disruptions can reveal unexpected functional dependencies and help the organization determine its ability to ensure resilience in the face of an actual cyber-attack.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-4 > CP-4(5)

CP-4(5) Contingency Plan Testing | Self-challenge
Family: Contingency Planning (CP) > CP-4 Contingency Plan Testing

Employ [Assignment: organization-defined mechanisms] to [Assignment: organization-defined system or system component] to disrupt and adversely affect the system or system component.
Security and Privacy Controls for Information Systems and Organizations
CP > CP-6

CP-6 Alternate Storage Site
Family: Contingency Planning (CP)

a. Establish an alternate storage site, including necessary agreements to permit the storage and retrieval of system backup information; and
b. Ensure that the alternate storage site provides controls equivalent to that of the primary site.