Security Group Exposes Non-Standard Ports Publicly

What this rule checks

Detects security groups used by sensitive services that allow 0.0.0.0/0 ingress on non-standard ports.

How to fix it

1. 1Restrict ingress rules to specific CIDR blocks or reference other security groups instead of allowing 0.0.0.0/0 on non-standard ports
2. 2Use a bastion host or VPN for administrative access

CDK Insights pinpoints the exact file and line in your CDK source for every finding, so you can jump straight to the fix.

Affected resource types

Intentional? Suppress this finding

Sometimes a flag is deliberate — a genuinely public endpoint, say. You can dismiss cross-resource-sg-nonstandard-public-ports and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "cross-resource-sg-nonstandard-public-ports", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::cross-resource-sg-nonstandard-public-ports',
  reason: 'Why this is intentional',
});

Use the rule ID cross-resource-sg-nonstandard-public-ports shown above — not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs →

More EC2 rules