Azure Sentinel for SIEM - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Azure Sentinel?

Azure Sentinel is a cloud-native security information and event management (SIEM) service that helps collect, detect, investigate, and respond to security threats across your enterprise.

beginner

How does Azure Sentinel collect data?

Azure Sentinel collects data from multiple sources like users, applications, servers, and devices using connectors that integrate with Microsoft and third-party services.

intermediate

What is the role of analytics rules in Azure Sentinel?

Analytics rules in Azure Sentinel analyze collected data to detect suspicious activities and generate alerts for potential security threats.

intermediate

Explain the purpose of playbooks in Azure Sentinel.

Playbooks automate response actions to security alerts using workflows, helping teams quickly respond to threats without manual steps.

beginner

Why is Azure Sentinel considered scalable and cost-effective?

Because it is cloud-native, Azure Sentinel scales automatically with your data volume and you pay only for the data you analyze, avoiding upfront infrastructure costs.

What type of service is Azure Sentinel?

A Virtual machine manager

B Cloud storage service

C Cloud-native SIEM

D Database service

Azure Sentinel is a cloud-native SIEM service designed for security event management.

Which of these is NOT a data source for Azure Sentinel?

A Network devices

B Application logs

C User activity logs

D Physical hardware sensors

Azure Sentinel collects data from digital sources like logs and devices, but not directly from physical hardware sensors.

What does an analytics rule in Azure Sentinel do?

A Detects suspicious activities

B Creates virtual networks

C Manages user accounts

D Stores data securely

Analytics rules analyze data to detect suspicious activities and generate alerts.

What is the main benefit of using playbooks in Azure Sentinel?

A Automated response to alerts

B Manual data entry

C Creating user reports

D Backing up data

Playbooks automate responses to security alerts, speeding up incident handling.

How does Azure Sentinel charge for its service?

A Fixed monthly fee

B Based on data analyzed

C Per user license

D Annual subscription only

Azure Sentinel charges based on the volume of data analyzed, making it cost-effective.

Describe how Azure Sentinel helps organizations detect and respond to security threats.

Think about the flow from gathering data to taking action.

Explain why Azure Sentinel is a good choice for companies looking for scalable security monitoring.

Consider how cloud services handle growth and costs.

Practice

1. What is the main purpose of Azure Sentinel in security management?

easy

A. To provide cloud storage for application data

B. To collect and analyze security data for threat detection

C. To manage user passwords and authentication

D. To store backups of all user files

Solution

1. Step 1: Understand Azure Sentinel's role

   Azure Sentinel is designed to collect security data from various sources to detect threats.

2. Step 2: Compare options with Sentinel's function

   Only To collect and analyze security data for threat detection describes collecting and analyzing security data for threat detection, which matches Sentinel's purpose.

3. Final Answer:

   To collect and analyze security data for threat detection -> Option B

4. Quick Check:

   Azure Sentinel = threat detection [OK]

Hint: Remember: Sentinel = security data + threat detection [OK]

Common Mistakes:

• Confusing Sentinel with backup or storage services
• Thinking Sentinel manages passwords directly
• Assuming Sentinel is just cloud storage

2. Which of the following is the correct way to create an alert rule query in Azure Sentinel using Kusto Query Language (KQL)?

easy

A. GET SecurityEvent WHERE EventID = 4625

B. SELECT * FROM SecurityEvent WHERE EventID = 4625

C. FIND SecurityEvent WITH EventID 4625

D. SecurityEvent | where EventID == 4625

Solution

1. Step 1: Identify the query language used in Azure Sentinel

   Azure Sentinel uses Kusto Query Language (KQL), which uses pipe operators and 'where' clauses.

2. Step 2: Match the syntax to KQL

   SecurityEvent | where EventID == 4625 uses KQL syntax correctly: table name, pipe, and 'where' condition. Other options use SQL or invalid syntax.

3. Final Answer:

   SecurityEvent | where EventID == 4625 -> Option D

4. Quick Check:

   KQL uses pipes and 'where' [OK]

Hint: KQL uses pipes (|) and 'where' for filters [OK]

Common Mistakes:

• Using SQL syntax instead of KQL
• Missing pipe operator in query
• Using incorrect keywords like GET or FIND

3. Given the following KQL query in Azure Sentinel alert rule:
SecurityEvent | where EventID == 4625 | summarize count() by Account
What does this query output?

medium

A. A count of all events without grouping

B. A list of all successful login events

C. A count of failed login attempts grouped by user account

D. A list of accounts with no login attempts

Solution

1. Step 1: Analyze the query filters and aggregation

   The query filters SecurityEvent for EventID 4625, which means failed login attempts, then counts them grouped by Account.

2. Step 2: Understand the summarize clause

   'summarize count() by Account' groups results by Account and counts events per account.

3. Final Answer:

   A count of failed login attempts grouped by user account -> Option C

4. Quick Check:

   EventID 4625 = failed logins, grouped count = A count of failed login attempts grouped by user account [OK]

Hint: EventID 4625 means failed login; summarize groups counts [OK]

Common Mistakes:

• Confusing EventID 4625 with successful logins
• Ignoring the grouping by Account
• Thinking it lists accounts without attempts

4. You wrote this KQL alert rule query in Azure Sentinel:
SecurityEvent | where EventID = 4625 | summarize count() by Account
Why does this query fail to run correctly?

medium

A. Because the equality operator should be '==' not '=' in KQL

B. Because 'summarize' cannot be used with 'count()'

C. Because 'Account' is not a valid field in SecurityEvent

D. Because 'where' clause must come after 'summarize'

Solution

1. Step 1: Check the operator syntax in the 'where' clause

   KQL requires '==' for equality comparison, not a single '=' which is assignment in some languages.

2. Step 2: Validate other parts of the query

   'summarize count() by Account' is valid, and 'Account' is a common field. 'where' must come before 'summarize'.

3. Final Answer:

   Because the equality operator should be '==' not '=' in KQL -> Option A

4. Quick Check:

   KQL equality uses '==' not '=' [OK]

Hint: Use '==' for equality in KQL, not '=' [OK]

Common Mistakes:

• Using single '=' instead of '==' in KQL
• Misplacing 'where' after 'summarize'
• Assuming 'count()' is invalid with 'summarize'

5. You want to create an Azure Sentinel alert that triggers when there are more than 5 failed login attempts from the same account within 10 minutes. Which KQL query correctly implements this logic?

hard

A. SecurityEvent | where EventID == 4625 | where TimeGenerated > ago(10m) | summarize FailedAttempts = count() by Account | where FailedAttempts > 5

B. SecurityEvent | where EventID == 4625 | summarize count() by Account | where count_ > 5

C. SecurityEvent | where EventID == 4625 and TimeGenerated < ago(10m) | summarize count() by Account | where count_ > 5

D. SecurityEvent | where EventID == 4625 | summarize count() by Account, TimeGenerated | where count_ > 5

Solution

1. Step 1: Filter failed login events within last 10 minutes

   SecurityEvent | where EventID == 4625 | where TimeGenerated > ago(10m) | summarize FailedAttempts = count() by Account | where FailedAttempts > 5 uses 'where TimeGenerated > ago(10m)' to filter recent events correctly.

2. Step 2: Group by Account and count attempts, then filter counts over 5

   SecurityEvent | where EventID == 4625 | where TimeGenerated > ago(10m) | summarize FailedAttempts = count() by Account | where FailedAttempts > 5 summarizes counts by Account and filters where count > 5, matching the requirement.

3. Final Answer:

   SecurityEvent | where EventID == 4625 | where TimeGenerated > ago(10m) | summarize FailedAttempts = count() by Account | where FailedAttempts > 5 -> Option A

4. Quick Check:

   Filter by time + count > 5 per account = SecurityEvent | where EventID == 4625 | where TimeGenerated > ago(10m) | summarize FailedAttempts = count() by Account | where FailedAttempts > 5 [OK]

Hint: Filter time first, then count and filter by count > 5 [OK]

Common Mistakes:

• Not filtering events by time range
• Using incorrect logical operators in filters
• Grouping by TimeGenerated causing wrong counts