A default security group is the baseline group AWS assigns when no custom group is selected. In the article’s context, it is risky because it can be left with overly open inbound and outbound behavior. Teams should replace it with explicitly designed groups that reflect actual workload needs.
How a Default Security Group Works
A default security group is the baseline AWS group assigned when no custom group is chosen. It is not a workload-specific design choice, which is why it can become a hidden starting point rather than a deliberate boundary. The practical issue is that a default posture often persists until someone explicitly replaces it with rules that match the workload.
That matters because cloud network security depends on intent, not inherited convenience. A default group can be harmless in a narrowly constrained environment, but it becomes risky when teams assume it is “just there” and do not review what it allows.
For broader cloud network design, see Cloud Network Security Guide, which covers how security groups, NACLs, private endpoints and egress controls fit together.
Why Default Security Groups Are Risky
The core problem is over-permissive default behavior. If a default security group is left in place with open inbound or outbound allowances, it can expose services that were meant to be private, widen lateral movement paths, or create unexpected egress reachability. The risk is especially acute when teams deploy quickly and inherit the default without testing its effect in the actual architecture.
Default network settings also create a false sense of safety. Because the resource exists automatically, it is easy to treat it as neutral, when in practice it may be the least tailored and least reviewed part of the design.
For AWS-specific baseline hardening, AWS Security Guide provides the broader account, logging and network context around security groups and other AWS controls.
For a wider look at insecure defaults and cloud drift, Cloud Misconfiguration Guide is useful because default security groups are one of the clearest examples of a configuration that must be actively replaced or tightened.
How Teams Should Evaluate Exposure
Exposure checks start with inventory and architecture review. Teams should identify where the default group is attached, which instances still depend on it, and whether any workload has inherited reachability that was never intended. That review should be paired with examination of whether the instance is internet-facing, reachable from peer networks, or connected to sensitive services through broad egress paths.
The same review should look for compensating controls such as restrictive route design, private connectivity, and flow logging. A default group is not just a rule set, it is part of the control boundary, so the question is whether the surrounding network design actually constrains what the group can do.
For practical VPC context, Amazon VPC Security Guide explains how security groups, network ACLs and flow logs work together in the AWS network plane.
The article's own guidance aligns with secure-by-default thinking, and CISA Secure by Design is a useful external reference for the principle that defaults should not leave customers to discover and correct preventable exposure.
Safer Replacement Patterns
The best replacement is a deliberately designed security group for each workload role, not a universal catch-all. That means separate rules for distinct tiers or functions, explicit inbound sources, and tightly scoped outbound paths that reflect what the workload truly needs to communicate with. If a team cannot explain why a rule exists, it probably does not belong in the group.
In practice, the replacement process should also include review of rule sprawl, overbroad CIDRs, and inherited allowances that were added “temporarily” and never removed. The value is not just tighter filtering, but a security boundary that can be understood, reviewed and changed without guesswork.
For a more formal control view, NIST SP 800-53 Rev 5 Security and Privacy Controls maps well to this topic through access control, system integrity and configuration management expectations.
Where AWS-specific governance is the main concern, Security by Design and by Default Guide is a strong companion because default security groups are exactly the kind of inherited baseline that secure-by-default programs are meant to eliminate.
Risk and Threat Considerations
Default security groups become dangerous when they are left as implicit trust boundaries. An over-open rule set can expose services to unintended peers, enable internal reconnaissance, or allow outbound paths that support command and control, data exfiltration or silent dependency abuse.
Failure mechanism: Teams assume the default group is benign, then deploy workloads into it without validating the actual inbound and outbound effect of its rules.
Impact: The result can be unnecessary attack surface, weaker segmentation, and a harder-to-detect path from initial access to later movement or data leakage.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-4 — Information Flow Enforcement | Default security group rules control network flow between workload zones. |
| CM-2 — Baseline Configuration | A default security group is a baseline configuration that should be intentionally defined and reviewed. | |
| CM-6 — Configuration Settings | Security group rules are configuration settings that need approved, documented control. | |
| Recommendation — Enforce AC-4 to restrict traffic paths to only the flows each workload requires. Define and maintain approved security baselines for security groups and replace inherited defaults. Apply CM-6 to standardize, review and approve security group rule settings. | ||
| CIS Controls v8 | CIS-4 — Secure Configuration of Enterprise Assets and Software | Default security groups are a cloud configuration issue that fits secure configuration control. |
| CIS-12 — Network Infrastructure Management | Security groups are a core network infrastructure control for segmentation and access restriction. | |
| Recommendation — Harden cloud network defaults and remove permissive inherited rules. Segment network access with approved controls and eliminate unnecessary exposure paths. | ||
Practitioner Guidance
What to watch for: Any workload still using the default security group deserves review, especially if its traffic patterns are not documented or if it has broad egress and no clear ownership.
Governance implication: Treat default groups as a temporary onboarding state, not an acceptable steady state. Ownership should sit with the platform or application team responsible for the workload boundary, with a clear rule that every production attachment is intentional.
Practitioner takeaway: A default security group is safe only when it is short-lived, narrowly scoped and actively replaced by a workload-specific design.
Related resources from NHI Mgmt Group
- What breaks when teams keep using the AWS default security group for different EC2 workloads?
- Why does a permissive default security group increase breach risk in cloud environments?
- What should security teams do first when they find EC2 instances using the default security group?
- Why should the default VPC security group restrict all traffic in AWS?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org