Most security strategies fail in one of two ways. Either they start with tools — a SIEM, an EDR, a zero-trust product — and work backwards to a justification, or they are a list of good intentions with no order and no owner. A strategy a board can fund starts from what the business must not lose, ranks risks against that, fixes the most dangerous first, and reports progress in the board’s language.
1 · The Nine Steps
| # | Step | What it involves | Output |
|---|---|---|---|
| 1 | Understand business objectives | Align security goals with business goals; identify the crown-jewel services, data and assets | Critical-asset list, business impact analysis |
| 2 | Conduct a risk assessment | Threats and vulnerabilities against those assets; likelihood and impact; rank by business impact | Risk register, top-10 risks |
| 3 | Establish security policies | Acceptable use, data handling, access, sharing; aligned to laws (DPDP Act, GDPR); reviewed as threats change | Policy set, communicated and acknowledged |
| 4 | Implement access management | Role-based access, MFA (phishing-resistant for admins), least privilege, regular access reviews | IAM baseline, privileged-access controls |
| 5 | Deploy security tools | Firewalls, IDS/IPS, endpoint protection, SIEM; then EDR/XDR and zero-trust access — configured and monitored, not just bought | Tool stack mapped to risks |
| 6 | Manage vendors | Assess third-party security; contract clauses; review vendor access regularly | Vendor tiering, third-party risk register |
| 7 | Build an incident response plan | Steps to identify, contain and recover; roles; communication; regular drills | IR plan, playbooks, tabletop record |
| 8 | Train employees | Phishing and social engineering, safe data handling; simulations; a culture where reporting is rewarded | Training and simulation programme |
| 9 | Monitor and audit continuously | Real-time monitoring, vulnerability assessments, internal audits, compliance tracking, findings to leadership | Metrics, audit reports, improvement backlog |
▸ Step 5 is where budgets go and where strategies go wrong. Each tool should be traceable to a risk from step 2. A tool that answers no ranked risk is shelfware with a renewal date.
2 · The Steps as a 12-Month Roadmap
The nine steps are not done once, in order. They overlap. This is how they usually fall across a CISO’s first year:
| Horizon | Focus | Deliverables |
|---|---|---|
| Days 0–30 | Listen & stop the bleeding | Meet business owners (step 1); asset and access inventory; MFA on email, VPN and admin accounts; confirm backups restore; an IR contact list and CERT-In reporting path |
| Days 31–90 | Assess & decide | Risk assessment and top-10 risks (2); risk appetite agreed with leadership; policy gaps (3); vendor tiering (6); first tabletop exercise (7) |
| Months 4–6 | Fix the top risks | Privileged access and access reviews (4); EDR coverage and logging into a SIEM (5); phishing programme live (8) |
| Months 7–12 | Prove & mature | KPIs and KRIs reported monthly (9); internal audit against ISO 27001 or NIST CSF; second exercise; next year’s budget built from the risk register |
▸ In India, two obligations belong in the first 30 days, not the first year: report specified cyber incidents to CERT-In within 6 hours of noticing them, and keep ICT system logs for 180 days (CERT-In directions of April 2022).
3 · Seven Layers the Strategy Must Cover
Defence in depth, stated as seven layers. A strategy that funds only two or three of them leaves a gap an attacker will find.
| Layer | Core controls |
|---|---|
| Human | Awareness training, phishing drills, insider-risk controls, a simple way to report |
| Physical | Badge access, visitor control, camera coverage, secure storage, asset protection |
| Perimeter | Firewall policy, email filtering, DNS security, secure web gateway |
| Network | Segmentation, traffic visibility, encrypted traffic, network access control |
| Endpoint | EDR/XDR, patch discipline, device compliance, local-privilege control |
| Application | Secure SDLC, code scanning, API security, runtime protection |
| Data | Classification, DLP, key management, backup integrity |
For the full twelve-domain view, see 12 Pillars of Cyber Defense; for the network layers in detail, OSI Model, Attacked Layer by Layer.
4 · The Resilience Spine: Five Verbs
Layers describe where controls sit. Resilience describes the order in which they matter during an attack. Five verbs make a strategy easy to explain to people outside security:
| Verb | What it means | Key controls |
|---|---|---|
| Know the estate | Assets, services, suppliers and dependencies — including what faces the internet | Asset inventory, external attack-surface monitoring, critical-service dependency maps |
| Control access | Users, devices, workloads and AI agents get only what they need | Phishing-resistant MFA and passkeys, just-in-time privileged access, human and machine identity lifecycle |
| Build securely | Remove weaknesses before release, not after | Secure-by-default products, SBOM and dependency checks, secret scanning, cloud posture control |
| Contain fast | Detect, isolate and coordinate | Telemetry from endpoint, identity, SaaS and cloud; containment playbooks; remediation prioritised by the CISA KEV list and business criticality |
| Recover cleanly | Restore trusted services and learn | Isolated, immutable backups; tested restores, including after a destructive attack; post-incident reviews |
▸ The test of the last verb: has anyone restored a critical system from backup, end to end, in the last six months? A backup that has never been restored is a hope, not a control.
5 · What the Board Should See
Boards fund risk reduction, not activity. Translate the programme into a small number of answers:
| Board question | Evidence to show |
|---|---|
| Are we within our risk appetite? | Top risks vs appetite, trend since last quarter |
| How fast do we spot and stop attacks? | MTTD and MTTR — see Cybersecurity KPIs |
| Are the basics done? | MFA coverage, patching of known-exploited vulnerabilities, EDR coverage |
| Could we recover? | Last restore test, RTO met or missed, last IR exercise |
| Are we compliant? | Open audit findings, regulatory deadlines, third-party issues |
Bottom line
- Start from the business — crown jewels and risk appetite come before any tool.
- Every tool traces to a risk — if it answers no ranked risk, do not buy it.
- Sequence, do not list — 30 days to stop the bleeding, 90 to decide, a year to prove.
- Cover all seven layers, and make the five verbs the story you tell the business.
- Report answers, not activity — appetite, speed, basics, recovery, compliance.
Sources & method. The nine steps reflect common CISO strategy practice; the roadmap, layer mapping and board questions are the author’s analysis. India obligations from CERT-In directions under section 70B(6) of the IT Act, 2000 (28 April 2022). KEV refers to CISA’s Known Exploited Vulnerabilities catalog. Timelines are typical, not prescriptive. Original analysis; no third-party graphics or text reproduced.
← Back to Cyber security