SKILLEMALL.ai
GitHub ↗ RU Sign in

CC detecting-azure-service-principal-abuse

Detect Azure service principal abuse in Microsoft Entra ID using KQL detection queries (Sentinel/Splunk) against Azure AD Audit and Sign-in Logs, covering added credentials, privileged role assignment, admin consent bypass, and service principal enumeration. Use when investigating suspected privilege escalation or persistence via service principals, or building threat-hunting queries for Entra ID identity abuse.

mukul975/Anthropic-Cybersecurity-Skills Agent Skills author: mukul975 Apache-2.0 8 files · 2 scripts body ≈ 1 904 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Detect Azure service principal abuse in Microsoft Entra ID using KQL detection queries (Sentinel/Splunk) against Azure AD Audit and Sign-in Logs, covering…

As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

AnalyzerAzureInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
97
Quality 40%
75
Run on models
none yet
Process rating
C
58/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 3

    ✓ No critical or high findings

    Medium and low: 3
    • low Risky intent intent-offensive-security references/workflows.md:17
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      3. Check role assignments for privilege escalation
    • low Risky intent intent-offensive-security SKILL.md:6
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      enumeration. Use when investigating suspected privilege escalation or persistence
    • low Risky intent intent-offensive-security SKILL.md:46
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
      Azure service principals are identity objects used by applications, services, and automation tools to access Azure resources. Attackers exploit service principals for privilege escalation, lateral mov
      detector

    Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "domain"
    • note frontmatter-key unknown frontmatter key "subdomain"
    • note frontmatter-key unknown frontmatter key "d3fend_techniques"
    • note frontmatter-key unknown frontmatter key "nist_csf"
    • note frontmatter-key unknown frontmatter key "mitre_attack"

    Process rating: all ten parameters 58/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 1 mutating operations with no state check
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 18 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1904 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -43 reference files, but SKILL.md never points to them: the model will not open them
    • -32 of 2 scripts are never mentioned in SKILL.md
    • +2Single-language instructions
    • +3Description length 415: enough signal without eating the budget
    • +4Structure: 21 headings
    • +3Step-by-step instructions: 18 items
    • +4Has examples (12 code blocks)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.