Latest feature: Compare your cloud against NIS and SOC2.

Book a demo

Audit-ready cloud, every day of the year.

AKRIBOS maps your AWS, Google Cloud and Azure configuration to the frameworks your auditors, supervisors and customers ask about: CIS, SOC 2, ISO 27001, DORA, NIS2, PCI DSS, NIST CSF, C5, DNB. Each control shows the resource behind the result, why it passes or fails, and the exact fix.

Updated

How a check works

The same review that maps attack paths produces the compliance evidence, so the two never disagree.

Read-only, every account

A scoped read-only role per account, project or subscription. AKRIBOS pulls the configuration across every region; nothing is changed.

Control by control, with reasoning

Each framework control is evaluated against the actual resources. The result names the resource and the setting behind it, not just pass or fail.

Evidence that stays current

Reviews run on a schedule you set. Every review, finding and approved fix is timestamped in the audit trail, which is what a Type II or surveillance audit needs.

Common cloud misconfigurations

The findings that fail compliance checks most often, what they look like in each cloud, and which controls they fall under.

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

Snapshots or machine images shared publicly

Critical

Disk snapshots, database snapshots or machine images that anyone with a cloud account can copy.

Read more

Over-permissive IAM policies

High

Identities, often service accounts, that can do anything in the account because a wildcard or a basic role was easier than a scoped policy.

Read more

SSH or RDP open to 0.0.0.0/0

High

Management ports reachable from any address on the internet.

Read more

Audit logging incomplete

High

Gaps in the record of who did what: missing regions, missing data-access events, or logs that can be altered.

Read more

Long-lived or unused credentials

High

Access keys, service account keys and client secrets that never rotate and are no longer needed.

Read more

Instance metadata without session tokens

High

Compute instances that answer metadata requests, including their temporary credentials, to any process that can reach the local metadata address.

Read more

Trust policies open to any account

High

Roles or bindings that let identities outside your organisation assume access, often for a vendor integration that was set up too generously.

Read more

Data at rest without the encryption you intended

Medium

Volumes, snapshots or databases created without encryption, or without the customer-managed keys your policy requires.

Read more

Transport encryption not enforced

Medium

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

Read more

Network flow logs off

Medium

No record of which addresses talked to which, so traffic to and from a compromised host cannot be reconstructed.

Read more

Default network with permissive rules

Medium

Workloads running in the cloud-created default network, which ships with rules nobody would write deliberately.

Read more
Browse all issues

Compliance questions

Which frameworks does AKRIBOS support?

CIS, SOC 2, ISO 27001, DORA, NIS2, PCI DSS, NIST CSF, C5 and DNB, across AWS, Google Cloud and Azure. Each framework has its own page with the controls that map to cloud configuration and the issues that fail them.

Can one review cover several frameworks at once?

Yes. A finding is reported once and mapped to every framework you have in scope, so the same public bucket shows up under CIS 2.1.4, SOC 2 CC6.1, ISO 27001 A.8.3 and DORA Article 9 without separate scans.

Does using AKRIBOS make us compliant?

No tool does. AKRIBOS covers the cloud-configuration part of each framework and gives you dated evidence for it. Policies, people, training and vendor management remain your programme.

How often should we review?

As often as your cloud changes. Most teams run a scheduled review at least weekly, plus on demand before an audit, so the evidence covers the whole period rather than audit day.

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 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.