Overview
Litware, Inc. is a pharmaceutical company that has a subsidiary named Fabrikam, Inc.
Litware has offices in Boston and Seattle, but has employees located across the United States. Employees connect remotely to either office by using a VPN connection.
Existing Environment
Identity Environment
The network contains an Active Directory forest named litware.com that is linked to a Microsoft Entra tenant named litware.com. Microsoft Entra Connect uses pass-through authentication and has password hash synchronization disabled.
Litware.com contains a user named User1 who oversees all application development. User1 is NOT assigned to any Microsoft Entra roles.
Litware implements Microsoft Entra Application Proxy.
Fabrikam has a Microsoft Entra tenant named fabrikam.com. The users at Fabrikam access the resources in litware.com by using guest accounts in the litware.com tenant.
Cloud Environment
All the users at Litware have Microsoft 365 Enterprise E5 licenses. All the built-in anomaly detection policies in Microsoft Defender for Cloud Apps are enabled.
Litware has an Azure subscription associated with the litware.com Microsoft Entra tenant. The subscription contains a Microsoft Sentinel instance that uses the Microsoft Entra ID data connector and the Office 365 data connector. Microsoft Sentinel currently collects the Microsoft Entra sign-in logs and audit logs.
On-premises Environment
The on-premises network contains the servers shown in the following table.
Both Litware offices connect directly to the internet. Both offices connect to virtual networks in the Azure subscription by using a site-to-site VPN connection. All on-premises domain controllers are prevented from accessing the internet.
Requirements
Delegation Requirements
Litware identifies the following delegation requirements:
- Delegate the management of privileged roles by using Microsoft Entra Privileged Identity Management (PIM).
- Prevent nonprivileged users from registering applications in the litware.com Microsoft Entra tenant.
- Use custom programs for Identity Governance.
- Ensure that User1 can create enterprise applications in the Microsoft Entra tenant.
- Use the principle of least privilege.
Licensing Requirements
Litware recently added a custom user attribute named LWLicenses to the litware.com Active Directory forest. Litware wants to manage the assignment of Microsoft Entra ID service plans by modifying the value of the LWLicenses attribute. Users who have the appropriate value for LWLicenses must be added automatically to a Microsoft 365 group that has the appropriate licenses assigned.
Management Requirements
Litware wants to create a group named LWGroup1 that will contain all the Microsoft Entra user accounts for Litware but exclude all the Microsoft Entra guest accounts.
Authentication Requirements
Litware identifies the following authentication requirements:
- Implement multi-factor authentication (MFA) for all Litware users by using Conditional Access policies.
- Exempt users from using MFA to authenticate to Microsoft Entra ID from the Boston office of Litware.
- Implement a banned password list for the litware.com forest.
- Enforce MFA when accessing on-premises applications.
- Automatically detect and remediate externally leaked credentials.
Access Requirements
Litware identifies the following access requirements:
- Control all access to all Azure resources and Microsoft Entra ID applications by using Conditional Access policies.
- Implement a Conditional Access policy that has session controls for Microsoft SharePoint Online.
- Control privileged access to applications by using Microsoft Entra Access Reviews.
Monitoring Requirements
Litware wants to use the Fusion rule in Microsoft Sentinel to detect multi-staged attacks that include a combination of suspicious Microsoft Entra sign-ins followed by anomalous Microsoft Office 365 activity.
