aws_compliance

AWS Compliance

AWS Elastic Compute Cloud (AWS EC2) Security Groups can help manage network access by providing stateful filtering of ingress and egress network traffic to AWS resources.

vpc_security_group_restrict_ingress_ssh_all

pci_dss_v321_requirement_1_2_1_a

1.2.1.a Examine firewall and router configuration standards to verify that they identify inbound and outbound traffic necessary for the cardholder data environment

pci_dss_v321_requirement_1_2_1_b

1.2.1.b Examine firewall and router configurations to verify that inbound and outbound traffic is limited to that which is necessary for the cardholder data environment

pci_dss_v321_requirement_1_2_1_c

1.2.1.c Examine firewall and router configurations to verify that all other inbound and outbound traffic is specifically denied, for example by using an explicit “deny all” or an implicit deny after allow statement

pci_dss_v321_requirement_1_3_1

1.3.1 Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports

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_1_ii_b

164.308(a)(1)(ii)(B) Risk management

hipaa_final_omnibus_security_rule_2013_164_308_a_1_ii_b

hipaa_final_omnibus_security_rule_2013_164_308_a_3_i

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

hipaa_final_omnibus_security_rule_2013_164_308_a_3_ii_b

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

hipaa_final_omnibus_security_rule_2013_164_308_a_4_i

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

hipaa_final_omnibus_security_rule_2013_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_c

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

hipaa_final_omnibus_security_rule_2013_164_312_a_1

164.312(a)(1) Access control

hipaa_final_omnibus_security_rule_2013_164_312_e_1

164.312(e)(1) Transmission security

audit_manager_control_tower_disallow_internet_connection_2_0_2

2.0.2 - Disallow internet connection through SSH

pci_dss_v321_requirement_2_2_2

2.2.2 Enable only necessary services, protocols, daemons, etc., as required for the function of the system

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_14

3.1.14 Route remote access via managed access control points

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_20

3.1.20 Verify and control/limit connections to and use of external systems

nist_800_171_rev_2_3_1_3

3.1.3 Control the flow of CUI in accordance with approved authorizations

nist_800_172_3_1_3_e

3.1.3e Employ [Assignment: organization-defined secure information transfer solutions] to control information flows between security domains on connected systems

nist_800_171_rev_2_3_13_1

3.13.1 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems

nist_800_171_rev_2_3_13_2

3.13.2 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems

nist_800_172_3_13_4_e

3.13.4e Employ [Selection: (one or more): [Assignment: organization-defined physical isolation techniques]; [Assignment: organization-defined logical isolation techniques]] in organizational systems and system components

nist_800_171_rev_2_3_13_5

3.13.5 Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks

nist_800_171_rev_2_3_13_6

3.13.6 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception)

nist_800_171_rev_2_3_4_7

3.4.7 Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services

cis_controls_v8_ig1_4_6

4.6 Securely Manage Enterprise Assets and Software

cis_controls_v8_ig1_4_7

4.7 Manage Default Accounts on Enterprise Assets and Software

nydfs_23_500_02_b_2

500.02(b)(2)

rbi_itf_nbfc_8_I

8.I Basic Security Aspects

fedramp_moderate_rev_4_ac_17_1

AC-17(1) Automated Monitoring/Control

nist_800_53_rev_5_ac_17_1

AC-17(1) Monitoring And Control

nist_800_53_rev_5_ac_17_10

AC-17(10) Authenticate Remote Commands

nist_800_53_rev_5_ac_17_4_a

AC-17(4)(a)

nist_800_53_rev_5_ac_17_9

AC-17(9) Disconnect Or Disable Access

nist_800_53_rev_5_ac_17_b

AC-17(b)

acsc_essential_eight_ml_1_5_4

ACSC-EE-ML1-5.4: Restrict administrative privileges ML1

acsc_essential_eight_ml_1_5_5

ACSC-EE-ML1-5.5: Restrict administrative privileges ML1

acsc_essential_eight_ml_1_8_5

ACSC-EE-ML1-8.5: Regular backups ML1

acsc_essential_eight_ml_1_8_6

ACSC-EE-ML1-8.6: Regular backups ML1

acsc_essential_eight_ml_2_5_5

ACSC-EE-ML2-5.5: Restrict administrative privileges ML2

acsc_essential_eight_ml_2_5_6

ACSC-EE-ML2-5.6: Restrict administrative privileges ML2

acsc_essential_eight_ml_2_5_7

ACSC-EE-ML2-5.7: Restrict administrative privileges ML2

acsc_essential_eight_ml_2_5_8

ACSC-EE-ML2-5.8: Restrict administrative privileges ML2

acsc_essential_eight_ml_2_5_9

ACSC-EE-ML2-5.9: Restrict administrative privileges ML2

acsc_essential_eight_ml_2_8_5

ACSC-EE-ML2-8.5: Regular backups ML2

acsc_essential_eight_ml_2_8_7

ACSC-EE-ML2-8.7: Regular backups ML2

acsc_essential_eight_ml_3_5_11

ACSC-EE-ML3-5.11: Restrict administrative privileges ML3

acsc_essential_eight_ml_3_5_6

ACSC-EE-ML3-5.6: Restrict administrative privileges ML3

acsc_essential_eight_ml_3_5_7

ACSC-EE-ML3-5.7: Restrict administrative privileges ML3

acsc_essential_eight_ml_3_5_8

ACSC-EE-ML3-5.8: Restrict administrative privileges ML3

acsc_essential_eight_ml_3_5_9

ACSC-EE-ML3-5.9: Restrict administrative privileges ML3

acsc_essential_eight_ml_3_8_5

ACSC-EE-ML3-8.5: Regular backups ML3

acsc_essential_eight_ml_3_8_7

ACSC-EE-ML3-8.7: Regular backups ML3

rbi_cyber_security_annex_i_5_1

Annex I (5.1)

rbi_cyber_security_annex_i_7_3

Annex I (7.3)

fedramp_low_rev_4_cm_2

Baseline Configuration (CM-2)

fedramp_moderate_rev_4_cm_2

nist_800_53_rev_4_sc_7

Boundary Protection (SC-7)

fedramp_low_rev_4_sc_7

fedramp_moderate_rev_4_sc_7

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_6

CC6.6 The entity implements logical access security measures to protect against threats from sources outside its system boundaries

soc_2_cc_7_2

CC7.2 The entity monitors system components and the operation of those components for anomalies that are indicative of malicious acts, natural disasters, and errors affecting the entity's ability to meet its objectives; anomalies are analyzed to determine whether they represent security events

nist_800_53_rev_5_cm_9_b

CM-9(b)

ffiec_d_3_pc_am_b_10

D3.PC.Am.B.10

ffiec_d_3_pc_im_b_2

D3.PC.IM.B.2

ffiec_d_3_pc_im_b_1

D3.PC.Im.B.1

ffiec_d_3_pc_im_b_6

D3.PC.Im.B.6

ffiec_d_4_c_co_b_2

D4.C.Co.B.2

nist_csf_de_ae_1

DE.AE-1

nist_800_53_rev_4_ac_4

Information Flow Enforcement (AC-4)

fedramp_moderate_rev_4_ac_4

fedramp_moderate_rev_4_sc_4

Information In Shared Resources (SC-4)

nist_csf_pr_ac_3

PR.AC-3

nist_csf_pr_ac_5

PR.AC-5

nist_csf_pr_pt_4

PR.PT-4

fedramp_low_rev_4_ac_17

Remote Access (AC-17)

nist_800_53_rev_5_sc_7_11

SC-7(11) Restrict Incoming communications Traffic

nist_800_53_rev_5_sc_7_12

SC-7(12) Host-Based Protection

nist_800_53_rev_5_sc_7_16

SC-7(16) Prevent Discovery Of System Components

nist_800_53_rev_5_sc_7_21

SC-7(21) Isolation Of System Components

nist_800_53_rev_5_sc_7_24_b

SC-7(24)(b)

nist_800_53_rev_5_sc_7_25

SC-7(25) Unclassified National Security System Connections

nist_800_53_rev_5_sc_7_26

SC-7(26) Classified National Security System Connections

nist_800_53_rev_5_sc_7_27

SC-7(27) Unclassified Non-National Security System Connections

nist_800_53_rev_5_sc_7_28

SC-7(28) Connections To Public Networks

fedramp_moderate_rev_4_sc_7_3

SC-7(3) Access Points

nist_800_53_rev_4_sc_7_3

nist_800_53_rev_5_sc_7_7

SC-7(7) Split Tunneling For Remote Devices

nist_800_53_rev_5_sc_7_a

SC-7(a)

nist_800_53_rev_5_sc_7_c

SC-7(c)

all_controls_vpc

cisa_cyber_essentials_your_data_2

Your Data-2

cisa_cyber_essentials_your_systems_3

Your Systems-3

VPC security groups should restrict ingress SSH access from 0.0.0.0/0

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: VPC security groups should restrict ingress SSH access from 0.0.0.0/0

Description

Usage

SQL

Tags