Skip to content
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.

Sign up for GitHub

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

🐛 Fix incorrect case for severity #8945

Merged
merged 1 commit into from
Sep 5, 2023
Merged

🐛 Fix incorrect case for severity #8945

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions Solutions/Azure Active Directory/Analytic Rules/MFASpammingfollowedbySuccessfullogin.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
id: a8cc6d5c-4e7e-4b48-b4ac-d8a116c62a8b
name: MFA Spamming followed by Successful login
description: |
'Identifies MFA Spamming followed by Successful logins and by a successful authentication within a given time window,
'Identifies MFA Spamming followed by Successful logins and by a successful authentication within a given time window,
Default Failure count is 10 and 1 successful login with default Time Window is 5 minutes.'
severity: high
severity: High
requiredDataConnectors:
- connectorId: AzureActiveDirectory
dataTypes:
Expand Down Expand Up @@ -55,5 +55,5 @@ entityMappings:
fieldMappings:
- identifier: Address
columnName: IPAddress
version: 1.0.0
version: 1.0.1
kind: Scheduled
Loading