Skip to content

Commit ec28a05

Browse files
committed
2 parents 3247c69 + 814b947 commit ec28a05

192 files changed

Lines changed: 3278 additions & 2773 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -564,6 +564,16 @@
564564
"source_path_from_root": "/articles/defender-for-cloud/tutorial-enable-containers-arc.md",
565565
"redirect_url": "/azure/defender-for-cloud/defender-for-containers-arc-enable-portal",
566566
"redirect_document_id": false
567+
},
568+
{
569+
"source_path_from_root": "/articles/defender-for-cloud/extract-resource-identifiers-support.md",
570+
"redirect_url": "/azure/defender-for-cloud/defender-portal/integration-faq#extracting-identifiers-for-support-cases",
571+
"redirect_document_id": false
572+
},
573+
{
574+
"source_path_from_root": "/articles/defender-for-cloud/monitor-connected-aws-resources.md",
575+
"redirect_url": "/azure/defender-for-cloud/quickstart-onboard-aws#validate-connector-health",
576+
"redirect_document_id": false
567577
}
568578
]
569579
}

.openpublishing.redirection.key-vault.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -549,6 +549,16 @@
549549
"source_path_from_root": "/articles/key-vault/secrets/secrets-best-practices.md",
550550
"redirect_url": "/azure/key-vault/secrets/secure-secrets",
551551
"redirect_document_id": false
552+
},
553+
{
554+
"source_path_from_root": "/articles/key-vault/general/dotnet2api-release-notes.md",
555+
"redirect_url": "/azure/key-vault/general/client-libraries",
556+
"redirect_document_id": false
557+
},
558+
{
559+
"source_path_from_root": "/articles/key-vault/general/customer-data.md",
560+
"redirect_url": "/azure/key-vault/general/monitor-key-vault",
561+
"redirect_document_id": false
552562
}
553563
]
554564
}

articles/cloud-hsm/authentication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Authentication is a crucial aspect of securely accessing and operating within Az
1515

1616
## Cloud HSM CLI authentication
1717

18-
You can authenticate by using CLI tools like `azcloudhsm_util` in either interactive mode or single-command mode. In interactive mode, use the `login` command. For single-command mode, include `singlecmd` and parameters for `loginHSM`. We advise you to securely store your HSM credentials when your application isn't using them.
18+
You can authenticate by using CLI tools like `azcloudhsm_util` in either interactive mode or single-command mode. In interactive mode, use the `loginHSM` command. For single-command mode, include `singlecmd` and parameters for `loginHSM`. We advise you to securely store your HSM credentials when your application isn't using them.
1919

2020
### Interactive mode
2121

articles/defender-for-cloud/TOC.yml

Lines changed: 43 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -52,11 +52,24 @@
5252
displayName: enable, defender for cloud, activate, turn on, Microsoft Defender XDR, alerts, integration, m365, m365d, m365 defender, free, trial, free trial
5353
href: connect-azure-subscription.md
5454
- name: Connect AWS accounts
55-
displayName: hybrid, multicloud, multicloud, amazon, arc, AWS, accounts, Microsoft Defender XDR, alerts, integration, m365, m365d, m365 defender
56-
href: quickstart-onboard-aws.md
55+
items:
56+
- name: Connect your AWS account
57+
href: quickstart-onboard-aws.md
58+
- name: Authentication architecture for AWS connectors
59+
href: concept-authentication-architecture-aws.md
60+
- name: Integrate AWS CloudTrail logs (Preview)
61+
href: integrate-cloud-trail.md
5762
- name: Connect GCP projects
58-
displayName: hybrid, multicloud, multicloud, google, gcp, Microsoft Defender XDR, alerts, integration, m365, m365d, m365 defender
59-
href: quickstart-onboard-gcp.md
63+
items:
64+
- name: Connect your GCP project
65+
displayName: gcp, connect, onboard
66+
href: quickstart-onboard-gcp.md
67+
- name: Configure GCP plans
68+
displayName: GCP, plans, configure
69+
href: configure-google-plans.md
70+
- name: Ingest GCP logging
71+
displayName: GCP, logging, ingest
72+
href: logging-ingestion.md
6073
- name: Connect individual non-Azure machines
6174
items:
6275
- name: Connect machines with Defender for Endpoint
@@ -65,6 +78,13 @@
6578
- name: Connect machines with Azure Arc
6679
displayName: azure stack, ash, windows, linux, hybrid, arc, on-premises, Microsoft Defender XDR, alerts, integration, m365, m365d, m365 defender
6780
href: quickstart-onboard-machines.md
81+
- name: Networking and connectivity
82+
items:
83+
- name: Microsoft Security Private Link for Microsoft Defender for Cloud (Preview)
84+
displayName: private endpoints, private link, security private link, networking, connectivity, VPN, ExpressRoute
85+
href: concept-private-links.md
86+
- name: Configure private endpoints with Microsoft Security Private Link (Preview)
87+
href: configure-private-endpoints.md
6888
- name: Enable specific plans
6989
expanded: false
7090
items:
@@ -501,6 +521,9 @@
501521
href: detect-exposed-ip-addresses.md
502522
- name: Review security recommendations
503523
items:
524+
- name: Security recommendations
525+
displayName: security, recommendations, overview, posture, management
526+
href: security-recommendations.md
504527
- name: Review security recommendations
505528
displayName: security, recommendations, owner, azure, resource, graph, azure resource graph, csv report
506529
href: review-security-recommendations.md
@@ -683,7 +706,6 @@
683706
href: deploy-vulnerability-assessment-byol-vm.md
684707
- name: Move to scanning with Defender Vulnerability Management
685708
displayName: qualys, rapid7, vulnerability, migrate, transition, Microsoft Defender Vulnerability Management, mdvm
686-
href: transition-to-built-in.md
687709
- name: Machine secrets scanning
688710
items:
689711
- name: Overview
@@ -859,20 +881,13 @@
859881
href: defender-for-sql-scan-results.md
860882
- name: Investigate and remediate
861883
items:
862-
- name: Investigate Defender for SQL security Alerts, reporting, and queries
884+
- name: Investigate Defender for SQL security alerts
863885
displayName: SQL, SQL servers, defender, machines
864886
href: defender-for-sql-alerts.md
865887
- name: Find and remediate vulnerabilities
866888
href: sql-azure-vulnerability-assessment-find.md
867-
- name: Vulnerability assessment rules
868-
href: sql-azure-vulnerability-assessment-rules.md
869-
- name: SQL vulnerability assessment rules changelog
870-
href: sql-azure-vulnerability-assessment-rules-changelog.md
871889
- name: Consume and export scan results
872890
href: defender-for-sql-scan-results.md
873-
- name: Investigate Defender for SQL security alerts
874-
href: defender-for-sql-alerts.md
875-
876891
- name: Defender for App Service
877892
items:
878893
- name: Overview
@@ -1489,6 +1504,21 @@
14891504
- name: Integrate CLI with CI/CD pipelines
14901505
DisplayName: Defender for Cloud CLI, CI/CD pipelines
14911506
href: episode-fifty-nine.md
1507+
- name: Code reachability analysis
1508+
DisplayName: Code reachability analysis, reachable vulnerabilities
1509+
href: episode-sixty.md
1510+
- name: Kubernetes lateral movement
1511+
DisplayName: Kubernetes lateral movement, Kubernetes RBAC, attack paths
1512+
href: episode-sixty-one.md
1513+
- name: Kubernetes gated deployment
1514+
DisplayName: Kubernetes gated deployment, gated rules
1515+
href: episode-sixty-two.md
1516+
- name: Agentless code scanning
1517+
DisplayName: Agentless code scanning
1518+
href: episode-sixty-three.md
1519+
- name: Storage aggregated logs
1520+
DisplayName: Storage aggregated logs, Advanced Hunting, CloudStorageAggregatedEvents
1521+
href: episode-sixty-four.md
14921522
- name: Microsoft Defender for IoT documentation
14931523
href: /azure/defender-for-iot/
14941524
- name: Azure security documentation

articles/defender-for-cloud/agentless-code-scanning.md

Lines changed: 15 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,9 @@ You can customize which scanners to run and define exactly which organizations,
2121
- **Supported use cases**:
2222
- [Security recommendations to prioritize and fix code vulnerabilities](defender-for-devops-introduction.md#manage-your-devops-environments-in-defender-for-cloud)
2323
- [Security recommendations to prioritize and fix Infrastructure-as-Code (IaC) misconfigurations](iac-vulnerabilities.md)
24-
24+
25+
- Cloud Security Explorer queries to locate repositories including dependencies resulting from an SBOM.
26+
2527
- [Supported cloud availability](support-matrix-defender-for-cloud.md).
2628

2729
- **Supported regions**: Australia East, Canada Central, Central US, East Asia, East US, North Europe, Sweden Central, UK South, West Europe.
@@ -47,15 +49,16 @@ Some of the key benefits of agentless code scanning in Microsoft Defender for Cl
4749
- **Rapid insights for quick remediation**: Receive actionable vulnerability insights right after onboarding. This allows quick fixes and reduces exposure time. 
4850
- **Developer-friendly and seamless**: Operate independently of continuous integration and continuous deployment (CI/CD) pipelines, without changes or direct developer involvement needed. This allows for continuous security monitoring without disrupting developer productivity or workflows.
4951
- **Flexible coverage and control:** Choose which scanners run and what gets scanned. You can cover everything by default or customize settings to include or exclude specific organizations, projects, or repositories. This allows you to match security coverage to your risk profile and operational needs, without extra complexity.
52+
- **Software Bill of Materials (SBOM) creation**: Automatically generating an SBOM on every scan gives teams a precise, queryable inventory of dependencies and versions across their repositories, without additional workflow changes. This enables rapid impact analysis, faster response to newly disclosed vulnerabilities, and confident decision-making when assessing exposure to specific packages or versions.
5053

5154
## Risks detection capabilities
5255

53-
Agentless code scanning improves security by offering targeted security recommendations for both code and infrastructure-as-code (IaC) templates. This is in addition to the foundational cloud security posture management security recommendations provided through the connector. Key detection capabilities include:
56+
Agentless code scanning improves security by delivering targeted, actionable recommendations across application code, infrastructure-as-code (IaC) templates, and third-party dependencies. This is in addition to the cloud security posture management security recommendations provided through the connector. Key detection capabilities include:
5457

5558
- **Code vulnerabilities**: Find common coding errors, unsafe coding practices, and known vulnerabilities in multiple programming languages.
5659
- **Infrastructure-as-Code misconfigurations**: Detect security misconfigurations in IaC templates that could lead to insecure deployments.
57-
5860
- **Dependency vulnerabilities**: Identify known vulnerabilities in open-source packages and OS packages discovered in repositories.
61+
- **Software Bill of Materials (SBOM)**: Automatically generate a comprehensive, queryable inventory of dependencies and their versions for each repository,
5962

6063
Creating the connector enhances security by providing foundational cloud security posture management recommendations for repositories, pipelines, and service connections.
6164

@@ -70,6 +73,7 @@ Agentless code scanning uses various open-source tools to find vulnerabilities a
7073
| **[Bandit](https://github.com/PyCQA/bandit)** |Python | [Apache 2.0](https://github.com/PyCQA/bandit/blob/master/LICENSE) |
7174
| **[ESLint](https://github.com/eslint/eslint)** |JavaScript, TypeScript, JSX, TSX | [MIT](https://github.com/eslint/eslint/blob/main/LICENSE) |
7275
| **[Trivy](https://www.github.com/aquasecurity/trivy/)**|Dependency and OS package vulnerability scanning from repository manifests and lockfiles (filesystem mode) |[Apache 2.0](https://github.com/aquasecurity/trivy/blob/main/LICENSE)|
76+
| **[Syft](https://github.com/anchore/syft/)**|Alpine (apk), Bitnami packages, C (conan), C++ (conan), Dart (pubs), Debian (dpkg), Dotnet (deps.json), Objective-C (cocoapods), Elixir (mix), Erlang (rebar3), Go (go.mod, Go binaries), GitHub (workflows, actions), Haskell (cabel, stack), Java (jar, ear, war, par, sar, nar, rar, native-image), JavaScript (npm, yarn), Jenkins Plugins (jpi, hpi), Linux kernel archives (vmlinz), Linux kernel modules (ko), Nix (outputs in /nix/store), PHP (composer, PECL, Pear), Python (wheel, egg, poetry, requirements.txt, uv), Red Hat (rpm), Ruby (gem), Rust (cargo.lock, auditable binary), Swift (cocoapods, swift-package-manager), Wordpress plugins, Terraform providers (.terraform.lock.hcl) | [Apache 2.0](https://github.com/anchore/syft/blob/main/LICENSE)|
7377

7478

7579
These tools support a wide range of languages and infrastructure-as-code (IaC) frameworks, ensuring thorough security analysis across your codebase.
@@ -147,7 +151,7 @@ Once you enable the agentless code scanning feature within a connector, the scan
147151

148152
1. **Code retrieval**: It securely retrieves the latest code from the default (main) branch of each repository for analysis, initially after connector setup and then daily.
149153

150-
1. **Analysis**: The system uses a set of built-in scanning tools managed and updated within Microsoft Defender for Cloud to find vulnerabilities and misconfigurations in code and infrastructure-as-code (IaC) templates.
154+
1. **Analysis**: The system uses a set of built-in scanning tools managed and updated within Microsoft Defender for Cloud to find vulnerabilities and misconfigurations in code and infrastructure-as-code (IaC) templates. It also creates an SBOM to allow for queryable package management.
151155

152156
1. **Findings processing**: It processes scan findings through Defender for Cloud’s backend to create actionable security recommendations.
153157

@@ -219,12 +223,17 @@ During the **public preview** phase, the following limitations apply:
219223

220224
- **No binary scanning**: Only code (SAST) and IaC scanning tools are executed.
221225
- **Scan frequency**: It scans repositories upon enablement, and then daily.
222-
223226
- **Repository size**: It limits scanning to repositories under 1 GB.
224-
225227
- **Branch coverage**: Scans cover only the default branch (usually `main`).
226228
- **Tool customization**: You can't customize scanning tools.
227229

230+
SBOM currently has the following limitations:
231+
- Repository needs a lock file otherwise only direct dependencies will be found
232+
- The SBOM size limitation is restricted to 1MB. If there are a lot of packages identified, our ingestion into the Cloud Map will fail.
233+
- SBOM enablement is not configurable. An SBOM will be generated on every Agentless scan.
234+
- Timeout is set to 15 minutes for the SBOM tool to run.
235+
- Disabling Agentless doesn't delete the SBOM recommendations.
236+
228237
## Related content
229238

230239
- [Overview of Microsoft Defender for Cloud DevOps security](defender-for-devops-introduction.md)

articles/defender-for-cloud/ai-security-posture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Defender for Cloud reduces risks to cross-cloud AI workloads by:
3232
> 1. In the Azure portal, go to the Environment Settings page and select the appropriate AWS connector.
3333
> 1. Select **Configure access**.
3434
> 1. Ensure the permissions type is set to **Least privilege access**.
35-
> 1. [Follow steps 5 - 8](quickstart-onboard-aws.md#select-defender-plans) to finish the configuration.
35+
> 1. [Follow steps 7 - 11](quickstart-onboard-aws.md#connect-your-aws-account) to finish the configuration.
3636
3737
## Discover generative AI apps
3838

articles/defender-for-cloud/ai-threat-protection.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -10,17 +10,11 @@ author: Elazark
1010

1111
# Overview - AI threat protection
1212

13-
Microsoft Defender for Cloud's threat protection for AI services identifies threats to generative AI applications in real time and helps respond to security issues.
14-
15-
Defender for Cloud's AI threat protection works with [Azure AI Content Safety Prompt Shields](/azure/ai-services/content-safety/concepts/jailbreak-detection) and Microsoft's threat intelligence to provide security alerts for threats like data leakage, data poisoning, jailbreak, and credential theft.
16-
17-
:::image type="content" source="media/ai-threat-protection/threat-protection-ai.png" alt-text="Diagram that shows how enabling, detection, and response works for threat protection." lightbox="media/ai-threat-protection/threat-protection-ai.png":::
13+
Microsoft Defender for Cloud's threat protection for AI services identifies threats to generative AI applications in real time and helps respond to security issues. Defender for Cloud's AI threat protection works with [Azure AI Content Safety Prompt Shields](/azure/ai-services/content-safety/concepts/jailbreak-detection) and Microsoft's threat intelligence to provide security alerts for threats like data leakage, data poisoning, jailbreak, and credential theft.
1814

1915
## Defender XDR integration
2016

21-
Threat protection for AI services integrates with the [Defender XDR](concept-integration-365.md), allowing security teams to centralize AI workload alerts in the Defender XDR portal.
22-
23-
Security teams can correlate AI workload alerts and incidents in the Defender XDR portal to understand the full scope of an attack, including malicious activities related to their generative AI applications.
17+
Threat protection for AI services integrates with the [Defender XDR](concept-integration-365.md), allowing security teams to centralize AI workload alerts in the Defender XDR portal. Security teams can correlate AI workload alerts and incidents in the Defender XDR portal to understand the full scope of an attack, including malicious activities related to their generative AI applications.
2418

2519
## Availability
2620

articles/defender-for-cloud/alerts-ai-workloads.md

Lines changed: 17 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,9 @@ This article lists the security alerts you might get for AI services from Micros
1919

2020
> [!NOTE]
2121
> Alerts from different sources might take different amounts of time to appear. For example, alerts that require analysis of network traffic might take longer to appear than alerts related to suspicious processes running on virtual machines.
22+
>
23+
> [!NOTE]
24+
> For alerts that are in preview: [!INCLUDE [Legalese](./includes/defender-for-cloud-preview-legal-text.md)]
2225
2326
## AI services alerts
2427

@@ -162,6 +165,16 @@ This article lists the security alerts you might get for AI services from Micros
162165

163166
**Severity**: Medium
164167

168+
### **Anomalous tool invocation**
169+
170+
(AI.Azure_AnomalousToolInvocation)
171+
172+
**Description:** This alert analyzes anomalous activity from an AI application connected to an Azure OpenAI model deployment. The application attempted to invoke a tool in a manner that deviates from expected behavior. This behavior may indicate potential misuse or an attempted attack through one of the tools available to the application.
173+
174+
**[MITRE tactics](alerts-reference.md#mitre-attck-tactics)**: Execution
175+
176+
**Severity**: Low
177+
165178
### (Preview) Suspicious anomaly detected in sensitive data exposed by an AI resource
166179

167180
(AI.Azure_SensitiveDataAnomaly)
@@ -172,19 +185,16 @@ This article lists the security alerts you might get for AI services from Micros
172185

173186
**Severity**: Medium
174187

175-
### **Anomalous tool invocation**
188+
### (Preview) LLM Reconnaissance Attempt Detected
176189

177-
(AI.Azure_AnomalousToolInvocation)
190+
(AI.Azure_LLMReconnaissance)
178191

179-
**Description:** This alert analyzes anomalous activity from an AI application connected to an Azure OpenAI model deployment. The application attempted to invoke a tool in a manner that deviates from expected behavior. This behavior may indicate potential misuse or an attempted attack through one of the tools available to the application.
192+
**Description:** A threat actor is interacting with your AI application in a way that resembles reconnaissance behavior, including attempts to extract system instructions, model capabilities, or bypass safety guardrails. These prompts may precede attempted prompt injection or jailbreak attacks. 
180193

181-
**[MITRE tactics](alerts-reference.md#mitre-attck-tactics)**: Execution
194+
**[MITRE tactics](alerts-reference.md#mitre-attck-tactics)**: Reconnaissance
182195

183196
**Severity**: Low
184197

185-
> [!NOTE]
186-
> For alerts that are in preview: [!INCLUDE [Legalese](./includes/defender-for-cloud-preview-legal-text.md)]
187-
188198
## Next steps
189199

190200
- [Security alerts in Microsoft Defender for Cloud](alerts-overview.md)

0 commit comments

Comments
 (0)