Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

When do we…

When can we close an improvement action, and when do we re-assess?

5 decision pointsThe pack behind this answer: Security Maturity & Internal Assessment

Add to board memo

The short answer

Recommendation
Close an action only when someone other than its owner re-assesses the practice and finds it at the level the action aimed for. Re-assess the touched domains after a significant incident, major change or new obligation, and run a full assessment at least every 12 months.
Reasoning
Closing is about the level, not the work (rule MA-18). A new procedure with no records of it being used is not yet Defined, so the practice must run and leave records first. When the owner says the work is done, the action is Ready for re-assessment, not Closed. Closing your own action is auditing your own work. A re-assessment uses the same criteria, confidence rules and independence as the assessment, on records made since the action started.
Considerations
  • Twelve months, six months at Defined before Managed, twenty working days to re-assess and a sample of three are the pack's defaults. Your own method may set others.
  • Where no one independent can re-assess, the action stays at Ready for re-assessment. Raise it with the sponsor.
  • A closed action means a level reached on re-assessment. It is not an audit finding closed and not evidence of compliance.
  • A second Not achieved goes to the approver: the board or a board risk committee it has delegated to, the management board in a two-tier structure, or executive management where there is no board.

The decision, step by step

Select any step for the reasoning behind it and where the pack covers it.

  • Start
  • Step
  • Decision
  • Outcome

Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.

Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one.

Read as text

The same flow written out: each step, its reasoning and where the pack covers it. 16 steps.
  1. Start

    An action may be done, or something may call for a re-assessment

    An action passes through five states: Open, In progress, Ready for re-assessment, then Closed or Not achieved. Closing is about the level, not the work. A re-assessment is also due on a fixed cycle and after certain events, whatever the actions say.

    In the pack

  2. Decision

    What has happened?

    Three things start a re-assessment: an owner says an action's work is done; an event touches a domain; or the cycle since the last full assessment is running out.

    In the pack

  3. Outcome

    Re-assess the domains it touches now, not at the cycle

    A significant incident that a practice should have prevented or limited, a major change such as a merger, a new platform or moving IT to a provider, or a new obligation such as a new law in scope or a customer contract. Re-assess the domains it touches. For a new obligation, review the domain's target too.

    In the pack

  4. Outcome

    Run a full assessment within twelve months of the last

    In the pack's default, the next full assessment's fieldwork ends within twelve months of the last one's, and it is planned when the approver approves this one's plan. If it will slip, tell the sponsor. Its results replace the levels now, and the next plan starts from them.

    In the pack

  5. Step

    Owner marks it Ready for re-assessment, with the evidence

    Ready means the owner says the work is done and the evidence is ready. It is not closed: the level has not been checked yet. The owner names a re-assessor with the assessment lead.

    In the pack

  6. Decision

    Can someone other than the owner re-assess it?

    The re-assessor must not own the action or run the practice: closing your own action is auditing your own work. Try a colleague from another function, a swap between people or teams, a reciprocal assessor from a peer organisation, then a contracted assessor. If no one is lined up, take the cautious branch.

    In the pack

  7. Outcome

    Do not close it: it stays Ready until someone independent checks

    An owner's own check is self-assessed and capped at Defined. The action stays at Ready for re-assessment until someone independent checks it. Raise it with the sponsor if no one can be found.

    In the pack

  8. Decision

    Does it aim for Managed within six months of reaching Defined?

    Managed can be claimed only after the practice has run at Defined, with records, for at least six months in the pack's default. If you do not know when it reached Defined, take the cautious branch.

    In the pack

  9. Outcome

    Too early: re-assess once the six months have run

    Managed cannot be claimed before the practice has run at Defined, with records, for the six months, so a re-assessment now cannot close the action. Setting it for the earliest date Managed can be claimed is a sensible default. Keep the practice running and leaving records until then.

    In the pack

  10. Step

    Re-assess on records made since the action started

    Use the same criteria, confidence rules and independence as the assessment. The re-assessor chooses a sample, three or all if fewer in the pack's default, from records dated since the action started, enough to show the practice is routine and not done once for the check. Defined needs at least Seen; Managed needs Tested. The pack's default is to do it within twenty working days of Ready.

    In the pack

  11. Decision

    Is the practice at the level aimed for, or higher?

    Judge the level, not the effort. A new procedure with no records of it being used is not yet Defined. If the evidence leaves it in doubt, take the cautious branch.

    In the pack

  12. Outcome

    Close it, recording who re-assessed it, when and the level found

    The practice's level now follows the re-assessment, and the domain's level is the lowest of its practices. A closed action means a level reached on re-assessment. It is not an audit finding closed, and not evidence of compliance.

    In the pack

  13. Step

    Set it to Not achieved and agree what is missing

    Record the level found; the practice's level follows the re-assessment. Agree what is missing and a new due date, or record the approver's decision to stop.

    In the pack

  14. Decision

    Is this its second Not achieved?

    One miss can be timing: a practice that has only just changed may not yet have left enough records. The pack takes an action that reaches Not achieved twice to the approver, above the security function.

    In the pack

  15. Outcome

    Take it to the approver to decide

    The approver is the one your governance sets: the board, or a board risk committee it has delegated to; the management board in a two-tier structure; executive management where there is no board. Ask for a decision: more effort, a new date, or stopping the action.

    In the pack

  16. Outcome

    Re-plan, and re-assess when the owner marks it Ready again

    Set the new due date in your tracker and report it in the next quarterly progress report. A priority action past its due date is named to the sponsor.

    In the pack

Practical checklist

  1. Have the owner mark the action Ready for re-assessment, with its evidence, and name a re-assessor with the assessment lead.
  2. Check that the re-assessor neither owns the action nor runs the practice.
  3. Wait until the practice has run at Defined for the six months before re-assessing for Managed.
  4. Re-assess on a sample the re-assessor chooses from records made since the action started.
  5. Close the action if the level aimed for is reached, recording who re-assessed it, when and the level found.
  6. Otherwise set it to Not achieved, and agree what is missing and a new due date.
  7. Re-assess the touched domains after an incident, major change or new obligation, and plan the next full assessment within 12 months.

Evidence to have ready

  • For each closed action: the re-assessor, the date, the sampled records and the level found.
  • For each action Not achieved: the level found, what is missing, the new due date or the approver's decision to stop.
  • The quarterly progress report to the sponsor, naming any priority action past its due date.
  • The plan for the next full assessment, with fieldwork ending within 12 months of the last.

Assumptions

  • Each action moves one practice up one level, with an owner, a due date and the evidence that will show it is done, kept in your own tracker.
  • Someone who does not own the action or run the practice can be found to re-assess it: a colleague from another function, a swap between teams, a reciprocal or a contracted assessor.
  • Twelve months, six months, twenty working days and a sample of three are the pack's defaults. Your own method may set others.

Not covered here