diff --git a/docs/cloud-native-security/cspm-benchmark-rules.asciidoc b/docs/cloud-native-security/cspm-benchmark-rules.asciidoc index 1601f05f0d..466e070e14 100644 --- a/docs/cloud-native-security/cspm-benchmark-rules.asciidoc +++ b/docs/cloud-native-security/cspm-benchmark-rules.asciidoc @@ -12,7 +12,7 @@ Each benchmark rule checks to see if a specific type of resource is configured a * `Ensure the default namespace is not in use` -When benchmark rules are evaluated, the resulting <> data appears on the <>. +When benchmark rules are evaluated, the resulting <> data appears on the <>. To find the Benchmark Integrations page, go to **Rules -> Benchmark rules**. From there, you can view the benchmark rules associated with an existing integration by clicking the integration name. diff --git a/docs/cloud-native-security/cspm-cloud-posture-dashboard.asciidoc b/docs/cloud-native-security/cspm-cloud-posture-dashboard.asciidoc index 044c2f0ecb..d225414cf9 100644 --- a/docs/cloud-native-security/cspm-cloud-posture-dashboard.asciidoc +++ b/docs/cloud-native-security/cspm-cloud-posture-dashboard.asciidoc @@ -1,14 +1,14 @@ [[cspm-posture-dashboard]] // Note: This page is intentionally duplicated by docs/dashboards/cloud-posture.asciidoc. When you update this page, update that page to match. And careful with the anchor links because they should not match. -= Cloud Posture dashboard += Cloud Security Posture dashboard -The Cloud Posture dashboard summarizes your cloud infrastructure's overall performance against <> defined by the Center for Internet Security (CIS). To get started monitoring your security posture, refer to <> or <>. +The Cloud Security Posture dashboard summarizes your cloud infrastructure's overall performance against <> defined by the Center for Internet Security (CIS). To get started monitoring your security posture, refer to <> or <>. [role="screenshot"] image::images/cloud-sec-dash-aws-version.png[The cloud Security dashboard] -The Cloud Posture dashboard shows: +The Cloud Security Posture dashboard shows: * Configuration risk metrics for all monitored cloud accounts and Kubernetes clusters * Configuration risk metrics for individual cloud accounts and Kubernetes clusters @@ -17,12 +17,12 @@ The Cloud Posture dashboard shows: .Requirements [sidebar] -- -* The Cloud Posture dashboard is available to all Elastic Cloud users. For on-prem deployments, it requires an https://www.elastic.co/pricing[Enterprise subscription]. +* The Cloud Security Posture dashboard is available to all Elastic Cloud users. For on-prem deployments, it requires an https://www.elastic.co/pricing[Enterprise subscription]. -- [discrete] [[cspm-posture-dashboard-UI]] -== Cloud Posture dashboard UI +== Cloud Security Posture dashboard UI At the top of the dashboard, you can switch between the Cloud accounts and Kubernetes cluster views. @@ -33,7 +33,7 @@ The remaining summary cards show your overall posture score, and total failed fi 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. [role="screenshot"] -image::images/cloud-sec-dash-aws-version-row.png[A row representing a single cluster in the Cloud Posture dashboard] +image::images/cloud-sec-dash-aws-version-row.png[A row representing a single cluster in the Cloud Security Posture dashboard] [discrete] [[cspm-posture-dashboard-faq]] diff --git a/docs/cloud-native-security/cspm-faq.asciidoc b/docs/cloud-native-security/cspm-faq.asciidoc index a1eace1077..9beb616e77 100644 --- a/docs/cloud-native-security/cspm-faq.asciidoc +++ b/docs/cloud-native-security/cspm-faq.asciidoc @@ -23,11 +23,11 @@ This capability is not currently supported but will be added in future iteration *When do newly enrolled cloud accounts appear on the dashboard?* -After you deploy the CSPM integration, it can take up to 10 minutes for resource fetching, evaluation, and data processing before a newly enrolled account appears on the Cloud Posture dashboard. +After you deploy the CSPM integration, it can take up to 10 minutes for resource fetching, evaluation, and data processing before a newly enrolled account appears on the Cloud Security Posture dashboard. *When do unenrolled cloud accounts disappear from the dashboard?* -Newly unenrolled cloud accounts can take a maximum of 24 hours to disappear from the Cloud Posture dashboard. +Newly unenrolled cloud accounts can take a maximum of 24 hours to disappear from the Cloud Security Posture dashboard. [discrete] diff --git a/docs/cloud-native-security/cspm.asciidoc b/docs/cloud-native-security/cspm.asciidoc index 60562fb0ab..6c036f56e4 100644 --- a/docs/cloud-native-security/cspm.asciidoc +++ b/docs/cloud-native-security/cspm.asciidoc @@ -17,4 +17,4 @@ This feature currently supports Amazon Web Services (AWS) and Google Cloud Platf == How CSPM works Using the read-only credentials you will provide during the setup process, it will evaluate the configuration of resources in your environment every 4 hours. -After each evaluation, the integration sends findings to Elastic. A high-level summary of the findings appears on the <>, and detailed findings appear on the <>. +After each evaluation, the integration sends findings to Elastic. A high-level summary of the findings appears on the <>, and detailed findings appear on the <>. diff --git a/docs/cloud-native-security/images/cnvm-findings-grouped.png b/docs/cloud-native-security/images/cnvm-findings-grouped.png index 7e6b7345e0..0f1525f725 100644 Binary files a/docs/cloud-native-security/images/cnvm-findings-grouped.png and b/docs/cloud-native-security/images/cnvm-findings-grouped.png differ diff --git a/docs/cloud-native-security/images/cnvm-findings-page.png b/docs/cloud-native-security/images/cnvm-findings-page.png index 707ab74181..f55908df66 100644 Binary files a/docs/cloud-native-security/images/cnvm-findings-page.png and b/docs/cloud-native-security/images/cnvm-findings-page.png differ diff --git a/docs/cloud-native-security/images/findings-page.png b/docs/cloud-native-security/images/findings-page.png index 2bf9cb2f5e..ecddcf3485 100644 Binary files a/docs/cloud-native-security/images/findings-page.png and b/docs/cloud-native-security/images/findings-page.png differ diff --git a/docs/cloud-native-security/images/vuln-management-dashboard.png b/docs/cloud-native-security/images/vuln-management-dashboard.png index 0bc5983962..063312fc0f 100644 Binary files a/docs/cloud-native-security/images/vuln-management-dashboard.png and b/docs/cloud-native-security/images/vuln-management-dashboard.png differ diff --git a/docs/cloud-native-security/kspm-benchmark-rules.asciidoc b/docs/cloud-native-security/kspm-benchmark-rules.asciidoc index 1fd397e6a0..2a41478692 100644 --- a/docs/cloud-native-security/kspm-benchmark-rules.asciidoc +++ b/docs/cloud-native-security/kspm-benchmark-rules.asciidoc @@ -12,7 +12,7 @@ Each benchmark rule checks to see if a specific type of resource is configured a * `Ensure the default namespace is not in use` -When benchmark rules are evaluated, the resulting <> data appears on the <>. +When benchmark rules are evaluated, the resulting <> data appears on the <>. To find the Benchmark Integrations page, go to **Rules -> Benchmark rules**. From there, you can view the benchmark rules associated with an existing integration by clicking the integration name. diff --git a/docs/cloud-native-security/kspm-cloud-posture-dashboard.asciidoc b/docs/cloud-native-security/kspm-cloud-posture-dashboard.asciidoc index ceeaf37890..307e97771a 100644 --- a/docs/cloud-native-security/kspm-cloud-posture-dashboard.asciidoc +++ b/docs/cloud-native-security/kspm-cloud-posture-dashboard.asciidoc @@ -1,14 +1,14 @@ [[cloud-nat-sec-posture-dashboard]] // Note: This page is intentionally duplicated by docs/dashboards/cloud-posture.asciidoc. When you update this page, update that page to match. And careful with the anchor links because they should not match. -= Cloud Posture dashboard += Cloud Security Posture dashboard -The Cloud Posture dashboard summarizes your cloud infrastructure's overall performance against <> defined by the Center for Internet Security (CIS). To start collecting this data, refer to <> or <>. +The Cloud Security Posture dashboard summarizes your cloud infrastructure's overall performance against <> defined by the Center for Internet Security (CIS). To start collecting this data, refer to <> or <>. [role="screenshot"] image::images/cloud-sec-dashboard.png[The cloud Security dashboard] -The Cloud Posture dashboard shows: +The Cloud Security Posture dashboard shows: * Configuration risk metrics for all monitored cloud accounts and Kubernetes clusters * Configuration risk metrics for individual cloud accounts and Kubernetes clusters @@ -17,12 +17,12 @@ The Cloud Posture dashboard shows: .Requirements [sidebar] -- -* The Cloud Posture dashboard is available to all Elastic Cloud users. For on-prem deployments, it requires an https://www.elastic.co/pricing[Enterprise subscription]. +* The Cloud Security Posture dashboard is available to all Elastic Cloud users. For on-prem deployments, it requires an https://www.elastic.co/pricing[Enterprise subscription]. -- [discrete] [[cloud-nat-sec-posture-dashboard-UI]] -== Cloud Posture dashboard UI +== Cloud Security Posture dashboard UI At the top of the dashboard, you can switch between the Cloud accounts and Kubernetes cluster views. @@ -33,7 +33,7 @@ The remaining summary cards show your overall posture score, and total failed fi 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. [role="screenshot"] -image::images/cloud-sec-dashboard-individual-row.png[A row representing a single cluster in the Cloud Posture dashboard] +image::images/cloud-sec-dashboard-individual-row.png[A row representing a single cluster in the Cloud Security Posture dashboard] [discrete] [[cloud-nat-sec-posture-dashboard-faq]] diff --git a/docs/cloud-native-security/kspm-faq.asciidoc b/docs/cloud-native-security/kspm-faq.asciidoc index 5c7c2f203d..7710d026fe 100644 --- a/docs/cloud-native-security/kspm-faq.asciidoc +++ b/docs/cloud-native-security/kspm-faq.asciidoc @@ -24,11 +24,11 @@ This capability is not currently supported but will be added in future iteration *When do newly enrolled cloud accounts appear on the dashboard?* -After you deploy the CSPM integration, it can take up to 10 minutes for resource fetching, evaluation, and data processing before a newly enrolled account appears on the Cloud Posture dashboard. +After you deploy the CSPM integration, it can take up to 10 minutes for resource fetching, evaluation, and data processing before a newly enrolled account appears on the Cloud Security Posture dashboard. *When do unenrolled cloud accounts disappear from the dashboard?* -Newly unenrolled cloud accounts can take a maximum of 24 hours to disappear from the Cloud Posture dashboard. +Newly unenrolled cloud accounts can take a maximum of 24 hours to disappear from the Cloud Security Posture dashboard. [[kspm-faq]] diff --git a/docs/cloud-native-security/kspm-get-started.asciidoc b/docs/cloud-native-security/kspm-get-started.asciidoc index 2549f7aa76..9d3009f0e6 100644 --- a/docs/cloud-native-security/kspm-get-started.asciidoc +++ b/docs/cloud-native-security/kspm-get-started.asciidoc @@ -34,7 +34,7 @@ The instructions differ depending on whether you're installing on EKS or on unma [discrete] === Name your integration and select a Kubernetes Deployment type -1. Go to *Dashboards -> Cloud Posture*. +1. Go to *Dashboards -> Cloud Security Posture*. 2. Click *Add a KSPM integration*. 3. Read the integration's description to understand how it works. Then, click {integrations-docs}/cloud_security_posture[*Add Kubernetes Security Posture Management*]. 4. Name your integration. Use a name that matches the purpose or team of the cluster(s) you want to monitor, for example, `IT-dev-k8s-clusters`. @@ -220,7 +220,7 @@ The *Add agent* wizard helps you deploy the KSPM integration on the Kubernetes c 1. Download the manifest and make any necessary revisions to its configuration to suit the needs of your environment. 2. Apply the manifest using the `kubectl apply -f` command. For example: `kubectl apply -f elastic-agent-managed-kubernetes.yaml` -After a few minutes, a message confirming the {agent} enrollment appears, followed by a message confirming that data is incoming. You can then click *View assets* to see where the newly-collected configuration information appears throughout {kib}, including the <> and the <>. +After a few minutes, a message confirming the {agent} enrollment appears, followed by a message confirming that data is incoming. You can then click *View assets* to see where the newly-collected configuration information appears throughout {kib}, including the <> and the <>. [discrete] @@ -233,7 +233,7 @@ Follow these steps to deploy the KSPM integration to unmanaged clusters. Keep in === Configure the KSPM integration To install the integration on unmanaged clusters: -. Go to *Dashboards -> Cloud Posture*. +. Go to *Dashboards -> Cloud Security Posture*. . Click *Add a KSPM integration*. . Read the integration's description to understand how it works. Then, click {integrations-docs}/cloud_security_posture[*Add Kubernetes Security Posture Management*]. . Name your integration. Use a name that matches the purpose or team of the cluster(s) you want to monitor, for example, `IT-dev-k8s-clusters`. @@ -254,7 +254,7 @@ The *Add agent* wizard helps you deploy the KSPM integration on the Kubernetes c 1. Download the manifest and make any necessary revisions to its configuration to suit the needs of your environment. 2. Apply the manifest using the `kubectl apply -f` command. For example: `kubectl apply -f elastic-agent-managed-kubernetes.yaml` -After a few minutes, a message confirming the {agent} enrollment appears, followed by a message confirming that data is incoming. You can then click *View assets* to see where the newly-collected configuration information appears throughout {kib}, including the <> and the <>. +After a few minutes, a message confirming the {agent} enrollment appears, followed by a message confirming that data is incoming. You can then click *View assets* to see where the newly-collected configuration information appears throughout {kib}, including the <> and the <>. [discrete] [[kspm-eck]] diff --git a/docs/cloud-native-security/kspm.asciidoc b/docs/cloud-native-security/kspm.asciidoc index d3996cdcf2..482e37aa85 100644 --- a/docs/cloud-native-security/kspm.asciidoc +++ b/docs/cloud-native-security/kspm.asciidoc @@ -20,7 +20,7 @@ This integration supports Amazon EKS and unmanaged Kubernetes clusters. For setu == How KSPM works . When you add a KSPM integration, it generates a Kubernetes manifest. When applied to a cluster, the manifest deploys an {agent} as a https://kubernetes.io/docs/concepts/workloads/controllers/daemonset[DaemonSet] to ensure all nodes are evaluated. . Upon deployment, the integration immediately assesses the security posture of your Kubernetes resources. The evaluation process repeats every four hours. -. After each evaluation, the integration sends findings to {es}. Findings appear on the <> and the <> page. +. After each evaluation, the integration sends findings to {es}. Findings appear on the <> and the <> page. [discrete] [[kspm-use-cases]] @@ -38,7 +38,7 @@ The KSPM integration helps you to: To identify and remediate failed failed findings: -. Go to the <>. +. Go to the <>. . Click *View all failed findings*, either for an individual cluster or for all monitored clusters. . Click a failed finding. The findings flyout opens. . Follow the steps under *Remediation* to correct the misconfiguration. @@ -61,7 +61,7 @@ To identify the Kubernetes resources generating the most failed findings: To identify risks in particular CIS sections: -. Go to the <> (*Dashboards -> Cloud Posture*). +. Go to the <> (*Dashboards -> Cloud Security Posture*). . In the Failed findings by CIS section widget, click the name of a CIS section to view all failed findings for that section. Alternatively: diff --git a/docs/cloud-native-security/security-posture-management.asciidoc b/docs/cloud-native-security/security-posture-management.asciidoc index 9546c40ac5..8d6b12481e 100644 --- a/docs/cloud-native-security/security-posture-management.asciidoc +++ b/docs/cloud-native-security/security-posture-management.asciidoc @@ -23,14 +23,14 @@ Using the data generated by these features, you can: *Identify and secure misconfigured infrastructure:* -. Go to the Cloud Posture dashboard (*Dashboards > Cloud Posture*). +. Go to the Cloud Security Posture dashboard (*Dashboards > Cloud Security Posture*). . Click *View all failed findings*, either for an individual resource or a group of resources. . Click a failed finding to open the Findings flyout. . Follow the steps under Remediation to fix the misconfiguration. *Identify the CIS Sections (security best practice categories) with which your resources are least compliant:* -. Go to the Cloud Posture dashboard (*Dashboards > Cloud Posture*). +. Go to the Cloud Security Posture dashboard (*Dashboards > Cloud Security Posture*). . Do one of the following: .. Under Failed findings by CIS section, click the name of a CIS section to view all failed findings from that section. .. 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. diff --git a/docs/dashboards/cloud-posture.asciidoc b/docs/dashboards/cloud-posture.asciidoc index e04f945498..5859b9ed13 100644 --- a/docs/dashboards/cloud-posture.asciidoc +++ b/docs/dashboards/cloud-posture.asciidoc @@ -1,13 +1,13 @@ [[cloud-posture-dashboard]] // Note: This page is intentionally duplicated by docs/cloud-native-security/cloud-nat-sec-posture.asciidoc. When you update this page, update that page to match. And careful with the anchor links because they should not match. -= Cloud Posture dashboard -The Cloud Posture dashboard summarizes your cloud infrastructure's overall performance against <> defined by the Center for Internet Security (CIS). To start collecting this data, refer to <> or <>. += Cloud Security Posture dashboard +The Cloud Security Posture dashboard summarizes your cloud infrastructure's overall performance against <> defined by the Center for Internet Security (CIS). To start collecting this data, refer to <> or <>. [role="screenshot"] image::images/cloud-sec-dashboard.png[The cloud Security dashboard] -The Cloud Posture dashboard shows: +The Cloud Security Posture dashboard shows: * Configuration risk metrics for all monitored cloud accounts and Kubernetes clusters * Configuration risk metrics for individual cloud accounts and Kubernetes clusters @@ -16,12 +16,12 @@ The Cloud Posture dashboard shows: .Requirements [sidebar] -- -* The Cloud Posture dashboard is available to all Elastic Cloud users. For on-prem deployments, it requires an https://www.elastic.co/pricing[Enterprise subscription]. +* The Cloud Security Posture dashboard is available to all Elastic Cloud users. For on-prem deployments, it requires an https://www.elastic.co/pricing[Enterprise subscription]. -- [discrete] [[cloud-posture-dashboard-UI]] -=== Cloud Posture dashboard UI +=== Cloud Security Posture dashboard UI At the top of the dashboard, you can switch between the Cloud accounts and Kubernetes cluster views. @@ -32,7 +32,7 @@ The remaining summary cards show your overall posture score, and total failed fi 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. [role="screenshot"] -image::images/cloud-sec-dashboard-individual-row.png[A row representing a single cluster in the Cloud Posture dashboard] +image::images/cloud-sec-dashboard-individual-row.png[A row representing a single cluster in the Cloud Security Posture dashboard] [discrete] [[cloud-posture-dashboard-faq]] diff --git a/docs/dashboards/images/kubernetes-dashboard.png b/docs/dashboards/images/kubernetes-dashboard.png index 9b4b73fd70..43e4a516a2 100644 Binary files a/docs/dashboards/images/kubernetes-dashboard.png and b/docs/dashboards/images/kubernetes-dashboard.png differ