Resolve syncing conflicts from repo_sync_working_branch to main

security-docs/zero-trust/deploy/overview.md

@@ -53,38 +53,21 @@ Technology pillars don't define outcomes (business solutions) or steps (technica
 
 | Technology pillar | Description |
 | --- | --- |
-| [![Fingerprint icon](../media/icon-identity-small.png)](identity.md) <br> [Identities](identity.md) | Identities—whether they represent people, services, or IoT devices—define the Zero Trust control plane. When an identity attempts to access a resource, verify that identity with strong authentication, and ensure access is compliant and typical for that identity. Follow least privilege access principles. |
-| [![Endpoints icon.](../media/icon-endpoints-small.png)](endpoints.md) <br> [Endpoints](endpoints.md) |  Once an identity has been granted access to a resource, data can flow to a variety of different endpoints (devices), from IoT devices to smartphones, BYOD to partner-managed devices, and on-premises workloads to cloud-hosted servers. This diversity creates a massive attack surface area. Monitor and enforce device health and compliance for secure access. |
-| [![Ones and zeroes icon.](../media/icon-data-small.png)](data.md) <br> [Data](data.md)  | Ultimately, security teams are protecting data. Where possible, data should remain safe even if it leaves the devices, apps, infrastructure, and networks the organization controls. Classify, label, and encrypt data, and restrict access based on those attributes. |
-| [![Application window icon.](../media/icon-applications-small.png)](applications.md) <br> [Apps](applications.md)| Applications and APIs provide the interface by which data is consumed. They may be legacy on-premises workloads, lifted-and-shifted to cloud workloads, or modern SaaS applications. Apply controls and technologies to discover shadow IT, ensure appropriate in-app permissions, gate access based on real-time analytics, monitor for abnormal behavior, control user actions, and validate secure configuration options. |
-| [![Data storage disks icon.](../media/icon-infrastructure-small.png)](infrastructure.md) <br> [Infrastructure](infrastructure.md) | Infrastructure—whether on-premises servers, cloud-based VMs, containers, or micro-services—represents a critical threat vector. Assess for version, configuration, and JIT access to harden defense. Use telemetry to detect attacks and anomalies, and automatically block and flag risky behavior and take protective actions. |
-| [![Network diagram icon.](../media/icon-networks-small.png)](networks.md) <br> [Network](networks.md) | All data is ultimately accessed over network infrastructure. Networking controls can provide critical controls to enhance visibility and help prevent attackers from moving laterally across the network. Segment networks (and do deeper in-network micro-segmentation) and deploy real-time threat protection, end-to-end encryption, monitoring, and analytics. |
-| [![Gear icon.](../media/icon-visibility-automation-orchestration-small.png)](visibility-automation-orchestration.md) <br> [Visibility, automation, and orchestration](visibility-automation-orchestration.md) | In our Zero Trust guides, we define the approach to implement an end-to-end Zero Trust methodology across identities, endpoints (devices), data, apps, infrastructure, and network. These activities increase your visibility, which gives you better data for making trust decisions. With each of these individual areas generating their own relevant alerts, we need an integrated capability to manage the resulting influx of data to better defend against threats and validate trust in a transaction. |
-
-## Documentation set
-
-Follow this table for the best Zero Trust documentation sets for your needs.
-
-|Documentation set|Helps you...|Roles|
-|---|---|---|
-|[Adoption framework](../adopt/zero-trust-adoption-overview.md) for phase and step guidance for key business solutions and outcomes|Apply Zero Trust protections from the C-suite to the IT implementation.|Security architects, IT teams, and project managers|
-|[Assessment and progress tracking resource](../zero-trust-assessment-progress-tracking-resources.md) |Assess your infrastructure's readiness and track your progress. |Security architects, IT teams, and project managers|
-|[Zero Trust partner kit](../zero-trust-partner-kit.md) |Co-branded tracking resources, workshop, and architecture illustrations |Partners and security architects |
-|[Deployment for technology pillars](../deploy/overview.md) for conceptual information and deployment objectives|Apply Zero Trust protections aligned with typical IT technology areas.|IT teams and security staff|
-|[Zero Trust for small businesses](../guidance-smb-partner.md)|Apply Zero Trust principles to small business customers.|Customers and partners working with Microsoft 365 for business|
-|[Zero Trust for Microsoft Copilots](../copilots/apply-zero-trust-copilots-overview.md) for stepped and detailed design and deployment guidance|Apply Zero Trust protections to Microsoft Copilots.|IT teams and security staff|
-|[Zero Trust deployment plan with Microsoft 365](/microsoft-365/security/microsoft-365-zero-trust?bc=%2fsecurity%2fzero-trust%2fbreadcrumb%2ftoc.json&toc=%2fsecurity%2fzero-trust%2ftoc.json) for stepped and detailed design and deployment guidance|Apply Zero Trust protections to your Microsoft 365 organization.|IT teams and security staff|
-|[Incident response with XDR and integrated SIEM](../siem-xdr-overview.md)|Set XDR tools and integrate these with Microsoft Sentinel|IT teams and security staff|
-|[Zero Trust for Azure services](../azure-infrastructure-overview.md) for stepped and detailed design and deployment guidance|Apply Zero Trust protections to Azure workloads and services.|IT teams and security staff|
-|[Partner integration with Zero Trust](../integrate/overview.md) for design guidance for technology areas and specializations|Apply Zero Trust protections to partner Microsoft cloud solutions.|Partner developers, IT teams, and security staff|
-|[Develop using Zero Trust principles](../develop/overview.md) for application development design guidance and best practices|Apply Zero Trust protections to your application.|Application developers|
-|US Government guidance for [CISA](/security/zero-trust/cisa-zero-trust-maturity-model-intro), [DoD](/security/zero-trust/dod-zero-trust-strategy-intro), and the [Memorandum for Zero Trust architecture](/entra/standards/memo-22-09-meet-identity-requirements) |Prescriptive recommendations for US Government requirements |IT Architects and IT teams|
-
-## Recommended training
-
-|Training  | [Establish the guiding principles and core components of Zero Trust](/training/paths/zero-trust-principles/) |
-|---------|---------|
-|:::image type="icon" source="../media/basics-of-zero-trust.png" border="false"::: | Use this learning path to understand the basics of applying Zero Trust principles to the key technology pillars of identities, endpoints, application access, networks, infrastructure, and data. |
-> [!div class="nextstepaction"]
-> [Start >](/training/paths/zero-trust-principles/)
+| [![Fingerprint icon](../media/icon-identity-small.png)](identity.md) <br> [Identities](identity.md) | Control access decisions. Every request starts with identity verification and enforcement of least privilege. |
+| [![Endpoints icon.](../media/icon-endpoints-small.png)](endpoints.md) <br> [Endpoints](endpoints.md) |  Evaluate and enforce device trust. Access depends on device health, compliance, and risk. |
+| [![Ones and zeroes icon.](../media/icon-data-small.png)](data.md) <br> [Data](data.md)  | Protect the asset itself. Security persists with the data through classification, labeling, encryption, and access control. |
+| [![Application window icon.](../media/icon-applications-small.png)](applications.md) <br> [Apps](applications.md)| Govern how data is accessed. Apply controls at the application and API layer, including permissions and session controls. |
+| [![Data storage disks icon.](../media/icon-infrastructure-small.png)](infrastructure.md) <br> [Infrastructure](infrastructure.md) | Secure compute resources. Harden servers, VMs, containers, and services through configuration, access control, and monitoring. |
+| [![Network diagram icon.](../media/icon-networks-small.png)](networks.md) <br> [Network](networks.md) | Control connectivity and movement. Segment and monitor traffic to prevent lateral movement and enforce secure communication.|
+| [![Gear icon.](../media/icon-visibility-automation-orchestration-small.png)](visibility-automation-orchestration.md) <br> [SecOps](visibility-automation-orchestration.md) |Integrate and operationalize all pillars. Detect, investigate, and respond using signals from across the environment. |
+
+## Zero Trust implementation workshops
+
+Microsoft's Zero Trust implementation workshops are available for each pillar. [Learn more](../workshop-zero-trust-overview.md).
+
+## What's next?
+
+- [Review](../implement-overview.md) technical solutions.
+- [Learn about](../security-adoption-model.md) our Zero Trust adoption model.
+- [Review](../security-adoption-business-scenarios-overview.md) critical security business scenarios.