The Cloud Posture dashboard summarizes your cloud infrastructure’s overall performance against security guidelines defined by the Center for Internet Security (CIS). To get started monitoring your security posture, refer to Get started with Cloud Security Posture Management or Get started with Kubernetes Security Posture Management.
The Cloud Posture dashboard shows:
- Configuration risk metrics for all monitored cloud accounts and Kubernetes clusters
- Configuration risk metrics for individual cloud accounts and Kubernetes clusters
- Configuration risks grouped by CIS Section (security guideline category)
Cloud Posture dashboard UIedit
At the top of the dashboard, you can switch between the Cloud accounts and Kubernetes cluster views.
The top section of either view summarizes your overall cloud security posture (CSP) by aggregating data from all monitored resources. Three summary cards on the left of this section show Cloud Accounts or Clusters evaluated, Resources evaluated, and Failed Findings. You can click Resources Evaluated or Failed Findings to open the Findings page grouped by resources or filtered for failed findings, respectively.
The remaining summary cards show your overall posture score, and total failed findings grouped by CIS section. Click any CIS section name to view failed findings from that section on the Findings page.
Below the summary section, each row shows the CSP of a single Cloud account or Kubernetes cluster, including its name, when its posture was last evaluated, its compliance score, and failed findings grouped by CIS section. When you begin to monitor a new account or cluster, a new row appears.
FAQ (Frequently Asked Questions)edit
When do newly-enrolled clusters appear on the dashboard?
It can take up to 10 minutes for deployment, resource fetching, evaluation, and data processing before a newly-enrolled cluster appears on the dashboard.
When do unenrolled clusters disappear from the dashboard?
A cluster will disappear as soon as the KSPM integration fetches data while that cluster is not enrolled. The fetch process repeats every four hours, which means a newly unenrolled cluster can take a maximum of four hours to disappear from the dashboard.
Intro to Kibana
ELK for Logs & Metrics