Singapore Cyber Trust mark
Pick a risk-appropriate mark level and prepare evidence for a certifier.
Cybersecurity directions under section 70B of the Information Technology Act
Set up the six-hour cyber incident workflow, logging, time synchronization and point of contact.
Entities covered by the directions, including specified service providers, intermediaries, data centres, bodies corporate and government organizations.
An exercised incident route, accountable contacts and retrievable logs with consistent timestamps.
Send available information within the reporting window for a covered incident. Record what is unknown and how you will follow up.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
India CERT-In directions kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Map the entity and named contact · Local legal + response lead [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
A hosting provider sees suspicious administrative logins. It classifies them against the directions, records the exact detection and handoff times, submits the facts it has through the required route and later adds the confirmed scope.
Check separately for a qualifying personal data incident and the applicable DPDP commencement phase.
The trigger is noticing the incident or being brought to notice of it. Check the directions and FAQ.
Official reference (opens in a new tab)Confirm coverage, storage location and availability for the entity.
Official reference (opens in a new tab)Checklist, instructions and 10 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Map the entity and named contact | Local legal + response lead | Before a qualifying incident | Set a start date | Applicability matrix; Escalation contacts | Open |
| Verify time sources and accessible logs | Infrastructure + security operations | As systems enter scope and on changes | Set a start date | Monitoring plan; Log retention worksheet; Test reports | Open |
| Exercise the six-hour report | Incident lead + designated contact | On noticing a qualifying incident or being notified | Set a start date | Incident classification; Reporting templates; Notification record | Open |
| Review recurring and provider obligations | Compliance + service owners | At supplier changes and incident reviews | Set a start date | Vendor review; Corrective-action register | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Define entity role, reportable incident types and additional requirements for listed services. Maintain the required contact and alternate.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Record approved time synchronization, log sources and retention. Test retrieval and confirm applicable storage jurisdiction and access.
Fictional details. Use the same fields with evidence from your work.
A person who receives the plan can tell when to act, what to check and where to save the result.
Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.
Fictional details. Use the same fields with evidence from your work.
An on-call person can locate the right event quickly and explain both retention and timestamp consistency.
Send the reviewed record to incident operations and retention owners.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Classify the event, preserve detection time and collect details available for the initial report. Record the submission and send updates when confirmed.
Fictional details. Use the same fields with evidence from your work.
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.
Fictional details. Use the same fields with evidence from your work.
Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.
Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.
Fictional details. Use the same fields with evidence from your work.
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.
Confirm record administration and extra directions that apply to each service, then review misses and schedule corrective tests.
Fictional details. Use the same fields with evidence from your work.
Each provider and contract record links to an actual function and all required identifiers are present.
Use the verified register in supplier reviews and put required submissions in the authority’s prescribed format.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.