Remediation & Action Management
Who is doing what, what is late or blocked, what has really been completed — and what evidence proves it. As at 31 Oct 2026 · compared with 30 Sept 2026
43 register actions in scope · separate from verification
- Identified0
- Assigned15
- In progress0
- Blocked5
- Awaiting verification11
- Verified2
- Closed10
- Cancelled / superseded0
Completed actions reaching each stage · each stage evaluated on its own evidence
- Reported complete23 / 23
- Completion evidence recorded19 / 23
- Independent verification available8 / 23
- Post-change evidence confirms effectiveness7 / 23
- Risk reduction demonstrated4 / 23
- Risk closed in register10 / 23
Actions in scope at each assessment — status as at that date
Master remediation register
The shared register actions — the same records the Material Risks, Exposure and Monitoring pages use. No action is created here.
Priority is derived from the material risk’s severity and the owner is the risk owner — neither is recorded per action. “Last update” is the latest dated event (identification, decision, completion, verifying export or closure). Nothing here can be edited.
Management attention & escalations
Owners and dates only where a record supports them · 16 items
None at this assessment.
None at this assessment.
Remediation priorities
Open actions ordered by factors, in sequence: risk severity → attack-path disruption (the Exposure choke-point score, reused) → business-critical assets protected → overdue → path evidence confidence → unblocked → effort → due date. No new score is created.
Path impact: Verified — disruption confirmed by post-change evidence; Expected — would interrupt an observed or assessor-inferred path if fully effective; Hypothetical — would interrupt a hypothetical scenario. Vulnerability or path counts alone never rank an action.
Verification & closure assurance
Completed actions against six independent checks · a completion date is never proof the exposure has gone
Effective = an accepted catalogue export collected strictly after the change that confirms the specific outcome (the shared standard used by Identity & Access and Exposure). An “Accepted with warnings” export is eligible only where its recorded warning does not undermine the specific outcome being confirmed. Acceptance is not, on its own, proof that the remediation is effective. Outcome confirmation is an assessor-recorded determination of what the export shows, made against synthetic demonstration data — not automated validation of the export contents. Risk closed = the register’s closure date; closure dates are preserved from the register. Formal closure approval evidence is not recorded and is never inferred from action completion.
- IAP-4 — Attack-path disruption verified (A-1112)
- CAP-1 — Attack-path disruption verified (A-1051)
- CAP-5 — No longer observed. Not credited to any action and not counted as verified remediation.
Closed risks at this assessment, qualified by whether the closing change has been technically verified. Closures are never reopened or re-dated.
- Closed — technical verification not established
Closed 18 Jul 2026 — preserved. A-1022: document only (Change record CHG-2291 — firmware upgrade (DEMO)).
Closure dates are preserved from the register. Formal closure approval evidence is not recorded and is never inferred from action completion. Closing change (completed on the closure date): A-1022. Verification uses the shared standard — an accepted export collected strictly after the change that confirms the outcome. Outcome confirmation is an assessor-recorded determination of what the export shows, made against synthetic demonstration data — not automated validation of the export contents.
- Closed — subsequently verified
Closed 12 Sept 2026. A-1053 verified by the DS-10 export of 26 Sept 2026.
Closure dates are preserved from the register. Formal closure approval evidence is not recorded and is never inferred from action completion. Closing change (completed on the closure date): A-1053. Verification uses the shared standard — an accepted export collected strictly after the change that confirms the outcome. Outcome confirmation is an assessor-recorded determination of what the export shows, made against synthetic demonstration data — not automated validation of the export contents.
- Closed — subsequently verified
Closed 20 Jun 2026. A-1081 verified by the DS-06 export of 20 Aug 2026.
Closure dates are preserved from the register. Formal closure approval evidence is not recorded and is never inferred from action completion. Closing change (completed on the closure date): A-1081. Verification uses the shared standard — an accepted export collected strictly after the change that confirms the outcome. Outcome confirmation is an assessor-recorded determination of what the export shows, made against synthetic demonstration data — not automated validation of the export contents.
- Closed — subsequently verified
Closed 22 Aug 2026. A-1112 verified by the DS-03 export of 22 Sept 2026.
Closure dates are preserved from the register. Formal closure approval evidence is not recorded and is never inferred from action completion. Closing change (completed on the closure date): A-1112. Verification uses the shared standard — an accepted export collected strictly after the change that confirms the outcome. Outcome confirmation is an assessor-recorded determination of what the export shows, made against synthetic demonstration data — not automated validation of the export contents.
- Closed — technical verification not established
Closed 9 Oct 2026 — preserved. A-1152: the only later DS-23 export (20 Oct 2026) is not accepted.
Closure dates are preserved from the register. Formal closure approval evidence is not recorded and is never inferred from action completion. Closing change (completed on the closure date): A-1152. Verification uses the shared standard — an accepted export collected strictly after the change that confirms the outcome. Outcome confirmation is an assessor-recorded determination of what the export shows, made against synthetic demonstration data — not automated validation of the export contents.
Risk reduction & outcomes
Five separate outcomes per material risk · each needs its own evidence · no Cyber Risk Index change is implied
“Risk reduced” needs a recorded mitigation that lowers the residual rating; completing actions alone never reduces a rating. Hover a mark for the evidence.
Risk reduction milestones
Dated events from shared history — asset measurements, progressions, verified path disruption and closures
- 7 MayExposure reducedRL-105EvidenceAnonymous access disabled on stmanifestsprod and stediarchive. Affected storage accounts permitting public blob access: 7 → 5.
- 26 MayPath disruption verifiedRL-105EvidenceCAP-1 attack-path disruption verified — A-1051 on 7 May 2026, first confirmed by the 26 May 2026 export.
- 20 JunMaterial risk closedRL-108AssessorRL-108 closed — Stale guest accounts in Entra ID.
- 18 JulMaterial risk closedRL-102AssessorRL-102 closed — Internet-facing VPN appliance with exploitable CVE.
- 29 JulExposure reducedRL-104Assessor18 head-office servers onboarded to Defender for Endpoint. Servers: 49 of 221 → 31 of 221 (Depot file servers 12, WMS application tier 9, Print servers 10).
- 12 AugExposure reducedRL-107EvidenceDomain controllers (4) connected via AMA — they were not connected before this date. In-scope log sources not connected to Microsoft Sentinel: not measured → 46 of 121 (Depot firewalls 18, Azure Linux VM syslog 25, SaaS audit 2, WMS audit 1).
- 22 AugMaterial risk closedRL-111AssessorRL-111 closed — Legacy authentication permitted by Conditional Access.
- 4 SeptExposure reducedRL-109PartialCUSTOMS-APP-01 and CUSTOMS-DB-01 enrolled in Azure Arc ESU. Servers: 17 of 221 → 17 of 221 (Covered by ESU 2, Without ESU 15).
- 12 SeptExposure reducedRL-105EvidenceDeny-public-access policy enforced on the remaining 5; RL-105 closed. Affected storage accounts permitting public blob access: 5 → 0.
- 12 SeptMaterial risk closedRL-105AssessorRL-105 closed — Azure storage accounts with public network access.
- 22 SeptPath disruption verifiedRL-111EvidenceIAP-4 attack-path disruption verified — A-1112 on 22 Aug 2026, first confirmed by the 22 Sept 2026 export.
- 9 OctMaterial risk closedRL-115AssessorRL-115 closed — Unrestricted USB removable media.
Attack-path integration
From the shared Exposure & Attack Paths graph — path statuses are not changed here
- Remediation recorded — verification pending
- None
- No longer observed — not remediation
- CAP-5
Choke points and candidate recommendations
Select actions for an illustrative what-if using the Exposure simulator — it never changes an action, risk or path record
- Enforce phishing-resistant authentication strength via Conditional AccessScore 3.1 · Hannah Lewis · due 2026-11-28
- Convert standing Owner roles to PIM-eligibleScore 3.1 · Marcus Bell · due 2026-11-30
- Review and revoke unjustified high-privilege grantsScore 1.6 · Marcus Bell · due 2026-12-18
- Migrate APP-WMS-01 to resource-based constrained delegationScore 0 · Daniel Okafor · due 2026-11-10
- Decommission APP-LEGACY-03 delegation and re-run path analysisScore 0 · Daniel Okafor · due 2026-11-15
- Migrate legacy file servers to Server 2025Score 0 · Daniel Okafor · due 2027-02-28
- CAND-MDC-03 Close SSH on AZ-LNX-16 and require BastionScore 1.8 · no due date · owner Marcus Bell (Exposure record)
- CAND-MDC-05 Remove the AllowAll firewall rule on sql-wms-reportingScore 1.8 · no due date · owner Marcus Bell (Exposure record)
- CAND-CA005 Extend compliant-device policy to the finance applicationScore 1.3 · no due date · owner not assigned
- CAND-CA011 Enforce CA011 admin sign-in frequencyScore 1.2 · no due date · owner not assigned
- CAND-EXP-2 Restrict privileged logons to legacy Server 2012 R2 hostsScore 1.2 · no due date · owner not assigned
- CAND-1009 Deploy the RD Gateway update or remove HQ-RDG-01's internet exposureScore 0 · no due date · owner not assigned
Dependencies & blockers
Only dependencies recorded in existing records · 7 actions have one; 36 show “No dependencies recorded”
- Enforce phishing-resistant authentication strength via Conditional AccessAssigned
- Prerequisite action: A-1013 not complete (due 14 Nov 2026). Source: Exposure & Attack Paths — action A-1014 preconditions.
- D-103-1Migrate APP-WMS-01 to resource-based constrained delegationBlocked
- Management approval: D-103-1 awaiting Priya Shah — needed by 7 Nov 2026. Source: Exposure & Attack Paths — action A-1033 preconditions; RL-103 decision D-103-1.
- D-106-1Execute and document full restore testBlocked
- Management approval: D-106-1 awaiting Priya Shah — needed by 5 Nov 2026. Source: RL-106 decision D-106-1.
- D-107-1Onboard depot firewall syslog (18 sources)Blocked
- Resource / budget approval: D-107-1 awaiting Priya Shah — needed by 20 Nov 2026. Source: RL-107 decision D-107-1.
- D-109-1Approve migration plan for remaining 15 serversBlocked
- Management approval: D-109-1 awaiting Priya Shah — needed by 25 Nov 2026. Source: RL-109 decision D-109-1.
- +D-109-1Migrate legacy file servers to Server 2025Blocked
- Prerequisite action: A-1092 not complete (due 25 Nov 2026). Source: Exposure & Attack Paths — action A-1093 preconditions.
- Management approval: D-109-1 awaiting Priya Shah — needed by 25 Nov 2026. Source: Exposure & Attack Paths — action A-1093 preconditions; RL-109 decision D-109-1.
- Review and revoke unjustified high-privilege grantsAssigned
- Prerequisite action: A-1161 not complete (due 12 Nov 2026). Source: Exposure & Attack Paths — action A-1162 preconditions.
- D-103-1RL-103Approve a WMS maintenance window for the delegation change (estimated 4 hours of downtime).Priya Shah · needed by 7 Nov 2026 · blocks A-1033
- D-106-1RL-106Approve a weekend window for the full restore test and confirm business sign-off for RTO targets.Priya Shah · needed by 5 Nov 2026 · blocks A-1063
- D-107-1RL-107Approve the increased Sentinel ingestion budget (approx. £38k a year) for depot firewall logs.Priya Shah · needed by 20 Nov 2026 · blocks A-1072 · resource constraint
- D-109-1RL-109Approve the migration plan and budget for the remaining 15 servers.Priya Shah · needed by 25 Nov 2026 · blocks A-1092, A-1093
Systems named in several actions’ titles — a coordination view, not recorded dependencies.
- Warehouse management system (WMS):
- Depot infrastructure:
- Conditional Access:
Materiality review queue (7)
Findings awaiting a materiality decision — not material risks, never converted automatically
Outstanding management decisions (6)
Recorded in the material-risk profiles
- D-106-1RL-106Approve a weekend window for the full restore test and confirm business sign-off for RTO targets.Priya Shah · needed by 5 Nov 2026 (5 days)
- D-103-1RL-103Approve a WMS maintenance window for the delegation change (estimated 4 hours of downtime).Priya Shah · needed by 7 Nov 2026 (7 days)
- D-107-1RL-107Approve the increased Sentinel ingestion budget (approx. £38k a year) for depot firewall logs.Priya Shah · needed by 20 Nov 2026 (20 days)
- D-109-1RL-109Approve the migration plan and budget for the remaining 15 servers.Priya Shah · needed by 25 Nov 2026 (25 days)
- D-110-1RL-110Decide whether MSP contracts must be amended to include right-to-audit and incident-notification clauses.Tom Whitfield · needed by 15 Dec 2026 (45 days)
- D-117-1RL-117Renew or revoke the risk acceptance when it expires on 31 Dec 2026.Priya Shah · needed by 31 Dec 2026 (61 days)
Historical remediation performance — May to October 2026
Each month uses the register as at that assessment date; October status is never applied retrospectively
- Start-of-work dates are not recorded per action, so “In progress” is never inferred; open actions show as Assigned.
- Decision raised dates are not recorded, so decision blockers are evaluated only at the latest assessment (Oct 2026).
- Owner changes and due-date changes are not recorded; the current owner and due date are shown for every period.
- No action has been cancelled or superseded in the register.
- Independently verified (accepted export after the change confirming the outcome)
- 7
- Dataset linked — awaiting an accepted post-change export
- 3
- Export cannot confirm the specific outcome
- 1
- Document referenced — not independent
- 10
- Self-reported only — no evidence linked
- 2
Exports are only counted if they exist in the evidence model with an Accepted validation status. Source-evidence freshness is shown per action in its panel.
Builds on the proposed v5.0 (50 / 116) → 52 datasets / 118 controls, proposed effective 1 Jul 2027. v1.0–v3.0 and the v4.0/v5.0 proposals are unchanged; Evidence Coverage and the Cyber Risk Index are not restated.
- DS-51Remediation task and change records (ITSM export)
- DS-52Risk committee decisions and closure approvals
- OPS-10Remediation status, owners and blockers evidenced
- OPS-11Risk closure approved against verification evidence
RiskLens · Demonstration build · Built from the shared remediation register. “Verified” refers to simulated evidence, not independent validation.