Alerting: Cayosoft Guardian built-in alerting rules
This document contains a list of built-in alerting rules in Cayosoft Guardian.
To enable, disable or modify built-in rules:
- Open Cayosoft Guardian web portal.
- Expand the Configuration node and click Alerting Rules node.
- To view or edit the rule select the rule and click Properties.
List of built-in alerting rules with description
Rule name and scope |
Threat description |
Rule description and additional information |
|---|---|---|
|
Name: AdminSDHolder security descriptor changed Scope: Active Directory |
Every hour, the domain controller that holds the primary domain controller (PDC) Flexible Single Master Operation (FSMO) role compares the ACL on all security principal accounts (users, groups, and machine accounts) present for its domain in Active Directory and that are in administrative or security-sensitive groups and which have AdminCount attribute = 1 against the ACL on the AdminSDHolder object. If the ACL on the principal account differs from the ACL on the AdminSDHolder object, then the ACL on the principal account is reset to match the ACL on the AdminSDHolder object and this event is generated. That means if an administrator sees inappropriate permission on a protected object and removes it, within an hour those permissions will be put back in place by SDProp. Described behaviour opens a potential attack path. An attacker might modify permissions on the AdminSDHolder object so those permissions will automatically be applied to all protected objects. This gives an attacker a way to create persistent access to privileged accounts within the domain. |
A built-in alerting rule AdminSDHolder security descriptor changed raises an alert in case of any modification of the AdminSDHolder object. Cayosoft Guardian also detects permission modifications made by SDProp and creates change records for each changed object. |
|
Name: AD Administrators Group membership changed Scope: Active Directory |
"Privileged" groups in Active Directory are those to which powerful rights, privileges, and permissions are granted that allow them to perform nearly any action in Active Directory and on domain-joined systems. A new account added to such a powerful group can impose a risk. |
A built-in alerting rule AD Administrators Group membership changed raises an alert in case of any members added to the following groups in the Active Directory Domain: Administrators, Backup Operators, Server Operators, ADSyncAdmins, DnsAdmins, Domain Admins, Enterprise Admins, Schema Admins. |
|
Name: Azure AD Global Administrator role membership changed Scope: Azure AD |
Global Administrator can manage all aspects of Azure AD and Microsoft services that use Azure AD identities. A new account added to such a powerful role can impose a risk. |
A built-in alerting rule Azure AD Global Administrator role membership changed raises an alert in case of any members added to the following roles in the Azure AD tenant: Global Administrator, Company Administrator. |
|
Name: Azure AD Global Administrator elevated access to Azure Resources Scope: Azure |
By default, a user with a Global Administrator role doesn’t have access to Azure resources. Azure AD and Azure resources are secured independently from one another. There are some scenarios mentioned by Microsoft where a user with a Global Administrator role requires access to Azure resources:
Any Global Administrator can assign himself a User Access Administrator role in Azure at the root scope (/). This elevated role allows a user with a Global Administrator role getting access to any subscription or management group in the directory. |
A built-in alerting rule Azure AD Global Administrator elevated access to Azure Resources raises an alert in case of any Global Administrator elevated access to manage all Azure subscriptions and management groups. |
|
Name: Guest user added to group Scope: Azure AD |
With External Identities previously known as Guests in Azure AD, you can allow people outside your organization to access your apps and resources while letting them sign in using whatever identity they prefer. Some groups might have access to sensitive data and it is important to monitor guest accounts that are added to such a group. |
A built-in alerting rule Guest user added to group raises an alert in case of any guest is added to a group in Azure AD. |
|
Name: New Guest user created Scope: Azure AD |
With External Identities previously known as Guests in Azure AD, you can allow people outside your organization to access your apps and resources while letting them sign in using whatever identity they prefer. Depending on Azure AD settings member user can invite guest users into the directory and guest user might get access to sensitive data. |
A built-in alerting rule New Guest user created raises an alert in each case of new guest user is created in the in Azure AD. |
|
Name: Full access permission added for Exchange mailbox Scope: Exchange Online |
In Exchange Online, you can use the Exchange admin center (EAC) or Exchange Online PowerShell to assign permissions to a mailbox or group so that other users can access the mailbox (the Full Access permission), or send email messages that appear to come from the mailbox or group (the Send As or Send on Behalf permissions). The users that are assigned these permissions on other mailboxes or groups are called delegates. Such delegation might impose a risk of exposing sensitive data. |
A built-in alerting rules Full access permission added for Exchange mailbox, SendAs access permission added for Exchange mailbox, Full access permission added for Exchange mailbox raise an alert in each case of related permission is assigned on an Exchange Online Mailbox. |
|
Name: SendAs access permission added for Exchange mailbox Scope: Exchange Online | ||
|
Name: Full access permission added for Exchange mailbox Scope: Exchange Online | ||
|
Name: Forwarding rule added for Exchange mailbox Scope: Exchange Online |
As an admin, you might have company requirements to restrict or control automatically forwarded messages to external recipients (recipients outside of your organization). Email forwarding can be a useful, but can also pose a security risk due to the potential disclosure of information. Attackers might use this information to attack your organization or partners. |
A built-in alerting rule Forwarding rule added for Exchange mailbox raises an alert in each case of a forwarding rule is added for Exchange Online Mailbox. |
|
Name: Team guest settings changes Scope: Teams |
With External Identities previously known as Guests in Azure AD, you can allow people outside your organization to access your apps and resources while letting them sign in using whatever identity they prefer. Depending on Team settings guest users might get access to sensitive data. |
A built-in alerting rule Team guest settings changes raise an alert in each case guest settings are changed for a specific Team. |
Comments
0 comments
Please sign in to leave a comment.