Weaken Encryption T1600
- Tactic
- Defense Impairment
- Platform
- Network Devices
- Version
- 2.0
- Created
- 19 October 2020
- Last modified
- 12 May 2026
Adversaries may compromise a network device’s encryption capability in order to bypass encryption that would otherwise protect data communications.[1]
Offense vs defense T1600
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
Weaken Encryption detection strategy DET0339
MITRE names one behaviour worth catching for this technique and breaks it into 1 analytic, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection Strategy for Weaken Encryption on Network Devices
AN0961 · Network Devices
Defenders may observe unauthorized modifications to encryption-related configuration files, firmware, or crypto modules on network devices. Suspicious patterns include changes to cipher suite configurations, unexpected firmware updates affecting crypto libraries, disabling of hardware cryptographic accelerators, or reductions in key length policies. Correlating configuration changes with anomalies in encrypted traffic characteristics (e.g., weaker ciphers or sudden plaintext transmission) strengthens detection.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Module LoadDC0016 | snmp:status | Status change in cryptographic hardware modules (enabled -> disabled) |
| File ModificationDC0061 | networkdevice:config | Configuration change events referencing encryption, TLS/SSL, or IPSec settings |
| Network Traffic ContentDC0085 | NSM:Flow | Traffic patterns showing downgrade from strong encryption (AES-256) to weaker or plaintext protocols |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| CipherSuiteWhitelist | List of approved encryption algorithms and key lengths; customizable to organizational policy. |
| TimeWindow | Correlation period between configuration changes and abnormal traffic; adjustable to reduce false positives. |
| AuthorizedFirmwareSources | Known trusted sources of firmware updates; deviations indicate possible compromise. |
| TrafficEntropyThreshold | Baseline entropy measurements of encrypted traffic; deviations may reveal weakening of encryption. |