Keep a camera access register without passwords
Prepared 22 October 2026 by NightMarshal

An access register should record the approved role, purpose, system, owner and review date for each access grant. Store credentials separately, and verify that departed staff and suppliers lose access through the supported process.

Instructions
1. List access paths and task permissions.
2. Record the approval owner and expiry or review point.
3. Check removal across all relevant systems.

Open the blank CSV in a spreadsheet app; add one row per item. Use Pending for unknowns and N/A only where a field truly does not apply. Review the separate example CSV; all example values are fictional. Keep completed sheets private. Do not include passwords, access codes, personal contacts, footage links or camera stream URLs. No input is collected by these downloads.

Fields
Account alias
System
Approved task
Approval reference
Expiry or review
Removal verified

Fictional example
Fictional review: an installer’s temporary cloud invitation remains active after a local account was disabled. IT closes the second path and records both checks.

Limits
The worksheet contains no credentials. A register supports governance but does not prove the underlying permission controls work.