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/Default network with permissive rules

Medium severity

Default network with permissive rules

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

Updated 13 October 2026

What it looks like in each cloud

AWS

Resources in the default VPC, and a default security group that allows traffic rather than denying everything.

Google Cloud

Projects still containing the default network with its default-allow-internal, default-allow-ssh and default-allow-rdp firewall rules.

Azure

Not applicable: Azure creates no default virtual network, so the equivalent finding is an NSG with an Allow-Any inbound rule.

Why it matters

Default networks are flat and permissive by design, so one compromised instance can reach every other one. They also complicate every later attempt at segmentation.

How it happens

The first workload is deployed into whatever network exists. Nobody owns the default network, so nobody hardens or removes it.

How to check

Flag the default network in every account and project, list what runs in it, and inspect the default security group and firewall rules.

How to fix it

Create purpose-built networks with explicit rules, migrate workloads, and either delete the default network or strip its rules so it allows nothing.

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 5.4 (default security group restricts all traffic); Google Cloud Foundations 3.1 (default network does not exist in a project).

SOC 2

CC6.6 (network boundaries).

ISO/IEC 27001

A.8.20 Networks security, A.8.22 Segregation of networks.

DORA

Art. 9(4)(b) network segregation.

NIS2

Art. 21(2)(e) secure configuration and maintenance.

PCI DSS v4

Req. 1.2 (network security controls configured), 2.2 (no vendor defaults).

NIST CSF 2.0

PR.IR-01 (segmentation).

BSI C5

COS (segmentation).

DNB Good Practice Information Security

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.