Skip to content

Commit 5fc5791

Browse files
Update secret-scanning.md
1 parent e70ec22 commit 5fc5791

File tree

1 file changed

+15
-13
lines changed

1 file changed

+15
-13
lines changed

articles/defender-for-cloud/secret-scanning.md

Lines changed: 15 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Manage secrets with agentless secrets scanning
33
description: Learn how to scan your servers for secrets with Defender for Server's agentless secrets scanning.
44
ms.topic: overview
5-
ms.date: 12/20/2023
5+
ms.date: 01/22/2024
66
---
77

88
# Manage secrets with agentless secrets scanning
@@ -11,7 +11,7 @@ Attackers can move laterally across networks, find sensitive data, and exploit v
1111

1212
Defender for Cloud's agentless secrets scanning for Virtual Machines (VM) locates plaintext secrets that exist in your environment. If secrets are detected, Defender for Cloud can assist your security team to prioritize and take actionable remediation steps to minimize the risk of lateral movement, all without affecting your machine's performance.
1313

14-
By using agentless secrets scanning, you can proactively discover the following types of secrets across your environments (in Azure, AWS and GCP cloud providers):
14+
By using agentless secrets scanning, you can proactively discover the following types of secrets across your environments (in Azure, AWS, and GCP cloud providers):
1515

1616
- Insecure SSH private keys:
1717

@@ -53,24 +53,26 @@ By using agentless secrets scanning, you can proactively discover the following
5353
- Plaintext OpenAI API Key.
5454
- Plaintext Azure Batch Shared Access Key.
5555
- Plaintext NPM Author Token.
56-
- Plaintext Azure Subscription Management Certificate.
56+
- Plaintext Azure Subscription Management Certificate.
5757

5858
Secrets findings can be found using the [Cloud Security Explorer](#remediate-secrets-with-cloud-security-explorer) and the [Secrets tab](#remediate-secrets-from-your-asset-inventory) with their metadata like secrets type, file name, file path, last access time, and more.
5959

60-
The following secrets can also be accessed from the `Security Recommendations` and `Attack Path`, across Azure, AWS and GCP cloud providers:
60+
The following secrets can also be accessed from the `Security Recommendations` and `Attack Path`, across Azure, AWS, and GCP cloud providers:
6161

6262
- Insecure SSH private keys:
6363

6464
- Supporting RSA algorithm for PuTTy files.
6565
- PKCS#8 and PKCS#1 standards.
6666
- OpenSSH standard.
67+
6768
- Plaintext Azure database connection string:
6869

6970
- Plaintext Azure SQL connection strings, supports SQL PAAS.
7071
- Plaintext Azure database for PostgreSQL.
7172
- Plaintext Azure database for MySQL.
7273
- Plaintext Azure database for MariaDB.
7374
- Plaintext Azure Cosmos DB, including PostgreSQL, MySQL and MariaDB.
75+
7476
- Plaintext AWS RDS connection string, supports SQL PAAS:
7577

7678
- Plaintext Amazon Aurora with Postgres and MySQL flavors.
@@ -87,7 +89,7 @@ The agentless scanner verifies whether SSH private keys can be used to move late
8789

8890
- An Azure account. If you don't already have an Azure account, you can [create your Azure free account today](https://azure.microsoft.com/free/).
8991

90-
- Access to [Defender for Cloud](get-started.md)
92+
- Access to [Defender for Cloud](get-started.md).
9193

9294
- [Enable](enable-enhanced-security.md#enable-defender-plans-to-get-the-enhanced-security-features) either or both of the following two plans:
9395
- [Defender for Servers Plan 2](plan-defender-for-servers-select-plan.md)
@@ -99,11 +101,11 @@ For requirements for agentless scanning, see [Learn about agentless scanning](co
99101

100102
## Remediate secrets with attack path
101103

102-
Attack path analysis is a graph-based algorithm that scans your [cloud security graph](concept-attack-path.md#what-is-cloud-security-graph). These scans expose exploitable paths that attackers might use to breach your environment to reach your high-impact assets. Attack path analysis exposes attack paths and suggests recommendations as to how best remediate issues that break the attack path and prevent successful breach.
104+
Attack path analysis is a graph-based algorithm that scans your [cloud security graph](concept-attack-path.md#what-is-cloud-security-graph). These scans expose exploitable paths that attackers might use to breach your environment to reach your high-impact assets. Attack path analysis exposes attack paths and suggests recommendations for how to best remediate issues that break the attack path and prevent successful breach.
103105

104106
Attack path analysis takes into account the contextual information of your environment to identify issues that might compromise it. This analysis helps prioritize the riskiest issues for faster remediation.
105107

106-
The attack path page shows an overview of your attack paths, affected resources and a list of active attack paths.
108+
The attack path page shows an overview of your attack paths, affected resources, and a list of active attack paths.
107109

108110
### Azure VM supported attack path scenarios
109111

@@ -149,9 +151,9 @@ Agentless secrets scanning for GCP VM instances supports the following attack pa
149151

150152
## Remediate secrets with recommendations
151153

152-
If a secret is found on your resource, that resource triggers an affiliated recommendation that is located under the Remediate vulnerabilities security control on the Recommendations page. Depending on your resources, either or both of the following recommendations appear:
154+
If a secret is found on your resource, that resource triggers an affiliated recommendation that is located under the Remediate vulnerabilities security control on the Recommendations page. Depending on your resources, either one or more of the following recommendations appear:
153155

154-
- **Azure resources**: `Machines should have secrets findings resolved`
156+
- **Azure resources**: `Machines should have secret findings resolved`
155157

156158
- **AWS resources**: `EC2 instances should have secret findings resolved`
157159

@@ -165,7 +167,7 @@ If a secret is found on your resource, that resource triggers an affiliated reco
165167

166168
1. Expand the **Remediate vulnerabilities** security control.
167169

168-
1. Select either:
170+
1. Select one of the following:
169171

170172
- **Azure resources**: `Machines should have secret findings resolved`
171173
- **AWS resources**: `EC2 instances should have secret findings resolved`
@@ -183,9 +185,9 @@ If a secret is found on your resource, that resource triggers an affiliated reco
183185

184186
1. Expand **Affected resources** to review the resources affected by this secret.
185187

186-
1. (Optional) You can select an affected resource to see that resources information.
188+
1. (Optional) You can select an affected resource to see that resource's information.
187189

188-
Secrets that don't have a known attack path, are referred to as `secrets without an identified target resource`.
190+
Secrets that don't have a known attack path are referred to as `secrets without an identified target resource`.
189191

190192
## Remediate secrets with cloud security explorer
191193

@@ -229,4 +231,4 @@ Different types of secrets have different sets of additional information. For ex
229231

230232
## Next steps
231233

232-
- [Use asset inventory to manage your resources' security posture](asset-inventory.md)
234+
- [Use asset inventory to manage your resources' security posture](asset-inventory.md).

0 commit comments

Comments
 (0)