Journalist user marks all submissions as seen out of scope

THREAT171 · Out of scope: Outside what this threat model covers. · Defined in catalog.py:2934

Risk
Low impact × Low likelihood = 2 low
After mitigations
Low impact × Low likelihood = 2 low (unchanged)

How statuses and scores work

A malicious journalist can potentially mark all source submissions as seen, which would change the global state in every journalist's source list (JI or SecureDrop Client). There is no limit to the number of submissions a journalist can mark as seen.

Threat actors: Malicious journalist

Mitigations

No mitigations in place.

Possible further mitigations

Where it applies

Applies to 1 component in 2 scenarios.

Journalist triage · Journalist Interface
Workstation: reading submissions · Journalist Interface

Notes

Existing mitigations: Seen data is recorded on a per-journalist basis. While it is currently aggregated into a global True/False status at the source level, in the event of a bulk operation, the previous state could be restored. Further mitigations: Switch to a personal inbox model to avoid global impact of individual journalist actions (MITIG244). Automated test for mitigation: Yes.

How this threat is matched

Listed for these components. A boundary covers every component inside it.