Firewall logs are not monitored inform
THREAT149
· Inform: Handled by telling users how to protect themselves.
· Defined in catalog.py:2563
- Risk
- Medium impact × Low likelihood = 4 medium
- After mitigations
- Medium impact × Low likelihood = 4 medium (unchanged)
In the case of an attack or attempted attack, firewall logs would provide visibility into the actions performed by an adversary.
Threat actors: Any
Mitigations
No mitigations in place.
Possible further mitigations
- Extract and monitor Firewall logs MITIG193 proposed
Where it applies
Applies to 1 component in 5 scenarios.
Source submission · Dedicated Hardware Firewall
Journalist triage · Dedicated Hardware Firewall
Admin access · Dedicated Hardware Firewall
Updates, time & DNS · Dedicated Hardware Firewall
Source discovery and OPSEC · Dedicated Hardware Firewall
Notes
Further mitigations: Logs should be extracted from the firewalls and stored/aggregated/analyzed (MITIG193). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.