{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/turn-guard-post-orders-observable-duties-limits-handoffs/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/turn-guard-post-orders-observable-duties-limits-handoffs/",
        "slug": "turn-guard-post-orders-observable-duties-limits-handoffs",
        "url": "https://update.dsesecurity.com/updates/turn-guard-post-orders-observable-duties-limits-handoffs/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/turn-guard-post-orders-observable-duties-limits-handoffs.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/turn-guard-post-orders-observable-duties-limits-handoffs/"
        },
        "title": "Turn guard post orders into observable duties, limits, and handoffs",
        "summary": "A post order should let a qualified officer understand the mission, authority, routine duties, prohibited actions, contacts, emergency priorities, required records, equipment checks, and relief process before accepting the post.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "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/"
            }
        ],
        "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-11T10:08:00+00:00",
        "modified_at": "2026-08-11T14:48:23+00:00",
        "reviewed_on": "2026-08-11",
        "reading_minutes": 3,
        "word_count": 642,
        "potentially_affected": "Contract and proprietary security officers, reception and lobby posts, patrols, gates, screening stations, control rooms, supervisors, contract managers, facilities, emergency contacts, incident records, and shift turnover.",
        "dse_recommendation": "Give every post a controlled order with a clear mission, authority and limits, task schedule, decision and escalation paths, site-specific emergency actions, equipment readiness, reporting standards, revision history, training, and documented handoff.",
        "primary_source": {
            "name": "CISA Interagency Security Committee: Armed Contract Security Officers in Federal Facilities—An ISC Best Practice",
            "url": "https://www.cisa.gov/sites/default/files/2023-07/Armed%20Contract%20Security%20Officers%20in%20Federal%20Facilities-An%20ISC%20Best%20Practice%202019.pdf",
            "published_on": "2019-01-01",
            "authority": "Cybersecurity and Infrastructure Security Agency"
        },
        "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": "<h2>Source facts: site-specific readiness comes before standing post</h2>\n<p>The Interagency Security Committee’s 2019 <a href=\"https://www.cisa.gov/sites/default/files/2023-07/Armed%20Contract%20Security%20Officers%20in%20Federal%20Facilities-An%20ISC%20Best%20Practice%202019.pdf\" target=\"_blank\" rel=\"noopener noreferrer\"><em>Armed Contract Security Officers in Federal Facilities</em></a> addresses program management, selection, training, equipment, responsibilities, and quality assurance for federal armed contract officers. It assigns roles to the government and contractor and emphasizes public safety, chain of command, judgment, and verified training.</p>\n<p>The guide says the government should determine site-specific training needed before a newly hired officer’s first assignment and should consider newly assigned officers familiar with post orders before they stand the post. It connects that familiarity with continuity, efficiency, and communication. The document also discusses training quality control, supervision, incident response, and written procedures for facility-specific duties.</p>\n<p>This federal armed-officer guide does not confer police powers, weapons authority, detention authority, or use-of-force permission on another organization. State licensing, labor law, contract terms, insurance, property authority, collective bargaining, and local law enforcement govern the actual guard program. DSE’s recommendations below apply to the clarity and assurance of post orders, whether a post is armed or unarmed.</p>\n\n<h2>DSE recommendation: make the order executable by the next qualified officer</h2>\n<p>Create one controlled document for each materially different post. A lobby, vehicle gate, mobile patrol, loading entrance, alarm-monitoring desk, and event screening station should not share a generic page that says “maintain security.” Give the order an owner, approval date, version, effective time, distribution list, and superseded-version process.</p>\n<ol>\n<li><strong>State the mission and boundary.</strong> Explain what people, property, areas, and operations the post protects; the geographic limits; hours; required staffing; who directs the officer; and what authority the officer does and does not possess. Separate observation, access denial, reporting, emergency aid, and law-enforcement functions.</li>\n<li><strong>Describe routine work observably.</strong> List opening checks, equipment inspection, access decisions, patrol route and randomized elements, key or badge control, log review, deliveries, contractor arrival, alarm handling, prohibited-item actions, safety observations, and end-of-shift reconciliation. Use triggers and expected records instead of vague phrases such as “as needed.”</li>\n<li><strong>Build decision tables.</strong> For common exceptions, show condition, immediate safe action, person to contact, alternate if unavailable, information to provide, authority required, and required report. Include unknown visitors, lost credentials, door faults, alarms, medical events, fire, severe weather, aggressive behavior, suspicious property, utility failure, and evacuation.</li>\n<li><strong>Protect the officer’s limits.</strong> Identify prohibited actions and situations requiring a supervisor, emergency services, facilities, HR, or law enforcement. Do not make an officer improvise a search, employment decision, repair, code determination, medical judgment, or hazardous-item examination beyond training and authority.</li>\n<li><strong>Control equipment and information.</strong> Inventory radios, phones, keys, duress devices, flashlights, protective equipment, forms, maps, contacts, and reference plans. Define readiness checks, defect escalation, charging or replacement, and custody. Keep sensitive details accessible to authorized officers but protected from casual public view.</li>\n<li><strong>Require a positive handoff.</strong> The relieving officer should receive unresolved incidents, disabled equipment, temporary access instructions, expected visitors, issued keys, active impairments, changed threats, and supervisor directions, then formally accept the post. A signature without a briefing is not continuity.</li>\n</ol>\n<p>Qualify officers on the actual post with walk-throughs, supervised performance, knowledge checks, and scenarios. Supervisors should observe duties across different shifts, reconcile logs and key counts, test contact paths, review report quality, and correct both officer performance and unclear instructions. Quality assurance should look for missed tasks and systemic barriers, not manufacture traps unrelated to the post mission.</p>\n<p>Revise post orders after layout or tenant changes, new equipment, changed law or contract, recurring exceptions, incidents, exercises, and responder feedback. Brief and document the change before it becomes effective. The best order does not attempt to predict every event; it gives a trained officer a stable mission, safe limits, current resources, and a reliable path to the person authorized to decide.</p>\n\n<h2>Official references</h2>\n<ul>\n<li>Cybersecurity and Infrastructure Security Agency, Interagency Security Committee, <a href=\"https://www.cisa.gov/sites/default/files/2023-07/Armed%20Contract%20Security%20Officers%20in%20Federal%20Facilities-An%20ISC%20Best%20Practice%202019.pdf\" target=\"_blank\" rel=\"noopener noreferrer\"><em>Armed Contract Security Officers in Federal Facilities: An ISC Best Practice</em></a>, 2019.</li>\n<li>CISA Interagency Security Committee, <a href=\"https://www.cisa.gov/about-interagency-security-committee\" target=\"_blank\" rel=\"noopener noreferrer\">ISC standards and best-practice program</a>.</li>\n</ul>",
        "content_text": "Source facts: site-specific readiness comes before standing post\nThe Interagency Security Committee’s 2019 Armed Contract Security Officers in Federal Facilities addresses program management, selection, training, equipment, responsibilities, and quality assurance for federal armed contract officers. It assigns roles to the government and contractor and emphasizes public safety, chain of command, judgment, and verified training.\nThe guide says the government should determine site-specific training needed before a newly hired officer’s first assignment and should consider newly assigned officers familiar with post orders before they stand the post. It connects that familiarity with continuity, efficiency, and communication. The document also discusses training quality control, supervision, incident response, and written procedures for facility-specific duties.\nThis federal armed-officer guide does not confer police powers, weapons authority, detention authority, or use-of-force permission on another organization. State licensing, labor law, contract terms, insurance, property authority, collective bargaining, and local law enforcement govern the actual guard program. DSE’s recommendations below apply to the clarity and assurance of post orders, whether a post is armed or unarmed.\n\nDSE recommendation: make the order executable by the next qualified officer\nCreate one controlled document for each materially different post. A lobby, vehicle gate, mobile patrol, loading entrance, alarm-monitoring desk, and event screening station should not share a generic page that says “maintain security.” Give the order an owner, approval date, version, effective time, distribution list, and superseded-version process.\n\nState the mission and boundary. Explain what people, property, areas, and operations the post protects; the geographic limits; hours; required staffing; who directs the officer; and what authority the officer does and does not possess. Separate observation, access denial, reporting, emergency aid, and law-enforcement functions.\nDescribe routine work observably. List opening checks, equipment inspection, access decisions, patrol route and randomized elements, key or badge control, log review, deliveries, contractor arrival, alarm handling, prohibited-item actions, safety observations, and end-of-shift reconciliation. Use triggers and expected records instead of vague phrases such as “as needed.”\nBuild decision tables. For common exceptions, show condition, immediate safe action, person to contact, alternate if unavailable, information to provide, authority required, and required report. Include unknown visitors, lost credentials, door faults, alarms, medical events, fire, severe weather, aggressive behavior, suspicious property, utility failure, and evacuation.\nProtect the officer’s limits. Identify prohibited actions and situations requiring a supervisor, emergency services, facilities, HR, or law enforcement. Do not make an officer improvise a search, employment decision, repair, code determination, medical judgment, or hazardous-item examination beyond training and authority.\nControl equipment and information. Inventory radios, phones, keys, duress devices, flashlights, protective equipment, forms, maps, contacts, and reference plans. Define readiness checks, defect escalation, charging or replacement, and custody. Keep sensitive details accessible to authorized officers but protected from casual public view.\nRequire a positive handoff. The relieving officer should receive unresolved incidents, disabled equipment, temporary access instructions, expected visitors, issued keys, active impairments, changed threats, and supervisor directions, then formally accept the post. A signature without a briefing is not continuity.\n\nQualify officers on the actual post with walk-throughs, supervised performance, knowledge checks, and scenarios. Supervisors should observe duties across different shifts, reconcile logs and key counts, test contact paths, review report quality, and correct both officer performance and unclear instructions. Quality assurance should look for missed tasks and systemic barriers, not manufacture traps unrelated to the post mission.\nRevise post orders after layout or tenant changes, new equipment, changed law or contract, recurring exceptions, incidents, exercises, and responder feedback. Brief and document the change before it becomes effective. The best order does not attempt to predict every event; it gives a trained officer a stable mission, safe limits, current resources, and a reliable path to the person authorized to decide.\n\nOfficial references\n\nCybersecurity and Infrastructure Security Agency, Interagency Security Committee, Armed Contract Security Officers in Federal Facilities: An ISC Best Practice, 2019.\nCISA Interagency Security Committee, ISC standards and best-practice program.",
        "content_markdown": "## Source facts: site-specific readiness comes before standing post\n\nThe Interagency Security Committee’s 2019 [Armed Contract Security Officers in Federal Facilities](https://www.cisa.gov/sites/default/files/2023-07/Armed%20Contract%20Security%20Officers%20in%20Federal%20Facilities-An%20ISC%20Best%20Practice%202019.pdf) addresses program management, selection, training, equipment, responsibilities, and quality assurance for federal armed contract officers. It assigns roles to the government and contractor and emphasizes public safety, chain of command, judgment, and verified training.\n\nThe guide says the government should determine site-specific training needed before a newly hired officer’s first assignment and should consider newly assigned officers familiar with post orders before they stand the post. It connects that familiarity with continuity, efficiency, and communication. The document also discusses training quality control, supervision, incident response, and written procedures for facility-specific duties.\n\nThis federal armed-officer guide does not confer police powers, weapons authority, detention authority, or use-of-force permission on another organization. State licensing, labor law, contract terms, insurance, property authority, collective bargaining, and local law enforcement govern the actual guard program. DSE’s recommendations below apply to the clarity and assurance of post orders, whether a post is armed or unarmed.\n\n## DSE recommendation: make the order executable by the next qualified officer\n\nCreate one controlled document for each materially different post. A lobby, vehicle gate, mobile patrol, loading entrance, alarm-monitoring desk, and event screening station should not share a generic page that says “maintain security.” Give the order an owner, approval date, version, effective time, distribution list, and superseded-version process.\n\n- State the mission and boundary. Explain what people, property, areas, and operations the post protects; the geographic limits; hours; required staffing; who directs the officer; and what authority the officer does and does not possess. Separate observation, access denial, reporting, emergency aid, and law-enforcement functions.\n\n- Describe routine work observably. List opening checks, equipment inspection, access decisions, patrol route and randomized elements, key or badge control, log review, deliveries, contractor arrival, alarm handling, prohibited-item actions, safety observations, and end-of-shift reconciliation. Use triggers and expected records instead of vague phrases such as “as needed.”\n\n- Build decision tables. For common exceptions, show condition, immediate safe action, person to contact, alternate if unavailable, information to provide, authority required, and required report. Include unknown visitors, lost credentials, door faults, alarms, medical events, fire, severe weather, aggressive behavior, suspicious property, utility failure, and evacuation.\n\n- Protect the officer’s limits. Identify prohibited actions and situations requiring a supervisor, emergency services, facilities, HR, or law enforcement. Do not make an officer improvise a search, employment decision, repair, code determination, medical judgment, or hazardous-item examination beyond training and authority.\n\n- Control equipment and information. Inventory radios, phones, keys, duress devices, flashlights, protective equipment, forms, maps, contacts, and reference plans. Define readiness checks, defect escalation, charging or replacement, and custody. Keep sensitive details accessible to authorized officers but protected from casual public view.\n\n- Require a positive handoff. The relieving officer should receive unresolved incidents, disabled equipment, temporary access instructions, expected visitors, issued keys, active impairments, changed threats, and supervisor directions, then formally accept the post. A signature without a briefing is not continuity.\n\nQualify officers on the actual post with walk-throughs, supervised performance, knowledge checks, and scenarios. Supervisors should observe duties across different shifts, reconcile logs and key counts, test contact paths, review report quality, and correct both officer performance and unclear instructions. Quality assurance should look for missed tasks and systemic barriers, not manufacture traps unrelated to the post mission.\n\nRevise post orders after layout or tenant changes, new equipment, changed law or contract, recurring exceptions, incidents, exercises, and responder feedback. Brief and document the change before it becomes effective. The best order does not attempt to predict every event; it gives a trained officer a stable mission, safe limits, current resources, and a reliable path to the person authorized to decide.\n\n## Official references\n\n- Cybersecurity and Infrastructure Security Agency, Interagency Security Committee, [Armed Contract Security Officers in Federal Facilities: An ISC Best Practice](https://www.cisa.gov/sites/default/files/2023-07/Armed%20Contract%20Security%20Officers%20in%20Federal%20Facilities-An%20ISC%20Best%20Practice%202019.pdf), 2019.\n\n- CISA Interagency Security Committee, [ISC standards and best-practice program](https://www.cisa.gov/about-interagency-security-committee)."
    },
    "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/turn-guard-post-orders-observable-duties-limits-handoffs/",
                "url": "https://update.dsesecurity.com/updates/turn-guard-post-orders-observable-duties-limits-handoffs/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-11"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/turn-guard-post-orders-observable-duties-limits-handoffs/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Turn guard post orders into observable duties, limits, and handoffs",
                        "item": "https://update.dsesecurity.com/updates/turn-guard-post-orders-observable-duties-limits-handoffs/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/turn-guard-post-orders-observable-duties-limits-handoffs/#article",
                "identifier": "https://update.dsesecurity.com/updates/turn-guard-post-orders-observable-duties-limits-handoffs/",
                "url": "https://update.dsesecurity.com/updates/turn-guard-post-orders-observable-duties-limits-handoffs/",
                "headline": "Turn guard post orders into observable duties, limits, and handoffs",
                "description": "A post order should let a qualified officer understand the mission, authority, routine duties, prohibited actions, contacts, emergency priorities…",
                "abstract": "A post order should let a qualified officer understand the mission, authority, routine duties, prohibited actions, contacts, emergency priorities, required records, equipment checks, and relief process before accepting the post.",
                "articleBody": "Source facts: site-specific readiness comes before standing post\nThe Interagency Security Committee’s 2019 Armed Contract Security Officers in Federal Facilities addresses program management, selection, training, equipment, responsibilities, and quality assurance for federal armed contract officers. It assigns roles to the government and contractor and emphasizes public safety, chain of command, judgment, and verified training.\nThe guide says the government should determine site-specific training needed before a newly hired officer’s first assignment and should consider newly assigned officers familiar with post orders before they stand the post. It connects that familiarity with continuity, efficiency, and communication. The document also discusses training quality control, supervision, incident response, and written procedures for facility-specific duties.\nThis federal armed-officer guide does not confer police powers, weapons authority, detention authority, or use-of-force permission on another organization. State licensing, labor law, contract terms, insurance, property authority, collective bargaining, and local law enforcement govern the actual guard program. DSE’s recommendations below apply to the clarity and assurance of post orders, whether a post is armed or unarmed.\n\nDSE recommendation: make the order executable by the next qualified officer\nCreate one controlled document for each materially different post. A lobby, vehicle gate, mobile patrol, loading entrance, alarm-monitoring desk, and event screening station should not share a generic page that says “maintain security.” Give the order an owner, approval date, version, effective time, distribution list, and superseded-version process.\n\nState the mission and boundary. Explain what people, property, areas, and operations the post protects; the geographic limits; hours; required staffing; who directs the officer; and what authority the officer does and does not possess. Separate observation, access denial, reporting, emergency aid, and law-enforcement functions.\nDescribe routine work observably. List opening checks, equipment inspection, access decisions, patrol route and randomized elements, key or badge control, log review, deliveries, contractor arrival, alarm handling, prohibited-item actions, safety observations, and end-of-shift reconciliation. Use triggers and expected records instead of vague phrases such as “as needed.”\nBuild decision tables. For common exceptions, show condition, immediate safe action, person to contact, alternate if unavailable, information to provide, authority required, and required report. Include unknown visitors, lost credentials, door faults, alarms, medical events, fire, severe weather, aggressive behavior, suspicious property, utility failure, and evacuation.\nProtect the officer’s limits. Identify prohibited actions and situations requiring a supervisor, emergency services, facilities, HR, or law enforcement. Do not make an officer improvise a search, employment decision, repair, code determination, medical judgment, or hazardous-item examination beyond training and authority.\nControl equipment and information. Inventory radios, phones, keys, duress devices, flashlights, protective equipment, forms, maps, contacts, and reference plans. Define readiness checks, defect escalation, charging or replacement, and custody. Keep sensitive details accessible to authorized officers but protected from casual public view.\nRequire a positive handoff. The relieving officer should receive unresolved incidents, disabled equipment, temporary access instructions, expected visitors, issued keys, active impairments, changed threats, and supervisor directions, then formally accept the post. A signature without a briefing is not continuity.\n\nQualify officers on the actual post with walk-throughs, supervised performance, knowledge checks, and scenarios. Supervisors should observe duties across different shifts, reconcile logs and key counts, test contact paths, review report quality, and correct both officer performance and unclear instructions. Quality assurance should look for missed tasks and systemic barriers, not manufacture traps unrelated to the post mission.\nRevise post orders after layout or tenant changes, new equipment, changed law or contract, recurring exceptions, incidents, exercises, and responder feedback. Brief and document the change before it becomes effective. The best order does not attempt to predict every event; it gives a trained officer a stable mission, safe limits, current resources, and a reliable path to the person authorized to decide.\n\nOfficial references\n\nCybersecurity and Infrastructure Security Agency, Interagency Security Committee, Armed Contract Security Officers in Federal Facilities: An ISC Best Practice, 2019.\nCISA Interagency Security Committee, ISC standards and best-practice program.",
                "datePublished": "2026-08-11T10:08:00+00:00",
                "dateModified": "2026-08-11T14:48:23+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/turn-guard-post-orders-observable-duties-limits-handoffs/"
                },
                "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/turn-guard-post-orders-observable-duties-limits-handoffs/#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": "Turn guard post orders into observable duties, limits, and handoffs"
                },
                "articleSection": [
                    "Access Control",
                    "Business Continuity"
                ],
                "keywords": [
                    "Access Control",
                    "Business Continuity",
                    "Guide",
                    "Advisory priority"
                ],
                "genre": "Guide",
                "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/"
                    }
                ],
                "wordCount": 642,
                "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": "CISA Interagency Security Committee: Armed Contract Security Officers in Federal Facilities—An ISC Best Practice",
                    "url": "https://www.cisa.gov/sites/default/files/2023-07/Armed%20Contract%20Security%20Officers%20in%20Federal%20Facilities-An%20ISC%20Best%20Practice%202019.pdf",
                    "datePublished": "2019-01-01"
                }
            }
        ]
    }
}