Australia version. Links each threat to the Privacy Act's Notifiable Data Breaches scheme: who is covered, the 30-day assessment and when the OAIC and affected people must be told. US version

Security Threat Checklist (Australia)

Build a threat checklist that ends in a data breach plan for the Notifiable Data Breaches scheme: the $3 million test, 30-day assessment and OAIC notice.

The interactive tool loads here when JavaScript runs.

About this tool

What is Security Threat Checklist?

For an Australian business the question after "how do we prevent this?" is "would this be an eligible data breach?". Under the Notifiable Data Breaches (NDB) scheme in Part IIIC of the Privacy Act 1988, an eligible data breach is unauthorised access to, unauthorised disclosure of, or loss of personal information that is likely to result in serious harm to one or more people, where you have not been able to prevent that likely harm with remedial action. If it is, you must notify the people at risk and give the OAIC a statement as soon as practicable.

Coverage is narrower than many owners assume. The OAIC says most small businesses, those with an annual turnover of $3 million or less, are not covered by the Privacy Act, but some are regardless of turnover, such as health service providers, credit reporting bodies and businesses that trade in personal information, and the OAIC lists tax file number recipients among the small businesses the NDB scheme reaches. Agencies, larger businesses and not-for-profits over the threshold are covered.

This version uses the 22-threat library to plan for that moment. Each entry you add has an "Incident reporting systems" or detection line where the NDB steps can go: contain the breach, assess it, notify if it is eligible, then review. When you only suspect an eligible breach, the assessment must be finished, taking all reasonable steps, within 30 calendar days of becoming aware of the grounds for suspicion.

  • 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
Read the guide: Preventing SQL Injection: Spotting Unsafe Queries in Code Review

Updated

How to use Security Threat Checklist

  1. Open Browse Threats and search or filter by domain and category.
  2. Click a card to read the full entry: attack methods, prevention, detection, impact and related threats.
  3. Click the plus button on each threat that applies to your system.
  4. Open the Security Checklist tab, rename the checklist and remove anything that does not apply.
  5. Click Download MD to save the checklist as Markdown with tick boxes.

Worked examples

A tradie business with online bookings

Input

Add Phishing & Deceptive Content, Broken Authentication and Cloud Misconfiguration

Output

A Markdown file with three sections; Broken Authentication rated Critical, Phishing and Cloud Misconfiguration rated High

First check coverage: if annual turnover has never been over $3 million since 2002 and no exception applies, the NDB scheme may not cover you, but the checklist still protects the booking data. If you are covered, a compromised mailbox that exposed customer addresses and phone numbers is a data breach to assess against the serious-harm test.

A medical clinic, covered whatever its turnover

Input

Add Malware & Virus Attacks, Insider Threat and Cryptographic Failures

Output

Three sections, Malware & Virus Attacks rated Critical, with "Backup and recovery systems" and "Data loss prevention (DLP)" among the prevention items

Health service providers are covered by the Privacy Act regardless of turnover. An employee browsing sensitive records without any legitimate purpose is one of the OAIC's own examples of unauthorised access, so write the 30-day assessment clock under Insider Threat.

A lost laptop that turns out not to be notifiable

Input

Add Cryptographic Failures and note the remedial action taken

Output

One section, rated High, with "Use strong encryption algorithms" and "Proper key management systems" as tick boxes

For a loss, the OAIC says remedial action is adequate if it prevents unauthorised access to or disclosure of the information. A fully encrypted laptop that is remotely wiped may never become an eligible data breach, which is why the encryption tick box is worth checking before an incident.

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

  • Judge serious harm as a reasonable person in your organisation's position would, and treat it as likely when it is more probable than not, not merely possible.
  • Serious harm can be physical, psychological, emotional, financial or reputational, so do not limit the assessment to money.
  • If several organisations hold the same data, only one needs to assess and notify; agree who in your supplier contracts.
  • Notifications to individuals should be in plain English and tell people what practical steps to take.

Sources and further reading

  1. Quick reference guide for responding to data breaches, Office of the Australian Information Commissioner. Who is covered, the four steps, serious harm, the 30-day assessment and notification.
  2. When to report a data breach, Office of the Australian Information Commissioner
  3. Small business, Office of the Australian Information Commissioner. The $3 million annual turnover test and the businesses covered regardless of turnover.
  4. OWASP Top 10, OWASP Foundation

Frequently asked questions

What is an eligible data breach in Australia?

Unauthorised access to, unauthorised disclosure of, or loss of personal information you hold, that is likely to result in serious harm to one or more individuals, where remedial action has not prevented that likely harm.

Does the Notifiable Data Breaches scheme apply to small businesses?

Most businesses with an annual turnover of $3 million or less are not covered by the Privacy Act. Some are covered regardless of turnover, including health service providers, businesses trading in personal information, credit reporting bodies and Commonwealth contractors.

How long do I have to assess a suspected data breach?

You must take all reasonable steps to complete the assessment within 30 calendar days after the day you became aware of the grounds that made you suspect an eligible data breach.

When must I notify the OAIC?

As soon as practicable once you have reasonable grounds to believe an eligible data breach has happened, unless an exception applies. You notify the OAIC with its Notifiable Data Breach form and tell the individuals at risk of serious harm.

What are the four steps in responding to a data breach?

The OAIC's quick reference guide lists contain the breach, assess it (including whether it is eligible), notify individuals and the OAIC if required, and review the incident to prevent future breaches.

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.