Data protection vulnerability in Journalist interface mitigated
THREAT15
· Mitigated: Controls in place bring the risk down to an acceptable level.
· Defined in catalog.py:276
- Risk
- Medium impact × Low likelihood = 4 medium
- After mitigations
- Medium impact × Low likelihood = 4 medium (unchanged)
Improper data protection may lead to information being leaked by the client.
Threat actors: Any
Mitigations
| Mitigation | Status |
|---|---|
| Source interface: Cache-Control nostore MITIG204 | implemented |
| Sensitive data sent in POST requests MITIG205 | implemented |
Where it applies
Applies to 1 component in 2 scenarios.
Journalist triage · Journalist Interface
Workstation: reading submissions · Journalist Interface
Notes
Existing mitigations: Cache-control header set to "no-store" (MITIG204). All sensitive data is sent through HTTP POST (MITIG205). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.