Private API has no resource policy restricting access

Severity
High
Service
API Gateway
Check ID
APIGW_PRIVATE_NO_POLICY

What this check finds

This API Gateway REST API uses a PRIVATE endpoint type but has no resource policy. Without a resource policy, the API may be reachable from unintended VPCs or principals.

Passing looks like: Private API has a restricting resource policy.

How to fix it

Attach a resource policy that explicitly allows access only from intended VPC endpoints.

AWS console

API Gateway → REST API → Resource Policy → Edit.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Compliance controls mapped to Private API has no resource policy restricting access
FrameworkControls
NIST SP 800-53 Rev5 (Moderate)
  • AC-3 Access Enforcement
  • SC-7 Boundary Protection
NIST Cybersecurity Framework 2.0
  • PR.AA-05 Access permissions and authorizations are enforced with least privilege
  • PR.IR-01 Networks and environments are protected from unauthorized logical access and usage
ISO/IEC 27001:2022 Annex A
  • A.5.15 Access control
  • A.8.20 Networks security

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More API Gateway checks

All API Gateway checks

Find out what is actually exposed in your AWS environment.

Connect one AWS account and run your first security assessment.

No credit card · Agentless · Read-only