aws_compliance

AWS Compliance

Ensure that the actual configuration of a Cloud Formation stack differs, or has drifted, from the expected configuration, a stack is considered to have drifted if one or more of its resources differ from their expected configuration.

cloudformation_stack_drift_detection_check

pci_dss_v321_requirement_1_2_2_b

1.2.2.b Examine router configurations to verify they are synchronized—for example, the running (or active) configuration matches the start-up configuration (used when machines are booted)

pci_dss_v321_requirement_2_2_a

2.2.a Examine the organization's system configuration standards for all types of system components and verify the system configuration standards are consistent with industry-accepted hardening standards

pci_dss_v321_requirement_2_2_d

2.2.d Verify that system configuration standards include the procedures like changing of all vendor-supplied defaults and elimination of unnecessary default accounts etc. for all types of system components

all_controls_cloudformation

CloudFormation

nist_csf_pr_ip_1

PR.IP-1

CloudFormation stacks differ from the expected configuration

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: CloudFormation stacks differ from the expected configuration

Description

Usage

SQL

Tags