No mitigation or revocation for compromised key partially mitigated
THREAT172
· Partially mitigated: Some controls are in place, but the risk is still too high.
· Defined in catalog.py:2950
- Risk
- High impact × Low likelihood = 6 medium
- After mitigations
- High impact × Very Low likelihood = 3 low
Compromised key has no built in recovery mechanism, requires a manual rotation (SCRDR-CR-26-120 in X41 2026 audit)
Threat actors: Nation State / Law Enforcement
Mitigations
| Mitigation | Status |
|---|---|
| Use of airgapped SVS key MITIG10 | implemented |
| Persistent storage FDE for SVS MITIG14 | implemented |
| Users instructed not to move the SVS key off the SVS workstation MITIG149 | implemented |
Where it applies
Applies to 1 component in 1 scenario.
Physical and host layer · Application Server (host)
Notes
Existing mitigations: Submission key airgapped (MITIG10), FDE on SVS (MITIG14), guided not to move SVS key off (MITIG149). Further mitigations: End-to-end encryption protocol with forward secrecy. Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.