Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

Tools · Smaller checks

What should I check this week?

For a security leader who has inherited a programme. Enter your first day in the role to see where you are in the first 90 days and what that phase is for. Below are the 20 things to find out, with what counts as proof. Free, no account, and nothing is stored.

Your first day in the role. It is day 1, and week 1 runs for seven days from it.
Today, unless you are planning ahead.

Where you are in the first 90 days

Enter your first day in the role, and the day, week and phase appear here, with what the phase is for.

Record your findings in the workbook, not here. This page has no place for what you find and keeps nothing you enter. The Inherited Security Programme Discovery Workbookholds each finding with what you saw and when.

The four phases

PhaseWeeksWhat it is for
Listen1 to 3Meet people, read what exists, and promise nothing. Learn who expects what.
Verify4 to 7Check what you were told against a record, a test or a system. End with the first executive briefing.
Decide8 to 10Choose the few priorities the findings support, agree the decision rights, and settle the plan.
Propose11 to 13Take the plan, the reporting rhythm and the asks to the executives and the management body.

What to find out, by area

10 areas, two items each. Ask for one kind of proof for each item. A statement is never proof. A Record is a document or a file you read. A Test is something you do or check yourself, on a sample. A System view is what the system shows you, on screen, with its dates.

DS-01 Governance

  1. DS-01-1 Who is accountable for security, and what authority do they hold in writing?
  2. DS-01-2 Has the management body approved the cybersecurity risk-management measures, and is there a minute?
Record
The role description, the appointment letter and the minute of the approval.
Test
Ask two members of the management body to say what they approved.
System view
The board portal or minute book, with the dates.

Read first: P12-A05 Management Body Cybersecurity Accountability Record

DS-02 Risk

  1. DS-02-1 Is there a risk register, with an owner and a review date for each risk?
  2. DS-02-2 Is residual risk compared with a stated appetite, and who decides on acceptance?
Record
The register, the appetite statement and the acceptance forms.
Test
Trace two risks from the register to a treatment action and its status.
System view
The register tool, with its edit history.

Read first: P05-A05 Information Security Risk Register

DS-03 Policy

  1. DS-03-1 Is there a register of policies, with owner, approval date and review date?
  2. DS-03-2 Do staff acknowledge the policies that apply to them?
Record
The policy register and the signed-off documents.
Test
Pick three policies and find the approval of each.
System view
The acknowledgement tool, with completion dates.

Read first: P04-A06 Policy Register & Review Schedule

DS-04 Access

  1. DS-04-1 Are leavers' accounts removed within the removal window?
  2. DS-04-2 Are privileged accounts listed, owned and reviewed?
Record
The last access review campaign file.
Test
Compare an extract of active accounts with the HR leaver list.
System view
The identity system's account and privilege lists.

Read first: P07-A04 Access Review Scope & System Inventory

DS-05 Vulnerabilities

  1. DS-05-1 Are systems scanned, and are findings fixed by a set deadline?
  2. DS-05-2 Who owns patching for each system, and is there a maintenance window?
Record
The scan reports and the remediation tracker.
Test
Pick five open findings and check each against the deadline.
System view
The scanner console, with its coverage and last run date.

Read first: P01-A06 Vulnerability Remediation Tracker

DS-06 Incidents

  1. DS-06-1 Is there an incident plan with named roles, and was it exercised in the last 12 months?
  2. DS-06-2 Is every closed incident followed by a review with actions?
Record
The plan, the exercise report and the post-incident reviews.
Test
Follow the latest incident from report to review.
System view
The incident log or ticket queue.

Read first: P09-A09 Incident Case & Action Log

DS-07 Suppliers

  1. DS-07-1 Is there a register of suppliers, with a tier for each?
  2. DS-07-2 Have the critical suppliers been assessed within their interval?
Record
The supplier register and the assessment reports.
Test
Pick two critical suppliers and find the contract clauses and the last assessment.
System view
The procurement or contract system.

Read first: P06-A08 Supplier Security Risk Register

DS-08 Resilience

  1. DS-08-1 Are backups taken for the critical systems, and are restores tested?
  2. DS-08-2 Are recovery objectives set for the critical services?
Record
The restore test reports and the recovery objectives.
Test
Ask for a restore of one file or one system, and watch it.
System view
The backup console, with job results.

Read first: P23-A08 Restore Test Evidence Report Template

DS-09 Awareness

  1. DS-09-1 Do all staff complete the baseline security course in its interval?
  2. DS-09-2 Has the management body followed training in the last 12 months?
Record
The completion register and the training attendance.
Test
Pick five staff and find each completion.
System view
The learning platform's completion report.

Read first: P16-A07 Training Completion & Evidence Register

DS-10 Assurance

  1. DS-10-1 Are controls tested by someone other than their owner, with a plan?
  2. DS-10-2 Are audit findings tracked to closure?
Record
The test plan, the workpapers and the audit findings tracker.
Test
Pick two audit findings and check each closure.
System view
The findings tracker, with dates.

Read first: P20-A09 Annual Control Testing Plan

The four finding words

A finding is one of these, with what was seen.

Evidenced
A record, a test result or a system view that you saw matches what you were told or what the document says.
Described only
You were told, or a document claims it, and you have seen nothing that shows it is done.
Not found
You asked for it, by a date, and nothing was produced and nothing could be found.
Contradicted
What you saw differs from what you were told or what the document says.

How this works, and what it is not

Your start date is day 1, and week 1 runs for seven days from it. Weeks run from 1 to13; a day before the start, or after week 13, has no phase. Discovery ends at the close of week 7. This is the workbook's own arithmetic.

Rules the workbook applies

  • TR-01. Change no policy, tool, team structure or priority until discovery ends at the close of week 7, except to stop harm, to act on a legal duty or to take a no-regret action. Spend the first three weeks listening.
  • TR-02. Every discovery finding states what was seen: a record, a test result or a system view. A statement alone is Described only. A finding is checked again after 6 months, or on a material change.
  • TR-14. Every item in the 100-day plan traces to a finding, an interview record, a handover gap or an inherited exception. The plan lists what was dropped and why. A promise outside the organisation follows the plan, and never leads it.

What it is not

  • Not a record. It keeps no finding, no note and no date. The workbook counts your findings by word and by area, and shows which are due for a second look.
  • Not a score. Findings are counted, never added up into a score or a share.
  • Not the whole list. The twenty items are a floor. Add your own for what the interviews raise.
Items and method from
Inherited Security Programme Discovery Workbook, version 1.0
Runs
In your browser. Nothing is sent or stored