Skip to content

Commit 8fe8bb5

Browse files
secrets docs
1 parent 3561938 commit 8fe8bb5

File tree

2 files changed

+34
-3
lines changed

2 files changed

+34
-3
lines changed

articles/defender-for-cloud/secrets-scanning-cloud-deployment.md

Lines changed: 30 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,42 @@ ms.date: 04/16/2024
88

99
# Protecting cloud deployment secrets
1010

11-
Defender for Cloud provides agentless secrets scanning for cloud deployments. Cloud deployments (infrastructure as code) refers to the process of deploying and managing resources on cloud providers such as Azure and AWS at scale, using tools such as Azure Resource Manager templates and AWS CloudFormation stack.
11+
Microsoft Defender for Cloud provides agentless secrets scanning for cloud deployments.
12+
13+
## What is cloud deployment?
14+
15+
Cloud deployments refers to the process of deploying and managing resources on cloud providers such as Azure and AWS at scale, using tools such as Azure Resource Manager templates and AWS CloudFormation stack. In other words, a cloud deployment is an instance of an infrastructure-as-code (IaC) template.
16+
17+
Each cloud provide exposes an API query, and when querying APIs for cloud deployment resources, you typically retrieve deployment metadata such as deployment templates, parameters, output, and tags.
18+
19+
20+
## Security from software development to runtime
21+
22+
Traditional secrets scanning solutions often detect misplaced secrets in code repositories, DevOps pipelines, or files within VMs and containers. Cloud deployment resources tend to be overlooked, and might potentially include plaintext secrets that can lead to critical assets, such as databases, blob storage, GitHub repositories, and Azure Open AI services. These secrets can allow attackers to exploit otherwise hidden attack surfaces within cloud environments.
23+
24+
25+
Scanning for cloud deployment secrets adds an extra layer of security, addressing scenarios such as:
26+
27+
- **Increased security coverage: In Defender for Cloud, DevOps security capabilities in Defender for Cloud [can identify exposed secrets](defender-for-devops-introduction.md) within source control management platforms. However, manually triggered cloud deployments from a developer’s workstation can lead to exposed secrets that might be overlooked. In addition, some secrets might only surface during deployment runtime, like those revealed in deployment outputs, or resolved from Azure Key Vault. Scanning for cloud deployment secrets bridges this gap.
28+
- **Preventing lateral movement**: Discovery of exposed secrets within deployment resources poses a significant risk of unauthorized access.
29+
- Threat actors can exploit these vulnerabilities to traverse laterally across an environment, ultimately compromising critical services
30+
- Using attack path analysis with cloud deployment secrets scanning will automatically discover attack paths involving an Azure deployment that might lead to a sensitive data breach.
31+
- **Resource discovery**: The impact of misconfigured deployment resources can be extensive, leading to the new resources being created on an expanding attack surface.
32+
- Detecting and securing secrets within resource control plane data can help prevent potential breaches.
33+
- Addressing exposed secrets during resource creation can be particularly challenging.
34+
- Cloud deployment secrets scanning helps to identify and mitigate these vulnerabilities at an early stage.
35+
1236

1337
Scanning helps you to quickly detect plaintext secrets in cloud deployments. If secrets are detected Defender for Cloud can assist your security team to prioritize action and remediate to minimize the risk of lateral movement.
1438

39+
40+
41+
1542
## How does cloud deployment secrets scanning work?
1643

17-
Secrets scanning for cloud deployment resources is agentless and uses cloud control plan APIs.
44+
Scanning helps you to quickly detect plaintext secrets in cloud deployments. Secrets scanning for cloud deployment resources is agentless and uses the cloud control plane API.
1845

19-
The Microsoft secrets scanning engine verifies whether SSH private keys can be used to move laterally in your network.
46+
The Microsoft secrets scanning engine verifies whether SSH private keys can be used to move laterally in your network.
2047

2148
- SSH keys that aren’t successfully verified are categorized as unverified on the Defender for Cloud Recommendations page.
2249
- Directories recognized as containing test-related content are excluded from scanning.

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,9 @@ Defender for Cloud provides secrets scanning for virtual machines, and for cloud
2121

2222
- **Virtual machines (VMs)**: Agentless secrets scanning on multicloud VMs.
2323
- **Cloud deployments**: Agentless secrets scanning across multicloud infrastructure-as-code deployment resources.
24+
- **Azure DevOps**: Scanning to discover exposed secrets in Azure DevOps.
25+
26+
2427

2528
## Deploying secrets scanning
2629

@@ -104,5 +107,6 @@ Plaintext Azure Service Bus Shared Access Signature.|No |Yes | Invento
104107
## Related content
105108
- [VM secrets scanning](secrets-scanning-servers.md).
106109
- [Cloud deployment secrets scanning](secrets-scanning-cloud-deployment.md)
110+
- [Azure DevOps scanning](devops-support.md)
107111

108112

0 commit comments

Comments
 (0)