Back to catalog
Static reviewDevelopment

Skill dossier

triaging-security-incident

Source declaration

Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM/EDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.

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

Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM/EDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.

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.

Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM/EDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization. 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/triaging-security-incident/SKILL.md:L56]
  • Step 1: Collect Initial Alert Data [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident/SKILL.md:L58]
  • Step 2: Classify the Incident Type [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident/SKILL.md:L80]
  • Step 3: Assign Severity Using Impact Matrix [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident/SKILL.md:L93]
  • Step 4: Perform Initial Enrichment [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident/SKILL.md:L112]
  • Step 5: Document and Escalate [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident/SKILL.md:L122]
  • Step 6: Initiate Containment Hold [Source statement; provisional, not tested. Evidence: skills/triaging-security-incident/SKILL.md:L142]

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/triaging-security-incident/SKILL.md:L1-L35]

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

File inventory

PathTypeBytes
skills/triaging-security-incident/LICENSEOther11 KB
skills/triaging-security-incident/references/api-reference.mdReference2.3 KB
skills/triaging-security-incident/scripts/agent.pyScript10.5 KB
skills/triaging-security-incident/SKILL.mdInstruction9.2 KB

SKILL.md frontmatter

{
  "name": "triaging-security-incident",
  "description": "Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM/EDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.",
  "domain": "cybersecurity",
  "subdomain": "incident-response",
  "tags": [
    "incident-triage",
    "NIST-800-61",
    "SANS-PICERL",
    "severity-classification",
    "SOC-operations"
  ],
  "mitre_attack": [
    "T1486",
    "T1490",
    "T1070",
    "T1078"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "d3fend_techniques": [
    "Executable Denylisting",
    "Execution Isolation",
    "File Metadata Consistency Validation",
    "Content Format Conversion",
    "File Content Analysis"
  ],
  "nist_csf": [
    "RS.MA-01",
    "RS.MA-02",
    "RS.AN-03",
    "RC.RP-01"
  ]
}

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: Collect Initial Alert Data

    Source-described action candidate under “Step 1: Collect Initial Alert Data”; not verified execution.

  4. 04
    Input

    Alert source: Which detection system generated the alert (EDR, SIEM, IDS/IPS, firewall, user report)

    Source-described input candidate under “Step 1: Collect Initial Alert Data”; not verified execution.

  5. 05
    Action

    Timestamp: When the event occurred and when it was detected (dwell time gap)

    Source-described action candidate under “Step 1: Collect Initial Alert Data”; not verified execution.

  6. 06
    Action

    Affected assets: Hostnames, IP addresses, user accounts involved

    Source-described action candidate under “Step 1: Collect Initial Alert Data”; not verified execution.

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

    Alert fidelity: Historical true-positive rate for this detection rule

    Source-described action candidate under “Step 1: Collect Initial Alert Data”; not verified execution.

  2. 08
    Action

    Raw evidence: Log entries, packet captures, process execution chains

    Source-described action candidate under “Step 1: Collect Initial Alert Data”; not verified execution.

  3. 09
    Action

    Step 2: Classify the Incident Type

    Source-described action candidate under “Step 2: Classify the Incident Type”; not verified execution.

  4. 10
    Action

    Step 3: Assign Severity Using Impact Matrix

    Source-described action candidate under “Step 3: Assign Severity Using Impact Matrix”; not verified execution.

  5. 11
    Action

    P1: Acknowledge within 15 minutes, containment within 1 hour

    Source-described action candidate under “Step 3: Assign Severity Using Impact Matrix”; not verified execution.

  6. 12
    Action

    P2: Acknowledge within 30 minutes, containment within 4 hours

    Source-described action candidate under “Step 3: Assign Severity Using Impact Matrix”; not verified execution.

  7. 13
    Action

    P3: Acknowledge within 2 hours, investigation within 24 hours

    Source-described action candidate under “Step 3: Assign Severity Using Impact Matrix”; not verified execution.

  8. 14
    Action

    P4: Acknowledge within 8 hours, investigation within 72 hours

    Source-described action candidate under “Step 3: Assign Severity Using Impact Matrix”; not verified execution.

  9. 15
    Action

    Step 4: Perform Initial Enrichment

    Source-described action candidate under “Step 4: Perform Initial Enrichment”; not verified execution.

  10. 16
    Action

    Threat intelligence: Check IOCs (IP, hash, domain) against TI platforms (VirusTotal, OTX, MISP)

    Source-described action candidate under “Step 4: Perform Initial Enrichment”; not verified execution.

  11. 17
    Action

    Asset context: Query CMDB for asset owner, business function, data classification

    Source-described action candidate under “Step 4: Perform Initial Enrichment”; not verified execution.

  12. 18
    Action

    User context: Check identity provider for recent authentication anomalies, MFA status

    Source-described action candidate under “Step 4: Perform Initial Enrichment”; not verified execution.

  13. 19
    Action

    Historical correlation: Search for related alerts on the same host/user in the past 30 days

    Source-described action candidate under “Step 4: Perform Initial Enrichment”; not verified execution.

  14. 20
    Decision

    Network context: Verify if source/destination IPs are internal, known partners, or external threat actors

    Source-described decision candidate under “Step 4: Perform Initial Enrichment”; not verified execution.

  15. 21
    Action

    Step 5: Document and Escalate

    Source-described action candidate under “Step 5: Document and Escalate”; not verified execution.

  16. 22
    Action

    Create a structured triage record and route to the appropriate response tier:

    Source-described action candidate under “Step 5: Document and Escalate”; not verified execution.

  17. 23
    Action

    Step 6: Initiate Containment Hold

    Source-described action candidate under “Step 6: Initiate Containment Hold”; not verified execution.

  18. 24
    Decision

    If severity is P1 or P2, initiate immediate containment actions while awaiting full investigation:

    Source-described decision candidate under “Step 6: Initiate Containment Hold”; not verified execution.

  19. 25
    Action

    Network-isolate the affected endpoint via EDR (CrowdStrike contain, Defender isolate)

    Source-described action candidate under “Step 6: Initiate Containment Hold”; not verified execution.

  20. 26
    Action

    Disable compromised user accounts in Active Directory or identity provider

    Source-described action candidate under “Step 6: Initiate Containment Hold”; not verified execution.

  21. 27
    Action

    Block identified malicious IPs/domains at firewall and DNS sinkhole

    Source-described action candidate under “Step 6: Initiate Containment Hold”; not verified execution.

  22. 28
    Action

    Preserve volatile evidence (memory dump) before any remediation

    Source-described action candidate under “Step 6: Initiate Containment Hold”; not verified execution.

  23. 29
    Action

    Key Concepts

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

  24. 30
    Action

    Tools & Systems

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

  25. 31
    Action

    Common Scenarios

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

  26. 32
    Action

    Decode the Base64 payload to determine the command intent

    Source-described action candidate under “Scenario: Encoded PowerShell from Email Client”; not verified execution.

  27. 33
    Action

    Check the parent process chain for anomalies (Outlook spawning PowerShell is abnormal)

    Source-described action candidate under “Scenario: Encoded PowerShell from Email Client”; not verified execution.

  28. 34
    Action

    Query VirusTotal for the decoded payload hash

    Source-described action candidate under “Scenario: Encoded PowerShell from Email Client”; not verified execution.

  29. 35
    Action

    Correlate with email gateway logs to identify the triggering email and sender

    Source-described action candidate under “Scenario: Encoded PowerShell from Email Client”; not verified execution.

  30. 36
    Decision

    Check if other recipients in the organization received the same email

    Source-described decision candidate under “Scenario: Encoded PowerShell from Email Client”; not verified execution.

  31. 37
    Action

    Isolate the endpoint and escalate to Tier 2 with full triage context

    Source-described action candidate under “Scenario: Encoded PowerShell from Email Client”; not verified execution.

  32. 38
    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

20 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

13 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 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.

Note

File modification is described or implemented

7 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 7 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/triaging-security-incident/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/triaging-security-incident/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/triaging-security-incident
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.