Do new compute instances and databases get no public IP address by default?
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Question 11 of the assessment asks: Do new compute instances and databases get no public IP address by default? If a public address needs an explicit decision, fewer resources are exposed by accident. It comes from Microsoft cloud security benchmark NS-1 and carries weight 2 in the network reachability domain.
Start the assessment ยท All 40 questions
Why it matters
If a public address needs an explicit decision, fewer resources are exposed by accident.
Answers and what each is worth
| Answer | Value |
|---|---|
| Yes, enforced by policy | 1 |
| By convention, not enforced | 0.5 |
| No or not known | 0 |
How to check it in each cloud
- AWS
- List instances and network interfaces with a public IP (aws ec2 describe-instances) and check subnet settings for auto-assign public IP, or the matching AWS Config rules.
- Azure
- Query Azure Resource Graph for network interfaces with a public IP address attached and for databases with public access enabled.
- Google Cloud
- List instances with external IPs (gcloud compute instances list) and check that the compute.vmExternalIpAccess org policy constraint is enforced.
The fix
Enforce a policy that denies public IP assignment on compute and databases unless an approved exception exists. Effort: medium.
Where it comes from
- Microsoft cloud security benchmark NS-1: Establish network segmentation boundaries
- NIST SP 800-53 Rev. 5 SC-7: source
Related pages
Sources
- Microsoft cloud security benchmark NS-1, read 16 Nov 2026
- NIST SP 800-53 Rev. 5 SC-7, read 16 Nov 2026
Last reviewed 16 Nov 2026.