How do we…
How do we score maturity consistently when different people assess?
Add to board memoOpen the memo
The short answer
- Recommendation
- Give every assessor the same written evidence criteria and the same calibration cases, have every result state how it was evidenced, and have the lead decide a few practices again from the file before the draft results go out.
- Reasoning
- Two assessors looking at the same evidence should give the same level. That happens only when the evidence for each level is written down, every result says how it was evidenced and differences are caught before results are shown. The confidence caps the level: Told supports Informal at most, Seen up to Defined, and only Tested, a sample the assessor chose and checked, supports Managed (rule MA-13). A difference found now costs a conversation; one found by an auditor costs trust in every result.
- Considerations
- A level is still a judgement on evidence. The method narrows the room for it; it does not remove it.
- Yearly calibration, three practices decided again and five working days for owners to add evidence are the pack's defaults. Your own procedure may set others.
- A change to a practice's evidence criteria is a break in series for that practice in later comparisons.
- A result for a practice the assessor owns or runs is marked self-assessed and capped at Defined, whatever its confidence (rule MA-14).
The decision, step by step
Select any step for the reasoning behind it and where the pack covers it.
- Start
- Step
- Decision
- Outcome
- Loop back
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. 21 steps.
Start
Several people will rate practices in one assessment
Two assessors looking at the same evidence should give the same level. That only happens when the evidence for each level is written down, every result says how it was evidenced, and differences are caught before the results are shown. A level is still a judgement on evidence; the method narrows the room for it.
In the pack
- P19-A02 Security Maturity Model & Scoring MethodPurpose
- P19-A02 Security Maturity Model & Scoring MethodLimitations
- P19-A01 P19-A01
Step
Give every assessor the same written criteria
For each practice: the question, the evidence Defined needs, what Managed adds, and a judging note on common cases that fall short. Not in place and Informal mean the same for every practice. Approve the model before the first assessment. Changing a practice's criteria later is a break in series for that practice.
In the pack
- P19-A02 Security Maturity Model & Scoring MethodWhat the assessor must see for each level (rules MA-01, MA-03)
- P19-A02 Security Maturity Model & Scoring MethodCalibrating assessors (rule MA-15)
- P19-A05 Assessment Evidence Request ChecklistLevel Evidence
- P19-A05 Assessment Evidence Request ChecklistEvidence Requests
Decision
Has each assessor worked the calibration cases this year?
The pack's model carries calibration cases: short findings with the level each should get, such as an owner who describes a weekly log review in detail but shows no record of one. Each assessor works them before their first assessment and every year after. If you do not know whether someone has, treat them as not calibrated.
- Yes: Brief assessors; owners explain records, never suggest a level
- No, or not known: Have each assessor work the cases alone, then compare
In the pack
- P19-A02 Security Maturity Model & Scoring MethodCalibrating assessors
- P19-A02 Security Maturity Model & Scoring MethodCalibration cases
- P19-A03 Internal Security Assessment ProcedurePH-1 Plan
Step
Have each assessor work the cases alone, then compare
Compare each answer with the expected level and discuss every difference. A pattern of differences shows a practice or a level whose evidence needs clearer wording: change it in the model and note it in the calibration record, which an auditor may ask to see.
In the pack
- P19-A02 Security Maturity Model & Scoring MethodCalibrating assessors
- P19-A02 Security Maturity Model & Scoring MethodCalibration record
- P19-A02 Security Maturity Model & Scoring MethodEvidence to have ready
Step
Brief assessors; owners explain records, never suggest a level
Walk through the four levels and the criteria for each practice assigned. The security team or the practice owner may explain what a record is and where it is kept. They do not suggest a level. Agree how notes are written: what was found, what the next level needs, and the evidence seen.
In the pack
- P19-A03 Internal Security Assessment ProcedureBriefing an assessor who is not a security specialist
Step
Score every practice through the same steps, in order
Check the practice applies. Set aside records outside the evidence window. Choose the sample yourself. Start at Not in place and go up one level at a time, stopping at the first level whose evidence is missing. A practice that is measured but not written down is Informal, because the levels build on each other.
In the pack
- P19-A02 Security Maturity Model & Scoring MethodScoring a practice (rules MA-02, MA-03, MA-04, MA-05)
- P19-A04 Security Programme Maturity AssessmentInstructions
Decision
How was the result evidenced?
Every result states its confidence, and the confidence caps the level. Told: described in an interview, with nothing shown. Seen: a document or record was shown, and it says what the practice needs. Tested: the assessor chose a sample of records and checked each one against the practice. Evidence promised but not shown is Told; the owner can add it at validation.
- Told: nothing shown: Cap the result at Informal
- Seen: a record shown: Cap the result at Defined
- Tested: own sample checked: Allow up to Managed, if Managed's evidence is there
In the pack
- P19-A02 Security Maturity Model & Scoring MethodHow a result was evidenced (rule MA-13)
- P19-A03 Internal Security Assessment ProcedureRunning the fieldwork well
- P19-A05 Assessment Evidence Request ChecklistHow to Judge (rule MA-13)
Step
Cap the result at Informal
An interview alone supports Informal at most, however detailed and convincing it is. The description is still useful: it tells the assessor what records to ask for.
In the pack
- P19-A02 Security Maturity Model & Scoring MethodHow a result was evidenced (rules MA-02, MA-13)
- P19-A02 Security Maturity Model & Scoring MethodCalibration cases
Step
Cap the result at Defined
Defined needs at least Seen, and Seen is enough for Defined when the record shown is the practice's Defined evidence. Where the assessor also checks a sample, every sampled record must pass. Seen is not enough for Managed, even if the documents describe measures, independent checks and improvements: in the pack's calibration case, a risk register read but not sampled is Defined.
In the pack
- P19-A02 Security Maturity Model & Scoring MethodWhat the assessor must see for each level (rule MA-05)
- P19-A02 Security Maturity Model & Scoring MethodHow a result was evidenced (rule MA-13)
- P19-A02 Security Maturity Model & Scoring MethodCalibration cases (rule MA-13)
Step
Allow up to Managed, if Managed's evidence is there
Tested supports any level, including Managed, but only the level the evidence shows. A sampled record that fails means the level is not met, unless the practice itself caught, corrected and recorded the failure. Managed also needs at least 6 months at Defined, with records.
In the pack
- P19-A02 Security Maturity Model & Scoring MethodHow a result was evidenced (rule MA-13)
- P19-A02 Security Maturity Model & Scoring MethodSampling (rule MA-05)
- P19-A02 Security Maturity Model & Scoring MethodOne level at a time (rule MA-12)
Decision
Does the assessor own or run this practice?
A practice is your own work if you own it, do it, manage the people who do it day to day, or wrote the procedure it follows. If that is unclear, treat the result as self-assessed.
- Yes, or not sure: Mark it self-assessed and cap it at Defined
- No: Write a note another assessor could re-derive
In the pack
- P19-A03 Internal Security Assessment ProcedureWho may assess what (rule MA-14)
- P08-A08 ISMS Internal Audit Programme & ProcedureIndependence (rule IS-07)
Step
Mark it self-assessed and cap it at Defined
Whatever the confidence, a self-assessed result cannot be above Defined until someone independent checks the evidence, because Managed needs a check by someone other than the person who does the work. The report counts self-assessed results.
In the pack
- P19-A02 Security Maturity Model & Scoring MethodIndependence (rule MA-14)
- P19-A03 Internal Security Assessment ProcedureWho may assess what (rule MA-14)
Step
Write a note another assessor could re-derive
Record what was seen, the reference of each sampled record and what it showed, the confidence, and what the next level needs. A note written this way is the finding if the practice is below target, and it lets someone else decide the level again from the file.
In the pack
- P19-A02 Security Maturity Model & Scoring MethodScoring a practice
- P19-A03 Internal Security Assessment ProcedurePH-4 Fieldwork
- P19-A03 Internal Security Assessment ProcedureRunning the fieldwork well
Step
Lead decides a few practices again from the file
On the last day of fieldwork the assessment lead decides practices again from the evidence on file, by the pack's default 3, including one from each assessor, and compares the result with the assessor's.
In the pack
- P19-A03 Internal Security Assessment ProcedurePH-4 Fieldwork
Decision
Does the lead's level differ from the assessor's?
Settle every difference before the draft results are shown to practice owners. A difference found now costs a conversation; one found by an auditor costs trust in every result.
- No: Show owners the draft; they may add evidence, not argue
- Yes: Did they read the same evidence differently?
In the pack
- P19-A03 Internal Security Assessment ProcedurePH-4 Fieldwork
Decision
Did they read the same evidence differently?
Two causes look alike. One assessor may have had a record the other did not see; then share it and decide again. Or both read the same record and disagreed on what it shows; then the wording of the criteria is the problem.
- No: different evidence: Share the missing evidence and decide again
- Yes: same evidence: Settle it on the criteria, and fix unclear wording
In the pack
- P19-A03 Internal Security Assessment ProcedurePH-4 Fieldwork
- P19-A02 Security Maturity Model & Scoring MethodCalibrating assessors
Step
Settle it on the criteria, and fix unclear wording
The lead decides on the criteria in the model. Where the wording allowed both readings, change it in the model and record the change in the calibration record; changes to the model are approved by the assessment sponsor. A change to a practice's evidence criteria is a break in series for that practice in later comparisons.
In the pack
- P19-A02 Security Maturity Model & Scoring MethodCalibrating assessors (rule MA-15)
- P19-A02 Security Maturity Model & Scoring MethodReview (rule MA-15)
- P19-A03 Internal Security Assessment ProcedurePH-5 Validate
Step
Show owners the draft; they may add evidence, not argue
Each practice owner sees the draft results and may add evidence within 5 working days by the pack's default. A record counts only if it is dated in the evidence window. The owner may not argue a level up without evidence. The lead decides, and records any disagreement and the reason.
In the pack
- P19-A03 Internal Security Assessment ProcedurePH-5 Validate (rule MA-16)
- P19-A02 Security Maturity Model & Scoring MethodThe evidence window (rule MA-04)
Decision
Did the owner add evidence dated in the window?
New evidence goes through the same steps and the same confidence caps as the rest. A document written after fieldwork does not raise this assessment's level; it counts for the next one.
- Yes: re-rate it: Score every practice through the same steps, in order (back to an earlier step)
- No: Results another assessor could reproduce
In the pack
- P19-A03 Internal Security Assessment ProcedurePH-5 Validate (rules MA-04, MA-16)
- P19-A02 Security Maturity Model & Scoring MethodThe evidence window (rule MA-04)
Outcome
Results another assessor could reproduce
After each assessment, have an assessor who did not rate the practices take results from the report, by the pack's default 3, including one above the default target and one self-assessed, and decide them again from the file. They should match, and each domain should be the lowest of its practices. Running this test yourself means the first time is not in front of an auditor.
In the pack
- P19-A02 Security Maturity Model & Scoring MethodThe re-derivation test (rule MA-06)
- P19-A07 Maturity Assessment Report TemplateBefore you send it (rules MA-13, MA-14)
Practical checklist
- Approve one written model with the evidence each level needs for every practice.
- Have each assessor work the calibration cases alone before their first assessment and every year after, then discuss every difference.
- Brief assessors, and let owners explain where records are kept without suggesting a level.
- Score every practice through the same steps, stating Told, Seen or Tested.
- Write each note so another assessor could decide the level again from the file.
- Have the lead decide practices again from the file, one from each assessor, and settle every difference on the criteria.
- Fix wording that allowed two readings, and record the change in the calibration record.
- Show owners the draft and accept only added evidence dated in the window.
Evidence to have ready
- The approved model and the calibration record, with each assessor's cases and any wording changed.
- For each result: the confidence, the sampled records' references and what each showed.
- The lead's re-decided practices, the differences found and how each was settled.
- The result of a re-derivation test by an assessor who did not rate the practices.
Assumptions
- All assessors work from one written model that says what evidence each level needs for each practice, approved before the first assessment.
- An assessment lead who runs none of the practices assessed decides each result and has the standing to overrule a manager.
- The numbers shown, such as the yearly calibration, three practices re-decided and five working days for owners to add evidence, are the pack's defaults. Your own procedure may set different ones.
Not covered here
- Who should assess when the team is too small to be independent. That is “Who should assess our security practices when the team is too small to be independent?”.
- How to judge whether one piece of evidence proves the level claimed. That is “How do we tell whether evidence actually proves the level someone claims?”.
- What to do when a level falls since the last assessment, or the model has changed. That is “If a re-assessment shows a lower level than last time, then what do we do?”.
Related questions
- How do we score risks consistently when two people assess them?
- How do we tell whether evidence actually proves the level someone claims?
- Who should assess our security practices when the team is too small to be independent?
- How do we tell whether our security programme is mature, and which gaps matter?