Loading

AWS Security Hub Integration for Elastic

Version 0.1.0 (View all)
Subscription level
What's this?
Basic
Developed by
What's this?
Elastic
Ingestion method(s) API
Minimum Kibana version(s) 9.3.0
The AWS Security Hub integration v0.1.0 is in beta

To use beta integrations, go to the Integrations page in Kibana, scroll down, and toggle on the Display beta integrations option.

The AWS Security Hub integration with Elastic enables the collection of findings for monitoring and analysis. This valuable data can be leveraged within Elastic to analyze security signals from multiple sources, such as posture management, vulnerability management (Amazon Inspector), sensitive data identification (Amazon Macie), and threat detection (Amazon GuardDuty).

This integration utilizes the AWS Security Hub API to collect Findings in the OCSF format.

The AWS Security Hub integration uses the REST API. It uses the GetFindingsV2 to collect findings in OCSF format.

The finding data stream uses the /findingsv2 endpoint to gather all findings starting from the configured Initial Interval. Subsequently, it fetches the recent findings available at each specified Interval.

The AWS Security Hub integration collects logs of the following types:

Integrating AWS Security Hub with Elastic SIEM provides a comprehensive view of the security state of your AWS resources. Leveraging AWS Security Hub integration helps you analyze security trends to identify and prioritize security issues across your AWS environment. It also adds support for the Elastic Cloud Security Workflow, allowing users to explore insights via the Elastic Vulnerability Findings page.

AWS Security Hub integration adds Elastic latest transforms. For more details, check the Transform setup and requirements.

Enable AWS Security Hub in your environment. For more detail, refer to the link here.

Users can authenticate using permanent security credentials, as well as temporary security credentials. They can also select Shared Credential File, Credential Profile Name to retrieve credentials. Additionally, they can use Role ARN to specify which AWS IAM role to assume for generating temporary credentials. An External ID can also be provided when assuming a role in another account.

The credentials must have permission to perform the securityhub:GetFindings action.

Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions. You can install only one Elastic Agent per host.

Elastic Agent is required to stream data from the syslog or log file receiver and ship the data to Elastic, where the events will then be processed via the integration's ingest pipelines.

Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. Agentless deployments provide a means to ingest data while avoiding the orchestration, management, and maintenance needs associated with standard ingest infrastructure. Using an agentless deployment makes manual agent deployment unnecessary, allowing you to focus on your data instead of the agent that collects it.

For more information, refer to Agentless integrations and Agentless integrations FAQ

  1. In the top search bar in Kibana, search for Integrations.

  2. In the search bar, type AWS Security Hub.

  3. Select the AWS Security Hub integration from the search results.

  4. Select Add AWS Security Hub to add the integration.

  5. Enable and configure Collect AWS Security Hub logs via API:

    • Configure AWS Authentication parameters and set the AWS Region and Top Level Domain. Adjust the integration configuration parameters as needed, including the Initial Interval, Interval, Batch Size etc. to enable data collection.
  6. Select Save and continue to save the integration.

  1. In the top search bar in Kibana, search for Dashboards.
  2. In the search bar, type AWS Security Hub.
  3. Select a dashboard for the dataset you are collecting, and verify the dashboard information is populated.
  1. In the top search bar in Kibana, search for Transforms.
  2. Select the Data / Transforms from the search results.
  3. In the search bar, type aws_securityhub.
  4. All transforms from the search results should indicate Healthy under the Health column.

For help with Elastic ingest tools, check Common problems.

For more information on architectures that can be used for scaling this integration, check the Ingest Architectures documentation.

These inputs are used in this integration:

This integration dataset uses the following APIs:

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.