{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/use-written-management-of-change-controls-before-modifying-covered-processes/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/use-written-management-of-change-controls-before-modifying-covered-processes/",
        "slug": "use-written-management-of-change-controls-before-modifying-covered-processes",
        "url": "https://update.dsesecurity.com/updates/use-written-management-of-change-controls-before-modifying-covered-processes/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/use-written-management-of-change-controls-before-modifying-covered-processes.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/use-written-management-of-change-controls-before-modifying-covered-processes/"
        },
        "title": "Use written management-of-change controls before modifying covered processes",
        "summary": "Use 40 CFR 68.75 -- Chemical Accident Prevention Provisions to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "playbook",
            "name": "Playbook"
        },
        "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:56+00:00",
        "modified_at": "2026-08-27T13:12:22+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 593,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 40 CFR 68.75 -- 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.75 -- Chemical Accident Prevention Provisions",
            "url": "https://www.ecfr.gov/current/title-40/section-68.75",
            "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>Keep this document to one review outcome: Use written management-of-change controls before modifying covered processes. 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.75\" target=\"_blank\" rel=\"noopener noreferrer\">40 CFR 68.75 &#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 establish and implement written procedures to manage changes (except for &#8220;replacements in kind&#8221;) to process chemicals, technology, equipment, and procedures; and, changes to stationary sources that affect a covered process. The research record locates this support at <strong>40 CFR 68.75(a) (eCFR anchor p-68.75(a))</strong>.</li>\n<li>Under 40 CFR 68, the rule requires that the procedures assure that the following considerations are addressed prior to any change: impact of change on safety and health. The research record locates this support at <strong>40 CFR 68.75(b)(2), read with 40 CFR 68.75(b) (eCFR anchor p-68.75(b)(2))</strong>.</li>\n</ul>\n<p>Keep the evidence boundary at these traced claims. They support a review of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths; they do not support conclusions outside the source&#8217;s stated conditions.</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.75(a) (eCFR anchor p-68.75(a))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>40 CFR 68.75(b)(2), read with 40 CFR 68.75(b) (eCFR anchor p-68.75(b)(2))</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. Anchor the review in the cited section and keep observation separate from interpretation. 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>An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders before and after the test, and store only sanitized operational evidence.</p>\n<h2>Verification and evidence</h2>\n<p>Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations <strong>40 CFR 68.75(a) (eCFR anchor p-68.75(a))</strong>; <strong>40 CFR 68.75(b)(2), read with 40 CFR 68.75(b) (eCFR anchor p-68.75(b)(2))</strong>. Favor facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions, linked to stable identifiers, time, and operator.</p>\n<p>Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today&#8217;s observation is not a continuing guarantee.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-40/section-68.75\" target=\"_blank\" rel=\"noopener noreferrer\">40 CFR 68.75 &#8212; Chemical Accident Prevention Provisions</a> — Environmental Protection Agency via eCFR</li>\n</ul>",
        "content_text": "Keep this document to one review outcome: Use written management-of-change controls before modifying covered processes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 40 CFR 68.75 — 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 establish and implement written procedures to manage changes (except for “replacements in kind”) to process chemicals, technology, equipment, and procedures; and, changes to stationary sources that affect a covered process. The research record locates this support at 40 CFR 68.75(a) (eCFR anchor p-68.75(a)).\nUnder 40 CFR 68, the rule requires that the procedures assure that the following considerations are addressed prior to any change: impact of change on safety and health. The research record locates this support at 40 CFR 68.75(b)(2), read with 40 CFR 68.75(b) (eCFR anchor p-68.75(b)(2)).\n\nKeep the evidence boundary at these traced claims. They support a review of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths; they do not support conclusions outside the source’s stated conditions.\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.75(a) (eCFR anchor p-68.75(a)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 40 CFR 68.75(b)(2), read with 40 CFR 68.75(b) (eCFR anchor p-68.75(b)(2)), 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. Anchor the review in the cited section and keep observation separate from interpretation. 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.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 40 CFR 68.75(a) (eCFR anchor p-68.75(a)); 40 CFR 68.75(b)(2), read with 40 CFR 68.75(b) (eCFR anchor p-68.75(b)(2)). Favor facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions, linked to stable identifiers, time, and operator.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\n40 CFR 68.75 — Chemical Accident Prevention Provisions — Environmental Protection Agency via eCFR",
        "content_markdown": "Keep this document to one review outcome: Use written management-of-change controls before modifying covered processes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [40 CFR 68.75 — Chemical Accident Prevention Provisions](https://www.ecfr.gov/current/title-40/section-68.75) 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 establish and implement written procedures to manage changes (except for “replacements in kind”) to process chemicals, technology, equipment, and procedures; and, changes to stationary sources that affect a covered process. The research record locates this support at 40 CFR 68.75(a) (eCFR anchor p-68.75(a)).\n\n- Under 40 CFR 68, the rule requires that the procedures assure that the following considerations are addressed prior to any change: impact of change on safety and health. The research record locates this support at 40 CFR 68.75(b)(2), read with 40 CFR 68.75(b) (eCFR anchor p-68.75(b)(2)).\n\nKeep the evidence boundary at these traced claims. They support a review of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths; they do not support conclusions outside the source’s stated conditions.\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.75(a) (eCFR anchor p-68.75(a)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 40 CFR 68.75(b)(2), read with 40 CFR 68.75(b) (eCFR anchor p-68.75(b)(2)), 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. Anchor the review in the cited section and keep observation separate from interpretation. 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\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders before and after the test, and store only sanitized operational evidence.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 40 CFR 68.75(a) (eCFR anchor p-68.75(a)); 40 CFR 68.75(b)(2), read with 40 CFR 68.75(b) (eCFR anchor p-68.75(b)(2)). Favor facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions, linked to stable identifiers, time, and operator.\n\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\n\n## Official references\n\n- [40 CFR 68.75 — Chemical Accident Prevention Provisions](https://www.ecfr.gov/current/title-40/section-68.75) — 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/use-written-management-of-change-controls-before-modifying-covered-processes/",
                "url": "https://update.dsesecurity.com/updates/use-written-management-of-change-controls-before-modifying-covered-processes/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/use-written-management-of-change-controls-before-modifying-covered-processes/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Use written management-of-change controls before modifying covered processes",
                        "item": "https://update.dsesecurity.com/updates/use-written-management-of-change-controls-before-modifying-covered-processes/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/use-written-management-of-change-controls-before-modifying-covered-processes/#article",
                "identifier": "https://update.dsesecurity.com/updates/use-written-management-of-change-controls-before-modifying-covered-processes/",
                "url": "https://update.dsesecurity.com/updates/use-written-management-of-change-controls-before-modifying-covered-processes/",
                "headline": "Use written management-of-change controls before modifying covered processes",
                "description": "Use 40 CFR 68.75 -- Chemical Accident Prevention Provisions to review this narrow operational decision without extending the source beyond its stated…",
                "abstract": "Use 40 CFR 68.75 -- Chemical Accident Prevention Provisions to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Keep this document to one review outcome: Use written management-of-change controls before modifying covered processes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 40 CFR 68.75 — 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 establish and implement written procedures to manage changes (except for “replacements in kind”) to process chemicals, technology, equipment, and procedures; and, changes to stationary sources that affect a covered process. The research record locates this support at 40 CFR 68.75(a) (eCFR anchor p-68.75(a)).\nUnder 40 CFR 68, the rule requires that the procedures assure that the following considerations are addressed prior to any change: impact of change on safety and health. The research record locates this support at 40 CFR 68.75(b)(2), read with 40 CFR 68.75(b) (eCFR anchor p-68.75(b)(2)).\n\nKeep the evidence boundary at these traced claims. They support a review of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths; they do not support conclusions outside the source’s stated conditions.\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.75(a) (eCFR anchor p-68.75(a)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 40 CFR 68.75(b)(2), read with 40 CFR 68.75(b) (eCFR anchor p-68.75(b)(2)), 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. Anchor the review in the cited section and keep observation separate from interpretation. 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.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 40 CFR 68.75(a) (eCFR anchor p-68.75(a)); 40 CFR 68.75(b)(2), read with 40 CFR 68.75(b) (eCFR anchor p-68.75(b)(2)). Favor facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions, linked to stable identifiers, time, and operator.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\n40 CFR 68.75 — Chemical Accident Prevention Provisions — Environmental Protection Agency via eCFR",
                "datePublished": "2026-08-27T12:09:56+00:00",
                "dateModified": "2026-08-27T13:12:22+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/use-written-management-of-change-controls-before-modifying-covered-processes/"
                },
                "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/use-written-management-of-change-controls-before-modifying-covered-processes/#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": "Use written management-of-change controls before modifying covered processes"
                },
                "articleSection": [
                    "Access Control",
                    "Business Continuity",
                    "Cybersecurity"
                ],
                "keywords": [
                    "Access Control",
                    "Business Continuity",
                    "Cybersecurity",
                    "Playbook",
                    "Advisory priority"
                ],
                "genre": "Playbook",
                "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": 593,
                "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.75 -- Chemical Accident Prevention Provisions",
                    "url": "https://www.ecfr.gov/current/title-40/section-68.75"
                }
            }
        ]
    }
}