Skip to content

elastic/cloudbeat

Folders and files

NameName
Last commit message
Last commit date

Latest commit

4749220 · Mar 24, 2025
Jan 27, 2025
Feb 18, 2025
Mar 24, 2025
Apr 22, 2024
Mar 11, 2025
Feb 12, 2025
Mar 13, 2025
Mar 12, 2025
Feb 11, 2025
Mar 24, 2025
Feb 5, 2024
Mar 4, 2025
Jan 30, 2025
Mar 11, 2025
Oct 10, 2024
Jan 30, 2025
Apr 3, 2023
May 23, 2023
Sep 9, 2024
Feb 11, 2025
Feb 12, 2025
Feb 7, 2025
Dec 11, 2024
Mar 20, 2025
Mar 7, 2022
Nov 12, 2024
Oct 30, 2023
Sep 24, 2024
Feb 14, 2022
Jan 13, 2025
Apr 22, 2024
Mar 3, 2025
Mar 3, 2025
Oct 24, 2024
Jan 17, 2025
Feb 4, 2024
Jun 27, 2023
Jun 17, 2024
Dec 7, 2022

Repository files navigation

Coverage Status Go Report Card Build status

Cloudbeat

Cloudbeat is a tool that analyzes cloud assets for security compliance and sends findings to Elasticsearch. It is designed to be used as part of the Cloud Security plugin in Kibana.

CSP Security Policies

Cloudbeat uses security policies from the Security Policies directory to evaluate cloud resources.

Getting Started

To get started with Cloud Security on your cluster, please refer to our documentation:


Deployment

To run Cloudbeat, you need to have Elastic Stack (Elasticsearch, Kibana, etc) running (locally/cloud). See our Elastic Stack Deployment options documentation.

Once your Elastic Stack is deployed, you can proceed with the deployment of Cloudbeat. For deployment instructions, see Cloudbeat Deployment options.

Development

Prerequisites

We use Hermit to manage our development tooling. Please refer to our README for detailed instructions on setting it up.


Note If you are a developer or contributor, or if you are looking for additional information, please visit our development documentation