Critical severity
Root or owner account without MFA
The most privileged identity in the account protected by a password alone.
Updated
What it looks like in each cloud
The AWS account root user has no MFA device, or still has active access keys.
Users holding roles/owner at the organisation or project level without 2-Step Verification enforced.
Global Administrator accounts without MFA, or without a Conditional Access policy requiring it.
Why it matters
The root or owner identity can disable logging, change billing, delete the account and remove every other control. A phished or reused password is all it takes.
How it happens
Accounts are created in a hurry, the root credentials are stored in a shared vault, and nobody goes back to add a hardware key. Owner roles are granted to engineers during setup and never reduced.
How to check
List every root, owner and global-administrator identity and confirm MFA, preferably a hardware key, is enforced rather than merely available.
How to fix it
Enrol a hardware MFA device on the root user, delete root access keys, and use the root identity only for the handful of tasks that require it. Enforce MFA for owners and global administrators through organisation policy or Conditional Access.
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.4 (no root access key), 1.5 and 1.6 (MFA and hardware MFA for root); Google Cloud Foundations 1.2 (MFA for all users); Azure Foundations 1.1.x (MFA for privileged users).
SOC 2
CC6.1 (authentication of users) and CC6.3 (privileged access).
ISO/IEC 27001
A.8.2 Privileged access rights, A.8.5 Secure authentication.
DORA
Art. 9(4)(d) strong authentication.
NIS2
Art. 21(2)(j) multi-factor authentication.
PCI DSS v4
Req. 8.4 (MFA for administrative access and all access into the CDE).
NIST CSF 2.0
PR.AA-03 (users authenticated), PR.AA-05 (privileged access).
BSI C5
IDM (strong authentication for privileged users).
DNB Good Practice Information Security
Logical access management (privileged access, strong authentication).
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
CriticalObject storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.
Read moreDatabase reachable from the internet
CriticalA managed database with a public address and a firewall that lets the world in.
Read moreSnapshots or machine images shared publicly
CriticalDisk snapshots, database snapshots or machine images that anyone with a cloud account can copy.
Read moreAttackers don't wait for your next audit. Neither does AKRIBOS.
Connect AWS, Google Cloud or Azure and get your first review today.
