-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for other rule types #12
Comments
Can we perhaps agree on some sort of documented format on how to store these as YAML?
|
Definitely. I will create some extensive YAML files that we can use for validation purposes |
The first two examples |
Basically we should implement a 1:1 version of the ARM template converted to YAML with the following changes:
Microsoft.SecurityInsights alertRules ScheduledalertDetailsOverride:
alertDescriptionFormat: string
alertDisplayNameFormat: string
alertDynamicProperties:
- alertProperty: string
value: string
alertSeverityColumnName: string
alertTacticsColumnName: string
id: string
customDetails: {}
description: string
name: string
enabled: bool
entityMappings:
- entityType: string
fieldMappings:
- columnName: string
identifier: string
eventGroupingSettings:
aggregationKind: string
incidentConfiguration:
createIncident: bool
groupingConfiguration:
enabled: bool
groupByAlertDetails:
- string
groupByCustomDetails:
- string
groupByEntities:
- string
lookbackDuration: string
matchingMethod: string
reopenClosedIncident: bool
query: string
queryFrequency: string
queryPeriod: string
sentinelEntitiesMappings:
- columnName: string
severity: string
suppressionDuration: string
suppressionEnabled: bool
tactics:
- string
relevantTechniques:
- string
version: string
triggerOperator: string
triggerThreshold: int |
Summary of the new feature / enhancement
Add support for
[ ] Fusion
[ ] NRT
[ ] ML
[ ] Threat Intelligence
[ ] Microsoft Security
Proposed technical implementation details (optional)
Based on YAML or ARM template rule detection
The text was updated successfully, but these errors were encountered: