Security Technician Wiki
A practical reference for security technicians, integrators and developers working with cameras, access control, alarms and connected systems.
On this page
The wiki covers how the equipment works, how systems communicate and what to check when something goes wrong. There are protocol notes, integration examples, troubleshooting guides and checklists for day to day work.
securitytechnician.wiki · Reading paths · Code examples · Protocol map · Quick reference
Where to start#
| What are you working on? | Start here | Topics covered |
|---|---|---|
| Learning the basics | Getting started | Equipment, networking, identity, events and system behaviour |
| Cameras and video | Video integration | ONVIF, streams, recording, events and platform APIs |
| Readers and doors | Access control | Credentials, OSDP, controllers, door state and permissions |
| MQTT and system events | Event integration | Message schemas, timestamps, delivery, retries and reconciliation |
| Fault finding | Troubleshooting | Symptoms, evidence, diagnostic checks and recovery |
| Checking an integration | Security review | Permissions, trust boundaries, failures and readiness |
Each path groups the relevant pages in a suggested order. The full reading guide also covers alarms and building systems.
Useful references#
The integration readiness checklist covers the checks before handing over a working integration. The event field guide helps with device identity, timestamps and state when connecting different systems.
For interface selection, use the protocol role matrix, protocol security comparison and vendor capability matrix. Confirm the product version and supported features against the manufacturer's documentation.
The code examples contain 14 small programs for API reads, event validation, protocol parsing, certificates and storage calculations. Each has a demo, a clear input format and the complete source. Start with the video storage calculator or event trace parser. Neither needs equipment or extra Python packages.
The defensive labs provide longer exercises using synthetic messages and traces.
Browse by section#
| Section | Contents |
|---|---|
| 00 · Start here | Reading paths, terminology and scope |
| 01 · Foundations | Architecture, networking, identity, media, power and time |
| 02 · Protocols | Video, access control, alarms, building systems and messaging |
| 03 · Systems | Cameras, VMS, PACS, intercoms, intrusion and integration platforms |
| 04 · Vendor APIs | Documented interfaces, access requirements and product versions |
| 05 · Development | Adapters, language guides, code examples and message handling |
| 06 · Security | Threat modelling, identity, parsing, hardening and privacy |
| 07 · Operations | Inventory, commissioning, monitoring, updates and recovery |
| 08 · Defensive labs | Offline exercises using synthetic data |
| 09 · Reference | Matrices, ports, field guides, glossaries and checklists |
| 10 · Sources and scope | Source selection, test boundaries and corrections |
The same articles are available on the website, in GitHub and in a local copy of this repository.
Sources and verification#
Articles link to primary sources and state their scope. Protocol release dates, deprecation notices and runtime support need checking against the version you use. Dated checks are shown on the relevant pages. The verification guide explains the difference between a source check, a software test and a result on equipment.
Check product instructions and site procedures before changing a system. Work involving locks, gates, lifts, fire interfaces or emergency communications needs the relevant engineering review and approval.
About this project#
Maintained by tegridydev. Original writing, diagrams, tables and examples use the MIT licence, unless a page states otherwise. Referenced standards, vendor documents and trademarks remain with their owners.
Corrections are welcome. Include the page, the relevant source and the product or specification version so the change can be checked.