Type to search.

Security posture management overview

Serverless Security

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    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.

Elastic’s Cloud Security Posture Management (CSPM) and Kubernetes Security Posture Management (KSPM) features help you discover and evaluate the services and resources in your cloud environment — like storage, compute, IAM, and more — against security guidelines defined by the Center for Internet Security (CIS). They help you identify and remediate configuration risks that could undermine the confidentiality, integrity, and availability of your cloud assets, such as publicly exposed storage buckets or overly permissive networking objects.

The KSPM feature assesses the security of your Kubernetes assets, while the CSPM feature assesses the security of your AWS resources such as storage, compute, IAM, and more.

For setup instructions, refer to:

Using the data generated by these features, you can:

Identify and secure misconfigured infrastructure:

  1. Find Cloud Security Posture in the navigation menu or use the global search field.
  2. Click View all failed findings, either for an individual resource or a group of resources.
  3. Click a failed finding to open the Findings flyout.
  4. Follow the steps under Remediation to fix the misconfiguration.

Identify the CIS Sections (security best practice categories) with which your resources are least compliant:

  1. Find Cloud Security Posture in the navigation menu or use the global search field.

  2. Do one of the following:

    1. Under Failed findings by CIS section, click the name of a CIS section to view all failed findings from that section.
    2. Go to the Findings page and filter by the rule.section field. For example, search for rule.section : API Server to view findings from the API Server category.

Identify your least compliant cloud resources

  1. Go to the Findings page.
  2. Click the Group by menu near the search box, and select Resource to sort resources by their number of failed findings.
  3. Click a resource ID to view associated findings.