steampipe-mod-aws-compliance VS steampipe-plugin-aws

In a prior post I showed how to install Steampipe in AWS CloudShell to instantly query over 460+ resource types from your AWS APIs using SQL, and another post on how to use the Steampipe AWS Compliance mod to assess over 25+ security benchmarks across your AWS accounts.

The Steampipe AWS Compliance mod, is packed with hundreds of controls that check your AWS accounts for compliance with 25 benchmarks including NIST, PCI, HIPAA, SOC2, FedRAMP and more, now includes new controls for AWS CIS v2.0. If you're new to Steampipe, download Steampipe, install and configure the AWS plugin, and run these commands.

The Steampipe AWS Compliance mod, is packed with hundreds of open source controls that evaluate your AWS accounts for compliance with 25 benchmarks (NIST, PCI, HIPAA, etc). The mod now also includes new controls for AWS CIS v2.0.

The Steampipe AWS Compliance mod has more coverage with 21 security benchmarks (e.g. CIS v1.5, PCI, Foundations, NIST 800-53 rev5, etc).

AWS Compliance mod: includes instant compliance reports for CIS, PCI, NIST, HIPAA, SOC2 & more: https://hub.steampipe.io/mods/turbot/aws_compliance

For example, the AWS Compliance Mod layers benchmarks and controls covering 13 compliance standards including CIS, HIPAA, NIST, PCI, FedRAMP, SOC 2 and more. Each benchmark includes a set of pass/fail controls. Each control tests for a compliance recommendation such as "EC2 instances" should be managed by AWS Systems Manager" and reports OK or Alarm.

Steampipe (https://steampipe.io) is an open source CLI to query AWS and more with SQL. The AWS Compliance mod (https://hub.steampipe.io/mods/turbot/aws_compliance) has over 500 controls out of the box covering CIS, PCI, NIST, HIPAA, SOC2 & more you can run in your terminal across all your AWS accounts.

be mindful of its AGPLv3 https://github.com/turbot/steampipe/blob/v0.21.8/LICENSE (AFAIK v0.4.3 is the last MIT release https://github.com/turbot/steampipe/blob/v0.4.3/LICENSE ) and the actual providers are Apache 2 <https://github.com/turbot/steampipe-plugin-aws/blob/v0.131.0...> (but I don't know if provider drift makes them compatible with 0.4 or not)

iasql seems to be AWS only, but good for them for taking this on:

It's a very similar approach querying any of the plugins (AWS, Azure, etc) as it's a common interface to query those APIs with SQL. The AWS plugin is one of the more widely used in the community, along with it's associated mods to visualize resources and compliance to security & ops benchmarks.

~$ steampipe plugin install aws aws [====================================================================] Done Installed plugin: aws@latest v0.78.0 Documentation: https://hub.steampipe.io/plugins/turbot/aws

Setting up CloudTrail is essential to understanding your users' AWS API activity: what happened, by whom and from where. One field in the event logs is source IP address. But that doesn't tell you where in the world those AWS API actions are coming from. In this post we'll show how to use Steampipe with the AWS and ipstack plugins to enrich your CloudTrail events with location information.

In my last post I showed how to install Steampipe and use it to instantly query your AWS APIs using SQL right in AWS CloudShell. For example here's a query that uses the Steampipe AWS plugin to query which AWS IAM users have MFA enabled:

It takes just a few seconds to install Steampipe itself, along with the AWS plugin that maps AWS API calls to Postgres tables.

Hint: We actually have some aws_cost_* tables in active development in this branch. Not ready for release yet, but we're excited about how they are coming together!