IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Ingest CNCF Falco data Ingest Wiz data »
Elastic Docs ›Elastic Security Solution [8.16] ›Cloud Security ›Ingest third-party cloud security data

Ingest AWS Security Hub data

edit

Ingest AWS Security Hub data

edit

In order to enrich your Elastic Security workflows with third-party cloud security posture data collected by AWS Security Hub:

  • Follow the steps to set up the AWS Security Hub integration.
  • Make sure the integration version is at least 2.31.1.
  • Ensure you have read privileges for the security_solution-*.misconfiguration_latest index.
  • While configuring the AWS Security Hub integration, turn on Collect AWS Security Hub Findings from AWS. We recommend you also set the Initial Interval value to 2160h (equivalent to 90 days) to ingest existing logs.
AWS Security Hub integration settings showing the findings toggle

After you’ve completed these steps, AWS Security Hub data will appear on the Misconfigurations tab of the Findings page.

Any available findings data will also appear in the entity details flyouts for related alerts. If alerts are present for a user or host that has findings data from AWS Security Hub, the findings will appear on the users, and hosts flyouts.

« Ingest CNCF Falco data Ingest Wiz data »