Singapore version. Adds the PDPA data breach notification rules (500 or more people, or likely significant harm; PDPC within 3 calendar days) and points to CSA's Cyber Essentials mark. US version

Security Threat Checklist (Singapore)

Build a threat checklist that ends in a PDPA breach plan: the 500-person and significant-harm triggers, the 3-day PDPC deadline and CSA Cyber Essentials.

The interactive tool loads here when JavaScript runs.

About this tool

What is Security Threat Checklist?

In Singapore a data breach turns into a deadline as soon as you decide it is notifiable. Under the Personal Data Protection Act, a breach must be notified to the PDPC if it is likely to result in significant harm to individuals or affects 500 or more individuals. Once the organisation determines that the breach is notifiable, it has no later than three calendar days to notify the PDPC, and the PDPC expects containment and assessment to start immediately after a potential breach is discovered.

This version uses the 22-threat library to prepare for that decision. Each entry you add has prevention and detection tick boxes; under each one, note which data the threat could expose and whether that data appears on the PDPC's significant-harm list (for example credit card details, financial information such as wages and bonuses, and specified medical information). A threat that only touches staff email addresses is a different notification problem from one that reaches card numbers.

For the prevention side, the Cyber Security Agency of Singapore runs the Cyber Essentials mark, a certification for organisations of all sizes. CSA describes its enhanced framework as going beyond traditional IT security to cover cloud security, operational technology security and AI security, so a checklist built here can serve as a working list before you engage an assessor.

  • 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

An e-commerce shop that stores payment details

Input

Add SQL Injection, Broken Authentication and Cryptographic Failures

Output

A Markdown file with three sections; SQL Injection and Broken Authentication rated Critical, Cryptographic Failures High

Credit card details are on the PDPC's significant-harm list, so an exploited injection flaw here is notifiable to the PDPC and to the customers affected, even if only a handful of records leak. Strong encryption counts: the PDPC lists a technological measure such as encryption in place before the breach among the exceptions to notifying individuals.

A cloud misconfiguration that exposes a customer list

Input

Add Cloud Misconfiguration and Insider Threat

Output

Two sections, both rated High, with "Regular configuration audits" and "Data access monitoring" among the tick boxes

If the exposed list covers 700 customers, the significant-scale trigger (500 or more individuals) makes it notifiable to the PDPC whatever data it holds. The PDPC's own example of this trigger is the exfiltration of 700 customers' personal data due to a hacking incident.

A scam message impersonating your firm

Input

Add Phishing & Deceptive Content and Social Engineering

Output

Two sections, rated High, both listing "Incident reporting systems" and awareness training

Add the advice CSA gives the public to your customer notice: check for the .gov.sg domain on government sites, be wary of callers asking for money transfers or bank log-in details, and call the ScamShield Helpline on 1799 if unsure.

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

  • If you process data for another organisation, you are a data intermediary: notify the data controller immediately on discovering the breach, and let the controller decide on PDPC notification.
  • Notify affected individuals only after, or at the same time as, the PDPC.
  • Prepare notification templates and train the response team on the three-day calculation in advance, as the PDPC suggests.
  • Use the PDPC's self-assessment tool when it is unclear whether a breach is notifiable, and keep the basis for your decision.

Sources and further reading

  1. Report your organisation's data breach, Personal Data Protection Commission. The two notification triggers, the three-day deadline, notifying individuals and the role of data intermediaries.
  2. Cyber Essentials, Cyber Security Agency of Singapore
  3. OWASP Top 10, OWASP Foundation

Frequently asked questions

When is a data breach notifiable under the PDPA?

When it meets at least one of two triggers: it is likely to result in significant harm to individuals, or it affects 500 or more individuals. If either applies, the PDPC must be notified.

How many days do I have to notify the PDPC?

No later than three calendar days after the organisation determines that the breach is notifiable. The clock starts at that determination, so the PDPC expects containment and assessment to begin immediately.

Do I need to tell the affected individuals as well?

Yes, when the breach is likely to cause significant harm to them, such as substantial financial loss, unless an exception applies. Notify them only after, or at the same time as, the PDPC.

What happens if we miss the three-day deadline?

The PDPC says the organisation may be in breach of the Data Breach Notification Obligation, and it may take enforcement action, including financial penalties and directions.

What is the CSA Cyber Essentials mark?

A cybersecurity certification from the Cyber Security Agency of Singapore designed for businesses of all sizes. Its enhanced framework covers cloud, operational technology and AI security alongside basic IT measures.

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.