LOWCIS 1.17

Ensure a support role has been created for AWS Support access

AWS provides a managed policy (AWSSupportAccess) that grants permissions to troubleshoot and resolve issues with AWS Support. Creating a dedicated role for this purpose follows least privilege.

Security Impact

Without a proper support role, troubleshooting may require using overly privileged accounts.

How to Remediate

Create an IAM role with the AWSSupportAccess managed policy. Assign this role to authorized support personnel only.

Affected Resources

AWS::IAM::Role

Compliance Frameworks

CIS AWS v1.5.0CIS AWS v2.0

How TigerGate Helps

TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all Identity and Access Management (IAM) resources across your AWS accounts every hour

  • Instant Alerts

    Get notified via Slack, email, or webhooks when this misconfiguration is detected

  • One-Click Remediation

    Fix this issue directly from the TigerGate dashboard with our guided remediation

  • Compliance Evidence

    Automatically collect audit evidence for CIS AWS v1.5.0, CIS AWS v2.0 compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-iam-17
Service
Identity and Access Management (IAM)
Category
Support Access
Severity
LOW
CIS Benchmark
1.17

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related Identity and Access Management (IAM) Checks

View all checks
aws-iam-1high

Avoid the use of root account

aws-iam-2critical

Ensure MFA is enabled for the root account

aws-iam-3high

Ensure hardware MFA is enabled for the root account

aws-iam-4critical

Ensure no root account access keys exist

aws-iam-5medium

Ensure IAM password policy requires at least one uppercase letter