building-cloud-siem-with-sentinel

name	building-cloud-siem-with-sentinel
description	Use when this skill covers deploying Microsoft Sentinel as a cloud-native SIEM and SOAR platform for centralized security operations. It details configuring data connectors for multi-cloud log ingestion, writing KQL detection queries, building automated response playbooks with Logic Apps, and leveraging the Sentinel data lake for petabyte-scale threat hunting across AWS, Azure, and GCP security telemetry.
domain	cybersecurity
tags	["microsoft-sentinel","cloud-siem","kql-queries","soar-automation","threat-detection"]
subdomain	cloud-security
version	1.0.0
author	oyi77
license	Apache-2.0
nist_ai_rmf	["MEASURE-2.7","MAP-5.1","MANAGE-2.4"]
atlas_techniques	["AML.T0070","AML.T0066","AML.T0082"]
nist_csf	["PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01"]

Building Cloud Siem With Sentinel

Overview

Cybersecurity skill for building cloud siem with sentinel. Follows industry best practices and security standards.

When to Use

Trigger phrases:

• "building cloud siem with sentinel"

• "This skill covers deploying Microsoft Sentinel as a cloud-native SIEM and SOAR p"

• When establishing a centralized security operations center for multi-cloud environments

• When migrating from legacy SIEM platforms (Splunk, QRadar) to cloud-native architecture

• When building automated incident response workflows for cloud-specific threats

• When performing large-scale threat hunting across petabytes of security telemetry

• When integrating threat intelligence feeds with cloud security log analysis

Do not use for AWS-only environments where Security Hub and GuardDuty suffice, for endpoint detection requiring EDR capabilities (use Defender for Endpoint), or for compliance posture monitoring (see building-cloud-security-posture-management).

When NOT to Use

• When you lack proper authorization for testing
• For production systems without change management
• When the task requires legal or compliance expertise beyond technical scope

Prerequisites

• Azure subscription with Microsoft Sentinel enabled on a Log Analytics workspace
• Data connector permissions for target log sources (AWS CloudTrail, Azure Activity, GCP)
• Logic Apps or Azure Functions for automated response playbooks
• KQL (Kusto Query Language) proficiency for writing detection rules and hunting queries

Workflow

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> :
     {k: re.findall(v, text)  k, v  IOC_PATTERNS.items()}