Skip to main content

💼 [IAM.21] IAM customer managed policies that you create should not allow wildcard actions for services

  • Contextual name: 💼 [IAM.21] IAM customer managed policies that you create should not allow wildcard actions for services

  • ID: /frameworks/aws-fsbp-v1.0.0/iam/21

  • Located in: 💼 Identity and Access Management (IAM)

Description​

When you assign permissions to AWS services, it is important to scope the allowed IAM actions in your IAM policies. You should restrict IAM actions to only those actions that are needed. This helps you to provision least privilege permissions. Overly permissive policies might lead to privilege escalation if the policies are attached to an IAM principal that might not require the permission.

Similar​

Similar Sections (Give Policies To)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 NIST SP 800-53 Revision 5 → 💼 AC-2 Account Management132034
💼 NIST SP 800-53 Revision 5 → 💼 AC-2(1) Account Management _ Automated System Account Management416
💼 NIST SP 800-53 Revision 5 → 💼 AC-3 Access Enforcement15537
💼 NIST SP 800-53 Revision 5 → 💼 AC-3(7) Access Enforcement _ Role-based Access Control14
💼 NIST SP 800-53 Revision 5 → 💼 AC-3(15) Access Enforcement _ Discretionary and Mandatory Access Control11
💼 NIST SP 800-53 Revision 5 → 💼 AC-5 Separation of Duties13
💼 NIST SP 800-53 Revision 5 → 💼 AC-6 Least Privilege102349
💼 NIST SP 800-53 Revision 5 → 💼 AC-6(2) Least Privilege _ Non-privileged Access for Nonsecurity Functions44
💼 NIST SP 800-53 Revision 5 → 💼 AC-6(3) Least Privilege _ Network Access to Privileged Commands2
💼 NIST SP 800-53 Revision 5 → 💼 AC-6(10) Least Privilege _ Prohibit Non-privileged Users from Executing Privileged Functions2

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlags