Set the variables:

cp config/template.tfvars .auto.tfvars

Start the environment to work with Sentinel:

terraform init
terraform apply -auto-approve

The scripts will provision and onboard a Log Analytics Workspace into Azure Sentinel.

Data connectors need to be enabled and configured manually. Optionally follow this reference.

Create the watchlist using the Portal for the file HighValue.csv, or via CLI:

This was bugged in Preview, so prefer the Portal

az sentinel watchlist create \
    --name HighValueHosts \
    --display-name HighValueHosts \
    --resource-group rg-healthcare \
    --workspace-name log-healthcare \
    --description "High value hosts." \
    --content-type "text/csv" \
    --provider "Microsoft" \
    --source "HighValue.csv" \
    --items-search-key Hostname 

To view the watchlist, simply select it and use the View in logs button:

_GetWatchlist('HighValueHosts')

A default domain-name threat indicator with threat type malicious-activity will be created.

You may modify the indicator, such as confidence threshold and kills chains.

To query it using KQL:

`ThreatIntelligenceIndicator | project DomainName`

Microsoft services connectors:

• Microsoft 365 (formerly Office) 365 - Data is stored in the OfficeActivity table.
• Azure Active Directory (being renamed to Microsoft Entra ID) - Activate Audit and Sign-in in the configurations
• Microsoft Entra ID Protection - Table is SecurityAlert. Auto-creation o incidents is supported
• Azure Activity - Azure Resource Manager operational data, service health events, write operations taken on the resources in your subscription, and the status of activities performed in Azure.

Install each of these connectors and enable the features in each of them.

Retention configuration can be managed in the SecurityEvent table within the Log Analytics workspace.

For this example:

1. Install the Windows Security Events connector in Sentinel.
2. Setup the connector will be done using the AMA option.
3. Add a data collection rule (DCR) set it under Basics.
4. Add the VM to the rule.
5. Select All security events.

It is also possible to collect Sysmon events via the Security Events connector.

There is also the legacy agent, not covered here.

This view will show the rules templates associated with the enabled connectors.

The Azure Activity data connector should be enabled and with Policy Assignment to it, and the primary log analytics workspace is selected.

Make sure you also tick the remediation task checkbox. If using managed identity, confirm the location.

There are many types of rules.

Fusion is enabled by default and cannot be customized.

⚠️ Fusion requires multiple data connectors and additional setup. Check the documentation.

Microsoft Sentinel Analytics includes built-in machine learning behavior analytics rules. You can't edit these built-in rules or review the rule settings.

You can configure the following security solutions to pass their alerts to Microsoft Sentinel:

• Microsoft Defender for Cloud Apps
• Microsoft Defender for Server
• Microsoft Defender for IoT
• Microsoft Defender for Identity
• Microsoft Defender for Office 365
• Microsoft Entra ID Protection
• Microsoft Defender for Endpoint

Create a sample scheduled rule:

AzureActivity
| where OperationName == "MICROSOFT.COMPUTE/VIRTUALMACHINES/WRITE"
| where ActivityStatus == "Succeeded"
| make-series dcount(ResourceId)  default=0 on EventSubmissionTimestamp in range(ago(7d), now(), 1d) by Caller

The Terraform configuration will create a specific scheduled rule to detect VM deletion following this exercise.

Workspace architecture options and log analytics workspace dependency.

https://learn.microsoft.com/en-us/training/modules/create-manage-azure-sentinel-workspaces/2-plan-for-azure-sentinel-workspace

• Lighthouse
• Workspace manager

Walkthrough exercises link.

For example, it can detect privileged escalation:

net user theusernametoadd /add
net user theusernametoadd ThePassword1!
net localgroup administrators theusernametoadd /add

One could use a log forwarder for CEF/Syslog data.

From the documentation:

The query length should be between 1 and 10,000 characters and cannot contain "search *" or "union *". You can use user-defined functions to overcome the query length limitation.

You can implement Playbooks with Sentinel:

1. Create an automation rule
2. Create a playbook
3. Add actions to a playbook
4. Attach a playbook to an automation rule or an analytics rule to automate threat response

General information dashboard, logs, and search.

• Incidents: Registered incidents
• Workbooks: Documentation in markdown with integrated queries and metrics
• Hunting: Workflow centered around hypothesis to seek out undetected threats and malicious behavior
• Notebooks: Jupyter notebooks integrated with Azure Machine Learning.
• Entity behavior: Tool to search for accounts, hosts, IP addresses, IoT devices or Azure resources. Works best with UEBA.
• Threat intelligence: Register indicators (domains, IPs, files, URLs). Data connectors and feeds can be used to import indicators. These indicators can be used in queries and rules.
• MITRE ATT&ACK (Preview): Integrated dashboard showing associated with rules and anomalies.

• Content hub: Solutions setup
• Repositories: Bring your own solutions from GH, ADO, etc.
• Community: General community integrated page

• Workspace manager (Preview): Enables users to centrally manage multiple Microsoft Sentinel workspaces within one or more Azure tenants
• Data connectors: Same as content hub?
• Analytics: Create and manage rules (Scheduled, NRT, Microsoft) that query data, creates alerts and register incidents, and associated automation rules.
• Watchlist: Investigate threats and respond to incidents quickly with fast import of IP addresses, file hashes, etc. from csv files.
• Automation: Automation rules are actions to take when an alert, incident or entity trigger happens.
  • General (Actions): Change information of the trigger
  • Playbooks (Action): Logic Apps
• Settings: General settings of the Sentinel account.

https://learn.microsoft.com/en-us/azure/sentinel/bookmarks#exploring-bookmarks-in-the-investigation-graph

TODO: CEF implementation

https://learn.microsoft.com/en-us/azure/sentinel/connect-common-event-format https://learn.microsoft.com/en-us/azure/sentinel/connect-log-forwarder?tabs=rsyslog https://learn.microsoft.com/en-us/azure/sentinel/connect-cef-ama

Failed login attempts (4625) to Windows machines:

let timeframe = 3d;
SecurityEvent
| where TimeGenerated > ago(1d)
| where AccountType == 'User' and EventID == 4625
| summarize failed_login_attempts=count(), latest_failed_login=arg_max(TimeGenerated, Account) by Account
| where failed_login_attempts > 5
| project-away Account1

Application Gateway V2 + WAF will be provisioned and can be integrated with the WAF connector for Sentinel.

Steps should follow as:

1. Enable log analytics (via Diagnostic Settings)
2. Install the data connector