Infrastructure register
An infrastructure register is a living record of the systems an organization depends on. It should be simple enough to maintain and complete enough to support handover and recovery.
Core fields
| Field | Purpose | Example |
|---|---|---|
| System name | Identify the asset or service. | Main website hosting |
| Purpose | Explain why the system matters. | Public website deployment and hosting |
| Owner | Name the accountable person or role. | Digital operations lead |
| Access method | Describe how authorized users access it. | Named admin accounts with MFA |
| Dependency | List connected systems it relies on. | Domain DNS, repository, billing card |
| Renewal or review date | Make time-based risks visible. | Annual renewal / quarterly review |
| Recovery route | Record how access or service can be restored. | Provider support route and backup admin |
Maintenance guidance
Keep the register in a location that is accessible to the right people, protected from unnecessary exposure, and reviewed on a fixed schedule. A register that is never updated becomes another source of risk.