Cognito Advanced Security Disabled

What this rule checks

Detects Cognito user pools without advanced security features.

How to fix it

1. 1Enable advanced security mode (AUDIT or ENFORCED)
2. 2Configure risk-based adaptive authentication

import * as cognito from 'aws-cdk-lib/aws-cognito';

new cognito.UserPool(this, 'Pool', {
  passwordPolicy: { minLength: 12, requireLowercase: true, requireUppercase: true, requireDigits: true, requireSymbols: true },
  mfa: cognito.Mfa.REQUIRED,
  mfaSecondFactor: { sms: false, otp: true },
});

import * as cognito from 'aws-cdk-lib/aws-cognito';

new cognito.UserPool(this, 'Pool', {
  passwordPolicy: { minLength: 12, requireLowercase: true, requireUppercase: true, requireDigits: true, requireSymbols: true },
  mfa: cognito.Mfa.REQUIRED,
  mfaSecondFactor: { sms: false, otp: true },
  advancedSecurityMode: cognito.AdvancedSecurityMode.ENFORCED,
});

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 cognito-advanced-security-disabled and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "cognito-advanced-security-disabled", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::cognito-advanced-security-disabled',
  reason: 'Why this is intentional',
});

Use the rule ID cognito-advanced-security-disabled shown above — not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs →

More Cognito rules