You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/secret-scanning.md
+15-13Lines changed: 15 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Manage secrets with agentless secrets scanning
3
3
description: Learn how to scan your servers for secrets with Defender for Server's agentless secrets scanning.
4
4
ms.topic: overview
5
-
ms.date: 12/20/2023
5
+
ms.date: 01/22/2024
6
6
---
7
7
8
8
# Manage secrets with agentless secrets scanning
@@ -11,7 +11,7 @@ Attackers can move laterally across networks, find sensitive data, and exploit v
11
11
12
12
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.
13
13
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):
15
15
16
16
- Insecure SSH private keys:
17
17
@@ -53,24 +53,26 @@ By using agentless secrets scanning, you can proactively discover the following
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.
59
59
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:
- 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
87
89
88
90
- 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/).
89
91
90
-
- Access to [Defender for Cloud](get-started.md)
92
+
- Access to [Defender for Cloud](get-started.md).
91
93
92
94
-[Enable](enable-enhanced-security.md#enable-defender-plans-to-get-the-enhanced-security-features) either or both of the following two plans:
93
95
-[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
99
101
100
102
## Remediate secrets with attack path
101
103
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.
103
105
104
106
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.
105
107
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.
107
109
108
110
### Azure VM supported attack path scenarios
109
111
@@ -149,9 +151,9 @@ Agentless secrets scanning for GCP VM instances supports the following attack pa
149
151
150
152
## Remediate secrets with recommendations
151
153
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:
153
155
154
-
-**Azure resources**: `Machines should have secrets findings resolved`
156
+
-**Azure resources**: `Machines should have secret findings resolved`
155
157
156
158
-**AWS resources**: `EC2 instances should have secret findings resolved`
157
159
@@ -165,7 +167,7 @@ If a secret is found on your resource, that resource triggers an affiliated reco
165
167
166
168
1. Expand the **Remediate vulnerabilities** security control.
167
169
168
-
1. Select either:
170
+
1. Select one of the following:
169
171
170
172
-**Azure resources**: `Machines should have secret findings resolved`
171
173
-**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
183
185
184
186
1. Expand **Affected resources** to review the resources affected by this secret.
185
187
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.
187
189
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`.
189
191
190
192
## Remediate secrets with cloud security explorer
191
193
@@ -229,4 +231,4 @@ Different types of secrets have different sets of additional information. For ex
229
231
230
232
## Next steps
231
233
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