Back to catalog
Static reviewDevelopment

Skill dossier

performing-disk-forensics-investigation

Source declaration

Conduct disk forensics investigations using forensic imaging, file system analysis, and timeline reconstruction, with tools such as FTK Imager, Autopsy, and The Sleuth Kit, for evidence acquisition, deleted file recovery, and artifact examination. Use when a security incident requires forensic analysis of persistent storage or when evidence must be preserved for legal or HR proceedings.

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

Conduct disk forensics investigations using forensic imaging, file system analysis, and timeline reconstruction, with tools such as FTK Imager, Autopsy, and The Sleuth Kit, for evidence acquisition, deleted file recovery, and artifact examination. Use when a security incident requires forensic analysis of persistent storage or when evidence must be preserved for legal or HR proceedings.

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.

Conduct disk forensics investigations using forensic imaging, file system analysis, and timeline reconstruction, with tools such as FTK Imager, Autopsy, and The Sleuth Kit, for evidence acquisition, deleted file recovery, and artifact examination. Use when a security incident requires forensic analysis of persistent storage or when evidence must be preserved for legal or HR proceedings. 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/performing-disk-forensics-investigation/SKILL.md:L55]
  • Step 1: Secure and Document the Evidence [Source statement; provisional, not tested. Evidence: skills/performing-disk-forensics-investigation/SKILL.md:L57]
  • Step 2: Create a Forensic Image [Source statement; provisional, not tested. Evidence: skills/performing-disk-forensics-investigation/SKILL.md:L79]
  • Step 3: Analyze File System Structure [Source statement; provisional, not tested. Evidence: skills/performing-disk-forensics-investigation/SKILL.md:L114]
  • Step 4: Reconstruct the Timeline [Source statement; provisional, not tested. Evidence: skills/performing-disk-forensics-investigation/SKILL.md:L148]
  • Step 5: Recover and Analyze Artifacts [Source statement; provisional, not tested. Evidence: skills/performing-disk-forensics-investigation/SKILL.md:L170]
  • Step 6: Document Findings [Source statement; provisional, not tested. Evidence: skills/performing-disk-forensics-investigation/SKILL.md:L181]

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/performing-disk-forensics-investigation/SKILL.md:L1-L32]

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

File inventory

PathTypeBytes
skills/performing-disk-forensics-investigation/LICENSEOther11 KB
skills/performing-disk-forensics-investigation/references/api-reference.mdReference2.1 KB
skills/performing-disk-forensics-investigation/scripts/agent.pyScript8.5 KB
skills/performing-disk-forensics-investigation/SKILL.mdInstruction10.5 KB

SKILL.md frontmatter

{
  "name": "performing-disk-forensics-investigation",
  "description": "Conduct disk forensics investigations using forensic imaging, file system analysis, and timeline reconstruction, with tools such as FTK Imager, Autopsy, and The Sleuth Kit, for evidence acquisition, deleted file recovery, and artifact examination. Use when a security incident requires forensic analysis of persistent storage or when evidence must be preserved for legal or HR proceedings.\n",
  "domain": "cybersecurity",
  "subdomain": "incident-response",
  "tags": [
    "disk-forensics",
    "forensic-imaging",
    "evidence-acquisition",
    "file-recovery",
    "chain-of-custody"
  ],
  "mitre_attack": [
    "T1486",
    "T1490",
    "T1070",
    "T1078",
    "T1005"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "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: Secure and Document the Evidence

    Source-described action candidate under “Step 1: Secure and Document the Evidence”; not verified execution.

  4. 04
    Action

    Photograph the system, noting serial numbers, labels, and cable connections

    Source-described action candidate under “Step 1: Secure and Document the Evidence”; not verified execution.

  5. 05
    Input

    Document the evidence source: device type, make, model, serial number, capacity

    Source-described input candidate under “Step 1: Secure and Document the Evidence”; not verified execution.

  6. 06
    Action

    Complete chain of custody form with date, time, handler name, and reason for acquisition

    Source-described action candidate under “Step 1: Secure and Document the Evidence”; not verified execution.

Inspect all extracted workflow candidates (49 candidate steps)
  1. 07
    Output

    Use a hardware write blocker when connecting the evidence drive to the forensic workstation

    Source-described output candidate under “Step 1: Secure and Document the Evidence”; not verified execution.

  2. 08
    Action

    Step 2: Create a Forensic Image

    Source-described action candidate under “Step 2: Create a Forensic Image”; not verified execution.

  3. 09
    Output

    Connect evidence drive through write blocker

    Source-described output candidate under “Step 2: Create a Forensic Image”; not verified execution.

  4. 10
    Input

    File > Create Disk Image > Select source drive

    Source-described input candidate under “Step 2: Create a Forensic Image”; not verified execution.

  5. 11
    Decision

    Choose E01 (Expert Witness Format) for compression and metadata

    Source-described decision candidate under “Step 2: Create a Forensic Image”; not verified execution.

  6. 12
    Action

    Set destination path and evidence item information

    Source-described action candidate under “Step 2: Create a Forensic Image”; not verified execution.

  7. 13
    Action

    Enable "Verify images after they are created"

    Source-described action candidate under “Step 2: Create a Forensic Image”; not verified execution.

  8. 14
    Input

    Record source and image hash values

    Source-described input candidate under “Step 2: Create a Forensic Image”; not verified execution.

  9. 15
    Action

    Step 3: Analyze File System Structure

    Source-described action candidate under “Step 3: Analyze File System Structure”; not verified execution.

  10. 16
    Action

    Identify partition layout (MBR/GPT, NTFS/ext4/APFS partitions)

    Source-described action candidate under “Step 3: Analyze File System Structure”; not verified execution.

  11. 17
    Action

    Examine the Master File Table (MFT) for NTFS or inode tables for ext4

    Source-described action candidate under “Step 3: Analyze File System Structure”; not verified execution.

  12. 18
    Action

    Identify deleted files and directories (marked as unallocated but not yet overwritten)

    Source-described action candidate under “Step 3: Analyze File System Structure”; not verified execution.

  13. 19
    Action

    Recover files from unallocated space using file carving

    Source-described action candidate under “Step 3: Analyze File System Structure”; not verified execution.

  14. 20
    Action

    Examine alternate data streams (NTFS ADS) for hidden data

    Source-described action candidate under “Step 3: Analyze File System Structure”; not verified execution.

  15. 21
    Action

    Step 4: Reconstruct the Timeline

    Source-described action candidate under “Step 4: Reconstruct the Timeline”; not verified execution.

  16. 22
    Action

    Generate timeline from all available sources (MFT, event logs, browser history, prefetch)

    Source-described action candidate under “Step 4: Reconstruct the Timeline”; not verified execution.

  17. 23
    Action

    Filter to the investigation timeframe

    Source-described action candidate under “Step 4: Reconstruct the Timeline”; not verified execution.

  18. 24
    Action

    Identify clusters of activity correlating with the incident

    Source-described action candidate under “Step 4: Reconstruct the Timeline”; not verified execution.

  19. 25
    Action

    Document the sequence of attacker actions based on file creation, modification, and access timestamps

    Source-described action candidate under “Step 4: Reconstruct the Timeline”; not verified execution.

  20. 26
    Action

    Step 5: Recover and Analyze Artifacts

    Source-described action candidate under “Step 5: Recover and Analyze Artifacts”; not verified execution.

  21. 27
    Action

    Extract and analyze specific forensic artifacts:

    Source-described action candidate under “Step 5: Recover and Analyze Artifacts”; not verified execution.

  22. 28
    Action

    Prefetch files: Parse with PECmd to determine program execution times and loaded DLLs

    Source-described action candidate under “Step 5: Recover and Analyze Artifacts”; not verified execution.

  23. 29
    Action

    Event logs: Parse with EvtxECmd for Windows XML Event Logs

    Source-described action candidate under “Step 5: Recover and Analyze Artifacts”; not verified execution.

  24. 30
    Action

    Registry: Parse with RegRipper or Registry Explorer for user activity and system configuration

    Source-described action candidate under “Step 5: Recover and Analyze Artifacts”; not verified execution.

  25. 31
    Action

    Browser artifacts: Parse with Hindsight (Chrome), KAPE, or DB Browser for SQLite databases

    Source-described action candidate under “Step 5: Recover and Analyze Artifacts”; not verified execution.

  26. 32
    Action

    USB device history: Extract from SYSTEM\CurrentControlSet\Enum\USBSTOR registry key

    Source-described action candidate under “Step 5: Recover and Analyze Artifacts”; not verified execution.

  27. 33
    Action

    $MFT analysis: Parse with MFTECmd for detailed file metadata including $SI and $FN timestamps

    Source-described action candidate under “Step 5: Recover and Analyze Artifacts”; not verified execution.

  28. 34
    Action

    Step 6: Document Findings

    Source-described action candidate under “Step 6: Document Findings”; not verified execution.

  29. 35
    Action

    Maintain evidence integrity documentation (hash chain)

    Source-described action candidate under “Step 6: Document Findings”; not verified execution.

  30. 36
    Action

    Document every tool used and its version

    Source-described action candidate under “Step 6: Document Findings”; not verified execution.

  31. 37
    Action

    Record all analysis steps in a reproducible manner

    Source-described action candidate under “Step 6: Document Findings”; not verified execution.

  32. 38
    Output

    Present findings factually without conjecture

    Source-described output candidate under “Step 6: Document Findings”; not verified execution.

  33. 39
    Action

    Clearly distinguish between facts (observed data) and interpretations (analyst conclusions)

    Source-described action candidate under “Step 6: Document Findings”; not verified execution.

  34. 40
    Action

    Key Concepts

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

  35. 41
    Action

    Tools & Systems

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

  36. 42
    Action

    Common Scenarios

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

  37. 43
    Output

    Image the workstation disk using FTK Imager with a write blocker

    Source-described output candidate under “Scenario: Employee Data Theft Investigation”; not verified execution.

  38. 44
    Action

    Parse USB device history from SYSTEM registry to identify connected devices

    Source-described action candidate under “Scenario: Employee Data Theft Investigation”; not verified execution.

  39. 45
    Action

    Examine ShellBags and Jump Lists for evidence of file browsing and copying to removable media

    Source-described action candidate under “Scenario: Employee Data Theft Investigation”; not verified execution.

  40. 46
    Action

    Parse LNK files in the Recent folder to identify recently accessed documents

    Source-described action candidate under “Scenario: Employee Data Theft Investigation”; not verified execution.

  41. 47
    Action

    Analyze browser history for personal cloud storage uploads (Google Drive, Dropbox)

    Source-described action candidate under “Scenario: Employee Data Theft Investigation”; not verified execution.

  42. 48
    Action

    Build a timeline correlating USB connections with file access events

    Source-described action candidate under “Scenario: Employee Data Theft Investigation”; not verified execution.

  43. 49
    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

26 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

6 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 6 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

20 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 20 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/performing-disk-forensics-investigation/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/performing-disk-forensics-investigation/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/performing-disk-forensics-investigation
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.