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/Over-permissive IAM policies

High severity

Over-permissive IAM policies

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

Updated 13 October 2026

What it looks like in each cloud

AWS

IAM policies with "Action": "*" on "Resource": "*" attached to users, groups or roles, including the AdministratorAccess managed policy on workloads.

Google Cloud

Basic roles (Owner, Editor) bound at the project or folder level, especially to service accounts; default service accounts with Editor.

Azure

Owner or Contributor assigned at subscription scope to service principals or managed identities.

Why it matters

Permissions are the fuel for lateral movement. A single compromised workload with administrative rights turns a minor incident into full account takeover, and it is the link in most attack paths that reach data.

How it happens

Developers grant broad rights to get something working and leave them in place. Managed policies are attached because the exact permission set is unknown. Default service accounts ship with Editor.

How to check

Enumerate every policy and role binding, flag wildcard actions and basic roles, and compare granted permissions with the permissions actually used over the last 90 days.

How to fix it

Replace wildcards with the actions the workload needs, scope resources explicitly, move to predefined or custom roles, and use permission-usage data to prune what has not been exercised.

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 1.16 (no policies with full administrative privileges); Google Cloud Foundations 1.x (service account and basic role restrictions); Azure Foundations 1.x (custom roles with limited scope).

SOC 2

CC6.1 (authorisation), CC6.3 (least privilege and role changes).

ISO/IEC 27001

A.5.15 Access control, A.5.18 Access rights, A.8.2 Privileged access rights.

DORA

Art. 9(4)(c) least-privilege access management.

NIS2

Art. 21(2)(i) access control policies.

PCI DSS v4

Req. 7.2 (least privilege), 7.3 (access control system).

NIST CSF 2.0

PR.AA-05 (access permissions managed on least privilege).

BSI C5

IDM (least privilege, privileged access management).

DNB Good Practice Information Security

Logical access management (need-to-have, periodic reviews).

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.