Zum Hauptinhalt springen
Starter Kit · Register

Threat Register

Updated on 2 min Reviewed by: Cenedril-Redaktion
A.5.7 ISO 27001ISO 27005BSI IT-Grundschutz

Which threats are relevant to your organisation? Ransomware, insider attacks, natural disasters, supply chain failures? A.5.7 requires you to collect and analyse information about threats to information security. The threat register provides the structured foundation for this analysis — and the starting point for every risk scenario.

What does it contain?

The template structures threats so they feed directly into the risk management process per ISO 27005:

  • Threat — name of the threat (e.g. ransomware, social engineering, power outage)
  • Category — classification by threat type (e.g. deliberate/human, negligent/human, environmental, technical)
  • Description — what exactly is the threat and how does it manifest?
  • Affected protection goals — which goals are at risk? (confidentiality, integrity, availability)
  • Typical attack vectors / triggers — how does the threat typically materialise?
  • Relevance — how relevant is the threat to your organisation? (high, medium, low)

How to use the template

1. Start with the template. The CSV contains a curated selection of threats relevant to most organisations. It covers deliberate attacks (malware, phishing, DDoS), human error (misconfiguration, accidental data loss), technical failures (hardware defect, software bug), and environmental events (power outage, water damage, fire).

2. Add sector-specific threats. Do you operate critical infrastructure? Then targeted sabotage and state-sponsored attacks belong in the register. Healthcare? Manipulation of medical data. Financial sector? Fraud and regulatory sanctions.

3. Remove what does not apply. An earthquake threat is negligible in regions with no seismic activity. An attack on industrial control systems (OT) does not concern a pure software company. Remove what is irrelevant to your context — and briefly document why.

4. Link to vulnerabilities and assets. The real work begins when threats meet specific vulnerabilities and assets. The combination “threat + vulnerability + asset” produces risk scenarios that are assessed in the risk register.

5. Update regularly. Threat landscapes change quickly. Schedule a review at least annually — and respond on an ad-hoc basis to new threats surfaced by threat intelligence, incidents, or industry developments.

Register Template

Threat Register

IDThreatCategorySourceDescriptionTTP (MITRE ATT&CK)RelevanceTargeted AssetsLikelihoodPotential ImpactMitigation ControlsLast Reviewed
T-001Ransomware (double extortion)MalwareBSI CSW + CERT-EUFinancially motivated groups (LockBit Black Basta Akira) target mid-size logisticsT1486 T1190 T1566.001HighFile servers domain controllers backupsHighCriticalOffline backups EDR MFA segmentation awareness2026-04-01
T-002Credential phishingSocial engineeringBSI Lagebericht 2025Large-scale phishing with adversary-in-the-middle kitsT1566.002 T1111HighUser accounts M365HighHighMail filter awareness phishing-resistant MFA2026-04-01
T-003Business email compromise (CEO fraud)Social engineeringAllianz Cyber-ReportImpersonation of CEO/CFO targeting financeT1534 T1656MediumFinance teamMediumHighDual approval for payments BEC training2026-04-01
T-004Supply chain compromiseSupply chainENISA Threat Landscape 2025Compromise via updates or dependencies (xz SolarWinds-style)T1195.002MediumBuild pipeline dependenciesMediumCriticalSBOM dependency scan vendor risk review2026-04-01
T-005Exploitation of public-facing servicesVulnerabilityCISA KEVMass exploitation of VPN firewall edge (Fortinet Ivanti Citrix)T1190HighVPN firewall perimeterHighHighPatch SLA asset exposure monitoring pentests2026-04-01
T-006Insider threat - malicious leaverInsiderACFE reportLeavers exfiltrating data via personal cloud/emailT1537 T1048MediumCRM HR finance dataMediumHighDLP leaver process access review2026-04-01
T-007DDoS against customer-facing servicesDoSNCSC advisoryHacktivist or extortion DDoST1498 T1499MediumCustomer portal websiteMediumMediumCDN/L7 protection rate limiting2026-04-01
T-008Data leakage via misconfigurationMisconfigurationCloud security reportsOpen cloud buckets DBs accidentally exposedT1530MediumCloud storage databasesMediumHighIaC scan least-privilege account guardrails2026-04-01
T-009Malicious browser extensionsMalwareChrome advisoriesCompromised extensions exfiltrate cookies and session tokensT1176MediumUser endpointsMediumHighExtension allowlist browser hardening2026-04-01
T-010Living-off-the-land attacksPost-exploitMITRE reportsAttackers using legitimate tools (PsExec WMI PowerShell)T1059.001 T1021.002MediumWindows serversMediumHighEDR behaviour rules PowerShell logging2026-04-01
T-011Drive-by compromise via watering holeWebGoogle TAG reportsTargeted websites serving exploitsT1189LowUser endpointsLowMediumWeb filter browser patching2026-04-01
T-012Physical theft of equipmentPhysicalInternal historyLaptop theft from vehicles or travelN/AMediumLaptops mobile devicesMediumMediumFull disk encryption remote wipe awareness2026-04-01

Sources

ISO 27001 Controls Covered

A.5.7 Threat intelligence

Frequently asked questions

What is the difference between a threat and a risk?

A threat is a potential event that can cause harm (e.g. ransomware attack). A risk arises when a threat meets a vulnerability and a specific asset is affected. The threat register captures threats — the risk register assesses the resulting risks.

How many threats should the register contain?

Depends on the size and sector of the organisation. For a mid-sized IT company, 30–60 threats is a realistic scope. The BSI Grundschutz catalogue lists over 40 elementary threats — the template contains a practical selection. Add sector-specific threats and remove what is irrelevant to your context.

How often must the threat register be updated?

A.5.7 requires that information about threats is collected and analysed. In practice: at least annually as part of the risk assessment, plus on an ad-hoc basis — e.g. after a security incident, when new attack vectors emerge, or after significant changes to the IT infrastructure.