add missing duplicate pages

Author: colleenmcginnis

docs/serverless/cloud-native-security/benchmark-rules.asciidoc

@@ -4,6 +4,10 @@
 :description: Review the cloud security benchmark rules used by the CSPM and KSPM integrations.
 :keywords: serverless, security, overview, cloud security
 
+:append:
+
+// tag::content[]
+
 preview:[]
 
 The Benchmarks page lets you view the cloud security posture (CSP) benchmarks for the <<security-cspm,Cloud security posture management>> (CSPM) and <<security-kspm,Kubernetes security posture management>> (KSPM) integrations.
@@ -12,7 +16,7 @@ The Benchmarks page lets you view the cloud security posture (CSP) benchmarks fo
 image::images/benchmark-rules/-cloud-native-security-benchmark-rules.png[Benchmark rules page]
 
 [discrete]
-[[security-benchmark-rules-what-are-benchmarks]]
+[id="security-benchmark-rules-what-are-benchmarks{append}"]
 == What are benchmarks?
 
 Each benchmark contains benchmark rules which are used by the CSPM and KSPM integrations to identify configuration risks in your cloud infrastructure. There are different benchmarks for different cloud services, such as AWS, GCP, or Azure. They are based on the Center for Internet Security's (CIS) https://www.cisecurity.org/cis-benchmarks/[secure configuration benchmarks].
@@ -32,7 +36,7 @@ Benchmark rules are not editable.
 ====
 
 [discrete]
-[[security-benchmark-rules-review-your-benchmarks]]
+[id="security-benchmark-rules-review-your-benchmarks{append}"]
 == Review your benchmarks
 
 To access your active benchmarks, go to **Rules -> Benchmarks**. From there, you can click a benchmark's name to view the benchmark rules associated with it. You can click a benchmark rule's name to see details including information about how to remediate it, and related links.
@@ -45,9 +49,13 @@ Disabling a benchmark rule automatically disables any associated detection rules
 ====
 
 [discrete]
-[[security-benchmark-rules-how-benchmark-rules-work]]
+[id="security-benchmark-rules-how-benchmark-rules-work{append}"]
 == How benchmark rules work
 
 . When a security posture management integration is deployed, and every four hours after that, {agent} fetches relevant cloud resources.
 . After resources are fetched, they are evaluated against all applicable enabled benchmark rules.
 . Finding values of `pass` or `fail` indicate whether the standards defined by benchmark rules were met.
+
+// end::content[]
+
+:append!:

docs/serverless/cloud-native-security/cspm-cloud-posture-dashboard-dash.asciidoc

@@ -0,0 +1,8 @@
+:append: -cspm
+
+[id="security-cloud-posture-dashboard-dash{append}"]
+= Cloud Security Posture dashboard
+
+include::../dashboards/cloud-posture-dashboard-dash.asciidoc[tag=content]
+
+:append!:

docs/serverless/cloud-native-security/cspm-findings-page.asciidoc

@@ -4,6 +4,10 @@
 :description: Review your cloud security posture management data.
 :keywords: serverless, security, overview, cloud security
 
+:append:
+
+// tag::content[]
+
 preview:[]
 
 The **Misconfigurations** tab on the Findings page displays the configuration risks identified by the <<security-cspm,CSPM>> and <<security-kspm,KSPM>> integrations.
@@ -12,19 +16,19 @@ The **Misconfigurations** tab on the Findings page displays the configuration ri
 image::images/findings-page/-cloud-native-security-findings-page.png[Findings page]
 
 [discrete]
-[[cspm-findings-page-what-are-findings]]
+[id="cspm-findings-page-what-are-findings{append}"]
 == What are CSPM and KSPM findings?
 
 CSPM and KSPM findings indicate whether a given resource passed or failed evaluation against a specific security guideline. Each finding includes metadata about the resource evaluated and the security guideline used to evaluate it. Each finding's result (`pass` or `fail`) indicates whether a particular part of your infrastructure meets a security guideline.
 
 [discrete]
-[[cspm-findings-page-group-filter]]
+[id="cspm-findings-page-group-filter{append}"]
 == Group and filter findings
 
 By default, the Findings page lists all findings, without grouping or filtering.
 
 [discrete]
-[[security-cspm-findings-page-group-findings]]
+[id="security-cspm-findings-page-group-findings{append}"]
 === Group findings
 
 Click **Group findings by** to group your data by a field. Select one of the suggested fields or **Custom field** to choose your own. You can select up to three group fields at once.
@@ -38,7 +42,7 @@ Multiple groupings apply to your data in the order you selected them. For exampl
 ====
 
 [discrete]
-[[cspm-findings-page-filter-findings]]
+[id="cspm-findings-page-filter-findings{append}"]
 === Filter findings
 
 You can filter findings data in two ways:
@@ -47,7 +51,7 @@ You can filter findings data in two ways:
 * **In-table value filters**: Hover over a finding to display available inline actions. Use the **Filter In** (plus) and **Filter Out** (minus) buttons.
 
 [discrete]
-[[security-cspm-findings-page-customize-the-findings-table]]
+[id="security-cspm-findings-page-customize-the-findings-table{append}"]
 == Customize the Findings table
 
 You can use the toolbar buttons in the upper-left of the Findings table to select which columns appear:
@@ -62,12 +66,12 @@ You can also click a column's name to open a menu that allows you to perform mul
 ====
 
 [discrete]
-[[cspm-findings-page-remediate-findings]]
+[id="cspm-findings-page-remediate-findings{append}"]
 == Remediate failed findings
 
 To remediate failed findings and reduce your attack surface:
 
-. First, <<cspm-findings-page-filter-findings,filter for failed findings>>.
+. First, <<cspm-findings-page-filter-findings{append},filter for failed findings>>.
 . Click the arrow to the left of a failed finding to open the findings flyout.
 . Follow the steps under **Remediation**.
 +
@@ -77,11 +81,15 @@ Remediation steps typically include commands for you to execute. These sometimes
 ====
 
 [discrete]
-[[cspm-create-rule-from-finding]]
+[id="cspm-create-rule-from-finding{append}"]
 == Generate alerts for failed Findings
 
 You can create detection rules that detect specific failed findings directly from the Findings page.
 
 . Click the arrow to the left of a Finding to open the findings flyout.
 . Click **Take action**, then **Create a detection rule**. This automatically creates a detection rule that creates alerts when the associated benchmark rule generates a failed finding.
 . To review or customize the new rule, click **View rule**.
+
+// end::content[]
+
+:append!:

docs/serverless/cloud-native-security/d4c-kubernetes-dashboard-dash.asciidoc

@@ -0,0 +1,8 @@
+:append: -d4c
+
+[id="security-kubernetes-dashboard-dash{append}"]
+= Kubernetes dashboard
+
+include::../dashboards/kubernetes-dashboard-dash.asciidoc[tag=content]
+
+:append!:

docs/serverless/cloud-native-security/kspm-benchmark-rules.asciidoc

@@ -0,0 +1,8 @@
+:append: -kspm
+
+[id="security-benchmark-rules{append}"]
+= Benchmarks
+
+include::./benchmark-rules.asciidoc[tag=content]
+
+:append!:

docs/serverless/cloud-native-security/kspm-cloud-posture-dashboard-dash.asciidoc

@@ -0,0 +1,8 @@
+:append: -kspm
+
+[id="security-cloud-posture-dashboard-dash{append}"]
+= Cloud Security Posture dashboard
+
+include::../dashboards/cloud-posture-dashboard-dash.asciidoc[tag=content]
+
+:append!:

docs/serverless/cloud-native-security/kspm-cspm-findings-page.asciidoc

@@ -0,0 +1,8 @@
+:append: -kspm
+
+[id="security-cspm-findings-page-kspm{append}"]
+= Findings page
+
+include::./cspm-findings-page.asciidoc[tag=content]
+
+:append!:

docs/serverless/cloud-native-security/vuln-management-dashboard-dash.asciidoc

@@ -0,0 +1,8 @@
+:append: -2
+
+[id="security-kubernetes-dashboard-dash{append}"]
+= Kubernetes dashboard
+
+include::../dashboards/vuln-management-dashboard-dash.asciidoc[tag=content]
+
+:append!:

docs/serverless/dashboards/cloud-posture-dashboard-dash.asciidoc

@@ -4,6 +4,10 @@
 :description: The Cloud Security Posture dashboard summarizes your cloud infrastructure's performance on CIS security benchmarks.
 :keywords: serverless, security, overview, cloud security
 
+:append:
+
+// tag::content[]
+
 ++++
 <titleabbrev>Cloud Security Posture</titleabbrev>
 ++++
@@ -22,7 +26,7 @@ The Cloud Security Posture dashboard shows:
 * Configuration risks grouped by CIS section (security guideline category)
 
 [discrete]
-[[cloud-posture-dashboard-UI]]
+[id="cloud-posture-dashboard-UI{append}"]
 == Cloud Security Posture dashboard UI
 
 At the top of the dashboard, you can switch between the Cloud accounts and Kubernetes cluster views.
@@ -37,7 +41,7 @@ Below the summary section, each row shows the CSP for a benchmark that applies t
 image::images/cloud-posture-dashboard/-dashboards-cloud-sec-dashboard-individual-row.png[A row representing a single cluster in the Cloud Security Posture dashboard]
 
 [discrete]
-[[cloud-posture-dashboard-faq]]
+[id="cloud-posture-dashboard-faq{append}"]
 == FAQ (Frequently Asked Questions)
 
 .When do newly-enrolled clusters appear on the dashboard?
@@ -51,3 +55,7 @@ It can take up to 10 minutes for deployment, resource fetching, evaluation, and
 =====
 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.
 =====
+
+// end::content[]
+
+:append!:

docs/serverless/dashboards/kubernetes-dashboard-dash.asciidoc

@@ -4,6 +4,10 @@
 :description: The Kubernetes dashboard provides insight into Linux process data from your Kubernetes clusters.
 :keywords: serverless, security, overview, cloud security
 
+:append:
+
+// tag::content[]
+
 ++++
 <titleabbrev>Kubernetes</titleabbrev>
 ++++
@@ -43,7 +47,7 @@ The **Metadata** tab is organized into these expandable sections:
 * **Orchestrator:** `resource.ip`, `resource.name`, `resource.type`, `namespace`, `cluster.id`, `cluster.name`, `parent.type`
 
 [discrete]
-[[k8s-dash-setup]]
+[id="k8s-dash-setup{append}"]
 == Setup
 
 To get data for this dashboard, set up <<security-d4c-get-started,Cloud Workload Protection for Kubernetes>> for the clusters you want to display on the dashboard.
@@ -101,3 +105,7 @@ This feature is currently available on GKE and EKS using Linux hosts and Kuberne
 ====
 This dashboard uses data from the `logs-*` index pattern, which is included by default in the <<security-advanced-settings,`securitySolution:defaultIndex` advanced setting>>. To collect data from multiple {es} clusters (as in a cross-cluster deployment), update `logs-*` to `*:logs-*`.
 ====
+
+// end::content[]
+
+:append!: