Loading

Inspector

Version 7.0.0 (View all)
Managed integration release status
Subscription level
What's this?
Basic
Ingestion method(s) API, AWS CloudWatch, AWS S3
Minimum Kibana version(s) 9.4.0
Important - Managed integrations on Elastic Cloud Hosted

You can use this integration as an Elastic Managed integration on Elastic Cloud Hosted deployments running this version or later.

The Amazon Inspector integration collects and parses data from Amazon Inspector Findings REST APIs.

Important

Extra AWS charges on API requests will be generated by this integration. Check API Requests for more details.

This module is tested against Amazon Inspector API version 2.0.

Agentless integrations allow you to collect data without having to manage Elastic Agent in your cloud. They make manual agent deployment unnecessary, so you can focus on your data instead of the agent that collects it. For more information, refer to Agentless integrations and the Agentless integrations FAQ.

Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. This functionality is in beta and is subject to change. Beta features are not subject to the support SLA of official GA features.

  1. Login to https://console.aws.amazon.com/.
  2. Go to https://console.aws.amazon.com/iam/ to access the IAM console.
  3. On the navigation menu, choose Users.
  4. Choose your IAM user name.
  5. Select Create access key from the Security Credentials tab.
  6. To see the new access key, choose Show.
  • For the current integration package, it is compulsory to add Secret Access Key and Access Key ID.
  • This data stream doesn't support setting a Role ARN.
  • Ensure your IAM has the inspector2:ListFindings permission granted. Without this permission, API requests will be denied.

Version 4.0.0 of the AWS integration adds support for Elastic Cloud Security workflow. The enhancement enables the users of the AWS Inspector integration to ingest their enriched vulnerabilities from the Amazon Inspector platform into Elastic and get insights directly from the Elastic Vulnerability Findings page. This update adds Elastic Latest Transform which copies the latest vulnerability findings from source indices matching the pattern logs-aws.inspector-* into new destination indices matching the pattern security_solution-aws.vulnerability_latest-*. The Elastic Vulnerability Findings page will display vulnerabilities based on the destination indices.

For existing users of the AWS integration, before upgrading to 4.0.0 please ensure the following requirements are met:

  1. Users need Elastic Security solution which has requirements documented here.
  2. To use transforms, users must have:
    • at least one transform node,
    • management features visible in the Kibana space, and
    • security privileges that:
      • grant use of transforms, and
      • grant access to source and destination indices For more details on Transform Setup, refer to the link here
  3. Because the latest copy of vulnerabilities is now indexed in two places, that is, in both source and destination indices, users must anticipate storage requirements accordingly.

The integration maps the Amazon Inspector finding status (aws.inspector.status) to the vulnerability.status field so the Vulnerability Findings page can distinguish active from remediated findings. vulnerability.status is a package-defined field that aligns with the ECS vulnerability.status field (added in ECS 9.5):

aws.inspector.status vulnerability.status
ACTIVE open
SUPPRESSED open
CLOSED fixed

CLOSED findings are mapped to fixed. SUPPRESSED findings are mapped to open because the vulnerability is still present on the resource; suppression in Amazon Inspector is a triage decision (for example, via a suppression rule) rather than a remediation.

Note

the Vulnerability Findings page does not currently filter on vulnerability.status, so by default all findings are shown regardless of status. To exclude remediated findings, add a filter such as NOT vulnerability.status: fixed. To also hide suppressed findings, add NOT aws.inspector.status: SUPPRESSED.

This is the Inspector data stream.

ECS Field Reference

Please refer to the following document for detailed information on ECS fields.

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.