# Record covered accidental releases and their onsite and offsite consequences > Use 40 CFR 68.42 -- Chemical Accident Prevention Provisions to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/record-covered-accidental-releases-and-their-onsite-and-offsite-consequences/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:10:11+00:00 - Modified: 2026-08-27T13:12:22+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Playbook - DSE priority: Advisory - Topics: Business Continuity, Cybersecurity - Reading time: 3 minutes ## What you need to know Use 40 CFR 68.42 -- Chemical Accident Prevention Provisions 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 40 CFR 68.42 -- Chemical Accident Prevention Provisions ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Keep this document to one review outcome: Record covered accidental releases and their onsite and offsite consequences. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [40 CFR 68.42 — Chemical Accident Prevention Provisions](https://www.ecfr.gov/current/title-40/section-68.42) from Environmental Protection Agency via eCFR supports the following bounded statements: - Under 40 CFR 68, the rule requires that the owner or operator include in the five-year accident history all accidental releases from covered processes that resulted in deaths, injuries, or significant property damage on site, or known offsite deaths, injuries, evacuations, sheltering in place, property damage, or environmental damage. The research record locates this support at 40 CFR 68.42(a) (eCFR anchor p-68.42(a)). - Under 40 CFR 68, the rule requires that for each accidental release included, the owner or operator report the following information: known offsite impacts. The research record locates this support at 40 CFR 68.42(b)(8), read with 40 CFR 68.42(b) (eCFR anchor p-68.42(b)(8)). Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives and the conditions the source actually describes. ## What the source does not establish Applies only to stationary sources and processes subject to 40 CFR part 68 and the applicable program level. Confirm coverage, regulated substances, process conditions, and current EPA requirements; this is not legal advice or a universal emergency-management standard. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery and the environment’s recorded constraints. ## Applicability questions - For source statement 1 at 40 CFR 68.42(a) (eCFR anchor p-68.42(a)), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at 40 CFR 68.42(b)(8), read with 40 CFR 68.42(b) (eCFR anchor p-68.42(b)(8)), 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. Use a two-person review for the source interpretation and the resulting operational decision. 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. Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery, while excluding secrets and sensitive personal or topology data from ordinary tickets. ## Verification and evidence Keep the source locations 40 CFR 68.42(a) (eCFR anchor p-68.42(a)); 40 CFR 68.42(b)(8), read with 40 CFR 68.42(b) (eCFR anchor p-68.42(b)(8)) adjacent to the sanitized artifacts used for comparison. Prefer business-impact records, dependency maps, exercise results, recovery timings, and open corrective actions, with enough identity and timing data for an independent recheck. Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes. ## Official references - [40 CFR 68.42 — Chemical Accident Prevention Provisions](https://www.ecfr.gov/current/title-40/section-68.42) — Environmental Protection Agency via eCFR ## Primary reference - Name: 40 CFR 68.42 -- Chemical Accident Prevention Provisions - Authority: www.ecfr.gov - URL: https://www.ecfr.gov/current/title-40/section-68.42 - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Record covered accidental releases and their onsite and offsite consequences,” DSE Security, https://update.dsesecurity.com/updates/record-covered-accidental-releases-and-their-onsite-and-offsite-consequences/ 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.