Failure to encrypt submissions as they are written to disk mitigated

THREAT21 · Mitigated: Controls in place bring the risk down to an acceptable level. · Defined in catalog.py:377

Risk
Medium impact × Low likelihood = 4 medium
After mitigations
Medium impact × Low likelihood = 4 medium (unchanged)

How statuses and scores work

Failure to encrypt files as they are streamed to a temporary file through Secure Temporary File wrapper as the files are streamed on disk prior to being encrypted by RSA may lead to decrypted documents being persisted to disc and potentially viewable through forensic investigation of app server hardware or remote access to the app server.

Threat actors: Any

Mitigations

Mitigation Status
Logging off for source interface MITIG41 implemented

Possible further mitigations

Where it applies

Applies to 1 component in 2 scenarios.

Source submission · Source Interface
Supply chain and dependencies · Source Interface

Notes

Existing mitigations: Sensitive information (source information, submission information) is not logged (MITIG41). Further mitigations: Application and mon servers should be encrypted at rest (MITIG134). Automated test for mitigation: Yes.

How this threat is matched

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