Security Threat Checklist
Browse 22 common threat classes, from XSS and SSRF to supply-chain attacks, with prevention and detection measures, and export your picks as a Markdown checklist.
The interactive tool loads here when JavaScript runs.
About this toolWhat is Security Threat Checklist?
The Security Threat Checklist is a reference of 22 common threat classes with the controls that address them. Each entry covers a description, severity, the domains it affects, typical attack methods at a high level, prevention measures, detection methods, impact and the systems usually targeted, plus links to related threats.
Search by name or keyword, filter by domain (Frontend, Backend, Database, API, Mobile, Cloud and others) or by category, and click the plus button to add a threat to your own checklist. The checklist tab lets you rename it and download it as a Markdown file with tick boxes, ready for a repository, a wiki page or a design review document.
The list is static reference content that ships with the page. Your checklist lives in the tab while you work and is not saved or uploaded, so download it before closing the page.
- 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 example
A checklist for a public REST API
Input
Domain filter API; add SQL Injection, Broken Authentication, API Security Vulnerabilities and SSRF
Output
A Markdown file with four sections, each listing prevention and detection items as - [ ] tick boxes
The file is named from the checklist title, for example my_security_checklist.md, and opens with a short disclaimer and the generation date.
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
- Keep the checklist short and specific. Replace generic prevention items with the actual control in your system, for example the name of the middleware that sets CSRF tokens.
- Severity labels are general guidance. Rate each threat again for your own system, since impact depends on the data you hold.
- The checklist is not saved between visits. Download the Markdown before closing the tab.
- Pair it with the SQL Injection Tester and Security Headers Analyzer to check two of the controls directly.
- Re-run the checklist when the architecture changes, not only once at launch.
Sources and further reading
- OWASP Top 10:2021, OWASP. The ten categories the checklist overlaps with
- Threat Modeling Cheat Sheet, OWASP. Using threats during design review
Frequently asked questions
What should a web application security checklist include?
At minimum: injection, cross-site scripting, broken authentication and session handling, access control, CSRF, SSRF, security misconfiguration including headers, vulnerable dependencies and logging. Filter this checklist by the Web Application and API domains to start, then add what your architecture needs.
How is this checklist related to the OWASP Top 10?
Many entries map directly onto OWASP Top 10 categories, such as injection, cryptographic failures, SSRF and broken authentication. The checklist also covers threats outside that list, including container escape, insider threats, phishing, IoT devices and denial of service.
Can I export the security checklist?
Yes. Add threats with the plus button, open the Security Checklist tab and click Download MD. You get a Markdown file with each threat's prevention and detection measures as tick boxes, which renders well on GitHub, GitLab and most wikis.
Is my checklist saved if I close the page?
No. The checklist is kept in the page while you work and is not stored in your browser or sent anywhere. Download the Markdown file before you leave or refresh the page.
How should a team use a threat checklist in design reviews?
Pick the threats that apply to the feature, and for each one write the specific control and how you would detect a failure. Review it with someone outside the team. A short, specific list that changes a design is worth more than a long generic one.
Does the checklist include instructions for attacking systems?
No. Attack methods are described at a high level so you can recognise the threat, and each entry focuses on prevention and detection. Testing a system for these weaknesses should only be done on systems you own or are authorised to test.
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.