|
| 1 | +--- |
| 2 | + |
| 3 | +title: Conditional access gap analyzer workbook in Azure AD | Microsoft Docs |
| 4 | +description: Learn how to use the conditional access gap analyzer workbook. |
| 5 | +services: active-directory |
| 6 | +documentationcenter: '' |
| 7 | +author: MarkusVi |
| 8 | +manager: karenho |
| 9 | +editor: '' |
| 10 | + |
| 11 | +ms.service: active-directory |
| 12 | +ms.topic: reference |
| 13 | +ms.workload: identity |
| 14 | +ms.subservice: report-monitor |
| 15 | +ms.date: 11/05/2021 |
| 16 | +ms.author: markvi |
| 17 | +ms.reviewer: sarbar |
| 18 | + |
| 19 | +ms.collection: M365-identity-device-management |
| 20 | +--- |
| 21 | + |
| 22 | +# Sensitive operations report workbook |
| 23 | + |
| 24 | + |
| 25 | + |
| 26 | +This article provides you with an overview of this workbook. |
| 27 | + |
| 28 | + |
| 29 | +## Description |
| 30 | + |
| 31 | + |
| 32 | + |
| 33 | + |
| 34 | +This workbook is intended to help identify suspicious application and service principal activity that may indicate compromises in your environment. |
| 35 | + |
| 36 | + |
| 37 | +This workbook identifies recent sensitive operations that have been performed in your tenant and which may service principal compromise. |
| 38 | + |
| 39 | + |
| 40 | + |
| 41 | + |
| 42 | +## Sections |
| 43 | + |
| 44 | +This workbook is split into four sections: |
| 45 | + |
| 46 | + |
| 47 | + |
| 48 | + |
| 49 | +- **Modified application and service principal credentials/authentication methods** - This report flags actors who have recently changed many service principal credentials, as well as how many of each type of service principal credentials have been changed. |
| 50 | + |
| 51 | +- **New permissions granted to service principals** - This workbook also highlights recently granted OAuth 2.0 permissions to service principals. |
| 52 | + |
| 53 | +- **Directory role and group membership updates for service principals** |
| 54 | + |
| 55 | + |
| 56 | + |
| 57 | +- **Modified federation settings** - This report highlights when a user or application modifies federation settings on a domain. For example, it reports when a new Active Directory Federated Service (ADFS) TrustedRealm object, such as a signing certificate, is added to the domain. Modification to domain federation settings should be rare. |
| 58 | + |
| 59 | + |
| 60 | + |
| 61 | + |
| 62 | +### Modified application and service principal credentials/authentication methods |
| 63 | + |
| 64 | +One of the most common ways for attackers to gain persistence in the environment is by adding new credentials to existing applications and service principals. This allows the attacker to authenticate as the target application or service principal, granting them access to all resources to which it has permissions. |
| 65 | + |
| 66 | +This section includes the following data to help you detect: |
| 67 | + |
| 68 | +- All new credentials added to apps and service principals, including the credential type |
| 69 | + |
| 70 | +- Top actors and the amount of credentials modifications they performed |
| 71 | + |
| 72 | +- A timeline for all credential changes |
| 73 | + |
| 74 | + |
| 75 | + |
| 76 | +### New permissions granted to service principals |
| 77 | + |
| 78 | +In cases where the attacker cannot find a service principal or an application with a high privilege set of permissions through which to gain access, they will often attempt to add the permissions to another service principal or app. |
| 79 | + |
| 80 | +This section includes a breakdown of the AppOnly permissions grants to existing service principals. Admins should investigate any instances of excessive high permissions being granted, including, but not limited to, Exchange Online, Microsoft Graph and Azure AD Graph. |
| 81 | + |
| 82 | + |
| 83 | +## Directory role and group membership updates for service principals |
| 84 | + |
| 85 | +Following the logic of the attacker adding new permissions to existing service principals and applications, another approach is adding them to existing directory roles or groups. |
| 86 | + |
| 87 | +This section includes an overview of all changes made to service principal memberships and should be reviewed for any additions to high privilege roles and groups. |
| 88 | + |
| 89 | + |
| 90 | + |
| 91 | +### Modified federation settings |
| 92 | + |
| 93 | +Another common approach to gaining a long-term foothold in the environment is modifying the tenant’s federated domain trusts and effectively adding an additional, attacker controlled, SAML IDP as a trusted authentication source. |
| 94 | + |
| 95 | +This section includes the following data: |
| 96 | + |
| 97 | +- Changes performed to existing domain federation trusts |
| 98 | + |
| 99 | +- Addition of new domains and trusts |
| 100 | + |
| 101 | + |
| 102 | + |
| 103 | + |
| 104 | + |
| 105 | +## Filters |
| 106 | + |
| 107 | +This workbook doesn't have filters. |
| 108 | + |
| 109 | + |
| 110 | +## Best practice |
| 111 | + |
| 112 | + |
| 113 | +**Use:** |
| 114 | + |
| 115 | +- **Modified application and service principal credentials** to look out for credentials being added to service principals which are not frequently used in your organization. Use the filters present in this section to further investigate any of the suspicious actors or service principals that were modified. |
| 116 | + |
| 117 | + |
| 118 | +- **New permissions granted to service principals** to look out for broad or excessive permissions being added to service principals by actors that may be compromised. |
| 119 | + |
| 120 | +- **Modified federation settings** section to confirm that the added or modified target domain/URL is a legitimate admin behavior. Any actions which modify or add domain federation trusts are rare and should be treated as high fidelity to be investigated as soon as possible. |
| 121 | + |
| 122 | + |
| 123 | + |
| 124 | + |
| 125 | + |
| 126 | +## Next steps |
| 127 | + |
| 128 | +- [How to use Azure AD workbooks](howto-use-azure-monitor-workbooks.md) |
0 commit comments