Back to catalog
Static reviewDevelopment

Skill dossier

building-cloud-siem-with-sentinel

Source declaration

Deploy Microsoft Sentinel as a cloud-native SIEM/SOAR by configuring multi-cloud data connectors (AWS, Azure, GCP), writing KQL detection and hunting queries, and building automated Logic Apps response playbooks. Use when establishing a centralized SOC for multi-cloud environments, migrating from a legacy SIEM, or performing petabyte-scale threat hunting; not for AWS-only setups where Security Hub/GuardDuty suffice or for endpoint EDR needs.

The author's original description, preserved in English. It describes intent, not verified performance.

Deploy Microsoft Sentinel as a cloud-native SIEM/SOAR by configuring multi-cloud data connectors (AWS, Azure, GCP), writing KQL detection and hunting queries, and building automated Logic Apps response playbooks. Use when establishing a centralized SOC for multi-cloud environments, migrating from a legacy SIEM, or performing petabyte-scale threat hunting; not for AWS-only setups where Security Hub/GuardDuty suffice or for endpoint EDR needs.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Deploy Microsoft Sentinel as a cloud-native SIEM/SOAR by configuring multi-cloud data connectors (AWS, Azure, GCP), writing KQL detection and hunting queries, and building automated Logic Apps response playbooks. Use when establishing a centralized SOC for multi-cloud environments, migrating from a legacy SIEM, or performing petabyte-scale threat hunting; not for AWS-only setups where Security Hub/GuardDuty suffice or for endpoint EDR needs. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/building-cloud-siem-with-sentinel/SKILL.md:L55]
  • Step 1: Provision Sentinel Workspace and Data Connectors [Source statement; provisional, not tested. Evidence: skills/building-cloud-siem-with-sentinel/SKILL.md:L57]
  • Step 2: Write KQL Detection Rules [Source statement; provisional, not tested. Evidence: skills/building-cloud-siem-with-sentinel/SKILL.md:L101]
  • Step 3: Build SOAR Playbooks with Logic Apps [Source statement; provisional, not tested. Evidence: skills/building-cloud-siem-with-sentinel/SKILL.md:L150]
  • Step 4: Configure Sentinel Data Lake for Long-Term Hunting [Source statement; provisional, not tested. Evidence: skills/building-cloud-siem-with-sentinel/SKILL.md:L196]
  • Step 5: Integrate Threat Intelligence [Source statement; provisional, not tested. Evidence: skills/building-cloud-siem-with-sentinel/SKILL.md:L219]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/building-cloud-siem-with-sentinel/SKILL.md:L1-L34]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
32.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/building-cloud-siem-with-sentinel/LICENSEOther11 KB
skills/building-cloud-siem-with-sentinel/references/api-reference.mdReference1.9 KB
skills/building-cloud-siem-with-sentinel/scripts/agent.pyScript6.7 KB
skills/building-cloud-siem-with-sentinel/SKILL.mdInstruction12.8 KB

SKILL.md frontmatter

{
  "name": "building-cloud-siem-with-sentinel",
  "description": "Deploy Microsoft Sentinel as a cloud-native SIEM/SOAR by configuring multi-cloud data connectors (AWS, Azure, GCP), writing KQL detection and hunting queries, and building automated Logic Apps response playbooks. Use when establishing a centralized SOC for multi-cloud environments, migrating from a legacy SIEM, or performing petabyte-scale threat hunting; not for AWS-only setups where Security Hub/GuardDuty suffice or for endpoint EDR needs.",
  "domain": "cybersecurity",
  "subdomain": "cloud-security",
  "tags": [
    "microsoft-sentinel",
    "cloud-siem",
    "kql-queries",
    "soar-automation",
    "threat-detection"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "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"
  ],
  "mitre_attack": [
    "T1078.004",
    "T1548.005",
    "T1485",
    "T1530",
    "T1021.007"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Provision Sentinel Workspace and Data Connectors

    Source-described action candidate under “Step 1: Provision Sentinel Workspace and Data Connectors”; not verified execution.

  4. 04
    Action

    Create a Log Analytics workspace optimized for security data and enable data connectors for multi-cloud ingestion.

    Source-described action candidate under “Step 1: Provision Sentinel Workspace and Data Connectors”; not verified execution.

  5. 05
    Output

    Step 2: Write KQL Detection Rules

    Source-described output candidate under “Step 2: Write KQL Detection Rules”; not verified execution.

  6. 06
    Action

    Create analytics rules using Kusto Query Language to detect cloud-specific threats. Map each rule to MITRE ATT&CK techniques.

    Source-described action candidate under “Step 2: Write KQL Detection Rules”; not verified execution.

Inspect all extracted workflow candidates (20 candidate steps)
  1. 07
    Action

    Step 3: Build SOAR Playbooks with Logic Apps

    Source-described action candidate under “Step 3: Build SOAR Playbooks with Logic Apps”; not verified execution.

  2. 08
    Action

    Create automated response playbooks that execute when analytics rules trigger incidents. Common actions include blocking users, isolating resources, and enriching alerts with threat intelligence.

    Source-described action candidate under “Step 3: Build SOAR Playbooks with Logic Apps”; not verified execution.

  3. 09
    Action

    Step 4: Configure Sentinel Data Lake for Long-Term Hunting

    Source-described action candidate under “Step 4: Configure Sentinel Data Lake for Long-Term Hunting”; not verified execution.

  4. 10
    Action

    Step 5: Integrate Threat Intelligence

    Source-described action candidate under “Step 5: Integrate Threat Intelligence”; not verified execution.

  5. 11
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  6. 12
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  7. 13
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  8. 14
    Action

    Create an analytics rule detecting Azure AD impossible travel or anomalous sign-in risk

    Source-described action candidate under “Scenario: Detecting Cross-Cloud Credential Theft Campaign”; not verified execution.

  9. 15
    Output

    Write a KQL query correlating the compromised Azure AD identity with AWS CloudTrail AssumeRoleWithSAML events

    Source-described output candidate under “Scenario: Detecting Cross-Cloud Credential Theft Campaign”; not verified execution.

  10. 16
    Action

    Build a Fusion detection rule that links Azure AD risk events with subsequent AWS privilege escalation activity

    Source-described action candidate under “Scenario: Detecting Cross-Cloud Credential Theft Campaign”; not verified execution.

  11. 17
    Action

    Deploy a SOAR playbook that automatically disables the Azure AD account and revokes AWS STS sessions

    Source-described action candidate under “Scenario: Detecting Cross-Cloud Credential Theft Campaign”; not verified execution.

  12. 18
    Action

    Create a workbook showing the timeline from initial compromise through lateral movement to AWS

    Source-described action candidate under “Scenario: Detecting Cross-Cloud Credential Theft Campaign”; not verified execution.

  13. 19
    Action

    Run a hunting query across the data lake to check for similar patterns affecting other accounts

    Source-described action candidate under “Scenario: Detecting Cross-Cloud Credential Theft Campaign”; not verified execution.

  14. 20
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

25 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

5 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 5 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

2 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

18 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 18 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/building-cloud-siem-with-sentinel/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/building-cloud-siem-with-sentinel/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/building-cloud-siem-with-sentinel
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.