Canada version. Maps the threat library to the Canadian Centre for Cyber Security's 13 baseline controls for organizations under 500 employees, and adds PIPEDA breach reporting and records. US version
Security Threat Checklist (Canada)
Map common threats to the Cyber Centre's 13 baseline controls for small and medium organizations, plus PIPEDA breach reporting and two-year breach records.
The interactive tool loads here when JavaScript runs.
About this toolWhat is Security Threat Checklist?
Canadian small and medium organizations have a home-grown starting point: the Baseline Cyber Security Controls from the Canadian Centre for Cyber Security (version 1.2). It is written for organizations with fewer than 500 employees and applies an 80/20 rule, aiming for most of the benefit from a small set of controls. There are 13, starting with an incident response plan and automatic patching and ending with secure websites, access control and portable media.
This version ties the 22 threats in the library to those controls, so the Markdown file you export shows both the threat and the Canadian control that answers it. Some controls have no matching threat (a written incident response plan, a decision on mobile device ownership, rules for USB drives), and those need lines of their own. Others are more specific than the generic advice in the library: the Cyber Centre asks for websites to meet OWASP ASVS Level 1 and for DMARC on every email service.
The legal side comes from PIPEDA. If a breach of security safeguards involving personal information creates a real risk of significant harm, you must report it to the Office of the Privacy Commissioner and notify the people affected as soon as feasible. Every breach, reportable or not, has to be recorded and the records kept for two years. The OPC confirms these duties apply to small businesses as well as large ones.
- 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
Baseline control gap check for a 40-person firm
Input
Add Malware & Virus Attacks, Phishing & Deceptive Content, Broken Authentication, Cloud Misconfiguration and Privilege Escalation
Output
A Markdown file with five sections, three rated Critical (Malware & Virus Attacks, Broken Authentication, Privilege Escalation)
Between them these cover controls 2 (automatic patching), 3 (security software), 5 (strong user authentication), 6 (awareness training), 7 (backup, through "Backup and recovery systems"), 10 (cloud and outsourced IT) and 12 (access control). Add control 1, a written incident response plan with a hard copy, and control 13, secure portable media, as your own lines: no threat entry covers them.
A lost laptop with client files
Input
Add Cryptographic Failures and Insider Threat
Output
Two sections, both rated High, with prevention items such as "Use strong encryption algorithms" and "Data loss prevention (DLP)"
Control 8 asks that mobile devices store sensitive information encrypted. If the laptop was not encrypted, run the OPC's real-risk-of-significant-harm assessment: the sensitivity of the information and the probability of misuse decide whether you report. Either way, the breach goes in your records for two years.
A small online shop
Input
Add SQL Injection, Cross-Site Scripting (XSS) and Phishing & Deceptive Content
Output
Three sections; SQL Injection rated Critical, with "Parameterized queries/prepared statements" and "Domain-based Message Authentication (DMARC)" among the prevention items
Control 11 sets the bar for the website at OWASP ASVS Level 1, and control 9 asks for DMARC and email filtering. If an outside agency runs the site, the Cyber Centre suggests making ASVS a contract requirement.
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
- The Cyber Centre recommends changing passwords only when there is suspicion or evidence of compromise, and two-factor authentication for financial, administrator, cloud admin and executive accounts.
- Keep long-term backups (weekly, for example) offline; daily backups may stay online. Test that restores work.
- Never connect a guest Wi-Fi network to your internal network, and isolate point-of-sale systems behind a firewall.
- Record every breach of security safeguards with enough detail for the OPC to see how you assessed the risk of harm.
Sources and further reading
- Baseline cyber security controls for small and medium organizations, Canadian Centre for Cyber Security. The 13 controls, the under-500-employee scope, ASVS Level 1 and DMARC.
- What you need to know about mandatory reporting of breaches of security safeguards, Office of the Privacy Commissioner of Canada. Real risk of significant harm, report contents, notification and two-year records.
- OWASP Top 10, OWASP Foundation
Frequently asked questions
What are the 13 Canadian baseline cyber security controls?
Develop an incident response plan; automatically patch operating systems and applications; enable security software; securely configure devices; use strong user authentication; provide employee awareness training; back up and encrypt data; secure mobility; establish basic perimeter defences; secure cloud and outsourced IT services; secure websites; implement access control and authorization; secure portable media.
Who are the baseline controls for?
Small and medium organizations in Canada, which the Cyber Centre defines using the Innovation, Science and Economic Development Canada threshold of fewer than 500 employees. Larger organizations are advised to invest in more comprehensive measures.
When must a business report a privacy breach to the OPC?
When a breach of security safeguards involving personal information poses a real risk of significant harm. The report must cover what happened and when, the information involved, how many people are affected, steps taken to reduce harm, how they will be notified and a contact person.
How long must breach records be kept under PIPEDA?
Two years, for every breach of security safeguards, whether or not it met the real risk of significant harm threshold. The OPC can ask to see them.
What counts as significant harm under PIPEDA?
The OPC lists bodily harm, humiliation, damage to reputation or relationships, loss of employment, business or professional opportunities, financial loss, identity theft, negative effects on the credit record and damage to or loss of property.
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.