Update defender-for-devops-recommendations.md

Author: ktoliver

articles/defender-for-cloud/includes/defender-for-devops-recommendations.md

@@ -1,7 +1,6 @@
 ---
 author: dcurwin
 ms.service: defender-for-cloud
-ms.custom: ignite-2022
 ms.topic: include
 ms.date: 09/27/2023
 ms.author: dacurwin
@@ -11,8 +10,6 @@ ms.author: dacurwin
 
 ### Azure DevOps recommendations
 
-There are **10** Azure DevOps recommendations in this category.
-
 | Recommendation | Description | Severity |
 |--|--|--|
 | [Azure DevOps repositories should have GitHub Advanced Security for Azure DevOps (GHAzDO) enabled](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsWithRulesBlade/assessmentKey/c7a934bf-7be6-407a-84d9-4f20e6e49592/showSecurityCenterCommandBar~/false) | DevOps security in Defender for Cloud uses a central console to empower security teams with the ability to protect applications and resources from code to cloud across Azure DevOps. With enablement of GitHub Advanced Security for Azure DevOps (GHAzDO) repositories includes GitHub Advanced Security for Azure DevOps you get findings about secrets, dependencies, and code vulnerabilities in your Azure DevOps repositories surfaced in Microsoft Defender for Cloud. | High |
@@ -28,8 +25,6 @@ There are **10** Azure DevOps recommendations in this category.
 
 ### GitHub recommendations
 
-There are **15** GitHub recommendations in this category.
-
 | Recommendation | Description | Severity |
 |--|--|--|
 | [GitHub repositories should have secret scanning enabled](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsWithRulesBlade/assessmentKey/b6ad173c-0cc6-4d44-b954-8217c8837a8e/showSecurityCenterCommandBar~/false) | GitHub scans repositories for known types of secrets, to prevent fraudulent use of secrets that were accidentally committed to repositories. Secret scanning will scan the entire Git history on all branches present in the GitHub repository for any secrets. Examples of secrets are tokens and private keys that a service provider can issue for authentication. If a secret is checked into a repository, anyone who has read access to the repository can use the secret to access the external service with those privileges. Secrets should be stored in a dedicated, secure location outside the repository for the project. | High |
@@ -50,8 +45,6 @@ There are **15** GitHub recommendations in this category.
 
 ### GitLab recommendations
 
-There are **4** GitLab recommendations in this category.
-
 | Recommendation | Description | Severity |
 |--|--|--|
 | [GitLab projects should have secret scanning findings resolved](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsWithRulesBlade/assessmentKey/867001c3-2d01-4db7-b513-5cb97638f23d/showSecurityCenterCommandBar~/false) | Secrets have been found in code repositories. This should be remediated immediately to prevent a security breach. Secrets found in repositories can be leaked or discovered by adversaries, leading to compromise of an application or service. | High |