[Serverless] Removes D4C documentation (#6236)

* Removes D4C documentation from serverless * minor fix * incorporates Nick's review * Update docs/serverless/cloud-native-security/vuln-management-dashboard-dash.asciidoc Co-authored-by: natasha-moore-elastic <[email protected]> * Update docs/serverless/dashboards/vuln-management-dashboard-dash.asciidoc Co-authored-by: natasha-moore-elastic <[email protected]> --------- Co-authored-by: natasha-moore-elastic <[email protected]>
elastic · Nov 27, 2024 · 44b15bd · 44b15bd
1 parent 5fb37a6
commit 44b15bd
Show file tree

Hide file tree

Showing 13 changed files with 3 additions and 488 deletions.
diff --git a/docs/serverless/billing.asciidoc b/docs/serverless/billing.asciidoc
@@ -34,7 +34,7 @@ You pay based on the number of protected endpoints you configure with the {elast
 Cloud Protection is an _optional_ add-on to Security Analytics that provides value-added protection capabilities for cloud assets. Cloud Protection is available in two tiers of carefully selected features to enable common cloud security operations:
 
 * **Cloud Protection Essentials** — Protects your cloud workloads, continuously tracks posture of your cloud assets, and helps you manage risks by detecting configuration issues per CIS benchmarks.
-* **Cloud Protection Complete** — Adds response capabilities and configuration drift prevention for Cloud Workloads.
+* **Cloud Protection Complete** — Adds response capabilities.
 
 Your total cost depends on the number of protected cloud workloads and other billable cloud assets you configure for use with Elastic Cloud Security.
 
@@ -60,8 +60,6 @@ For <<security-kspm,KSPM>>, billing is based on how many Kubernetes nodes (`agen
 
 For <<security-vuln-management-overview,CNVM>>, billing is based on how many cloud assets (`cloud.instance.id` s) you monitor.
 
-For <<security-d4c-overview,D4C>>, billing is based on how many agents (`agent.id` s) you use.
-
 Logs, events, alerts, and configuration data ingested into your security project are billed using the **Ingest** and **Retention** pricing described above.
 
 For more details about {elastic-sec} serverless project rates and billable assets, refer to Cloud Protection in the https://cloud.elastic.co/cloud-pricing-table?productType=serverless&project=security[Elastic Cloud pricing table].
diff --git a/docs/serverless/cloud-native-security/cloud-native-security-overview.asciidoc b/docs/serverless/cloud-native-security/cloud-native-security-overview.asciidoc
@@ -34,14 +34,6 @@ Scans your cloud workloads for known vulnerabilities. When it finds a vulnerabil
 
 <<security-vuln-management-overview,Read the CNVM docs>>.
 
-[discrete]
-[[security-cloud-native-security-overview-cloud-workload-protection-for-kubernetes]]
-== Cloud Workload Protection for Kubernetes
-
-Provides cloud-native runtime protections for containerized environments by identifying and (optionally) blocking unexpected system behavior in Kubernetes containers. These capabilities are sometimes referred to as container drift detection and prevention. The solution also captures detailed process and file telemetry from monitored containers, allowing you to set up custom alerts and protection rules.
-
-<<security-d4c-overview,Read the CWP for Kubernetes docs>>.
-
 [discrete]
 [[security-cloud-native-security-overview-cloud-workload-protection-for-vms]]
 == Cloud Workload Protection for VMs

diff --git a/docs/serverless/cloud-native-security/cloud-workload-protection.asciidoc b/docs/serverless/cloud-native-security/cloud-workload-protection.asciidoc
@@ -21,5 +21,4 @@ To continue setting up your cloud workload protection, learn more about:
 
 * <<security-install-edr,**Getting started with {elastic-defend}**>>: configure {elastic-defend} to protect your hosts. Be sure to select one of the "Cloud workloads" presets if you want to collect session data by default, including process, file, and network telemetry.
 * <<security-session-view,**Session view**>>: examine Linux process data organized in a tree-like structure according to the Linux logical event model, with processes organized by parentage and time of execution. Use it to monitor and investigate session activity, and to understand user and service behavior on your Linux infrastructure.
-* <<security-kubernetes-dashboard-dash,**The Kubernetes dashboard**>>: Explore an overview of your protected Kubernetes clusters, and drill down into individual sessions within your Kubernetes infrastructure.
 * <<security-environment-variable-capture,**Environment variable capture**>>: Capture the environment variables associated with process events, such as `PATH`, `LD_PRELOAD`, or `USER`.
diff --git a/docs/serverless/cloud-native-security/d4c-get-started.asciidoc b/docs/serverless/cloud-native-security/d4c-get-started.asciidoc
diff --git a/docs/serverless/cloud-native-security/d4c-kubernetes-dashboard-dash.asciidoc b/docs/serverless/cloud-native-security/d4c-kubernetes-dashboard-dash.asciidoc
diff --git a/docs/serverless/cloud-native-security/d4c-overview.asciidoc b/docs/serverless/cloud-native-security/d4c-overview.asciidoc
diff --git a/docs/serverless/cloud-native-security/d4c-policy-guide.asciidoc b/docs/serverless/cloud-native-security/d4c-policy-guide.asciidoc