aws_compliance

AWS Compliance

AWS Identity and Access Management (IAM) can help you incorporate the principles of least privilege and separation of duties with access permissions and authorizations, by ensuring that IAM groups have at least one IAM user.

iam_group_not_empty

gxp_21_cfr_part_11_11_10_d

11.10(d) Limiting system access to authorized individuals

gxp_21_cfr_part_11_11_10_g

11.10(g) Use of authority checks to ensure that only authorized individuals can use the system, electronically sign a record, access the operation or computer system input or output device, alter a record, or perform the operation at hand

hipaa_security_rule_2003_164_308_a_3_i

164.308(a)(3)(i) Workforce security

hipaa_final_omnibus_security_rule_2013_164_308_a_3_i

hipaa_final_omnibus_security_rule_2013_164_308_a_3_ii_a

164.308(a)(3)(ii)(A) Authorization and/or supervision

hipaa_final_omnibus_security_rule_2013_164_308_a_3_ii_b

164.308(a)(3)(ii)(B) Workforce clearance procedure

hipaa_security_rule_2003_164_308_a_3_ii_b

hipaa_security_rule_2003_164_308_a_4_i

164.308(a)(4)(i) Information access management

hipaa_final_omnibus_security_rule_2013_164_308_a_4_i

hipaa_security_rule_2003_164_308_a_4_ii_b

164.308(a)(4)(ii)(B) Access authorization

hipaa_final_omnibus_security_rule_2013_164_308_a_4_ii_b

hipaa_final_omnibus_security_rule_2013_164_308_a_4_ii_c

164.308(a)(4)(ii)(C) Access establishment and modification

hipaa_security_rule_2003_164_308_a_4_ii_c

hipaa_final_omnibus_security_rule_2013_164_312_a_1

164.312(a)(1) Access control

hipaa_security_rule_2003_164_312_a_1

nist_800_171_rev_2_3_1_1

3.1.1 Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems)

nist_800_171_rev_2_3_1_2

3.1.2 Limit system access to the types of transactions and functions that authorized users are permitted to execute

nist_800_171_rev_2_3_1_4

3.1.4 Separate the duties of individuals to reduce the risk of malevolent activity without collusion

nist_800_171_rev_2_3_1_5

3.1.5 Employ the principle of least privilege, including for specific security functions and privileged accounts

nist_800_171_rev_2_3_1_7

3.1.7 Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs

nist_800_171_rev_2_3_13_3

3.13.3 Separate user functionality from system management functionality

cis_controls_v8_ig1_3_3

3.3 Configure Data Access Control Lists

fedramp_moderate_rev_4_ac_2_j

AC-2(j)

fedramp_moderate_rev_4_ac_5_c

AC-5(c)

fedramp_low_rev_4_ac_3

Access Enforcement (AC-3)

nist_800_53_rev_4_ac_3

fedramp_moderate_rev_4_ac_3

nist_800_53_rev_4_ac_2

Account Management (AC-2)

fedramp_low_rev_4_ac_2

fedramp_moderate_rev_4_sc_2

Application Partitioning (SC-2)

nist_800_53_rev_4_sc_2

soc_2_cc_1_3

CC1.3 COSO Principle 3: Management establishes, with board oversight, structures, reporting lines, and appropriate authorities and responsibilities in the pursuit of objectives

soc_2_cc_6_1

CC6.1 The entity implements logical access security software, infrastructure, and architectures over protected information assets to protect them from security events to meet the entity's objectives

soc_2_cc_6_2

CC6.2 Prior to issuing system credentials and granting system access, the entity registers and authorizes new internal and external users whose access is administered by the entity

soc_2_cc_6_3

CC6.3 The entity authorizes, modifies, or removes access to data, software, functions, and other protected information assets based on roles, responsibilities, or the system design and changes, giving consideration to the concepts of least privilege and segregation of duties, to meet the entity’s objectives

ffiec_d_3_pc_am_b_1

D3.PC.Am.B.1

ffiec_d_3_pc_am_b_16

D3.PC.Am.B.16

ffiec_d_3_pc_am_b_3

D3.PC.Am.B.3

ffiec_d_3_pc_am_b_6

D3.PC.Am.B.6

all_controls_iam

nist_800_53_rev_4_ac_6

Least Privilege (AC-6)

fedramp_moderate_rev_4_ac_6

nist_csf_pr_ac_1

PR.AC-1

nist_csf_pr_ac_4

PR.AC-4

nist_800_53_rev_4_ac_5

Separation Of Duties (AC-5)

IAM groups should have at least one user

Run individual configuration, compliance and security controls or full compliance benchmarks for CIS, FFIEC, PCI, NIST, HIPAA, RBI CSF, GDPR, SOC 2, Audit Manager Control Tower, FedRAMP, GxP and AWS Foundational Security Best Practices controls across all your AWS accounts using Powerpipe and Steampipe.

Apache License 2.0

steampipe-mod-aws-compliance

Control: IAM groups should have at least one user

Description

Usage

SQL

Tags