{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/",
        "slug": "update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points",
        "url": "https://update.dsesecurity.com/updates/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/"
        },
        "title": "Update the regulated risk-management plan after process changes and five-year review points",
        "summary": "Use 40 CFR 68.190 -- Chemical Accident Prevention Provisions to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "explainer",
            "name": "Explainer"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "continuity-recovery",
            "label": "Continuity & recovery",
            "alt": "Paired infrastructure paths converging on a stable recovered service.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T12:10:13+00:00",
        "modified_at": "2026-08-27T13:12:21+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 594,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 40 CFR 68.190 -- 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.",
        "primary_source": {
            "name": "40 CFR 68.190 -- Chemical Accident Prevention Provisions",
            "url": "https://www.ecfr.gov/current/title-40/section-68.190",
            "published_on": null,
            "authority": "www.ecfr.gov"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>Frame this document as a source-led configuration and assurance check: Update the regulated risk-management plan after process changes and five-year review points. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://www.ecfr.gov/current/title-40/section-68.190\" target=\"_blank\" rel=\"noopener noreferrer\">40 CFR 68.190 &#8212; Chemical Accident Prevention Provisions</a> from Environmental Protection Agency via eCFR supports the following bounded statements:</p>\n<ul>\n<li>Under 40 CFR 68, the rule requires that the owner or operator of a stationary source revise and update the RMP submitted under section 68.150 as follows: no later than three years after a newly regulated substance is first listed by EPA. The research record locates this support at <strong>40 CFR 68.190(b)(2), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(2))</strong>.</li>\n<li>Under 40 CFR 68, the rule requires that the owner or operator of a stationary source revise and update the RMP submitted under section 68.150 as follows: within six months of a change that alters the Program level that applied to any covered process. The research record locates this support at <strong>40 CFR 68.190(b)(7), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(7))</strong>.</li>\n</ul>\n<p>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.</p>\n<h2>What the source does not establish</h2>\n<p>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&#8217;s recorded constraints.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>40 CFR 68.190(b)(2), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(2))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>40 CFR 68.190(b)(7), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(7))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which owner can attest to the recorded state of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives, including exceptions?</li>\n<li>What baseline for identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery must accompany the source-specific observation?</li>\n<li>Which success, stop, and escalation criteria are written before testing begins?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>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.</p>\n<p>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.</p>\n<h2>Verification and evidence</h2>\n<p>Keep the source locations <strong>40 CFR 68.190(b)(2), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(2))</strong>; <strong>40 CFR 68.190(b)(7), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(7))</strong> 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.</p>\n<p>Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-40/section-68.190\" target=\"_blank\" rel=\"noopener noreferrer\">40 CFR 68.190 &#8212; Chemical Accident Prevention Provisions</a> — Environmental Protection Agency via eCFR</li>\n</ul>",
        "content_text": "Frame this document as a source-led configuration and assurance check: Update the regulated risk-management plan after process changes and five-year review points. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 40 CFR 68.190 — Chemical Accident Prevention Provisions from Environmental Protection Agency via eCFR supports the following bounded statements:\n\nUnder 40 CFR 68, the rule requires that the owner or operator of a stationary source revise and update the RMP submitted under section 68.150 as follows: no later than three years after a newly regulated substance is first listed by EPA. The research record locates this support at 40 CFR 68.190(b)(2), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(2)).\nUnder 40 CFR 68, the rule requires that the owner or operator of a stationary source revise and update the RMP submitted under section 68.150 as follows: within six months of a change that alters the Program level that applied to any covered process. The research record locates this support at 40 CFR 68.190(b)(7), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(7)).\n\nDo 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.\nWhat the source does not establish\nApplies 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.\nApplicability questions\n\nFor source statement 1 at 40 CFR 68.190(b)(2), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(2)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 40 CFR 68.190(b)(7), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(7)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives, including exceptions?\nWhat baseline for identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE 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.\nFor 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.\nVerification and evidence\nKeep the source locations 40 CFR 68.190(b)(2), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(2)); 40 CFR 68.190(b)(7), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(7)) 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.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\n40 CFR 68.190 — Chemical Accident Prevention Provisions — Environmental Protection Agency via eCFR",
        "content_markdown": "Frame this document as a source-led configuration and assurance check: Update the regulated risk-management plan after process changes and five-year review points. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [40 CFR 68.190 — Chemical Accident Prevention Provisions](https://www.ecfr.gov/current/title-40/section-68.190) from Environmental Protection Agency via eCFR supports the following bounded statements:\n\n- Under 40 CFR 68, the rule requires that the owner or operator of a stationary source revise and update the RMP submitted under section 68.150 as follows: no later than three years after a newly regulated substance is first listed by EPA. The research record locates this support at 40 CFR 68.190(b)(2), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(2)).\n\n- Under 40 CFR 68, the rule requires that the owner or operator of a stationary source revise and update the RMP submitted under section 68.150 as follows: within six months of a change that alters the Program level that applied to any covered process. The research record locates this support at 40 CFR 68.190(b)(7), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(7)).\n\nDo 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.\n\n## What the source does not establish\n\nApplies 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.\n\n## Applicability questions\n\n- For source statement 1 at 40 CFR 68.190(b)(2), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(2)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 40 CFR 68.190(b)(7), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(7)), which observable configuration, record, or test can confirm applicability here?\n\n- Which owner can attest to the recorded state of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives, including exceptions?\n\n- What baseline for identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery must accompany the source-specific observation?\n\n- Which success, stop, and escalation criteria are written before testing begins?\n\n## DSE recommendation:\n\nDSE 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.\n\nFor 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.\n\n## Verification and evidence\n\nKeep the source locations 40 CFR 68.190(b)(2), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(2)); 40 CFR 68.190(b)(7), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(7)) 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.\n\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\n\n## Official references\n\n- [40 CFR 68.190 — Chemical Accident Prevention Provisions](https://www.ecfr.gov/current/title-40/section-68.190) — Environmental Protection Agency via eCFR"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/",
                "url": "https://update.dsesecurity.com/updates/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Update the regulated risk-management plan after process changes and five-year review points",
                        "item": "https://update.dsesecurity.com/updates/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/#article",
                "identifier": "https://update.dsesecurity.com/updates/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/",
                "url": "https://update.dsesecurity.com/updates/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/",
                "headline": "Update the regulated risk-management plan after process changes and five-year review points",
                "description": "Use 40 CFR 68.190 -- Chemical Accident Prevention Provisions to review this narrow operational decision without extending the source beyond its stated…",
                "abstract": "Use 40 CFR 68.190 -- Chemical Accident Prevention Provisions to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Frame this document as a source-led configuration and assurance check: Update the regulated risk-management plan after process changes and five-year review points. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 40 CFR 68.190 — Chemical Accident Prevention Provisions from Environmental Protection Agency via eCFR supports the following bounded statements:\n\nUnder 40 CFR 68, the rule requires that the owner or operator of a stationary source revise and update the RMP submitted under section 68.150 as follows: no later than three years after a newly regulated substance is first listed by EPA. The research record locates this support at 40 CFR 68.190(b)(2), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(2)).\nUnder 40 CFR 68, the rule requires that the owner or operator of a stationary source revise and update the RMP submitted under section 68.150 as follows: within six months of a change that alters the Program level that applied to any covered process. The research record locates this support at 40 CFR 68.190(b)(7), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(7)).\n\nDo 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.\nWhat the source does not establish\nApplies 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.\nApplicability questions\n\nFor source statement 1 at 40 CFR 68.190(b)(2), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(2)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 40 CFR 68.190(b)(7), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(7)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives, including exceptions?\nWhat baseline for identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE 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.\nFor 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.\nVerification and evidence\nKeep the source locations 40 CFR 68.190(b)(2), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(2)); 40 CFR 68.190(b)(7), read with 40 CFR 68.190(b) (eCFR anchor p-68.190(b)(7)) 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.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\n40 CFR 68.190 — Chemical Accident Prevention Provisions — Environmental Protection Agency via eCFR",
                "datePublished": "2026-08-27T12:10:13+00:00",
                "dateModified": "2026-08-27T13:12:21+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/update-the-regulated-risk-management-plan-after-process-changes-and-five-year-review-points/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Update the regulated risk-management plan after process changes and five-year review points"
                },
                "articleSection": [
                    "Business Continuity",
                    "Cybersecurity"
                ],
                "keywords": [
                    "Business Continuity",
                    "Cybersecurity",
                    "Explainer",
                    "Advisory priority"
                ],
                "genre": "Explainer",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    }
                ],
                "wordCount": 594,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "40 CFR 68.190 -- Chemical Accident Prevention Provisions",
                    "url": "https://www.ecfr.gov/current/title-40/section-68.190"
                }
            }
        ]
    }
}