United Kingdom version. Maps the threat library to the five technical controls in the NCSC Cyber Essentials requirements (v3.3) and adds the UK GDPR 72-hour breach reporting rule to your plan. US version
Security Threat Checklist (UK)
Build a threat checklist mapped to the five Cyber Essentials controls, add the UK GDPR 72-hour breach rule, and export it as Markdown for your next review.
The interactive tool loads here when JavaScript runs.
About this toolWhat is Security Threat Checklist?
Most UK small firms meet security checklists through Cyber Essentials, the government-backed scheme run by the National Cyber Security Centre with IASME as its delivery partner. The April 2026 requirements (v3.3) sort everything under five technical controls: firewalls, secure configuration, security update management, user access control and malware protection. This version shows where the 22 threats in the library land on those five headings, so the Markdown file you export can double as a pre-assessment worksheet.
The mapping also shows what the certificate leaves out. The requirements state that bespoke and custom components of web applications are out of scope, so SQL injection, XSS, CSRF, SSRF and business logic flaws, which make up most of an in-house development team's exposure, are not assessed at all. Passing Cyber Essentials and running a secure web application are two different claims; one checklist can cover both if you add the application threats yourself.
Plan the response as well as the prevention. Article 33 of the UK GDPR requires a controller to report a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to people's rights and freedoms. Since 30 September 2026 the amended text names the regulator as the Information Commission (section 114A of the Data Protection Act 2018), which took over the functions of the Information Commissioner, the ICO (section 119 of the Data (Use and Access) Act 2025).
- 22 threat classes across web, API, cloud, mobile, IoT and human factors
- Search plus domain and category filters
- Prevention, detection, impact and related-threat links for each entry
- Custom checklist with Markdown export and tick boxes
- Static reference; nothing is uploaded or stored
Updated
How to use Security Threat Checklist
- Open Browse Threats and search or filter by domain and category.
- Click a card to read the full entry: attack methods, prevention, detection, impact and related threats.
- Click the plus button on each threat that applies to your system.
- Open the Security Checklist tab, rename the checklist and remove anything that does not apply.
- Click Download MD to save the checklist as Markdown with tick boxes.
Worked examples
A Cyber Essentials pre-assessment pack
Input
Add Privilege Escalation, Malware & Virus Attacks, Phishing & Deceptive Content, Cloud Misconfiguration and IoT Device Vulnerabilities; rename the checklist "Cyber Essentials prep"
Output
cyber_essentials_prep.md with five numbered sections, two rated Critical (Privilege Escalation, Malware & Virus Attacks), each with tick boxes for attack methods, prevention and detection
Privilege Escalation sits under user access control, where the requirements ask for separate accounts for admin work and for privileges to be removed when no longer needed. Its "Security updates and patches" item is the security update management control: fixes rated critical or high risk, or CVSS v3 7 and above, go on within 14 days of release. The IoT entry's "Change default credentials" is secure configuration, and Cloud Misconfiguration matters because v3.3 states that cloud services cannot be excluded from scope.
The part of an in-house web app that the certificate skips
Input
Add SQL Injection, Cross-Site Scripting (XSS), Cross-Site Request Forgery (CSRF) and Business Logic Vulnerabilities
Output
Four sections, SQL Injection rated Critical and XSS High, with items such as "Parameterized queries/prepared statements" and "Content Security Policy (CSP)"
None of these is tested for Cyber Essentials, because custom web application code is out of scope; the requirements point developers to the Software Security Code of Practice instead. Keep this file alongside the certification evidence so nobody reads the certificate as covering the application.
A breach drill for a phishing incident
Input
Add Phishing & Deceptive Content and Social Engineering, then note who starts the 72-hour clock
Output
Two sections, both listing "Incident reporting systems" under prevention
Write the Article 33 deadline next to that tick box. Under Article 33(5) every personal data breach must be documented, including the ones you decide not to report, and Article 34 adds a duty to tell the people affected without undue delay when the risk to them is high.
Background and insight
The entries overlap with the OWASP Top 10 for web applications (Broken Access Control, Cryptographic Failures, Injection, Insecure Design, Security Misconfiguration, Vulnerable and Outdated Components, Identification and Authentication Failures, Software and Data Integrity Failures, Logging and Monitoring Failures and SSRF in the 2021 edition), and add infrastructure, human and device risks such as container escape, insider threats, phishing, IoT devices and denial of service.
A threat checklist is most useful early, during design review or threat modelling, when "how would we detect this?" can still change an architecture decision. Used at the end of a project it tends to become a box-ticking exercise. Picking the five or six threats that genuinely apply to a feature and writing down the specific control for each beats exporting all 22.
Earlier versions offered a fixed category list that left out several categories present in the data, such as Cryptography Security and File Security, so those threats could only be found by search. The category filter is now built from the data.
Common use cases
Design reviews
Attach a checklist of the threats that apply to a new feature and the control chosen for each.
Threat modelling sessions
Use the domains and related-threat links as prompts when walking through a data-flow diagram.
Onboarding and training
Give new engineers a readable overview of common attack classes and their defences.
Audit preparation
Build a list of controls to evidence, grouped by threat, before a security questionnaire or audit.
Tips and limitations
- For user access control, Cyber Essentials expects MFA wherever it is available and always for cloud services. Where passwords are the only defence, use at least 12 characters, or at least 8 with a deny list of common passwords.
- Brute-force protection is spelt out: throttle to no more than 10 guesses in 5 minutes, or lock after no more than 10 failed attempts.
- Firewall admin interfaces must not be reachable from the internet unless there is a documented business need and MFA or an IP allow list protects them.
- Software that is no longer supported must come off in-scope devices, or be fenced into a sub-set with no internet traffic. Add it as a line in your checklist so it is reviewed each year.
- Keep your breach log separate from the Markdown checklist: the checklist is a plan, the log is the evidence the regulator can ask to see.
Sources and further reading
- Cyber Essentials: overview, National Cyber Security Centre. The five controls, Cyber Essentials Plus, pricing from £320 plus VAT and supplier requirements.
- Cyber Essentials: Requirements for IT Infrastructure v3.3, National Cyber Security Centre. Scope (custom web application code excluded, cloud services included), 14-day patching, MFA and password rules.
- UK GDPR Article 33: Notification of a personal data breach, legislation.gov.uk. The 72-hour rule, reasons for delay and the duty to document every breach.
- UK GDPR Article 34: Communication of a personal data breach to the data subject, legislation.gov.uk
- Data (Use and Access) Act 2025, section 119, legislation.gov.uk. Functions of the Information Commissioner transferred to the Information Commission; in force from 30 September 2026.
- OWASP Top 10, OWASP Foundation
Frequently asked questions
What are the five Cyber Essentials controls?
Firewalls, secure configuration, security update management, user access control and malware protection. The NCSC requirements for IT infrastructure (v3.3, April 2026) set out what each one demands, from blocking unauthenticated inbound connections by default to running anti-malware or application allow listing on every in-scope device.
Does Cyber Essentials cover SQL injection and other web application flaws?
No. Commercial web applications are in scope by default, but bespoke and custom components of web applications are out of scope. If your team writes its own web code, add the injection, XSS, CSRF and business logic entries from this checklist and test them separately.
How quickly must security updates be installed for Cyber Essentials?
Within 14 days of release when the update fixes vulnerabilities the vendor calls critical or high risk, those with a CVSS v3 base score of 7 or above, or when the vendor gives no severity. The NCSC strongly recommends, but does not require, applying every update within 14 days.
What is the difference between Cyber Essentials and Cyber Essentials Plus?
The NCSC describes Plus as the same protections with more rigorous, independent technical testing of your systems. Basic Cyber Essentials is priced in tiers starting from £320 plus VAT on the NCSC overview page; Plus is quoted on the size and complexity of your network.
Do I have to report a data breach within 72 hours in the UK?
You must report a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to people's rights and freedoms. A late report has to give reasons for the delay. Breaches you do not report still have to be documented.
Do suppliers to UK organisations need Cyber Essentials?
Sometimes. The NCSC notes that a growing number of organisations require suppliers to be certified to bid for work. Check the tender or contract: the requirement comes from the buyer, not from a general law.
Is there an in-depth guide to Security Threat Checklist?
Yes. “Preventing SQL Injection: Spotting Unsafe Queries in Code Review” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.