Three audiences, one graph. Each pack is a view over the same objects, so the board, a regulator, and a customer can never be told different facts, only different levels of detail. The customer pack is checked on every build for dollar figures, internal codes, and staff names.
Regulator pack · control environment statement
Compliance posture and evidence
For: Regulators and external auditors
1. Scope
This statement covers 8 requirements across 2 frameworks, the controls mapped to them, and the policies those controls enforce. 7 of 8 requirements have a mapped control with test evidence from the last 180 days. Every requirement without that evidence is listed below rather than omitted.
2. Requirement coverage and test evidence
| Framework | Requirement | Controls | Last tested | Status |
|---|---|---|---|---|
| ISO 27001 | A.5.15 · Access control | CTL-031 | 2026-10-03 | Evidenced |
| ISO 27001 | A.5.34 · Privacy and protection of PII | CTL-090 | 2026-09-13 | Evidenced |
| ISO 27001 | A.8.12 · Data leakage prevention | CTL-054 | 2026-10-05 | Evidenced |
| ISO 27001 | A.8.16 · Monitoring activities | — | — | No control |
| ISO 27001 | A.8.5 · Secure authentication | CTL-031 | 2026-10-03 | Evidenced |
| SOC 2 | CC6.1 · Logical access security | CTL-031 | 2026-10-03 | Evidenced |
| SOC 2 | CC7.2 · Monitoring for anomalies | CTL-007 | 2026-10-24 | Evidenced |
| SOC 2 | CC9.2 · Vendor risk management | CTL-077 | 2026-08-19 | Evidenced |
A control untested for more than 180 days has its effectiveness halved in every residual risk score it supports.
3. Policy governance
| Policy | Version | Approved | Review due | Enforced by |
|---|---|---|---|---|
| POL-01 · Access Control Policy | 3.2 | 2026-05-21 | 2027-05-21 | CTL-031, CTL-112 |
| POL-02 · Security Monitoring & Detection Standard | 1.4 | 2025-10-06 | 2026-10-06 (overdue) | CTL-007, CTL-054 |
| POL-03 · Third-Party Risk Policy | 2.0 | 2026-01-14 | 2027-01-14 | CTL-077 |
| POL-04 · Data Retention & Privacy Policy | 4.1 | 2026-07-05 | 2027-07-05 | CTL-090 |
| POL-05 · Acceptable Messaging Use Policy | 1.0 | 2026-08-05 | 2027-08-05 | no control |
4. Incidents on regulated risks
| Incident | Date | Risk | Customers affected | Root cause | Status |
|---|---|---|---|---|---|
| INC-2026-063 · Contractor bulk export | 2026-10-14 | RSK-033 | under investigation | under investigation | investigating |
| INC-2026-041 · ATO cluster via legacy login | 2026-07-18 | RSK-014 | 118 | Credential stuffing through legacy login endpoint lacking MFA enforcement | closed |
| INC-2026-022 · Deletion requests missed in backup tier | 2026-06-03 | RSK-041 | 40 | Retention pipeline skipped cold-storage backups when honoring deletion requests | closed |
5. Third-party oversight
| Vendor | Tier | Holds PII | Last review | Status |
|---|---|---|---|---|
| VND-01 · Primary cloud provider | 1 | yes | 2025-07-24 | review lapsed |
| VND-02 · SMS aggregator (route partner A) | 1 | no | 2026-06-17 | current |
| VND-03 · Identity verification provider | 2 | yes | 2026-09-08 | current |
| VND-04 · Offshore support BPO | 2 | yes | never | review lapsed |
6. Remediation commitments
| Action | Risk | Owner | Due | Status |
|---|---|---|---|---|
| ACT-95 · Retire legacy login endpoint | RSK-014 | SecEng | 2026-11-23 | in progress |
| ACT-91 · Deploy AIT detection on messaging spend | RSK-021 | R. Delgado | 2026-12-04 | open |
| ACT-88 · Passkey rollout for customer console | RSK-014 | K. Osei | 2026-12-19 | in progress |
| ACT-97 · Automate quarterly privileged-access review | RSK-033 | M. Chen | 2027-01-05 | open |
7. Known gaps disclosed
- Broken lineage: 8
- Paper policy: 1
- Vendor review lapsed: 2
- Stale assessment: 1
- Unmapped requirement: 1
- Untested control: 1
- Policy review overdue: 1
Gaps come from the same engine that drives the internal gap board, so this list cannot drift from what the risk team sees.
Issue this pack
Issuing freezes the pack exactly as rendered above. The snapshot is hash-chained to the one before it, and the database refuses any edit or delete, so what was sent stays provable after the underlying data moves on.