AWS Security Hub CSPM
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless Security
Generally available
Stack
9.3+
Generally available since 9.3
This integration uses the AWS Security Hub API to ingest misconfiguration findings which appear in Elastic’s native vulnerability workflows. This page explains how to make data from the AWS Security Hub CSPM integration appear in the following places within Elastic Security:
- Findings page: Data appears on the Misconfigurations tab.
- Alert and Entity details flyouts: Applicable data appears in the Insights section.
In order for AWS Security Hub CSPM data to appear in these workflows:
- Follow the steps to set up the AWS Security Hub CSPM integration.
- Make sure the integration version is at least 2.31.1.
- Ensure you have
readprivileges for thesecurity_solution-*.misconfiguration_latestindex. - While configuring the AWS Security Hub CSPM integration, turn on Collect AWS Security Hub CSPM Findings from AWS. We recommend you also set the Initial Interval value to
2160h(equivalent to 90 days) to ingest existing logs.
You can ingest data from the AWS Security Hub CSPM integration for other purposes without following these steps.