NTP accepted
THREAT105
· Accepted: The team has decided to live with this risk.
· Defined in catalog.py:1827
- Risk
- Medium impact × Medium likelihood = 6 medium
- After mitigations
- Medium impact × Medium likelihood = 6 medium (unchanged)
An attacker with a privileged network position could spoof/tamper with NTP responses and cause DoS, as Tor Hidden services are sensitive to clock skew.
Threat actors: Nation State / Law Enforcement Large Corporation
Mitigations
No mitigations in place.
Possible further mitigations
- Use authenticated version of NTP to harden against e.g. DNS attacks - tlsdate? research needed here MITIG97 proposed
Residual risk
Candidate for further mitigation efforts.
Where it applies
Applies to 1 component in 1 scenario.
Updates, time & DNS · NTP server
Notes
Further mitigations: NTP over TLS (e.g.: tlsdate) (MITIG97). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.