Back to catalog
Static reviewDevelopment

Skill dossier

securing-azure-with-microsoft-defender

Source declaration

Deploys and configures Microsoft Defender for Cloud as a CNAPP for Azure, multi-cloud, and hybrid environments: enabling Defender plans for servers, containers, storage, and databases, configuring recommendations, and managing Secure Score via the unified Defender portal. Use when onboarding workloads to Defender for Cloud or setting up cloud workload protection and threat monitoring.

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

Deploys and configures Microsoft Defender for Cloud as a CNAPP for Azure, multi-cloud, and hybrid environments: enabling Defender plans for servers, containers, storage, and databases, configuring recommendations, and managing Secure Score via the unified Defender portal. Use when onboarding workloads to Defender for Cloud or setting up cloud workload protection and threat monitoring.

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.

Deploys and configures Microsoft Defender for Cloud as a CNAPP for Azure, multi-cloud, and hybrid environments: enabling Defender plans for servers, containers, storage, and databases, configuring recommendations, and managing Secure Score via the unified Defender portal. Use when onboarding workloads to Defender for Cloud or setting up cloud workload protection and threat monitoring. 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/securing-azure-with-microsoft-defender/SKILL.md:L61]
  • Step 1: Enable Defender for Cloud Plans [Source statement; provisional, not tested. Evidence: skills/securing-azure-with-microsoft-defender/SKILL.md:L63]
  • Step 2: Configure Environment Connectors for Multi-Cloud [Source statement; provisional, not tested. Evidence: skills/securing-azure-with-microsoft-defender/SKILL.md:L90]
  • Step 3: Review and Prioritize Secure Score Recommendations [Source statement; provisional, not tested. Evidence: skills/securing-azure-with-microsoft-defender/SKILL.md:L115]
  • Step 4: Configure Adaptive Application Controls and JIT Access [Source statement; provisional, not tested. Evidence: skills/securing-azure-with-microsoft-defender/SKILL.md:L135]
  • Step 5: Set Up Security Alerts and Workflow Automation [Source statement; provisional, not tested. Evidence: skills/securing-azure-with-microsoft-defender/SKILL.md:L164]
  • Step 6: Enable Cloud Security Graph and Attack Path Analysis [Source statement; provisional, not tested. Evidence: skills/securing-azure-with-microsoft-defender/SKILL.md:L191]

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/securing-azure-with-microsoft-defender/SKILL.md:L1-L40]

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
31.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/securing-azure-with-microsoft-defender/LICENSEOther11 KB
skills/securing-azure-with-microsoft-defender/references/api-reference.mdReference2 KB
skills/securing-azure-with-microsoft-defender/scripts/agent.pyScript6.8 KB
skills/securing-azure-with-microsoft-defender/SKILL.mdInstruction11.7 KB

SKILL.md frontmatter

{
  "name": "securing-azure-with-microsoft-defender",
  "description": "Deploys and configures Microsoft Defender for Cloud as a CNAPP for Azure, multi-cloud, and hybrid environments: enabling Defender plans for servers, containers, storage, and databases, configuring recommendations, and managing Secure Score via the unified Defender portal. Use when onboarding workloads to Defender for Cloud or setting up cloud workload protection and threat monitoring.\n",
  "domain": "cybersecurity",
  "subdomain": "cloud-security",
  "tags": [
    "microsoft-defender",
    "azure-security",
    "cnapp",
    "secure-score",
    "cloud-workload-protection"
  ],
  "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",
    "T1530",
    "T1537",
    "T1580",
    "T1610"
  ]
}

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: Enable Defender for Cloud Plans

    Source-described action candidate under “Step 1: Enable Defender for Cloud Plans”; not verified execution.

  4. 04
    Action

    Step 2: Configure Environment Connectors for Multi-Cloud

    Source-described action candidate under “Step 2: Configure Environment Connectors for Multi-Cloud”; not verified execution.

  5. 05
    Action

    Step 3: Review and Prioritize Secure Score Recommendations

    Source-described action candidate under “Step 3: Review and Prioritize Secure Score Recommendations”; not verified execution.

  6. 06
    Action

    Analyze the Secure Score across all subscriptions. Each recommendation includes a risk priority based on asset exposure, internet exposure, and threat intelligence context.

    Source-described action candidate under “Step 3: Review and Prioritize Secure Score Recommendations”; not verified execution.

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

    Step 4: Configure Adaptive Application Controls and JIT Access

    Source-described action candidate under “Step 4: Configure Adaptive Application Controls and JIT Access”; not verified execution.

  2. 08
    Action

    Step 5: Set Up Security Alerts and Workflow Automation

    Source-described action candidate under “Step 5: Set Up Security Alerts and Workflow Automation”; not verified execution.

  3. 09
    Action

    Step 6: Enable Cloud Security Graph and Attack Path Analysis

    Source-described action candidate under “Step 6: Enable Cloud Security Graph and Attack Path Analysis”; not verified execution.

  4. 10
    Action

    Use the cloud security graph to visualize attack paths that adversaries could exploit to reach critical assets. Prioritize remediation based on actual exploitability rather than individual finding severity.

    Source-described action candidate under “Step 6: Enable Cloud Security Graph and Attack Path Analysis”; 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

    Review the attack path in the cloud security graph showing: Internet -> SQL Server (CVE) -> Service Principal -> Key Vault

    Source-described action candidate under “Scenario: Internet-Exposed SQL Server with Known Vulnerability”; not verified execution.

  9. 15
    Action

    Immediately restrict the SQL Server firewall to private endpoints only

    Source-described action candidate under “Scenario: Internet-Exposed SQL Server with Known Vulnerability”; not verified execution.

  10. 16
    Action

    Apply the SQL Server security patch through Azure Update Management

    Source-described action candidate under “Scenario: Internet-Exposed SQL Server with Known Vulnerability”; not verified execution.

  11. 17
    Action

    Rotate the service principal credentials and scope its permissions to only the required database operations

    Source-described action candidate under “Scenario: Internet-Exposed SQL Server with Known Vulnerability”; not verified execution.

  12. 18
    Action

    Add a Key Vault access policy requiring the service principal to authenticate via managed identity rather than secret-based credentials

    Source-described action candidate under “Scenario: Internet-Exposed SQL Server with Known Vulnerability”; not verified execution.

  13. 19
    Action

    Verify the attack path is resolved in Defender CSPM within 24 hours

    Source-described action candidate under “Scenario: Internet-Exposed SQL Server with Known Vulnerability”; 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.

Items warrant review

18 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 useNot observed
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.

Note

File modification is described or implemented

13 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 13 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/securing-azure-with-microsoft-defender/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/securing-azure-with-microsoft-defender/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/securing-azure-with-microsoft-defender
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.