← Back to rule catalog
Rule R-HTTP-ENDPOINT
active

Plaintext HTTP endpoints are immediate transport failures

Current non-compliance rule for any endpoint still exposed over HTTP.

Applies to
*
Cases
1
Evaluation order
50
Tags
transport, tls, current-failure
Overlay-specific scope
gdpr, nis2, dora, pci-dss-4, hipaa
Engine description
Plaintext HTTP endpoints fail current transport-security expectations.

Match cases

Case 1 high · replace-now
When
  • endpointUrl protocol is http:
Finding title template
{{asset.name}} uses plaintext HTTP
Current crypto template
Plaintext HTTP - no TLS
Severity / status
high · already-non-compliant
Effort / deadline
low
Recommended replacement
Move the endpoint to HTTPS with TLS 1.2 or later, and prefer TLS 1.3 when both sides support it. If the target service lacks TLS, terminate the connection behind a managed proxy before exposing the callout.
Rationale
NIST SP 800-52 Rev. 2 and SP 800-53 treat protected transport and cryptographic protection as baseline controls, and GDPR Art. 32 and NIS 2 Art. 21 require encryption of data in transit as a state-of-the-art measure. Plaintext HTTP leaves data and credentials exposed in transit and is not an acceptable steady-state configuration in any jurisdiction.
Citations
  • NIST_SP_800_52 · Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations
  • NIST_SP_800_53 · Security and Privacy Controls for Information Systems and Organizations
  • GDPR_ART_32 · GDPR Article 32 — security of processing
  • NIS2 · NIS 2 Directive — cybersecurity risk-management measures

Transport failures need to be reviewable as policy, not hidden in code. This document is the source for both the logic and the remediation language.