India CERT-In directions
Set up the six-hour cyber incident workflow, logging, time synchronization and point of contact.
ASD Essential Eight Maturity Model
Assess the maturity of common cyber mitigations and improve them together.
Australian organizations using ASD’s baseline mitigation strategies, including entities with separate government or contractual expectations.
Evidence-backed maturity assessment and improvement roadmap.
Set target maturity using your threat profile and applicable policy. Avoid treating a strong result in one mitigation as covering weaknesses elsewhere.
Monitor progress against the target, failed control tests and gaps that leave a critical service exposed.
Fill this in with your sponsor and send it to the people who own the work.
Essential Eight 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 Determine scope and target maturity · Security lead + business owners [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. Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target. 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.
Checklist, instructions and 9 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Determine scope and target maturity | Security lead + business owners | Before evidence collection | Set a start date | Scope memo; Target and assessment plan | Open |
| Baseline the eight strategies | IT operations + assessor | At assessment | Set a start date | Control evidence; Assessed maturity results | Open |
| Remediate by exposure and feasibility | Engineering + system owners | Based on risk and policy | Set a start date | Prioritized backlog; Exception decisions; Rollout evidence | Open |
| Validate and report improvements | Assessor + leadership | At follow-up and policy cadence | Set a start date | Follow-up report; Maturity roadmap | 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 systems and operating environments, applicable policy and target maturity. Select assessment evidence and sampling approach.
Fictional details. Use the same fields with evidence from your work.
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
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.
Review application control, patching, macro restrictions, hardening, admin privileges, MFA and backups against applicable criteria.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Fictional details. Use the same fields with evidence from your work.
The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.
Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.
Prioritize critical gaps and dependencies. Test changes and retain evidence of rollout and exceptions.
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.
Fictional details. Use the same fields with evidence from your work.
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Retest implemented changes, document residual gaps and schedule repeat reviews when the environment changes.
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.
Fictional details. Use the same fields with evidence from your work.
The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.
Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.