All hands-on labs

Premium Hands-on labbeginnerblue teamAWS

Check policies for new access before deployment with IAM Access Analyzer

Before deploying changes to IAM policies, it's important to assess whether the new policy introduces additional permissions. While there may be instances where granting extra permissions is necessary, it's essential to make sure that you don't accidentally grant more access than intended, especially in production. IAM Access Analyzer has an API called CheckNoNewAccess that enables you to run custom policy checks to determine whether new access is allowed in an updated policy when compared to the existing policy. Gain hands-on experience using CheckNoNewAccess for both identity and resource policies.

  • 10 guided tasks

Scenario

So picture this scenario: you have a DevOps pipeline that makes changes to a production environment once the development team has finished coding and testing their changes. One of the developers attempts to modify the permissions in a policy document for the application running in that production AWS account. For security reasons, the DevOps team has added a pre-deploy check that runs the CheckNoNewAccess command before any deployment to check for policy changes. If any new access is detected, the deployment gets halted and the security team gets notified so they can investigate.

What you will learn

  • Learn how IAM Access Analyzer helps simplify least privilege
  • Explore custom policy checks including CheckNoNewAccess
  • Gain hands-on experience using CheckNoNewAccess for both identity and resource policies
  • Run the check-no-new-access CLI command to compare a new policy with an existing policy
  • Choose between IDENTITY_POLICY and RESOURCE_POLICY when you run the check
Hands-on lab

Check policies for new access before deployment with IAM Access Analyzer

Included in Cybr Premium.