Skip to main content

BCD-11.8: Dual Authorization For Backup Media Destruction

BCD 5 — Medium Protect

Mechanisms exist to implement and enforce dual authorization for the deletion or destruction of sensitive backup media and data.

Control Question: Does the organization implement and enforce dual authorization for the deletion or destruction of sensitive backup media and data?

General (4)
Framework Mapping Values
IEC 62443-4-2 2019 CR 2.1 (6.3.3(4))
NIST 800-53 R4 CP-9(7)
NIST 800-53 R5 (source) CP-9(7)
NIST 800-53 R5 (NOC) (source) CP-9(7)

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to implement and enforce dual authorization for the deletion or destruction of sensitive backup media and data.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to implement and enforce dual authorization for the deletion or destruction of sensitive backup media and data.

Level 2 — Planned & Tracked

C|P-CMM2 is N/A, since a well-defined process is required to implement and enforce dual authorization for the deletion or destruction of sensitive backup media and data.

Level 3 — Well Defined

Business Continuity & Disaster Recovery (BCD) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • A formal Business Continuity & Disaster Recovery (BC/DR) program exists with defined roles and responsibilities to restore functionality in the event of a catastrophe, emergency, or significant disruptive incident that is handled in accordance with a Continuity of Operations Plan (COOP).
  • BC/DR personnel work with business stakeholders to identify business-critical systems, services, internal teams and third-party service providers.
  • Specific criteria are defined to initiate BC/DR activities that facilitate business continuity operations capable of meeting applicable RTOs and/or RPOs.- Application/system/process owners conduct a Business Impact Analysis (BIA) at least annually, or after any major technology or process change, to identify assets critical to the business in need of protection, as well as single points of failure.
  • Recovery Time Objectives (RTOs) are defined for business-critical systems and services.
  • Recovery Point Objectives (RPOs) are defined and technologies exist to conduct transaction-level recovery, in accordance with RPOs.
  • Controls are assigned to sensitive/regulated assets to comply with specific BC/DR requirements to facilitate recovery operations in accordance with RTOs and RPOs.
  • IT personnel work with business stakeholders to develop Disaster Recovery Plans (DRP) to recover business-critical systems and services within RPOs.
  • Business stakeholders work with IT personnel to develop Business Continuity Plans (BCPs) to ensure business functions are sustainable both during and after an incident within RTOs.
  • The data backup function is formally assigned with defined roles and responsibilities.
  • BC/DR personnel have pre-established methods to communicate the status of recovery activities and progress in restoring operational capabilities to designated internal and external stakeholders.
  • The integrity of backups and other restoration assets are verified prior to using them for restoration.
Level 4 — Quantitatively Controlled

See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to implement and enforce dual authorization for the deletion or destruction of sensitive backup media and data.

Level 5 — Continuously Improving

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to implement and enforce dual authorization for the deletion or destruction of sensitive backup media and data.

Assessment Objectives

  1. BCD-11.8_A01 critical or sensitive system and organizational operations for which dual authorization is to be enforced are identified.
  2. BCD-11.8_A02 dual authorization is employed to execute critical or sensitive system and organizational operations.
  3. BCD-11.8_A03 backup information for which to enforce dual authorization in order to delete or destroy is defined.
  4. BCD-11.8_A04 dual authorization for the deletion or destruction of backup information is enforced.

Technology Recommendations

Micro/Small

  • Logical Access Control (LAC)
  • Physical Access Control (PAC)
  • Role Based Access Control (RBAC)
  • Separation of Duties (SoD)

Small

  • Logical Access Control (LAC)
  • Physical Access Control (PAC)
  • Role Based Access Control (RBAC)
  • Separation of Duties (SoD)

Medium

  • Logical Access Control (LAC)
  • Physical Access Control (PAC)
  • Role Based Access Control (RBAC)
  • Separation of Duties (SoD)

Large

  • Logical Access Control (LAC)
  • Physical Access Control (PAC)
  • Role Based Access Control (RBAC)
  • Separation of Duties (SoD)

Enterprise

  • Logical Access Control (LAC)
  • Physical Access Control (PAC)
  • Role Based Access Control (RBAC)
  • Separation of Duties (SoD)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.