ciphersense --docs
Documentation is a deliverable, not an afterthought
Every engagement ships the same package: topology, schemas, inventory, and a recovery playbook — so your environment can be supported by anyone, not just us. Here's a sample of what that looks like.
DOC-01 · TOPOLOGY
CURRENT AS OF DEPLOYMENT
current
Every device, every link, every VLAN boundary — drawn accurately and kept current.
No "approximately correct" diagrams.
DOC-02 · VLAN / IP SCHEMA
SEGMENTATION MAP
enforced
VLAN 10corporate10.0.10.0/24
VLAN 20guests10.0.20.0/24
VLAN 30iot10.0.30.0/24
VLAN 40cameras10.0.40.0/24
VLAN 99mgmt10.0.99.0/24
VLAN IDs, names, subnets, and firewall rules — one source of truth, so nobody has to
reverse-engineer the network from memory.
DOC-03 · DEVICE INVENTORY
REGISTER
synced
UDM-PROgatewayfw 7.2.9
USW-24-POEcorefw 6.6.65
UAP-AC-PRO ×2wlanfw 6.6.65
G4-BULLET ×4camfw 4.65.4
Model, role, firmware, and location for every managed device — the register that makes
firmware planning and warranty tracking possible.
DOC-04 · RECOVERY PLAYBOOK
IF-TOO / THEN
tested
IFgateway diesrestore backup → swap unit
IFwifi outagecheck APs → PoE port → reboot
IFcam offlinevlan 40 → poe → unifi app
IFretention dropscheck NVR disk → bitrate audit
Step-by-step recovery for the failures that actually happen — written for a human under
pressure, not a documentation committee.
This is the standard, not the exception
Every engagement ships this package — scoped projects and lifecycle partnerships alike.