SMTP relay compromised partially mitigated
THREAT71
· Partially mitigated: Some controls are in place, but the risk is still too high.
· Defined in catalog.py:1251
- Risk
- Low impact × Low likelihood = 2 low
- After mitigations
- Low impact × Low likelihood = 2 low (unchanged)
Can send out arbitrary OSSEC and/or Journalist alert emails, read all incoming/outgoing emails except for OSSEC/Journalist alerts which are encrypted. Can cause denial of service and prevent OSSEC and/or Journalist alerts from being sent. An attacker may also obtain email addresses and identity of the SecureDrop instance administrators and journalsits, as well as some metadata on SecureDrop instance health and existence of new submissions to the Source Interface.
Mitigations
| Mitigation | Status |
|---|---|
| OSSEC emails are gpg encrypted MITIG235 | implemented |
| OSSEC emails should be signed MITIG236 | proposed |
Possible further mitigations
- Use Signal for OSSEC alerts MITIG237 proposed
Residual risk
Furthermore, if the SMTP relay suffers a denial-of-service attack, OSSEC alerts may not be delivered to administrator(s).
Where it applies
Applies to 1 component in 2 scenarios.
Monitoring & alerting · SMTP relay
Corporate and legal zone · SMTP relay
Notes
Existing mitigations: Emails are GPG-encrypted to provide confidentiality (MITIG235). However, they are not signed, therefore they can be spoofed. (MITIG236). Further mitigations: Move Ossec alerts to Signal (MITIG237). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.