Rename container-registries files to containers

Author: bmansheim

.openpublishing.redirection.defender-for-cloud.json

@@ -684,6 +684,16 @@
             "source_path_from_root": "/articles/defender-for-cloud/defender-for-kubernetes-azure-arc.md",
             "redirect_url": "/azure/defender-for-cloud/defender-for-containers-enable?pivots=defender-for-container-arc#protect-arc-enabled-kubernetes-clusters",
             "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/defender-for-cloud/defender-for-container-registries-cicd.md",
+            "redirect_url": "/azure/defender-for-cloud/defender-for-containers-cicd",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/defender-for-cloud/defender-for-container-registries-usage.md",
+            "redirect_url": "/azure/defender-for-cloud/defender-for-containers-usage",
+            "redirect_document_id": true
         }
       ]
 }

articles/defender-for-cloud/TOC.yml

@@ -237,10 +237,10 @@
       href: defender-for-containers-enable.md
     - name: Vulnerability assessment
       displayName: ACR, registry, images, qualys
-      href: defender-for-container-registries-usage.md
+      href: defender-for-containers-usage.md
     - name: Scan images in your CI/CD workflows
       displayName: ACR, registry, images, trevi, vulnerabilities, scanner
-      href: defender-for-container-registries-cicd.md
+      href: defender-for-containers-cicd.md
     - name: Kubernetes data plane hardening
       displayName: k8s, containers, aks
       href: kubernetes-workload-protections.md

articles/defender-for-cloud/auto-deploy-vulnerability-assessment.md

@@ -45,4 +45,4 @@ To assess your machines for vulnerabilities, you can use one of the following so
 Defender for Cloud also offers vulnerability assessment for your:
 
 - SQL databases - see [Explore vulnerability assessment reports in the vulnerability assessment dashboard](defender-for-sql-on-machines-vulnerability-assessment.md#explore-vulnerability-assessment-reports)
-- Azure Container Registry images - see [Use Microsoft Defender for container registries to scan your images for vulnerabilities](defender-for-container-registries-usage.md)
+- Azure Container Registry images - see [Use Microsoft Defender for container registries to scan your images for vulnerabilities](defender-for-containers-usage.md)

articles/defender-for-cloud/custom-dashboards-azure-workbooks.md

@@ -92,7 +92,7 @@ Learn more about using these scanners:
 
 - [Find vulnerabilities with Microsoft threat and vulnerability management](deploy-vulnerability-assessment-tvm.md)
 - [Find vulnerabilities with the integrated Qualys scanner](deploy-vulnerability-assessment-vm.md)
-- [Scan your registry images for vulnerabilities](defender-for-container-registries-usage.md)
+- [Scan your registry images for vulnerabilities](defender-for-containers-usage.md)
 - [Scan your SQL resources for vulnerabilities](defender-for-sql-on-machines-vulnerability-assessment.md)
 
 Findings for each resource type are reported in separate recommendations:

articles/defender-for-cloud/defender-for-cloud-introduction.md

@@ -95,7 +95,7 @@ Review the findings from these vulnerability scanners and respond to them all fr
 Learn more on the following pages:
 
 - [Defender for Cloud's integrated Qualys scanner for Azure and hybrid machines](deploy-vulnerability-assessment-vm.md)
-- [Identify vulnerabilities in images in Azure container registries](defender-for-container-registries-usage.md#identify-vulnerabilities-in-images-in-other-container-registries)
+- [Identify vulnerabilities in images in Azure container registries](defender-for-containers-usage.md#identify-vulnerabilities-in-images-in-other-container-registries)
 
 ## Optimize and improve security by configuring recommended controls
 

articles/defender-for-cloud/defender-for-container-registries-introduction.md

@@ -90,12 +90,12 @@ If you connect unsupported registries to your Azure subscription, Defender for C
 ### Can I customize the findings from the vulnerability scanner?
 Yes. If you have an organizational need to ignore a finding, rather than remediate it, you can optionally disable it. Disabled findings don't impact your secure score or generate unwanted noise.
 
-[Learn about creating rules to disable findings from the integrated vulnerability assessment tool](defender-for-container-registries-usage.md#disable-specific-findings).
+[Learn about creating rules to disable findings from the integrated vulnerability assessment tool](defender-for-containers-usage.md#disable-specific-findings).
 
 ### Why is Defender for Cloud alerting me to vulnerabilities about an image that isn’t in my registry?
 Defender for Cloud provides vulnerability assessments for every image pushed or pulled in a registry. Some images may reuse tags from an image that was already scanned. For example, you may reassign the tag “Latest” every time you add an image to a digest. In such cases, the ‘old’ image does still exist in the registry and may still be pulled by its digest. If the image has security findings and is pulled, it'll expose security vulnerabilities.
 
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Scan your images for vulnerabilities](defender-for-container-registries-usage.md)
+> [Scan your images for vulnerabilities](defender-for-containers-usage.md)

articles/defender-for-cloud/defender-for-container-registries-cicd.md renamed to articles/defender-for-cloud/defender-for-containers-cicd.md

@@ -49,7 +49,7 @@ To enable vulnerability scans of images in your GitHub workflows:
 1. In the pane that appears, select an Application Insights account to push the CI/CD scan results from your workflow.
 1. Copy the authentication token and connection string into your GitHub workflow.
 
-    :::image type="content" source="./media/defender-for-container-registries-cicd/enable-cicd-integration.png" alt-text="Enable the CI/CD integration for vulnerability scans of container images in your GitHub workflows." lightbox="./media/defender-for-container-registries-cicd/enable-cicd-integration.png":::
+    :::image type="content" source="./media/defender-for-containers-cicd/enable-cicd-integration.png" alt-text="Enable the CI/CD integration for vulnerability scans of container images in your GitHub workflows." lightbox="./media/defender-for-containers-cicd/enable-cicd-integration.png":::
 
     > [!IMPORTANT]
     > The authentication token and connection string are used to correlate the ingested security telemetry with resources in the subscription. If you use invalid values for these parameters, it'll lead to dropped telemetry.
@@ -105,27 +105,27 @@ To enable vulnerability scans of images in your GitHub workflows:
 
 1. Open the **affected resources** list and select an unhealthy registry to see the repositories within it that have vulnerable images.
 
-    :::image type="content" source="media/defender-for-container-registries-cicd/select-registry.png" alt-text="Select an unhealthy registry.":::
+    :::image type="content" source="media/defender-for-containers-cicd/select-registry.png" alt-text="Select an unhealthy registry.":::
 
     The registry details page opens with the list of affected repositories.
 
 1. Select a specific repository to see the repositories within it that have vulnerable images.
 
-    :::image type="content" source="media/defender-for-container-registries-cicd/select-repository.png" alt-text="Select an unhealthy repository.":::
+    :::image type="content" source="media/defender-for-containers-cicd/select-repository.png" alt-text="Select an unhealthy repository.":::
 
     The repository details page opens. It lists the vulnerable images together with an assessment of the severity of the findings.
 
 1. Select a specific image to see the vulnerabilities.
 
-    :::image type="content" source="media/defender-for-container-registries-cicd/select-image.png" alt-text="Select an unhealthy image.":::
+    :::image type="content" source="media/defender-for-containers-cicd/select-image.png" alt-text="Select an unhealthy image.":::
 
     The list of findings for the selected image opens.
 
-    :::image type="content" source="media/defender-for-container-registries-cicd/cicd-scan-results.png" alt-text="Image scan results.":::
+    :::image type="content" source="media/defender-for-containers-cicd/cicd-scan-results.png" alt-text="Image scan results.":::
 
 1. To learn more about which GitHub workflow is pushing these vulnerable images, select the information bubble:
 
-    :::image type="content" source="media/defender-for-container-registries-cicd/cicd-findings.png" alt-text="CI/CD findings about specific GitHub branches and commits.":::
+    :::image type="content" source="media/defender-for-containers-cicd/cicd-findings.png" alt-text="CI/CD findings about specific GitHub branches and commits.":::
 
 ## Next steps
 

articles/defender-for-cloud/defender-for-containers-introduction.md

@@ -67,7 +67,7 @@ Defender for Containers includes an integrated vulnerability scanner for scannin
 - When you import the image to your Azure Container Registry
 - Continuously in specific situations
 
-Learn more in [Vulnerability assessment](defender-for-container-registries-usage.md).
+Learn more in [Vulnerability assessment](defender-for-containers-usage.md).
 
 :::image type="content" source="./media/defender-for-containers/recommendation-acr-images-with-vulnerabilities.png" alt-text="Sample Microsoft Defender for Cloud recommendation about vulnerabilities discovered in Azure Container Registry (ACR) hosted images." lightbox="./media/defender-for-containers/recommendation-acr-images-with-vulnerabilities.png":::
 

articles/defender-for-cloud/defender-for-container-registries-usage.md renamed to articles/defender-for-cloud/defender-for-containers-usage.md

@@ -14,7 +14,7 @@ This page explains how to use the built-in vulnerability scanner to scan the con
 When the scanner, powered by Qualys, reports vulnerabilities to Defender for Cloud, Defender for Cloud presents the findings and related information as recommendations. In addition, the findings include related information such as remediation steps, relevant CVEs, CVSS scores, and more. You can view the identified vulnerabilities for one or more subscriptions, or for a specific registry.
 
 > [!TIP]
-> You can also scan container images for vulnerabilities as the images are built in your CI/CD GitHub workflows. Learn more in [Identify vulnerable container images in your CI/CD workflows](defender-for-container-registries-cicd.md).
+> You can also scan container images for vulnerabilities as the images are built in your CI/CD GitHub workflows. Learn more in [Identify vulnerable container images in your CI/CD workflows](defender-for-containers-cicd.md).
 
 There are four triggers for an image scan:
 
@@ -142,7 +142,7 @@ To create a rule:
 1. Define your criteria.
 1. Select **Apply rule**.
 
-    :::image type="content" source="./media/defender-for-container-registries-usage/new-disable-rule-for-registry-finding.png" alt-text="Create a disable rule for VA findings on registry.":::
+    :::image type="content" source="./media/defender-for-containers-usage/new-disable-rule-for-registry-finding.png" alt-text="Create a disable rule for VA findings on registry.":::
 
 1. To view, override, or delete a rule:
     1. Select **Disable rule**.
@@ -168,7 +168,7 @@ If you connect unsupported registries to your Azure subscription, Defender for C
 ### Can I customize the findings from the vulnerability scanner?
 Yes. If you have an organizational need to ignore a finding, rather than remediate it, you can optionally disable it. Disabled findings don't impact your secure score or generate unwanted noise.
 
-[Learn about creating rules to disable findings from the integrated vulnerability assessment tool](defender-for-container-registries-usage.md#disable-specific-findings).
+[Learn about creating rules to disable findings from the integrated vulnerability assessment tool](defender-for-containers-usage.md#disable-specific-findings).
 
 ### Why is Defender for Cloud alerting me to vulnerabilities about an image that isn’t in my registry?
 Some images may reuse tags from an image that was already scanned. For example, you may reassign the tag “Latest” every time you add an image to a digest. In such cases, the ‘old’ image does still exist in the registry and may still be pulled by its digest. If the image has security findings and is pulled, it'll expose security vulnerabilities.

articles/defender-for-cloud/deploy-vulnerability-assessment-byol-vm.md

@@ -144,4 +144,4 @@ When you set up your solution, you must choose a resource group to attach it to.
 Defender for Cloud also offers vulnerability analysis for your:
 
 - SQL databases - see [Explore vulnerability assessment reports in the vulnerability assessment dashboard](defender-for-sql-on-machines-vulnerability-assessment.md#explore-vulnerability-assessment-reports)
-- Azure Container Registry images - see [Use Microsoft Defender for container registries to scan your images for vulnerabilities](defender-for-container-registries-usage.md)
+- Azure Container Registry images - see [Use Microsoft Defender for container registries to scan your images for vulnerabilities](defender-for-containers-usage.md)