Security System Domain

Overview#

An investigator reviewing a theft at a distribution warehouse wants to know which cameras cover the loading dock and whether the access control panel logged any entries during the incident window. She opens the Security System domain, searches by facility zone, and finds three camera records and one access panel assigned to that area, each with its system identifier and current operational status. She links them to the investigation and retrieves the relevant footage and access logs without hunting through spreadsheets or calling a facilities manager. The Security System domain is the catalogue that makes this lookup instant: a registry of physical security hardware that connects to alerts, events, and investigations.

Key Features#

• Security Asset Catalog: Maintain a registry of physical security systems including cameras, intrusion alarms, access control panels, and other security equipment with unique system identifiers.

• System Registration: Register new security systems with descriptive names and system identifiers for easy reference during incident investigations and facility management.

• Status Tracking: Monitor which security systems are active and operational to ensure coverage gaps are identified and addressed promptly.

• Event Association: Link security system records to alerts and events, enabling investigators to quickly identify which hardware was involved in or captured relevant data during an incident.

• Programmable API Access: Integrate security system data with other platforms through a structured API that supports creating, retrieving, and listing security system records.

Use Cases#

Physical security asset catalogues are valuable wherever investigations or audits need to map incidents to specific hardware. Key industries include retail and logistics, critical infrastructure, and corporate and campus security.

• Incident Investigation: Quickly identify which security systems cover a specific area of interest during an investigation to retrieve relevant footage or access logs.

• Facility Security Assessment: Review the complete inventory of security systems at a location to assess overall protection levels and plan upgrades.

• Maintenance Planning: Track security system installations and coordinate maintenance schedules to minimise equipment downtime.

• Compliance Verification: Document that required security systems are installed and operational to satisfy regulatory and insurance requirements.

Integration#

The Security System domain connects with other platform capabilities:

• Surveillance: Camera systems feed into the surveillance monitoring platform
• Alert Management: Security system events trigger platform alerts
• Investigation Management: Security system data links to active investigations
• Location Services: Systems are associated with physical facility locations

Open Standards#

• GraphQL (June 2018 specification): All security system queries, mutations, and operations picture requests are served over a typed GraphQL API, enabling structured, schema-validated access to asset data.
• OAuth 2.0 (RFC 6749) and JSON Web Tokens (RFC 7519): Every API call requires a Bearer JWT verified via RS256 against a JWKS endpoint, enforcing authenticated and authorised access to security asset records.
• RFC 4122 (UUID): All security system, organisation, zone, and investigation records are identified by RFC 4122 version-4 universally unique identifiers, ensuring collision-free references across distributed systems.
• ISO 8601 / RFC 3339 (date and time): Timestamps for record creation, last-seen heartbeats, last events, and time-window queries are stored and exchanged in UTC-based ISO 8601 format.
• WGS 84 (EPSG:4326): Physical locations of security systems are recorded as decimal-degree latitude and longitude coordinates on the WGS 84 datum, compatible with standard geospatial and mapping tools.
• JSON (RFC 8259): Flexible metadata associated with each security system asset is stored and transmitted as structured JSON, enabling extensible, schema-optional annotation without breaking the core record model.
• NATO Information Security Marking conventions: Asset records carry a secrecy_level field using NATO-aligned classification labels (UNCLASSIFIED as the baseline), and row-level clearance filtering enforces need-to-know access consistent with multilateral data-sharing standards.

Last Reviewed: 2026-02-05 Last Updated: 2026-04-14