India version. Adds the CERT-In directions of 28 April 2022 under section 70B(6) of the IT Act: 6-hour incident reporting, 180 days of ICT logs and NIC or NPL time sync. US version
Security Threat Checklist (India)
Build a threat checklist with the CERT-In directions built in: report listed incidents within 6 hours, keep 180 days of logs, sync clocks to NIC or NPL.
The interactive tool loads here when JavaScript runs.
About this toolWhat is Security Threat Checklist?
In India a security checklist has a reporting deadline attached. The CERT-In directions issued on 28 April 2022 under section 70B(6) of the Information Technology Act, 2000 require service providers, intermediaries, data centres, body corporate and Government organisations to report the cyber incidents listed in Annexure I to CERT-In within 6 hours of noticing them or being told about them. The list has 20 incident types, from targeted scanning and phishing to data breaches, data leaks, attacks on digital payment systems and fake mobile apps.
Most of those types match entries in this library, so this version uses the checklist as the bridge between prevention and reporting. When you add a threat, note which Annexure I item it would trigger and who sends the report. Reports go to incident@cert-in.org.in, phone 1800-11-4949 or fax 1800-11-6969, and each organisation must designate a Point of Contact to deal with CERT-In, using the format in Annexure II.
Two other directions change how the detection items in each entry work. Logs of all ICT systems must be enabled and kept securely for a rolling 180 days within Indian jurisdiction, and handed to CERT-In with an incident report or on request. CERT-In's FAQ on the directions (Q35) says the logs may also be stored outside India, provided they can be produced to CERT-In within a reasonable time. And every ICT system clock must be synchronised to the NTP servers of the National Informatics Centre (NIC) or the National Physical Laboratory (NPL), or to servers traceable to them, so that timestamps across systems can be lined up during an investigation.
- 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 UPI-linked payments app
Input
Add Phishing & Deceptive Content, Mobile Application Vulnerabilities, API Security Vulnerabilities and Broken Authentication
Output
A Markdown file with four sections, Broken Authentication rated Critical, each with tick boxes for attack methods, prevention and detection
Next to each section, write the Annexure I items it could trigger: identity theft, spoofing and phishing (vii), attacks affecting digital payment systems (xiv), attacks through malicious mobile apps (xv) and fake mobile apps (xvi). A cloned app in a store impersonating yours is reportable even if your own systems were never touched.
A SaaS product hosted in the cloud
Input
Add Cloud Misconfiguration, Denial of Service (DoS/DDoS), Supply Chain Attack and Insider Threat
Output
Four sections, Supply Chain Attack rated Critical, with detection items such as "Access log analysis" and "Data access monitoring"
These map to Annexure I items for cloud systems (xviii), DoS and DDoS (viii), unauthorised access (iii), data breach (xi) and data leak (xii). The detection items only work if the logs exist: check that each system keeps 180 days of logs you can hand to CERT-In before you tick "Access log analysis".
Turning the checklist into a 6-hour runbook
Input
Rename the checklist "CERT-In incident runbook" and add Malware & Virus Attacks
Output
cert_in_incident_runbook.md with the Malware & Virus Attacks section, which includes "Incident response tools" and "Forensic analysis" under detection
Add three lines under the file heading by hand: the Point of Contact, the reporting channels, and the rule that the 6 hours start when the incident is noticed or brought to notice, not when the investigation ends.
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
- Point every server, firewall and cloud log source at NIC or NPL time (or a source traceable to them). Entities spread across countries may use another accurate source, as long as it does not deviate from NPL and NIC.
- Check log retention per system: 180 days is a rolling minimum. The directions say within Indian jurisdiction, and CERT-In's FAQ allows storage abroad if you can produce the logs in reasonable time.
- If you run data centres, VPS, cloud or VPN services, the directions add subscriber records (validated names, IPs allotted, purpose of hire and more) kept for 5 years or longer.
- Keep the reporting channels and your Point of Contact in the exported Markdown so the runbook works when the usual tools are down.
Sources and further reading
- Directions under section 70B(6) of the IT Act, 2000 (28 April 2022), CERT-In, Ministry of Electronics and Information Technology. The 6-hour rule, Annexure I incident types, 180-day logs, NTP synchronisation and reporting channels.
- CERT-In directions relating to information security practices, CERT-In
- FAQs on the cyber security directions of 28 April 2022 (May 2022), CERT-In. Q35: logs may be stored outside India if they can be produced to CERT-In in a reasonable time.
- OWASP Top 10, OWASP Foundation
Frequently asked questions
What is the CERT-In 6-hour reporting rule?
Under the directions of 28 April 2022, service providers, intermediaries, data centres, body corporate and Government organisations must report the incident types in Annexure I to CERT-In within 6 hours of noticing them or being brought to notice about them.
Which incidents must be reported to CERT-In?
Annexure I lists 20 types, including targeted scanning of critical systems, unauthorised access, website defacement, malicious code such as ransomware, phishing and identity theft, DoS and DDoS attacks, data breaches and data leaks, attacks on digital payment systems, malicious or fake mobile apps, and attacks on cloud, IoT and AI systems.
How long must logs be kept under the CERT-In directions?
For a rolling period of 180 days, kept securely and provided to CERT-In with an incident report or when CERT-In directs. The directions say within Indian jurisdiction, and CERT-In's FAQ (Q35) allows storage abroad if you can produce the logs in reasonable time.
Which time server should we use for CERT-In compliance?
The NTP server of the National Informatics Centre (NIC) or the National Physical Laboratory (NPL), or NTP servers traceable to them. Organisations spread across geographies may use another accurate standard source if it does not deviate from NPL and NIC.
How do I report an incident to CERT-In?
By email to incident@cert-in.org.in, phone 1800-11-4949 or fax 1800-11-6969. CERT-In publishes reporting methods and formats on its website and may update them.
Do the directions apply to startups and small companies?
The directions name body corporate without a size threshold, so a registered company falls within the wording. Failing to furnish information or comply may invite action under section 70B(7) of the IT Act. Take legal advice if you are unsure how they apply to your setup.
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.