Latest feature: Compare your cloud architecture against known frameworks such as NIS and SOC2.Compare your cloud against NIS and SOC2.

Book a demo
AKRIBOS AI
ProductComplianceEngineersSecurityFAQ
Sign InTry AKRIBOSTry AKRIBOS
Home/Compliance/Common issues/Transport encryption not enforced

Medium severity

Transport encryption not enforced

Endpoints that still accept plaintext or outdated TLS, even though an encrypted path exists.

Updated 13 October 2026

What it looks like in each cloud

AWS

S3 buckets without a policy denying non-TLS requests, load balancers with HTTP listeners that do not redirect, and databases that do not require SSL.

Google Cloud

HTTP(S) load balancers serving on port 80 without redirect, Cloud SQL instances that do not require SSL.

Azure

Storage accounts with Secure transfer required off or a minimum TLS version below 1.2, and database servers that allow non-SSL connections.

Why it matters

A plaintext path lets anyone on the network read or alter traffic, and it fails the encryption-in-transit control every framework includes. Allowing both is as bad as allowing only plaintext, because clients fall back.

How it happens

HTTP is left enabled for a health check or a legacy client. Storage accounts predate the secure-transfer setting. The database driver's default was never changed.

How to check

Find every listener, bucket policy, storage setting and database flag that permits unencrypted connections or TLS below 1.2.

How to fix it

Require TLS 1.2 or higher everywhere, redirect HTTP to HTTPS, add a deny-unless-secure-transport condition to bucket policies, and set the require-SSL flag on databases.

Frameworks that require this

The controls this issue falls under. AKRIBOS reports the finding once and maps it to each framework you have in scope.

CIS Benchmarks

AWS Foundations 2.1.1 (S3 bucket policy denies HTTP requests); Google Cloud Foundations 6.x (Cloud SQL requires SSL); Azure Foundations 3.1 and 3.x (secure transfer required, minimum TLS 1.2).

SOC 2

CC6.7 (transmission of data).

ISO/IEC 27001

A.8.24 Use of cryptography, A.8.21 Security of network services.

DORA

Art. 9(3)(a) security of the means of data transfer.

NIS2

Art. 21(2)(h) cryptography and encryption.

PCI DSS v4

Req. 4.2.1 (strong cryptography in transit), 2.2.7 (encrypted non-console administrative access).

NIST CSF 2.0

PR.DS-02 (data in transit protected).

BSI C5

CRY (encryption in transit), COS (communication security).

DNB Good Practice Information Security

Cryptography; network security.

How AKRIBOS handles it

AKRIBOS finds this during a read-only review of every connected account, project and subscription, shows the exact resource and setting behind the finding, and ranks it by the attack path it enables rather than in isolation. The fix is proposed as CLI commands or Terraform for you to review and approve, and the approval is recorded in the audit trail together with the compliance controls it satisfies.

Related issues

Storage bucket open to the internet

Critical

Object storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.

Read more

Root or owner account without MFA

Critical

The most privileged identity in the account protected by a password alone.

Read more

Database reachable from the internet

Critical

A managed database with a public address and a firewall that lets the world in.

Read more
All common issues

Attackers don't wait for your next audit. Neither does AKRIBOS.

Connect AWS, Google Cloud or Azure and get your first review today.

Run your first reviewRun your first review
Cinematic desert landscape at dusk with a lone silhouette standing before a warm amber glow, surrounded by dark rolling hills and a deep blue sky.
AKRIBOS

The AI agent that reviews and hardens your cloud, right from your terminal or our dashboard.

Navigation

How It WorksAttack PathsContinuous ReviewsComplianceCommon Cloud IssuesFor EngineersSecurityFAQ

Information

ContactPrivacy PolicyTerms of ServiceData Processing AgreementResponsible Disclosure

Socials

LinkedIn

© 2026 AKRIBOS AI B.V. All rights reserved.

AKRIBOS is a trade name of AKRIBOS AI B.V., registered with the Netherlands Chamber of Commerce (KvK) under number 83548335, Amsterdam, The Netherlands.