Skip to content
Security leadership

CISO Cheat Sheet: Best Practices on One Page

This is a one-page reference for security leaders: what to do in your first 90 days, the metrics boards ask about, the main frameworks side by side, the first hour of an incident and how to think about budget.

Each section links to a lab where you can practise it. Part of the CISO Resource Bundle. General guidance, not legal advice.

Updated 22 November 2026

Your first 30, 60 and 90 days

Days 1 to 30: listen and map

  • Meet every executive and ask what worries them, what they need from security and what they think security gets wrong.
  • Learn how the business makes money and which systems and data it cannot run without.
  • Read the last incidents, audit reports, penetration tests and the risk register.
  • Find out who owns what: identity, cloud, endpoints, backups, suppliers.
  • Check the basics quietly: who has admin rights, whether backups restore, whether sign-in uses multi-factor.

Days 31 to 60: find the top risks

  • Write the five to seven risks that could hurt the business most, in business terms.
  • Agree a risk appetite with the executive team, or start the conversation if there is none.
  • Fix anything urgent you found, and tell people you fixed it.
  • Assess the programme against a framework so you have a baseline.

Days 61 to 90: set the plan

  • Present a plan with priorities, owners, dates and the budget it needs.
  • Agree the metrics you will report and the cadence to the board.
  • Settle your mandate in writing: reporting line, board access, budget authority, the right to escalate.

Practise this: The Mandate · NIST CSF 2.0 self-assessment · CISO handbook

The 10 metrics boards ask about

Show each as a trend over several periods against a target the board agreed. Lead with anything outside appetite.

  1. Posture against risk appetite: how many top risks sit above tolerance.
  2. Top risks and their direction since last quarter.
  3. Notable incidents and near misses, with severity, not a raw count.
  4. Mean time to detect and to respond.
  5. Critical or internet-facing vulnerabilities open past their fix deadline.
  6. Coverage of critical assets by endpoint detection and logging.
  7. Phishing-resistant multi-factor sign-in coverage, especially for admins.
  8. Recovery readiness: critical systems with a tested restore inside the target time.
  9. Critical suppliers assessed and within tolerance.
  10. Open audit and regulatory findings, with due dates.

Leave out blocked emails, total alerts and number of tools. They rise with threat volume and map to no decision. The board metrics template sets targets and owners for each.

Practise this: Board Metrics Selection Lab · CISO Board Deck Template

Frameworks at a glance

FrameworkWhat it isUse it to
NIST CSF 2.0A voluntary framework from NIST, published February 2024, with six functions: Govern, Identify, Protect, Detect, Respond, Recover.Structure the programme and report on it in a language executives follow.
ISO/IEC 27001:2022An international standard for an information security management system, with Annex A controls grouped into organisational, people, physical and technological themes. Certifiable by an accredited body.Run security as a managed system and prove it with a certificate.
CIS ControlsA prioritised set of technical safeguards from the Center for Internet Security, split into Implementation Groups by organisation size and resources.Decide which technical work to do first.
SOC 2An independent auditor's report under the AICPA Trust Services Criteria (security, availability, processing integrity, confidentiality, privacy). Type I covers a point in time; Type II covers a period.Show customers your controls are designed and working.

They overlap. A common pattern: CSF to structure the programme, CIS Controls to prioritise the work, ISO 27001 or SOC 2 to prove it to others.

Practise this: Security framework comparison · ISO 27001 readiness · SOC 2 readiness

Incident: the first hour

  1. Confirm it is real and name one incident lead.
  2. Open a separate channel (phone bridge, out-of-band chat) in case email or chat is compromised.
  3. Contain: isolate affected hosts or accounts, but do not wipe or rebuild. Keep evidence.
  4. Start a timeline: who saw what, when, and every action taken.
  5. Call the people your plan names: executive on call, legal, communications, your insurer's hotline if you have cover.
  6. Check which notification clocks may have started (regulators, customers, contracts, disclosure rules).
  7. Decide the next check-in time and who is on it.

Do not, in the first hour: pay a ransom, talk to the press, or let people fix things without logging what they did.

Practise this: IR Playbook Lab · Incident severity router · Cyber War Room

Budget rules of thumb

  • Our Security Budget Benchmark compiles public figures: Gartner research commonly puts security at roughly 5 to 15% of the IT budget, and Deloitte's “State of Cyber” survey gives a typical point of around 10% of IT spend and roughly 0.5% of revenue.
  • Use those as context for a conversation, not as a target. Regulation, risk and maturity decide the right figure.
  • Tie every line of spend to a top risk it reduces. Spend you cannot link to a risk is the first to be cut.
  • Count the people time to run a tool, not just the licence. Use a weighted scorecard and a proof of concept before you buy.
  • Show the board options, including doing nothing and its consequence.

Practise this: Security Budget Benchmark · Budget Siege · Security Tool Evaluation Framework

Frequently asked questions

What should a new CISO do in the first 90 days?

Listen and map in the first 30 days: meet executives, learn how the business makes money, find the crown jewels and read past incidents and audits. In days 31 to 60, find the top risks, agree the risk appetite and fix the urgent gaps. In days 61 to 90, present a plan and its budget to the executive team and the board, and set the metrics you will report on.

What metrics do boards ask a CISO about?

Usually: posture against risk appetite, the top risks and their trend, notable incidents, time to detect and respond, critical vulnerabilities past their fix deadline, control coverage on critical assets, third-party risk, phishing-resistant sign-in coverage, recovery readiness, and audit or regulatory findings. Show each as a trend against a target.

Which security framework should I use: NIST CSF, ISO 27001, CIS Controls or SOC 2?

They do different jobs. NIST CSF 2.0 organises a programme around six functions. ISO/IEC 27001 is a certifiable management-system standard. CIS Controls are a prioritised list of technical safeguards. SOC 2 is an independent auditor's report on controls, often asked for by customers. Many organisations use CSF to structure the programme, CIS Controls to prioritise the work, and ISO 27001 or SOC 2 to prove it to others.

What should happen in the first hour of a cyber incident?

Confirm it is real and name an incident lead, open a dedicated channel that does not rely on possibly compromised systems, contain without destroying evidence, start a timeline, tell the executive and legal contacts in your plan, and check which notification clocks may have started. Do not wipe machines, pay anyone or speak publicly in the first hour.

How much should a company spend on cybersecurity?

There is no single right figure. Our Security Budget Benchmark page compiles public figures: Gartner research commonly puts security at roughly 5 to 15% of the IT budget, and Deloitte's survey gives a typical point of around 10% of IT spend and roughly 0.5% of revenue. Treat these as context, not targets: your risk and regulation decide the right number.

Sources

Take this with you
The full guide · FAQ answers · Sources