# Separate emergency operating records from legal and financial rights records > Use 36 CFR 1223.12 - Objectives of a vital records program to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/separate-emergency-operating-records-from-legal-and-financial-rights-records/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:11:35+00:00 - Modified: 2026-08-27T13:07:00+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Briefing - DSE priority: Advisory - Topics: Business Continuity, Cybersecurity - Reading time: 3 minutes ## What you need to know Use 36 CFR 1223.12 - Objectives of a vital records program to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of 36 CFR 1223.12 - Objectives of a vital records program ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Use this document to resolve one bounded operational decision: Separate emergency operating records from legal and financial rights records. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [36 CFR 1223.12 – Objectives of a vital records program](https://www.ecfr.gov/current/title-36/section-1223.12) from National Archives and Records Administration via eCFR supports the following bounded statements: - Under 36 CFR 1223, a vital records program has two objectives: it provides an agency with the information it needs to conduct its business under other than normal operating conditions and to resume normal business afterward. The research record locates this support at 36 CFR 1223.12(a), read with the unnumbered introductory paragraph of 36 CFR 1223.12 (eCFR anchor p-1223.12(a)). - Under 36 CFR 1223, it enables agency officials to identify and protect the most important records dealing with the legal and financial rights of the agency and of persons directly affected by the agency’s actions. The research record locates this support at 36 CFR 1223.12(b) (eCFR anchor p-1223.12(b)). The source support ends with the statements listed above. Use them to examine essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives in the applicable environment, not to imply a wider guarantee. ## What the source does not establish Federal agency records-management regulation; record designation requires agency functions, approved schedules, legal obligations, and current NARA guidance. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery are healthy. Documented options are review inputs, not universal mandates. ## Applicability questions - For source statement 1 at 36 CFR 1223.12(a), read with the unnumbered introductory paragraph of 36 CFR 1223.12 (eCFR anchor p-1223.12(a)), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at 36 CFR 1223.12(b) (eCFR anchor p-1223.12(b)), which observable configuration, record, or test can confirm applicability here? - Which owner can attest to the recorded state of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives, including exceptions? - What baseline for identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery must accompany the source-specific observation? - Which success, stop, and escalation criteria are written before testing begins? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives, observed and expected states, owner, and reason for deviation. For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence. ## Verification and evidence Build a reproducible chain from 36 CFR 1223.12(a), read with the unnumbered introductory paragraph of 36 CFR 1223.12 (eCFR anchor p-1223.12(a)); 36 CFR 1223.12(b) (eCFR anchor p-1223.12(b)) to the observed environment. Useful domain evidence includes business-impact records, dependency maps, exercise results, recovery timings, and open corrective actions; label every item with scope, timestamp, collector, and stable identifier. Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes. ## Official references - [36 CFR 1223.12 – Objectives of a vital records program](https://www.ecfr.gov/current/title-36/section-1223.12) — National Archives and Records Administration via eCFR ## Primary reference - Name: 36 CFR 1223.12 - Objectives of a vital records program - Authority: www.ecfr.gov - URL: https://www.ecfr.gov/current/title-36/section-1223.12 - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Separate emergency operating records from legal and financial rights records,” DSE Security, https://update.dsesecurity.com/updates/separate-emergency-operating-records-from-legal-and-financial-rights-records/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.