Overview
Fabrikam, Inc. is a financial services company.
The company has branch offices in New York, London, and Singapore. Fabrikam has remote users located across the globe. The remote users access company resources, including cloud resources, by using a VPN connection to a branch office.
Existing Environment
Identity Environment
The network contains an Active Directory Domain Services (AD DS) forest named fabrikam.com that syncs with an Azure AD tenant named fabrikam.com. To sync the forest, Fabrikam uses Azure AD Connect with pass-through authentication enabled and password hash synchronization disabled.
The fabrikam.com forest contains two global groups named Group1 and Group2.
Microsoft 365 Environment
All the users at Fabrikam are assigned a Microsoft 365 E5 license and an Azure Active Directory Premium Plan 2 license.
Fabrikam implements Microsoft Defender for Identity and Microsoft Defender for Cloud Apps and enables log collectors.
Azure Environment
Fabrikam has an Azure subscription that contains the resources shown in the following table.
Amazon Web Services (AWS) Environment
Fabrikam has an Amazon Web Services (AWS) account named Account1. Account1 contains 100 Amazon Elastic Compute Cloud (EC2) instances that run a custom Windows Server 2022. The image includes Microsoft SQL Server 2019 and does NOT have any agents installed.
Current Issues
When the users use the VPN connections, Microsoft 365 Defender raises a high volume of impossible travel alerts that are false positives.
Defender for Identity raises a high volume of Suspected DCSync attack alerts that are false positives.
Requirements
Planned changes
Fabrikam plans to implement the following services:
1. Microsoft Defender for Cloud
2. Microsoft Sentinel
Business Requirements
Fabrikam identifies the following business requirements:
1. Use the principle of least privilege, whenever possible.
2. Minimize administrative effort.
Microsoft Defender for Cloud Apps Requirements
Fabrikam identifies the following Microsoft Defender for Cloud Apps requirements:
1. Ensure that impossible travel alert policies are based on the previous activities of each user.
2. Reduce the amount of impossible travel alerts that are false positives.
Microsoft Defender for Identity Requirements
Minimize the administrative effort required to investigate the false positive alerts.
Microsoft Defender for Cloud Requirements
Fabrikam identifies the following Microsoft Defender for Cloud requirements:
1. Ensure that the members of Group2 can modify security policies.
2. Ensure that the members of Group1 can assign regulatory compliance policy initiatives at the Azure subscription level.
3. Automate the deployment of the Azure Connected Machine agent for Azure Arc-enabled servers to the existing and future resources of Account1.
4. Minimize the administrative effort required to investigate the false positive alerts.
Microsoft Sentinel Requirements
Fabrikam identifies the following Microsoft Sentinel requirements:
1. Query for NXDOMAIN DNS requests from the last seven days by using built-in Advanced Security
Information Model (ASIM) unifying parsers.
2. From AWS EC2 instances, collect Windows Security event log entries that include local group membership changes.
3. Identify anomalous activities of Azure AD users by using User and Entity Behavior Analytics (UEBA).
4. Evaluate the potential impact of compromised Azure AD user credentials by using UEBA.
5. Ensure that App1 is available for use in Microsoft Sentinel automation rules.
6. Identify the mean time to triage for incidents generated during the last 30 days.
7. Identify the mean time to close incidents generated during the last 30 days.
8. Ensure that the members of Group1 can create and run playbooks.
9. Ensure that the members of Group1 can manage analytics rules.
10. Run hunting queries on Pool1 by using Jupyter notebooks.
11. Ensure that the members of Group2 can manage incidents.
12. Maximize the performance of data queries.
13. Minimize the amount of collected data.
