Assessment Objectives

In addition to relevant policies, standards and procedures, the assessor shall examine, interview, and/or test to determine if appropriately scoped evidence exists to support the claim that:

• BCD-07_A01 a contingency plan is developed that identifies essential mission and business functions and associated contingency requirements.
  Assessment rigor: 1
  Origin: 53A_R5_CP-02a.01
• BCD-07_A02 personnel or roles to review a contingency plan is/are defined.
  Assessment rigor: 1
  Origin: 53A_R5_CP-02_ODP[01]
• BCD-07_A03 the contingency plan is updated to address changes to the organization, system or environment of operation.
  Assessment rigor: 1
  Origin: 53A_R5_CP-02e.[01]
• BCD-07_A04 contingency plan changes are communicated to key contingency personnel.
  Assessment rigor: 1
  Origin: 53A_R5_CP-02f.[01]
• BCD-07_A05 the contingency plan is updated to address problems encountered during contingency plan implementation, execution or testing.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02e.[02]
• BCD-07_A06 personnel or roles to approve a contingency plan is/are defined.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02_ODP[02]
• BCD-07_A07 key contingency personnel (identified by name and/or by role) to whom copies of the contingency plan are distributed are defined.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02_ODP[03]
• BCD-07_A08 key contingency organizational elements to which copies of the contingency plan are distributed are defined.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02_ODP[04]
• BCD-07_A09 the frequency of contingency plan review is defined.
  Defined parameters: at least annually
  Assessment rigor: 3
  Origin: 53A_R5_CP-02_ODP[05]
• BCD-07_A10 key contingency personnel (identified by name and/or by role) to communicate changes to are defined.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02_ODP[06]
• BCD-07_A11 key contingency organizational elements to communicate changes to are defined.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02_ODP[07]
• BCD-07_A12 a contingency plan for the system is developed that provides recovery objectives.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02a.02[01]
• BCD-07_A13 a contingency plan for the system is developed that provides restoration priorities.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02a.02[02]
• BCD-07_A14 a contingency plan for the system is developed that provides metrics.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02a.02[03]
• BCD-07_A15 a contingency plan for the system is developed that addresses contingency roles.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02a.03[01]
• BCD-07_A16 a contingency plan for the system is developed that addresses contingency responsibilities.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02a.03[02]
• BCD-07_A17 a contingency plan for the system is developed that addresses assigned individuals with contact information.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02a.03[03]
• BCD-07_A18 a contingency plan for the system is developed that addresses maintaining essential mission and business functions despite a disruption, compromise or failure of a system, application or service.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02a.04
• BCD-07_A19 a contingency plan for the system is developed that addresses eventual, full-system restoration without deterioration of the controls originally planned and implemented.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02a.05
• BCD-07_A20 a contingency plan for the system is developed that addresses the sharing of contingency information.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02a.06
• BCD-07_A21 a contingency plan for the system is developed that is reviewed by personnel or roles.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02a.07[01]
• BCD-07_A22 a contingency plan for the system is developed that is approved by personnel or roles.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02a.07[02]
• BCD-07_A23 copies of the contingency plan are distributed to key contingency personnel.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02b.[01]
• BCD-07_A24 copies of the contingency plan are distributed to organizational elements.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02b.[02]
• BCD-07_A25 contingency planning activities are coordinated with incident handling activities.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02c.
• BCD-07_A26 the contingency plan for the system is reviewed frequently.
  Defined parameters: at least annually
  Assessment rigor: 3
  Origin: 53A_R5_CP-02d.
• BCD-07_A27 contingency plan changes are communicated to organizational elements.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02f.[02]
• BCD-07_A28 lessons learned from contingency plan testing or actual contingency activities are incorporated into contingency testing.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02g.[01]
• BCD-07_A29 lessons learned from contingency plan training or actual contingency activities are incorporated into contingency testing and training.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02g.[02]
• BCD-07_A30 the contingency plan is protected from unauthorized disclosure.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02h.[01]
• BCD-07_A31 the contingency plan is protected from unauthorized modification.
  Assessment rigor: 3
  Origin: 53A_R5_CP-02h.[02]

Propojené úkoly

• Secure Controls Framework -

  The Secure Controls Framework® (SCF)

  "The SCF is the Common Controls Framework™ (CCF), the world's most comprehensive cybersecurity and data privacy metaframework - it is also free to use. The entire concept is building secure, compliant and resilient capabilities in the most efficient and cost-effective manner possible.
  
  The SCF is more than just a unified control catalog, since its included content creates a playbook for Governance, Risk & Compliance (GRC) capabilities. Used globally by organizations of every size, the SCF is a robust and scalable solution for security, compliance and resilience controls. As a comprehensive security framework, the SCF maps 1,400+ controls across 200+ laws, regulations, and industry frameworks so you can implement once and comply everywhere.
  
  Like it or not, cybersecurity is a protracted war on an asymmetric battlefield, where the threats are everywhere and as defenders we have to make the effort to work together to help improve cybersecurity and data privacy practices, since we all suffer when massive data breaches occur or when cyber attacks have physical impacts. Hackers share information on attack methods with other hackers, so why shouldn’t the good guys share information on how to best protect an organization? We decided to take action and make a difference, since we feel it is too important to wait for someone else to fix the problems that exist.
  
  The SCF is made up of volunteers, mainly specialists within the cybersecurity profession, who focus on GRC and the cybersecurity side of data privacy. These are auditors, engineers, architects, incident responders, consultants and other specialists who live and breathe these topics on a daily basis. The end product is "expert-derived content" that makes up the SCF." https://securecontrolsframework.com/ 

  Terms & Conditions

  The SCF End User License Agreement (EULA) governs the use of the Secure Controls Framework® (SCF) under the Creative Commons Attribution-No Derivatives 4.0 International Public License.