Out-of-the-Box Detection Rules
Last updated
Was this helpful?
Last updated
Was this helpful?
Scanner provides pre-configured detection rules for common enterprise log sources, enabling immediate security monitoring capabilities across your cloud and SaaS infrastructure. These detections are maintained as YAML files in public GitHub repositories, making them easy to review, import, and customize.
Scanner currently supports the following log sources with ready-to-use detection rules:
AWS CloudTrail - Detection rules for AWS audit logs and CloudTrail events
Repository:
Google Cloud Platform (GCP) - Detection rules for GCP audit and security logs
Repository:
Microsoft Azure - Detection rules for Azure activity and security logs
Repository:
Okta - Detection rules for Okta authentication and administration events
Repository:
Auth0 - Detection rules for Auth0 authentication logs
Repository:
Cisco Duo - Detection rules for Duo Security authentication events
Repository:
GitHub - Detection rules for GitHub organization and repository events
Microsoft 365 - Detection rules for Microsoft 365 audit logs
Slack - Detection rules for Slack workspace events
Google Workspace (formerly GSuite) - Detection rules for Google Workspace admin and security logs
Snowflake - Detection rules for Snowflake database access and usage
Windows Process Creation Events - Detection rules for Windows process creation events
To add these detection rules in your Scanner environment:
Navigate to Detections.
Click New > Add Rules From Github:
Under Connected Repositories, click Add Repository:
Under Repository, enter the name of the repository containing the out-of-the-box detection rules you want to add, eg. scanner-inc/detection-rules-aws-cloudtrail. A matching option should appear in the dropdown list - click it:
Under Branch, select main.
Once the repository and branch have been selected, you should see Assign Event Sinks, which will allow you to send alerts of different severity levels to different destinations as you wish:
Click Add Repository.
The out-of-the-box detection rules will be continuously synced to your environment as new commits are pushed to the main branch of the repository.
Scanner's detection rules are designed to be flexible and adaptable to your organization's specific needs. You can fork any of the detection rule repositories to create your own customized version while maintaining the ability to pull updates from the official repositories. Through Scanner's interface, individual rules can be enabled or disabled, allowing you to activate only the detections relevant to your environment.
Detection rules include configurable parameters that can be adjusted to match your security requirements, such as detection thresholds, time windows, and severity levels. These parameters can be modified in the YAML files to optimize detection sensitivity for your environment.
If you develop improvements that could benefit the broader community, you can contribute them back to the main repositories through pull requests.
Repository:
Repository:
Repository:
Repository:
Repository:
Repository:
