SCHEMA TEMPLATES
Security Risk Register
Give every security risk a consistent record, so teams can compare exposure, assign treatment and revisit it on time.
Security risks are easier to act on when every team describes the affected asset, threat, assessment and owner in the same way. This template gives reviewers a common register for comparing open risks and scheduling treatment; the assessment and decisions remain yours.
Fields
When a new concern appears, what would your team need to decide whether to act now or revisit it later? This structure keeps the conversation anchored in a shared assessment and a clear next step.
| Field | Type | What it captures |
|---|---|---|
| Risk IDRequired · Indexed | Text | Stable identifier used to track and refer to the risk. |
| AssetRequired · Indexed | Text | System, information or other asset exposed to the risk. |
| ThreatRequired | Text | Security scenario that could affect the asset. |
| LikelihoodRequired · Indexed | Single choice | Estimated chance that the threat will occur.Choices: Low, Medium, High, Critical |
| ImpactRequired · Indexed | Single choice | Severity of the consequences if the security threat occurs.Choices: Low, Medium, High, Critical |
| Risk scoreIndexed | Number | Numeric assessment recorded for the risk; no automatic calculation is built in. |
| OwnerRequired · Indexed | Confluence user | Person responsible for this risk, policy or document record. |
| Treatment | Text | Planned response or mitigation for the risk. |
| StatusRequired · Indexed | Single choice | Current stage of the record's workflow or lifecycle.Choices: Open, Accepted, Mitigating, Resolved |
| Review dateIndexed | Date | Date planned for the next review of the risk, document or decision. |