Skip to main content

💼 [IAM.2] IAM users should not have IAM policies attached

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

Description

By default, IAM users, groups, and roles have no access to AWS resources. IAM policies grant privileges to users, groups, or roles. We recommend that you apply IAM policies directly to groups and roles but not to users. Assigning privileges at the group or role level reduces the complexity of access management as the number of users grows. Reducing access management complexity might in turn reduce the opportunity for a principal to inadvertently receive or retain excessive privileges.

Similar

Similar Sections (Give Policies To)

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 NIST SP 800-53 Revision 5 → 💼 AC-2 Account Management132044no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-2(1) Account Management _ Automated System Account Management423no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-3 Access Enforcement15553no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-3(7) Access Enforcement _ Role-based Access Control26no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-3(15) Access Enforcement _ Discretionary and Mandatory Access Control18no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-6 Least Privilege102364no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-6(3) Least Privilege _ Network Access to Privileged Commands2no data
💼 PCI DSS v3.2.1 → 💼 7.2.1 Coverage of all system components.11no data

Sub Sections

SectionSub SectionsInternal RulesPoliciesFlagsCompliance

Policies (1)

PolicyLogic CountFlagsCompliance
🛡️ AWS IAM User has inline or directly attached policies🟢1🟠 x1, 🟢 x5no data

Internal Rules

RulePoliciesFlags
✉️ dec-x-4157c58a1