{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/evaluate-contractors-and-communicate-covered-process-hazards-before-work/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/evaluate-contractors-and-communicate-covered-process-hazards-before-work/",
        "slug": "evaluate-contractors-and-communicate-covered-process-hazards-before-work",
        "url": "https://update.dsesecurity.com/updates/evaluate-contractors-and-communicate-covered-process-hazards-before-work/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/evaluate-contractors-and-communicate-covered-process-hazards-before-work.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/evaluate-contractors-and-communicate-covered-process-hazards-before-work/"
        },
        "title": "Evaluate contractors and communicate covered-process hazards before work",
        "summary": "Use 40 CFR 68.87 -- Chemical Accident Prevention Provisions to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "checklist",
            "name": "Checklist"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "physical-security",
            "label": "Physical security",
            "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "access-control",
                "name": "Access Control",
                "url": "https://update.dsesecurity.com/topic/access-control/"
            },
            {
                "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:09:49+00:00",
        "modified_at": "2026-08-27T13:12:22+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 592,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 40 CFR 68.87 -- 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.87 -- Chemical Accident Prevention Provisions",
            "url": "https://www.ecfr.gov/current/title-40/section-68.87",
            "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>Treat this document as a focused evidence review: Evaluate contractors and communicate covered-process hazards before work. 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.87\" target=\"_blank\" rel=\"noopener noreferrer\">40 CFR 68.87 &#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 inform contract owner or operator of the known potential fire, explosion, or toxic release hazards related to the contractor&#8217;s work and the process. The research record locates this support at <strong>40 CFR 68.87(b)(2) (eCFR anchor p-68.87(b)(2))</strong>.</li>\n<li>Under 40 CFR 68, the rule requires that the owner or operator develop and implement safe work practices consistent with section 68.69(d), to control the entrance, presence, and exit of the contract owner or operator and contract employees in covered process areas. The research record locates this support at <strong>40 CFR 68.87(b)(4) (eCFR anchor p-68.87(b)(4))</strong>.</li>\n</ul>\n<p>Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths 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. A correct source interpretation can still be inapplicable to a particular design. Confirm identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders, ownership, and change authority instead of treating documented behavior as a deployment guarantee.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>40 CFR 68.87(b)(2) (eCFR anchor p-68.87(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.87(b)(4) (eCFR anchor p-68.87(b)(4))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which owner can attest to the recorded state of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, including exceptions?</li>\n<li>What baseline for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders 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 critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, 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 and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders 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.87(b)(2) (eCFR anchor p-68.87(b)(2))</strong>; <strong>40 CFR 68.87(b)(4) (eCFR anchor p-68.87(b)(4))</strong> adjacent to the sanitized artifacts used for comparison. Prefer facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and 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.87\" target=\"_blank\" rel=\"noopener noreferrer\">40 CFR 68.87 &#8212; Chemical Accident Prevention Provisions</a> — Environmental Protection Agency via eCFR</li>\n</ul>",
        "content_text": "Treat this document as a focused evidence review: Evaluate contractors and communicate covered-process hazards before work. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 40 CFR 68.87 — 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 inform contract owner or operator of the known potential fire, explosion, or toxic release hazards related to the contractor’s work and the process. The research record locates this support at 40 CFR 68.87(b)(2) (eCFR anchor p-68.87(b)(2)).\nUnder 40 CFR 68, the rule requires that the owner or operator develop and implement safe work practices consistent with section 68.69(d), to control the entrance, presence, and exit of the contract owner or operator and contract employees in covered process areas. The research record locates this support at 40 CFR 68.87(b)(4) (eCFR anchor p-68.87(b)(4)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths 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. A correct source interpretation can still be inapplicable to a particular design. Confirm identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\nApplicability questions\n\nFor source statement 1 at 40 CFR 68.87(b)(2) (eCFR anchor p-68.87(b)(2)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 40 CFR 68.87(b)(4) (eCFR anchor p-68.87(b)(4)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, including exceptions?\nWhat baseline for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders 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 critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, 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 and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders 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.87(b)(2) (eCFR anchor p-68.87(b)(2)); 40 CFR 68.87(b)(4) (eCFR anchor p-68.87(b)(4)) adjacent to the sanitized artifacts used for comparison. Prefer facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and 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.87 — Chemical Accident Prevention Provisions — Environmental Protection Agency via eCFR",
        "content_markdown": "Treat this document as a focused evidence review: Evaluate contractors and communicate covered-process hazards before work. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [40 CFR 68.87 — Chemical Accident Prevention Provisions](https://www.ecfr.gov/current/title-40/section-68.87) 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 inform contract owner or operator of the known potential fire, explosion, or toxic release hazards related to the contractor’s work and the process. The research record locates this support at 40 CFR 68.87(b)(2) (eCFR anchor p-68.87(b)(2)).\n\n- Under 40 CFR 68, the rule requires that the owner or operator develop and implement safe work practices consistent with section 68.69(d), to control the entrance, presence, and exit of the contract owner or operator and contract employees in covered process areas. The research record locates this support at 40 CFR 68.87(b)(4) (eCFR anchor p-68.87(b)(4)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths 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. A correct source interpretation can still be inapplicable to a particular design. Confirm identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\n\n## Applicability questions\n\n- For source statement 1 at 40 CFR 68.87(b)(2) (eCFR anchor p-68.87(b)(2)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 40 CFR 68.87(b)(4) (eCFR anchor p-68.87(b)(4)), which observable configuration, record, or test can confirm applicability here?\n\n- Which owner can attest to the recorded state of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, including exceptions?\n\n- What baseline for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders 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 critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, 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 and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders 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.87(b)(2) (eCFR anchor p-68.87(b)(2)); 40 CFR 68.87(b)(4) (eCFR anchor p-68.87(b)(4)) adjacent to the sanitized artifacts used for comparison. Prefer facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and 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.87 — Chemical Accident Prevention Provisions](https://www.ecfr.gov/current/title-40/section-68.87) — 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/evaluate-contractors-and-communicate-covered-process-hazards-before-work/",
                "url": "https://update.dsesecurity.com/updates/evaluate-contractors-and-communicate-covered-process-hazards-before-work/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/evaluate-contractors-and-communicate-covered-process-hazards-before-work/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Evaluate contractors and communicate covered-process hazards before work",
                        "item": "https://update.dsesecurity.com/updates/evaluate-contractors-and-communicate-covered-process-hazards-before-work/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/evaluate-contractors-and-communicate-covered-process-hazards-before-work/#article",
                "identifier": "https://update.dsesecurity.com/updates/evaluate-contractors-and-communicate-covered-process-hazards-before-work/",
                "url": "https://update.dsesecurity.com/updates/evaluate-contractors-and-communicate-covered-process-hazards-before-work/",
                "headline": "Evaluate contractors and communicate covered-process hazards before work",
                "description": "Use 40 CFR 68.87 -- Chemical Accident Prevention Provisions to review this narrow operational decision without extending the source beyond its stated…",
                "abstract": "Use 40 CFR 68.87 -- Chemical Accident Prevention Provisions to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Treat this document as a focused evidence review: Evaluate contractors and communicate covered-process hazards before work. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 40 CFR 68.87 — 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 inform contract owner or operator of the known potential fire, explosion, or toxic release hazards related to the contractor’s work and the process. The research record locates this support at 40 CFR 68.87(b)(2) (eCFR anchor p-68.87(b)(2)).\nUnder 40 CFR 68, the rule requires that the owner or operator develop and implement safe work practices consistent with section 68.69(d), to control the entrance, presence, and exit of the contract owner or operator and contract employees in covered process areas. The research record locates this support at 40 CFR 68.87(b)(4) (eCFR anchor p-68.87(b)(4)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths 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. A correct source interpretation can still be inapplicable to a particular design. Confirm identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\nApplicability questions\n\nFor source statement 1 at 40 CFR 68.87(b)(2) (eCFR anchor p-68.87(b)(2)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 40 CFR 68.87(b)(4) (eCFR anchor p-68.87(b)(4)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, including exceptions?\nWhat baseline for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders 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 critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, 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 and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders 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.87(b)(2) (eCFR anchor p-68.87(b)(2)); 40 CFR 68.87(b)(4) (eCFR anchor p-68.87(b)(4)) adjacent to the sanitized artifacts used for comparison. Prefer facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and 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.87 — Chemical Accident Prevention Provisions — Environmental Protection Agency via eCFR",
                "datePublished": "2026-08-27T12:09:49+00:00",
                "dateModified": "2026-08-27T13:12:22+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/evaluate-contractors-and-communicate-covered-process-hazards-before-work/"
                },
                "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/evaluate-contractors-and-communicate-covered-process-hazards-before-work/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Evaluate contractors and communicate covered-process hazards before work"
                },
                "articleSection": [
                    "Access Control",
                    "Business Continuity",
                    "Cybersecurity"
                ],
                "keywords": [
                    "Access Control",
                    "Business Continuity",
                    "Cybersecurity",
                    "Checklist",
                    "Advisory priority"
                ],
                "genre": "Checklist",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Access Control",
                        "url": "https://update.dsesecurity.com/topic/access-control/"
                    },
                    {
                        "@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": 592,
                "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.87 -- Chemical Accident Prevention Provisions",
                    "url": "https://www.ecfr.gov/current/title-40/section-68.87"
                }
            }
        ]
    }
}