🐛 Fix incorrect case for severity

Azure · Sep 5, 2023 · 97cf8a0 · 97cf8a0
1 parent f80a66a
commit 97cf8a0
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/Solutions/Azure Active Directory/Analytic Rules/MFASpammingfollowedbySuccessfullogin.yaml b/Solutions/Azure Active Directory/Analytic Rules/MFASpammingfollowedbySuccessfullogin.yaml
@@ -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:
@@ -55,5 +55,5 @@ entityMappings:
     fieldMappings:
       - identifier: Address
         columnName: IPAddress
-version: 1.0.0
+version: 1.0.1
 kind: Scheduled