All pages

Pick the system or task you're working on, then follow the relevant reading path. This section also explains the terminology, sources and safety labels used in the wiki.

Work through camera discovery, media sessions, events and video platform APIs.

Work through event fields, MQTT delivery, timestamps and recovery after a connection fails.

Start with the symptom, collect the relevant observations and use them to narrow down the cause.

A camera vendor, an access control engineer and a developer can use the same word differently. These definitions explain how terms are used throughout the wiki.

Start with what you're trying to understand or fix. Follow the links to the relevant specification and product documentation, and check which parts apply to your equipment.

Choose a reading path for your current task. Each path links the background, protocols and practical checks you need to work through it.

Start with the main systems, then work through the networking, identity and event handling needed for an integration.

Review the integration's scope, permissions, sources, failure handling and acceptance requirements.

This wiki covers the software and interfaces used in physical security systems. Installation, site engineering and approvals still require the relevant product instructions and qualified people.

Work through credentials, readers, controllers and door state, including how access decisions reach the equipment.

Software can affect doors, alarms, cameras, gates and emergency workflows. Check the physical outcome, permissions and failure behaviour before making changes to a live system.

Networking, power, identity, events and system architecture are common to most integrations. These pages explain the basics and link to the relevant protocol references.

Break the system into electrical interfaces, network transport, messages and application decisions. Identifying the layer involved helps you choose the right diagnostic check.

Follow a credential through issue, use, expiry and revocation. Check how the card, phone or biometric is linked to an identity and an access decision.

Agree on identity, state, timestamps and units before mapping data between systems. Record which system owns each field and how conflicting values are handled.

A dry contact reports an electrical state. Its meaning depends on the wiring, configuration and system design, so record those details before interpreting it as a door event.

Validate incoming data before using it. Check its size, encoding, structure and values, including data from devices on a private network.

Check the whole power path when planning PoE. Include device startup, cable losses, switch capacity, backup power and shared points of failure.

Events record changes, state describes the current view of a system, and commands request an action. Keep those records distinct when building an integration.

Record the identity, how it is authenticated and which operations it may perform. Apply permissions to the relevant devices, resources and actions.

Check the exact product, firmware, role, profile and optional features when reviewing compatibility. Keep the supporting documentation with the integration requirements.

Record the addresses, routes, ports and connection direction used by each service. Verify the responding device and its identity separately.

Follow the video through capture, encoding, session setup, transport, decoding and storage. Check each stage when investigating playback, quality or recording problems.

Check how discovery traffic crosses the network and how devices are enrolled afterwards. Verify device identity before using an advertised service.

Video, voice, management and alarm traffic have different network requirements. Plan for each flow's capacity, timing, packet loss and recovery needs.

Useful diagnostics record the source, timestamp and result of each observation. Keep enough context to trace a problem through the devices and services involved.

Map the devices, services and people involved in each workflow. Record which components observe events, make decisions and control equipment.

A controller may act before its response is lost. Account for uncertain results when setting timeouts, retries and recovery behaviour.

Plan identity, supported versions, failure handling and recovery during design. Assign ownership for the integration after commissioning and through to retirement.

Check the electrical interface, bus layout, framing, addressing and application protocol before connecting serial equipment. Record the settings used by both ends.

Keep device time and receipt time with each event. Use both when investigating delay, clock drift and events that arrive out of order.

Check certificate identity, trust, expiry and renewal as part of the connection setup. Include certificate failures and recovery in the operating plan.

Mark where ownership, identity, permissions and physical control change across the system. Use those boundaries to plan segmentation and access rules.

Radio links depend on range, interference, obstructions and the surrounding environment. Check device authentication and recovery as well as signal quality.

These pages cover reader communication, credential formats and mobile credential technologies. Use them alongside the access control system references.

Follow alarm reports from the premises through the receiver to monitoring software. Check message acceptance, supervision and the operator response at each stage.

These references cover interfaces used by building and industrial systems. Define the required data exchange and approval for any control functions before planning an integration.

These references cover older and less common interfaces. Check the supported version, device role and limitations before using them in an integration.

Addressing, identity, time, power and administration support the main application. Use these references when checking the services and interfaces underneath an integration.

Browse the protocols by system or function. Each page explains the interface, common integration requirements, limitations and supporting sources.

Video systems use separate paths for control, media, metadata and events. These references explain the protocols involved in each part.

These interfaces carry requests and events between applications. Choose a delivery mechanism, then define message meaning, permissions, retries and recovery.

Check network admission and application permissions separately. Record how devices join the network and what each operator or service may access afterwards.

Contact ID represents alarm reports using defined event codes. Record how the account, event, acknowledgement and monitoring response are mapped in your integration.

AMQP 1.0 defines messaging, delivery state and flow control. Map its settlement behaviour to how your application stores, processes and acknowledges security events.

BACnet uses objects and services to exchange building system data. Check the network type, supported device functions and security configuration for the installation.

BACnet MS/TP runs over a shared serial bus. Check bus timing, addresses and topology alongside the objects and services used by the application.

BACnet Secure Connect protects BACnet communication using its own connection and certificate model. Plan device identity, certificate management and application permissions together.

BACnet/IP carries BACnet traffic over an IP network. Check discovery, broadcasts and routing alongside the objects, services and access rules your integration needs.

CAN provides the bus, while CANopen and J1939 define additional communication rules. Identify the message model and device profile before interpreting traffic.

CAP and EDXL exchange warning and emergency information. Check the issuing authority, message lifecycle, recipients and acknowledgement requirements of the receiving workflow.

CoAP, OSCORE and LwM2M provide different parts of a constrained device system. Document which combination handles transport, message protection and device management.

Match the codec profile, level and packetisation to the decoder and recording system. Include playback and export when checking compatibility.

Check both the contactless interface and the credential application. Record how identity, authentication and credential management work with the chosen card and reader.

A credential includes its issuer, identity binding, keys and lifecycle. Check how those details are carried between physical cards, phones and access control systems.

Device discovery, address assignment and identity verification are separate steps. Validate the advertised service information before using it to establish a connection.

DNP3 exchanges point values, events and commands. Check event classes, timestamps, quality flags and the security features supported by each device.

Federation passes authentication information from an identity provider to an application. Check claims, sessions, account changes and the permissions applied by the receiving service.

EtherNet/IP uses the CIP object and service model. Identify the required objects, timing and permissions, and separate monitoring from industrial control.

GB/T 28181 includes registration, signalling and media exchange. Check the edition, device roles and supported flows for each side of the integration.

gRPC uses typed service definitions and serialised messages. Define permissions, deadlines and failure handling for each operation alongside the API schema.

HTTP provides request and response behaviour for web APIs. Define the resources, permissions and physical effects associated with each operation.

The IEC alarm transmission publications cover different parts of the reporting system. Identify the relevant publication for the premises equipment, receiver and message exchange.

The IEC 60870 telecontrol family defines transport and information exchange for operational systems. Check the applicable edition, message objects, timing and control responsibilities.

IEC 61850 includes several models and communication services. Identify the service, timing requirements and engineering context before designing a gateway or data consumer.

List the endpoints, transports and connection direction your integration requires. Use that list to define routing, segmentation and firewall rules.

KNX exchanges building control information through devices and group addresses. Document what each address means and which components may send or act on it.

KNX Secure provides specific protection for KNX communication. Check the secure mode, device support, key management and commissioning process used on the site.

Wiegand can refer to the electrical interface or the credential bit format. Record both, along with the authentication and protection provided elsewhere in the system.

Matter defines device communication, identity and commissioning. Check the required device types and supported features against the exact products involved.

Modbus exchanges values using function codes and addresses. Use the device's register map to interpret data types, byte order, units and permitted operations.

Modbus RTU uses a serial connection. Check addressing, framing and timing, then use the device's register map to interpret the returned values.

Modbus Security adds protected transport and peer identity to Modbus. Apply it alongside the device register map and permissions for each read or write.

Modbus TCP carries Modbus exchanges over IP. Check the register map, network restrictions and permitted operations for the device you're connecting.

Health monitoring and remote administration require different permissions. Separate collection accounts from configuration access and record administrative sessions.

MQTT moves messages between clients through a broker. Define topic meaning, publish and subscribe permissions, retained state and delivery handling in the application.

NFC, BLE and UWB provide communication or ranging functions. Check how the credential is authenticated and how the access control system uses the result.

Time services support event ordering, certificate checks and evidence handling. Record the clock source and the application's response to clock faults or outages.

ONVIF defines services and profiles for devices and clients. Check the registered product, firmware, service capabilities and operations required by your integration.

OPC UA provides information models, services and security policies. Check which ones the server implements and how client identities are authorised.

OSDP connects readers and other peripheral devices to a controller. Check Secure Channel support, key setup, supervision and recovery on both ends of the connection.

Pelco D and P are legacy camera control protocols. Use offline traces to inspect the command set, addressing and response behaviour for the relevant equipment.

Power, USB and GPIO connections can affect device security and physical behaviour. Check their electrical requirements, exposed functions and control permissions.

PROFINET connects industrial devices with defined timing and engineering requirements. Record the device roles, configuration and supported traffic before planning an integration.

PLAI exchanges identity and access information between systems. Track the source identity, destination permissions and enforcement state when checking synchronisation and revocation.

PSIA publishes several interoperability specifications. Identify the relevant specification, product version and supported role before selecting an interface.

RTSP controls a media session, SDP describes it, RTP carries the media packets and RTCP reports session information. Check each part when investigating a stream.

SCIM exchanges identity lifecycle information between systems. Track provisioning results and check whether changes have reached dependent credentials and access policies.

Agree on electrical signalling, framing, timing and addressing before decoding serial messages. Check the settings and supported interfaces at both ends.

SIA AV01 covers audio verification for alarm monitoring. Check how its voice and control functions interact with the premises equipment and monitoring workflow.

SIA Format describes alarm messages exchanged by transmitters and receivers. Check the message structure, account identity, event mapping and acknowledgement behaviour.

SIA DC07 carries information from a receiver to monitoring automation. Check receiver status, event storage and operator handling as separate stages.

SIA DC09 carries alarm reports over IP networks. Check receiver acknowledgement, account identity, security settings and recovery when delivery is uncertain.

SIP manages call signalling while SRTP protects media. Check both paths, and give any door control its own authentication and permissions.

SOAP, WSDL and XML Schema describe service messages and interfaces. Check parser limits, authentication and operation rules when building a client.

VISCA carries camera control commands. Check supported operations, addressing and responses, then confirm how the device reports its final state.

SRT and RIST transport media across networks with packet loss and delay. Check the required protocol, recovery settings and compatible endpoints.

Review TLS settings alongside certificate provisioning, validation, renewal and recovery. Check the identity and trust requirements of each device and service.

WebAuthn and FIDO provide authentication mechanisms. Check the authenticator, relying party, account recovery and application permissions when using passkeys for administration.

WebRTC provides browser media and data communication. Plan signalling, user identity, permissions and connection setup as part of the application.

WebSocket, SSE and webhooks support different connection directions and lifetimes. Choose the required delivery model, then define ordering, retries, permissions and recovery.

Check radio performance, power use, device authentication and key management together. Include battery loss, interference and reconnection in the recovery plan.

Integration platforms combine information from several systems. Record the owner of each event, decision and control function, and restrict access to the required operations.

Intercom and emergency communication systems can share devices and networks. Check the authority, supervision and availability requirements for each service.

Intrusion systems detect conditions, report alarms and support a response. These pages follow those stages through the panel, communicator, receiver and monitoring service.

Perimeter systems combine sensors, assessment and response. Keep the source and uncertainty with each detection as it moves through the workflow.

Access control links identities and credentials to decisions made by controllers. These pages cover the readers, doors, permissions and operating conditions involved.

These pages explain the equipment and platforms used in physical security. Follow the devices, decisions and dependencies involved in each workflow.

Follow video from the scene through viewing, recording and export. Check picture quality, storage and retrieval when assessing whether the system meets its purpose.

Trace the report from the communicator through the receiver to monitoring software. Record what each acknowledgement confirms and how the response is handled.

Path supervision checks communication availability. Alarm verification gathers information about the reported condition. Record and monitor the results separately.

ANPR and LPR systems interpret number plates from images. Keep the confidence, original observation and matching rule with any resulting access decision.

Biometric systems compare a sample with a stored reference. Record the match threshold, operating conditions, uncertainty and recovery process used by the application.

Define the data exchanged with building or industrial systems. Check ownership and approval for any controls exposed through the integration.

Cameras combine imaging, encoding, services and device management. Check those functions separately when investigating video or integration problems.

Cloud services introduce provider, network and tenant dependencies. Record what runs locally, what relies on the provider and how the site operates during an outage.

Manage credentials through issue, expiry, revocation and replacement. Check how each change reaches controllers, including equipment that is temporarily offline.

Duress, panic and fire events require their own response rules. Preserve the original event class and the authorised workflow when mapping them into another system.

Emergency phones, mass notification and public address serve different workflows. Check supervision, priority, privacy and availability for the service being provided.

Gates and barriers involve moving machinery. Access software can request passage, while the approved local controller and safety functions govern movement.

HR records, visits and access entitlements have separate owners and lifecycles. Define how changes move between the systems and how conflicts are resolved.

Trace call signalling, media and notifications separately. Give door release its own identity check, permissions and recorded result.

Break an intercom system into identity, call control, media, notifications and physical outputs. Record which component handles each function.

Preserve the panel's zone states, faults and tamper reports when collecting events. Document any mapping or additional context applied by the receiving system.

Lock and egress behaviour depends on the opening, failure condition and approved design. Check the requirements for each door with the responsible site professionals.

Mobile access spans the phone, app or wallet, issuer, reader and access control platform. Include lost devices, replacement and account recovery in the design.

Offline controllers may use cached credentials and rules. Document the allowed behaviour during an outage and how credentials, events and occupancy are reconciled afterwards.

Identify where access decisions are made and where records are managed. Check how controllers enforce cached rules when the server or network is unavailable.

Readers, lock outputs, door contacts and requests to exit report different information. Track access decisions, relay state and door state separately.

Pedestrian portals combine access decisions, movement control and local safety functions. Record the responsibilities and approvals for each part of the passage sequence.

Map the perimeter into detection zones and assessment areas. Define the purpose, response path and responsible operator for each sensor layer.

PSIM and command platforms bring events and operator workflows together. Keep source information, operator decisions and control permissions visible in the shared interface.

PTZ movement and device outputs can affect the physical environment. Apply permissions and operating limits separately from access to the video stream.

Radar, fence and buried sensors measure different physical effects. Include installation conditions, environmental effects and uncertainty when interpreting their outputs.

Check recording from capture through storage, indexing, retrieval and playback. Compare the retained footage with the required duration and quality.

SIEM, SOAR and case management systems collect and process security information. Assign ownership for telemetry, investigation records and any automated physical actions.

Video analytics reports observations from a model operating in a particular scene. Retain the model, confidence and scene context when applying downstream rules.

Keep file hashes, source details, transformations and custody records with video exports. Record what the available evidence establishes about the footage and its timestamps.

Check image freshness, usability and recording as well as camera connectivity. Record which function was tested and when the observation was made.

Visitor, HR, access control and lift systems own different records and decisions. Define the approved exchange and permissions between them.

VMS, NVR and cloud video platforms manage different combinations of devices, recording, users and events. Identify the supported interface for the workflow you're building.

These references cover identity, credential and event interfaces in access control platforms. Confirm access conditions and product support before implementing a client.

Choose between communicating with device services and deploying an application on the device. Check permissions, deployment requirements and product support for that approach.

Find the supported API for the exact product and version. These pages cover public documentation, access requirements, licensing and integration checks.

These references cover video platform interfaces for live media, events, recording, export and administration. Check support for each required workflow.

Check whether the integration uses a 2N device API or a platform service. Apply separate permissions to calls, events, status and relay control.

VAPIX provides device interfaces while ACAP supports applications on Axis devices. Check the model, firmware and capabilities required by the chosen approach.

Identify the Bosch product and supported integration method. Check media, device control, events and platform functions against the relevant documentation.

Check the Brivo API workflow, access requirements and supported resources. Map identities, credentials, events and permissions to the needs of your integration.

Check whether the Dahua integration uses CGI or NetSDK. Record supported models, firmware, authentication and callback behaviour before implementing the client.

Check the Eagle Eye API and authentication flow for the required customer scope. Review media access, event retrieval and retention before implementation.

Choose the supported Command Centre interface for the task. Record licensing, product versions and operation permissions before implementing the integration.

Choose the appropriate Security Center SDK or web API interface. Check licensing, versions and roles against the functions required by your application.

SUNAPI provides device access, while Open Platform supports applications on compatible Hanwha devices. Check firmware, supported operations and deployment requirements.

Trace the HID service, mobile credential lifecycle and reader interaction. Check provisioning and revocation across the full access path.

Choose the appropriate ISAPI or HEOP integration approach. Confirm device and firmware support, API permissions, event handling and application lifecycle requirements.

Confirm the C•CURE product version, supported interface and access requirements. Check event behaviour and compatibility against the documentation for that release.

Identify the Kisi resources and permissions needed by the application. Handle account changes, event delivery and physical controls as separate operations.

Identify the exact OnGuard or Elements platform and supported interface. Check where OpenAccess applies before planning identity, event or control integration.

Compare MIP SDK and API Gateway against the required XProtect workflow. Check supported versions, permissions and deployment before implementing video, event or configuration access.

Identify the exact Avigilon platform and release. Check its interfaces, access requirements and supported media or event functions.

Choose the Nx interface for server access, client integration, device support or analytics. Record the product version and supported SDK or API capabilities.

Identify the SALTO product family, then check its API, credential model and access requirements. Record the supported operations for the specific platform.

Check the BioStar 2 version and supported API path. Review sessions, identity changes and event handling against the device and platform configuration.

Compare APIs against the required workflow. Record product versions, access conditions, identity handling, event support and the operations your application needs.

Check the Command API and organisation scope for the integration. Assign separate permissions for credentials, events, media and control operations.

Select the Zenitel interface for the communication workflow. Check product support for call state, media, notifications and any physical control.

Small programs for common integration tasks. Download one file, run its demo and inspect the result.

These pages cover adapter patterns, language choices and implementation examples. Start with the interface requirements, then plan validation, error handling and recovery.

These patterns cover retries, stale state, reconnection, schemas and secrets. Apply them consistently across adapters and document the behaviour your application relies on.

Choose a language that suits the interface and deployment. These notes cover validation, resource ownership, cancellation and recovery in each environment.

Define whether the component forwards transport data, translates a protocol or maps application meaning. Document the fields and behaviour it changes or preserves.

C gives direct control over bytes, memory and native interfaces. Check buffer limits, ownership and error paths, then compile and test for the intended target.

In C#, check cancellation, asynchronous lifetimes and typed data handling. Define reconnect behaviour and how the application represents uncertain operation results.

Use explicit ownership and resource limits when working with C++ SDKs. Document callback threads, object lifetimes and error handling in the adapter.

Use a shared schema while preserving the source event. Keep the raw record, mapping version and any uncertainty with the normalised fields.

Validate saved JSONL events and convert their occurrence timestamps to UTC.

Go supports small integration services with explicit timeouts and cancellation. Define resource ownership and connection settings for each device or API client.

Read one HTTPS health endpoint with certificate validation and a bounded JSON response.

Read holding or input registers from one authorised Modbus TCP endpoint.

Check the size, fields and CRC of a captured Modbus RTU register response.

Check an MQTT topic and JSON event against a small, explicit application contract.

Read a health endpoint using a validated server certificate and your own client certificate.

Design logs and metrics around the faults you'll need to investigate. Trace events across the integration while protecting credentials and retaining source context.

Send a read only GetDeviceInformation request to one ONVIF device service over HTTPS.

Polling and subscriptions provide different views of system changes. Plan gap detection and state reconciliation so the application can recover after missed events.

Python suits adapters, offline analysis and small services. Validate incoming data, limit network and file operations, and keep dependencies appropriate to the task.

Define what happens to queued work during an outage. Limit backlog growth, handle stale events and account for consumers that process messages slowly.

Plan retries, timeouts and idempotency together. Check whether repeating an operation could repeat a physical action after the original response was lost.

Inspect the media descriptions in a saved RTSP DESCRIBE response.

Keep credentials and trust settings out of source control, examples and logs. Give deployed configuration an owner, validation rules and a recovery process.

Store an event once and detect an identity reused with different content.

Keep event occurrence and receipt times separate while converting both to UTC.

Check the certificate presented by one TLS endpoint without bypassing chain or hostname validation.

TypeScript describes expected data during development. Validate incoming messages at runtime and manage connection state, permissions and cancellation in the application.

Estimate continuous recording capacity from measured bitrate, retention and free space requirements.

Verify an HMAC signature over an unchanged request body and its timestamp.

Read a short stream of door state events over WSS using Node and its native WebSocket API.

Review the integration from its inputs through to the equipment it can affect. Record permissions, deployed versions, failure cases and the evidence supporting each control.

Check who can publish an event and what the consumer may do with it. Validate the message, its source and its authority before acting.

Review an update's origin, supported installation path and effect on the deployed system. Check compatibility and rollback limits before scheduling the change.

Review identities, authentication methods and permissions across devices, operators and services. Include credential changes, denied operations and account removal in the checks.

Keep source records, clock information and transformation history together. Record which device produced each event and how the application processed it.

Plan how certificates, keys and secrets are issued, stored, renewed and removed. Assign ownership and recovery procedures for each part of the lifecycle.

Video, access and alarm records can contain sensitive information. Limit collection and access to the workflow's needs, and obtain the required privacy and governance review.

Give each remote support session a defined purpose, scope and expiry. Restrict permissions and record administrative actions through the site's approved process.

Test restoration of the required system state and plan operation during dependency outages. Include reconciliation of changes made while services were unavailable.

Verify device identity, software, configuration and ownership during commissioning. Record the approved settings and recovery process before putting the device into service.

Check message size, structure, types and meaning before processing the contents. Apply the same limits to network data, SDK callbacks and saved captures.

Use the relevant product guidance to establish security settings. Record the intended outcome, implemented controls, exceptions and evidence for the deployed configuration.

Define the required network flows and permissions between zones. Use segmentation alongside device security, application access rules and monitoring.

Trace events and commands through the system. Assess forged, delayed, duplicated and lost messages, including their possible effects on physical equipment.

Map vulnerability findings to the installed version, configuration and exposure. Use that context to plan remediation, approvals and the change window.

These pages cover the work after development: inventory, commissioning, monitoring, updates, recovery and retirement. Assign an owner for each operating task.

Record device versions, identities, owners and dependencies in the inventory. Include the recovery information needed to assess changes and investigate incidents.

Maintain records for certificates, service accounts, operators and physical credentials. Assign owners, review triggers and removal processes for each.

Check updates against the interfaces your integration uses. Review authentication, events, codecs, storage, timing and rollback before deploying a new version.

Collect acceptance evidence from the installed system. Include normal operation, denied requests, degraded conditions and recovery after failures.

Revoke device identities, cloud claims, credentials and integrations during retirement. Handle stored data and backups through the approved disposal process.

Assess the impact on physical security while investigating an incident. Preserve evidence and obtain approval before isolating equipment or changing a live service.

Monitor the function each service provides, including video freshness, event delivery and controller state. Record connectivity separately from those functional checks.

Write runbooks with the symptom, checks, expected results and escalation point. Keep live changes tied to the site's approved procedures.

Write requirements that can be tested against a product and version. Specify the required profiles, operations, failure behaviour and acceptance evidence.

Record layout, power, network routes, interfaces, ownership and dependencies during the survey. Mark uncertain assumptions for confirmation before implementation.

Practise using synthetic traces, sanitised configurations and tabletop scenarios. The exercises stay offline and separate from operational devices, real credentials and physical controls.

Compare a sanitised configuration with the matching product documentation. Record the supported controls, missing evidence and items requiring further review.

Work through certificate renewal and restoration on paper. Identify owners, dependencies and recovery steps for expiry and broken trust relationships.

Set the scope before starting a lab. Use the supplied synthetic or sanitised records, calculations and local simulations, with no connection to operational equipment.

Interpret synthetic Modbus values and BACnet objects using the supplied definitions. Record uncertain mappings and keep the exercise separate from building equipment.

Review broker trust and topic permissions in a synthetic design. Check publisher and subscriber access, retained messages and replay handling.

Read an offline trace with a specific question in mind. Record the observed bytes, supported conclusions and information missing from the capture.

Map a fictional ONVIF device through discovery, services, media and events. Use the supplied offline material to follow each stage.

Decode synthetic reader messages locally. Compare electrical framing, payload interpretation and authentication without using real credentials or hardware.

Use a fictional incident to practise evidence collection, approvals and service continuity decisions. Record the proposed response without making changes to live systems.

Follow session setup and packet flow in a synthetic media trace. Use the observations to identify which protocol layer needs further investigation.

Plan an alarm reporting test using a fictional system. Specify evidence for message acceptance, supervision and monitoring response without generating a real alarm.

Compare synthetic SNMP and syslog records for the same components. Keep identity and clock context with each observation when assessing service health.

Use synthetic timestamps to distinguish clock drift from delivery delay. Compare device time, receipt time and the expected event order.

Inspect an offline certificate chain against its intended identity. Check trust, names and validity, and record the reason for each result.

Calculate a fictional video recording budget. State the bitrate, retention, overhead and failure capacity assumptions so the result can be checked.

Follow a synthetic WebSocket event through validation, processing and recovery. Check connection loss and repeated messages without contacting a production service.

Look up matrices, field guides and checklists here. Follow the linked topic pages for the explanation and sources behind each entry.

Look up acronyms used in the wiki and follow the relevant topic when you need more detail.

Check cable, equipment, distance and power requirements against the actual installation. Have the responsible qualified person confirm the design and applicable requirements.

Find a runnable program by task.

Compare credential technologies across issue, authentication, storage, recovery and revocation. Include the reader and access control platform in the assessment.

Find diagrams of system components, responsibilities and data flows. These support the explanations in the wiki and require site specific engineering before installation use.

Check the scope of discovery and multicast traffic. Verify the identity and advertised services of a device before using the returned addresses.

Map event identity, time, state and source information into a consistent schema. Retain the original record and document any changes made during normalisation.

Look up the terms used across the wiki. Follow the linked references for definitions that depend on a particular system or protocol.

Review the supported interface, permissions, failure handling and recovery before accepting an integration. Record the test results and unresolved requirements.

Calculate network capacity and recording capacity separately. State bitrate, retention and overhead assumptions so the result can be reviewed.

Use this reference to look up common ports, transports and protection options. Confirm the configured service and identity on the actual endpoint.

Look up a technology's layer and role before comparing interfaces. Use the linked pages for the relevant protocol, codec, profile or system details.

Compare transport protection, peer identity, permissions, replay handling and key management separately. Check the supported configuration for the specific product.

Identify the equipment affected by a control change and the person authorised to approve it. Review the physical consequences through the site's safety process.

This is a dated record of standards and profile status. Confirm the current edition and lifecycle information with the original publisher before using it.

Find the interfaces commonly involved in each system workflow. Follow the linked references to check what information or control each one carries.

Use this matrix when discussing an integration with a vendor. Confirm product versions, licensing, access programmes and supported operations for the intended deployment.

How to read the references, check product support and report a correction.

Use the wiki for reading and approved offline exercises. Live system work requires its own authorisation, procedures and safety review.

Where the reference stops and product documentation or an authorised test is needed.

Scoped evidence for corrected source identities, publication status and moved documentation links.

Use original specifications and product documentation for technical claims. Record the edition, access date and limits of the source.

Source checks, software tests and equipment tests answer different questions.

A practical reference for security technicians, integrators and developers working with cameras, access control, alarms and connected systems.

MIT License

Report vulnerabilities privately and understand the boundaries of the static website, local builder and example programs.

Find protocols by the task they perform, then follow the detailed references for each family.