docs: add and update ZTW workshop guidance (AI + devices) (#1452)

…update

Author: tylchan

src/react/docs/workshop-guidance/AI/AI_089.md

@@ -1,21 +1,32 @@
-# Deploy Microsoft Sentinel workspace for AI threat detection
+# AI related data connectors enabled on Microsoft Sentinel/SIEM workspace
 
-**Implementation Effort:** Medium – Requires provisioning a Log Analytics workspace, onboarding Microsoft Sentinel, configuring data connectors for AI workload telemetry, and setting retention policies appropriate for security investigation timelines.  
-**User Impact:** Low – Infrastructure deployment; end users are not affected.
+**Implementation Effort:** Medium – Requires enabling and configuring multiple data connectors in an existing Microsoft Sentinel workspace, validating that AI-relevant log tables are ingesting correctly, and confirming alert flow end-to-end from each source into Sentinel incidents.  
+**User Impact:** Low – Infrastructure configuration; end users are not affected.
 
 ## Overview
 
-AI workloads generate security-relevant telemetry — Azure OpenAI diagnostic logs, agent identity sign-in events, Copilot interaction records — but without a centralized SIEM platform, this data sits in isolated logs with no correlation, no detection logic, and no incident management workflow. Deploying a Microsoft Sentinel workspace is the foundational step that makes everything else in the AI threat detection and response lifecycle possible: analytics rules, playbooks, automation rules, workbooks, and Defender XDR integration all depend on this workspace existing.
+A Microsoft Sentinel workspace without the right data connectors provides no visibility into AI threats. The connectors determine which telemetry is available for analytics rules, workbooks, hunting queries, and incident investigation — and for AI security, those sources span identity, cloud posture, data governance, and AI-native signals. Enabling the correct set of AI-related connectors is the prerequisite for every downstream detection and response capability in this pillar.
 
-The workspace must be scoped and configured with AI threat detection in mind. This means connecting the right data sources — Azure OpenAI diagnostics, Entra ID sign-in and audit logs for agent identities, Defender for Cloud alerts for AI services, and Microsoft 365 activity logs for Copilot interactions — and setting retention periods long enough to support investigation of slow-moving AI threats like gradual model manipulation or sustained prompt injection campaigns.
++ The **Microsoft Defender XDR** connector is the highest-priority integration. It streams correlated incidents and raw alerts from across the Defender portfolio — endpoint, identity, cloud apps, and AI services — into Sentinel as unified incidents. This is what enables cross-domain attack chain visibility: a phishing campaign leading to identity compromise, followed by agent abuse, surfaces as a single correlated incident rather than isolated alerts across separate consoles. 
 
-This supports *Assume breach* by establishing the detection and investigation platform that enables the organization to identify, correlate, and respond to AI-specific security events. It supports *Verify explicitly* by centralizing the identity and activity telemetry needed to validate whether AI workload behavior is legitimate. Without this workspace, the organization has no ability to detect, investigate, or respond to threats targeting its AI workloads — alerts go uncreated, incidents go unmanaged, and threat actors operate unobserved.
++ The **Microsoft Entra ID** and **Microsoft Entra ID Protection** connectors provide identity telemetry for agent workload identities. Sign-in logs, audit logs, and risk detections for service principals, managed identities, and app registrations are essential for detecting anomalous authentication patterns — unexpected token issuances, unauthorized changes to agent app permissions, or risk events on identities that should exhibit consistent, predictable behavior. Without these connectors, identity-based threats to agent infrastructure generate no signal in Sentinel.
+
++ **Defender for AI Services alerts via Microsoft Defender for Cloud (MDC)** delivers platform-level AI threat signals: prompt injection detections, jailbreak attempts, credential harvesting patterns, and data exfiltration indicators from Azure OpenAI and Azure AI Foundry endpoints. This connector is the primary source of AI-native security alerts and must be validated to confirm alerts flow from Defender for Cloud into Sentinel before analytics rules that depend on `SecurityAlert` are authored. 
+
++ The **Microsoft Purview Information Protection** connector surfaces data sensitivity events — DLP policy violations and high-sensitivity label activity triggered by AI-generated content — enabling detection of data oversharing through Copilot and agent interfaces. These events are frequently the earliest observable signal of an AI workload accessing or emitting data beyond its intended scope.
+
++ The **Microsoft 365 Copilot** connector (via Microsoft Purview Audit) ingests Copilot interaction logs: user prompts, Copilot responses, plugin and connector activity, and grounding data access events. This data is required for investigating Copilot-specific incidents such as prompt injection through document grounding or unintended exposure of sensitive data in Copilot responses. 
+
++ The **Agent 365** connector provides agent lifecycle and activity telemetry from the Agent 365 Registry, enabling detection of unauthorized agent deployments, access control modifications, and anomalous runtime behavior across the organization's agent population. Together, these seven connectors establish the complete telemetry surface needed to detect, investigate, and respond to threats across the full AI workload lifecycle — from identity compromise and network interception to data exfiltration and agent runtime abuse.
+
+This supports *Assume breach* by ensuring that every layer of the AI stack — identity, platform, data, and application — contributes security telemetry to a centralized detection surface. It supports *Verify explicitly* by enabling continuous correlation of AI workload activity against known-bad patterns and organization-specific behavioral baselines. Without these connectors enabled and validated, analytics rules produce no results, investigations have no evidence, and threat actors targeting AI infrastructure operate without generating a single Sentinel alert.
 
 ## Reference
 
-* [Microsoft Sentinel overview](https://learn.microsoft.com/en-us/azure/sentinel/overview)
-* [Prerequisites for deploying Microsoft Sentinel](https://learn.microsoft.com/en-us/azure/sentinel/prerequisites)
-* [Onboard Microsoft Sentinel](https://learn.microsoft.com/en-us/azure/sentinel/quickstart-onboard)
-* [Best practices for Microsoft Sentinel workspace architecture](https://learn.microsoft.com/en-us/azure/sentinel/best-practices-workspace-architecture)
-* [Connect data sources to Microsoft Sentinel](https://learn.microsoft.com/en-us/azure/sentinel/connect-data-sources)
-* [Microsoft Sentinel pricing](https://learn.microsoft.com/en-us/azure/sentinel/billing)
+* [Connect Microsoft Defender XDR data to Microsoft Sentinel](https://learn.microsoft.com/en-us/azure/sentinel/connect-microsoft-365-defender)
+* [Connect Microsoft Entra ID data to Microsoft Sentinel](https://learn.microsoft.com/en-us/azure/sentinel/connect-azure-active-directory)
+* [Microsoft Entra ID Protection connector for Microsoft Sentinel](https://learn.microsoft.com/en-us/azure/sentinel/data-connectors/microsoft-entra-id-protection)
+* [Integrate Microsoft Defender for Cloud alerts with Microsoft Sentinel](https://learn.microsoft.com/en-us/azure/sentinel/connect-defender-for-cloud)
+* [Overview of AI threat protection in Microsoft Defender for Cloud](https://learn.microsoft.com/en-us/azure/defender-for-cloud/ai-threat-protection)
+* [Microsoft Purview Information Protection connector for Microsoft Sentinel](https://learn.microsoft.com/en-us/azure/sentinel/data-connectors/microsoft-purview-information-protection)
+* [Connect Microsoft 365 Copilot data to Microsoft Sentinel](https://learn.microsoft.com/en-us/azure/sentinel/data-connectors/microsoft-copilot-for-microsoft-365)

src/react/docs/workshop-guidance/AI/AI_104.md

@@ -1,21 +1,20 @@
-# Enable Defender for Cloud AI security posture management
+# Discover AI workloads & models with Defender CSPM
+
+**Implementation Effort:** Medium – Requires enabling the Defender CSPM plan on Azure subscriptions hosting AI workloads; for AWS accounts, permissions must be reconfigured to enable AI posture capabilities.
 
-**Implementation Effort:** Medium – Requires the Defender CSPM plan to be enabled on Azure subscriptions hosting AI workloads; for AWS accounts, permissions must be reconfigured to enable AI posture capabilities.  
 **User Impact:** Low – Infrastructure-level security assessment; end users are not affected.
 
 ## Overview
 
-Organizations deploying Azure OpenAI, Azure AI Foundry, Azure Machine Learning, and multi-cloud AI workloads on AWS Bedrock or Google Vertex AI need to know what AI components exist in their environment and whether those components are securely configured. Without AI security posture management, the security team cannot systematically discover deployed AI models, identify vulnerable AI library dependencies in container images, detect Infrastructure as Code misconfigurations in AI service deployments, or analyze attack paths that could expose AI workloads to compromise. Each of these gaps represents a category of risk that remains invisible until exploited.
+Before AI workloads can be secured, they must be discovered. Azure AI Foundry models, Azure OpenAI deployments, MCP servers, and AI-enabled applications are cloud resources that accumulate misconfigurations and exposure risks just like any other workload — but they often fall outside the scope of existing cloud security reviews because they are newer, moved quickly through deployment, and lack the same governance maturity as traditional infrastructure. Defender CSPM provides the discovery and posture assessment layer that brings AI resources into the same security management surface as the rest of the cloud estate.
+
+Enabling the Defender CSPM plan on subscriptions hosting AI workloads activates agentless scanning that identifies Azure OpenAI and Azure AI Foundry resources, assesses their configurations against the Microsoft Cloud Security Benchmark, and surfaces AI-specific security recommendations. These recommendations cover model endpoint exposure, network access controls, diagnostic logging enablement, private endpoint configuration, and identity-based access to model deployments. The cloud security explorer allows security teams to query relationships between AI resources, the identities that access them, and the data they interact with — enabling attack path analysis that reveals how a misconfigured AI endpoint could serve as a lateral movement vector into broader cloud infrastructure.
 
-Defender for Cloud's AI security posture management, part of the Defender CSPM plan, provides continuous discovery of the AI Bill of Materials — application components, data sources, and AI artifacts — from code to cloud. It discovers AI workloads across Azure OpenAI, Azure AI Foundry, Azure Machine Learning, Amazon Bedrock, and Google Vertex AI, and extends to AI agent workloads deployed through Azure AI Foundry and Copilot Studio. The capability surfaces security recommendations on identity, data security, and internet exposure, detects IaC misconfigurations early in the development cycle, identifies vulnerable generative AI library dependencies, and provides attack path analysis that maps how threat actors could move from an initial foothold to AI workload compromise.
+For multicloud environments, the CSPM plan can be extended to AWS accounts where AI workloads are deployed. The resulting asset inventory feeds directly into the Microsoft Security Dashboard for AI, providing the model and application layer of the AI inventory alongside agents registered in Agent 365.
 
-This supports *Assume breach* by continuously analyzing how AI workloads could be attacked and what data would be exposed, enabling the organization to remediate the highest-risk paths before they are exploited. It supports *Verify explicitly* by assessing each AI workload's configuration against security recommendations and surfacing deviations from secure baselines. Without this capability, AI workloads are deployed and operated without systematic security assessment, misconfigurations persist undetected, and the organization's AI attack surface grows with each new model deployment.
+This supports *Assume breach* by providing continuous posture assessment of AI resources, ensuring that newly deployed models and endpoints are evaluated against security requirements before they can be exploited. It supports *Verify explicitly* by maintaining a live inventory of AI workloads with their current configuration state, making it possible to verify that every deployed model meets the organization's security baseline. Without this plan enabled, AI resources are invisible to the cloud security posture management surface — misconfigurations go undetected, attack paths through AI endpoints go unanalyzed, and the Security Dashboard for AI shows an incomplete inventory.
 
 ## Reference
 
-* [AI security posture management overview](https://learn.microsoft.com/en-us/azure/defender-for-cloud/ai-security-posture)
-* [Discover generative AI workloads](https://learn.microsoft.com/en-us/azure/defender-for-cloud/identify-ai-workload-model)
-* [Explore risks to predeployed generative AI artifacts](https://learn.microsoft.com/en-us/azure/defender-for-cloud/explore-ai-risk)
-* [Identify and remediate attack paths](https://learn.microsoft.com/en-us/azure/defender-for-cloud/how-to-manage-attack-path)
-* [Manage generative AI apps for your organization](https://learn.microsoft.com/en-us/copilot/microsoft-365/manage-generative-ai-apps)
-* [Microsoft Defender for Cloud pricing](https://learn.microsoft.com/en-us/azure/defender-for-cloud/plan-defender-for-servers-select-plan)
+* [Enable Defender CSPM plan](https://learn.microsoft.com/en-us/azure/defender-for-cloud/tutorial-enable-cspm-plan)
+* [AI security posture management in Defender for Cloud](https://learn.microsoft.com/en-us/azure/defender-for-cloud/ai-security-posture)