Must the customer replace an existing PACS or VMS?

No. A suitable existing platform may remain authoritative when its integration, cybersecurity, support and evidence contract is accepted.

Does central monitoring replace local door or alarm behavior?

No. Required local access, egress, alarm and recording functions continue according to their approved design during WAN or Cloud loss.

How is video privacy handled?

Live view, playback, export, retention, legal hold, watermarking, redaction, tenant scope and disclosure rights are explicitly governed and audited.

Are guard services part of the software platform?

Guard, patrol and response may be included through the contracted service model and applicable licensed providers. The technology, post orders, dispatch and evidence are integrated into the same operating workflow.

DCOS SecureDCOS-SEC

DCOS Secure

Physical security & critical comms from perimeter to rack

Physical security, critical communications and response from perimeter to rack — perimeter, access control, video, intrusion, visitor and contractor workflows, intercom and duress, ALPR, guard coordination, dispatch, central monitoring and evidence.

Request an Architecture Review Configure a Reference Architecture

Domains: PACS · VMS · Intrusion
Identity: Strong, least-privilege
Convergence: Physical + cyber + OT
Governance: Data domain + evidence

DCOS Secure covers perimeter, access control, video, intrusion, visitor and contractor workflows, intercom and duress, ALPR, guard and patrol coordination, dispatch, central monitoring and evidence. It can deliver a new integrated system, operate an approved existing platform or support a shared-responsibility model. Physical security is both a protective system and an operational data domain: DCOS Secure preserves local access and alarm behavior, protects sensitive personnel and video data, and correlates authorized events without granting broad cross-system authority.

Outcomes

What this component is designed to make true when it is in place.

Converged incident context

Physical, cyber and OT events share context so responders see one situation, not three consoles.

Least privilege, enforced

Access and command authority follow least privilege with strong identity across every security system.

Evidence by default

Security events and access decisions are captured as linked evidence for audit and investigation.

Security domains

Access control (PACS)

Perimeter and interior access control with strong identity, zones and time-bound authority.

Video (VMS)

Governed video with retention policy, access authority and event linkage to incidents.

Intrusion detection

Perimeter and interior intrusion detection correlated with access and video context.

Visitor management

Controlled visitor lifecycle from pre-authorization through escort and departure, with evidence.

Dispatch & response

Coordinated dispatch and response procedures integrated with the shared event lifecycle.

Critical communications

Reliable critical comms for security operations, integrated with operations and escalation.

Security engineering

Each domain is engineered to preserve local protective behavior while producing governed evidence.

Access-control engineering

Local controller and door behavior
Credential, role, area and time entitlement
Mantrap, anti-passback, escort and two-person policies where required
Rapid disable and offboarding
Forced/held door and controller-health alarms
Code-compliant emergency egress
Complete access and operator evidence

Video engineering

Coverage purpose and scene requirements
Lens, resolution, frame rate, WDR, IR, thermal and PTZ
PoE and UPS calculations
Bandwidth and storage
Continuous or event recording
Retention, legal hold and export
VMS health, time and failover
Role, tenant, privacy, redaction and chain of custody

Intrusion and duress

Perimeter, building, room, cage and rack zones
Alarm verification
Discrete panic/duress path
Independent communicator health
Guard, central station, SOC, NOC and emergency response
Testing, battery and bypass records

Visitor and contractor lifecycle

Request → Review → Pre-arrival → Check-in → Presence → Check-out → Review

Operating contract

How this component upholds the shared platform contract.

What this component upholds

Every door, camera, sensor and credential carries stable identity and declared authority.
Read authority over security data is separate from command authority over security systems.
Security events join the shared lifecycle and converge with cyber and OT context.
Access decisions and security events are retained as linked evidence under governed policy.

Reference profiles

Reference security profiles; exact policy and integration depth are set per site and regulatory profile.
Domain	Primary function	Governance	Convergence
Access control	Zone & time-bound access	Strong identity, least privilege	Into incident context
Video	Surveillance & review	Retention & access policy	Linked to events
Intrusion	Perimeter/interior detection	Alarm authority	Correlated with access/video
Visitor mgmt	Controlled visitor lifecycle	Pre-authorization & evidence	Into operations
Dispatch	Coordinated response	Procedure-driven	Shared event lifecycle

Reference security profiles; exact policy and integration depth are set per site and regulatory profile.

Scope & boundaries

What this component is — and deliberately is not — responsible for.

DCOS Secure operates security systems and governs their data; it does not replace life-safety systems mandated by code.
Command authority over security systems is granted explicitly and separately from visibility.
Convergence provides shared context; it does not merge distinct regulatory retention obligations.

Technical FAQs

Frequently asked questions

Explore the family

Bring DCOS Secure into your reference architecture

We map this component to your sites, existing systems and assurance obligations, then agree a delivery path.

Request an Architecture Review Review Configuration Options