01Description
Services were identified that accept connections using TLS 1.0 and/or TLS 1.1. Both protocol versions were formally deprecated by the IETF in RFC 8996 (2021) and lack modern cryptographic protections.
02Impact
Deprecated protocol versions are exposed to known weaknesses and limit the use of strong cipher suites. A capable attacker in a privileged network position may be able to downgrade or weaken the protection of data in transit. Supporting these versions may also fail compliance requirements.
03Severity
Typically
Low
Typically Low. Usually Low, as practical attacks against these versions are limited. Raise to Medium where compliance requirements such as PCI DSS apply, as both versions are deprecated.
04How to verify
- 1Enumerate supported protocol versions with a tool such as testssl.sh or sslscan.
- 2Record each host and port accepting TLS 1.0 or 1.1.
- 3Confirm whether any legitimate clients still depend on the old versions before recommending removal.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Disable TLS 1.0 and TLS 1.1 on all services, keeping TLS 1.2 and TLS 1.3 enabled.
- 2On Windows, configure SCHANNEL protocol settings via registry or Group Policy; on web servers, update the protocol directive (for example ssl_protocols in nginx).
- 3Identify and upgrade any legacy clients that still require the old versions.
- 4Re-scan to confirm removal.
Draft findings like this from your own evidence
Book a demo