[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B4NQ1TTXZHRSCD6D9DMSYA":3,"skill-same:01M7B4NQ1TTXZHRSCD6D9DMSYA":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":13,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M7B4NQ1TTXZHRSCD6D9DMSYA","analyzing-disk-image-with-autopsy",null,"Perform comprehensive forensic analysis of raw (dd), E01, or AFF disk images with Autopsy and The Sleuth Kit, recovering deleted files, examining metadata and embedded artifacts, keyword searching, and building investigation timelines with visual reports. Use for structured analysis of a forensic disk image or when stakeholders need visual reports from evidence.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fanalyzing-disk-image-with-autopsy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fanalyzing-disk-image-with-autopsy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analyzing-disk-image-with-autopsy\ndescription: Perform comprehensive forensic analysis of raw (dd), E01, or AFF disk images with Autopsy and The Sleuth Kit, recovering deleted files, examining metadata and embedded artifacts, keyword searching, and building investigation timelines with visual reports. Use for structured analysis of a forensic disk image or when stakeholders need visual reports from evidence.\ndomain: cybersecurity\nsubdomain: digital-forensics\ntags:\n- forensics\n- autopsy\n- disk-analysis\n- sleuth-kit\n- file-recovery\n- artifact-analysis\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- RS.AN-03\n- DE.AE-02\n- RS.MA-01\nmitre_attack:\n- T1005\n- T1074.001\n- T1070.004\n- T1083\n---\n\n# Analyzing Disk Image with Autopsy\n\n## When to Use\n- When you have a forensic disk image and need structured analysis of its contents\n- During investigations requiring file recovery, keyword searching, and timeline analysis\n- When non-technical stakeholders need visual reports from forensic evidence\n- For examining file system metadata, deleted files, and embedded artifacts\n- When building a comprehensive case from multiple disk images\n\n## Prerequisites\n- Autopsy 4.x installed (Windows) or Autopsy 4.x with The Sleuth Kit (Linux)\n- Forensic disk image in raw (dd), E01 (EnCase), or AFF format\n- Minimum 8GB RAM (16GB recommended for large images)\n- Java Runtime Environment (JRE) 8+ for Autopsy\n- Sufficient disk space for the Autopsy case database (2-3x image size)\n- Hash databases (NSRL, known-bad hashes) for file identification\n\n## Workflow\n\n### Step 1: Install Autopsy and Configure Environment\n\n```bash\n# On Linux, install Sleuth Kit and Autopsy\nsudo apt-get install autopsy sleuthkit\n\n# Download Autopsy 4.x (GUI version) from official source\nwget https:\u002F\u002Fgithub.com\u002Fsleuthkit\u002Fautopsy\u002Freleases\u002Fdownload\u002Fautopsy-4.21.0\u002Fautopsy-4.21.0.zip\nunzip autopsy-4.21.0.zip -d \u002Fopt\u002Fautopsy\n\n# On Windows, run the MSI installer from sleuthkit.org\n# Launch Autopsy\n\u002Fopt\u002Fautopsy\u002Fbin\u002Fautopsy --nosplash\n\n# For Sleuth Kit command-line analysis alongside Autopsy\nsudo apt-get install sleuthkit\n```\n\n### Step 2: Create a New Case and Add the Disk Image\n\n```\n1. Launch Autopsy > \"New Case\"\n2. Enter Case Name: \"CASE-2024-001-Workstation\"\n3. Set Base Directory: \u002Fcases\u002Fcase-2024-001\u002Fautopsy\u002F\n4. Enter Case Number, Examiner Name\n5. Click \"Add Data Source\"\n6. Select \"Disk Image or VM File\"\n7. Browse to: \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd\n8. Select Time Zone of the original system\n9. Configure Ingest Modules (see Step 3)\n```\n\n```bash\n# Alternatively, use Sleuth Kit CLI to verify the image first\nimg_stat \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd\n\n# List partitions in the image\nmmls \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd\n\n# Output example:\n# DOS Partition Table\n# Offset Sector: 0\n# Units are in 512-byte sectors\n#      Slot    Start        End          Length       Description\n#      00:  -----   0000000000   0000002047   0000002048   Primary Table (#0)\n#      01:  00:00   0000002048   0001026047   0001024000   NTFS (0x07)\n#      02:  00:01   0001026048   0976771071   0975745024   NTFS (0x07)\n\n# List files in a partition (offset 2048 sectors)\nfls -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd\n```\n\n### Step 3: Configure and Run Ingest Modules\n\n```\nEnable the following Autopsy Ingest Modules:\n- Recent Activity: Extracts browser history, downloads, cookies, bookmarks\n- Hash Lookup: Compares files against NSRL and known-bad hash sets\n- File Type Identification: Identifies files by signature, not extension\n- Keyword Search: Indexes content for full-text searching\n- Email Parser: Extracts emails from PST, MBOX, EML files\n- Extension Mismatch Detector: Finds files with wrong extensions\n- Exif Parser: Extracts metadata from images (GPS, camera, timestamps)\n- Encryption Detection: Identifies encrypted files and containers\n- Interesting Files Identifier: Flags files matching custom rule sets\n- Embedded File Extractor: Extracts files from ZIP, Office docs, PDFs\n- Picture Analyzer: Categorizes images using PhotoDNA or hash matching\n- Data Source Integrity: Verifies image hash during ingest\n```\n\n```bash\n# Configure NSRL hash set for known-good filtering\n# Download NSRL from https:\u002F\u002Fwww.nist.gov\u002Fitl\u002Fssd\u002Fsoftware-quality-group\u002Fnational-software-reference-library-nsrl\nwget https:\u002F\u002Fs3.amazonaws.com\u002Frds.nsrl.nist.gov\u002FRDS\u002Fcurrent\u002Frds_modernm.zip\nunzip rds_modernm.zip -d \u002Fopt\u002Fautopsy\u002Fhashsets\u002F\n\n# Import into Autopsy:\n# Tools > Options > Hash Sets > Import > Select NSRLFile.txt\n# Mark as \"Known\" (to filter out known-good files)\n```\n\n### Step 4: Analyze File System and Recover Deleted Files\n\n```bash\n# In Autopsy GUI: Navigate tree structure\n# - Data Sources > evidence.dd > vol2 (NTFS)\n# - Examine directory tree, note deleted files (marked with X)\n\n# Using Sleuth Kit CLI for targeted recovery\n# List deleted files\nfls -rd -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd\n\n# Recover a specific deleted file by inode\nicat -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd 14523 > \u002Fcases\u002Fcase-2024-001\u002Frecovered\u002Fdeleted_document.docx\n\n# Extract all files from a directory\ntsk_recover -o 2048 -d \u002FUsers\u002Fsuspect\u002FDocuments \\\n   \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd \\\n   \u002Fcases\u002Fcase-2024-001\u002Frecovered\u002Fdocuments\u002F\n\n# Get detailed file metadata\nistat -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd 14523\n# Shows: creation, modification, access, MFT change timestamps, size, data runs\n```\n\n### Step 5: Perform Keyword Searches and Tag Evidence\n\n```\nIn Autopsy:\n1. Keyword Search panel > \"Ad Hoc Keyword Search\"\n2. Search terms: credit card patterns, SSN regex, email addresses\n3. Example regex for credit cards: \\b(?:4[0-9]{12}(?:[0-9]{3})?|5[1-5][0-9]{14})\\b\n4. Example regex for SSN: \\b\\d{3}-\\d{2}-\\d{4}\\b\n5. Review results > Right-click items > \"Add Tag\"\n6. Create tags: \"Evidence-Critical\", \"Evidence-Supporting\", \"Requires-Review\"\n7. Add comments to tagged items documenting relevance\n```\n\n```bash\n# Using Sleuth Kit for CLI keyword search\nsrch_strings -a -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd | \\\n   grep -iE '(password|secret|confidential)' > \u002Fcases\u002Fcase-2024-001\u002Fkeyword_hits.txt\n\n# Search for specific file signatures\nsigfind -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd 25504446\n# 25504446 = %PDF header signature\n```\n\n### Step 6: Build Timeline and Generate Reports\n\n```\nIn Autopsy:\n1. Timeline viewer: Tools > Timeline\n2. Select date range of interest (incident window)\n3. Filter by event type: File Created, Modified, Accessed, Web Activity\n4. Zoom into suspicious time periods\n5. Export timeline events as CSV for external analysis\n\nGenerate Report:\n1. Generate Report > HTML Report\n2. Select tagged items and data sources to include\n3. Configure report sections: file listings, keyword hits, timeline\n4. Export to \u002Fcases\u002Fcase-2024-001\u002Freports\u002F\n```\n\n```bash\n# Using Sleuth Kit mactime for CLI timeline\nfls -r -m \"\u002F\" -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd > \u002Fcases\u002Fcase-2024-001\u002Fbodyfile.txt\n\n# Generate timeline from bodyfile\nmactime -b \u002Fcases\u002Fcase-2024-001\u002Fbodyfile.txt -d > \u002Fcases\u002Fcase-2024-001\u002Ftimeline.csv\n\n# Filter timeline to specific date range\nmactime -b \u002Fcases\u002Fcase-2024-001\u002Fbodyfile.txt \\\n   -d 2024-01-15..2024-01-20 > \u002Fcases\u002Fcase-2024-001\u002Fincident_timeline.csv\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Ingest Modules | Automated analysis plugins that process data sources upon import |\n| MFT (Master File Table) | NTFS metadata structure recording all file entries and attributes |\n| File carving | Recovering files from unallocated space using file signatures |\n| Hash filtering | Using NSRL or custom hash sets to exclude known-good or flag known-bad files |\n| Timeline analysis | Chronological reconstruction of file system and user activity events |\n| Deleted file recovery | Restoring files whose directory entries are removed but data remains |\n| Keyword indexing | Full-text search index built from all file content including slack space |\n| Artifact extraction | Automated parsing of browser, email, registry, and OS-specific artifacts |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Autopsy | Open-source GUI forensic platform for disk image analysis |\n| The Sleuth Kit (TSK) | Command-line forensic toolkit underlying Autopsy |\n| fls | List files and directories in a disk image including deleted entries |\n| icat | Extract file content by inode number from a disk image |\n| mactime | Generate timeline from TSK bodyfile format |\n| mmls | Display partition layout of a disk image |\n| NSRL | NIST hash database for identifying known software files |\n| sigfind | Search for file signatures at the sector level |\n\n## Common Scenarios\n\n**Scenario 1: Employee Data Theft Investigation**\nImport the employee workstation image, run all ingest modules, search for company-confidential file names and keywords, examine USB connection artifacts in Recent Activity, check for cloud storage client artifacts, review deleted files for evidence of data staging, generate HTML report for legal team.\n\n**Scenario 2: Malware Infection Forensics**\nAdd the compromised system image, enable Extension Mismatch and Encryption Detection modules, examine the prefetch directory for execution evidence, search for known malware hashes, build timeline around the infection window, extract suspicious executables for further analysis in a sandbox.\n\n**Scenario 3: Child Exploitation Material (CSAM) Investigation**\nImport image with PhotoDNA and Project VIC hash sets enabled, run Picture Analyzer module, hash all image files against known-bad databases, tag and categorize matches by severity, generate law enforcement report with chain of custody documentation.\n\n**Scenario 4: Intellectual Property Dispute**\nImport multiple employee disk images as separate data sources in one case, perform keyword searches for proprietary terms and project names, compare file hashes between sources, build timeline showing file access and transfer patterns, export evidence for legal review.\n\n## Output Format\n\n```\nAutopsy Case Analysis Summary:\n  Case:           CASE-2024-001-Workstation\n  Image:          evidence.dd (500GB NTFS)\n  Partitions:     2 (System Reserved + Primary)\n  Total Files:    245,832\n  Deleted Files:  12,456 (recoverable: 8,234)\n\n  Ingest Results:\n    Hash Matches (Known Bad):  3 files\n    Extension Mismatches:      17 files\n    Keyword Hits:              234 across 45 files\n    Encrypted Files:           5 containers detected\n    EXIF Data Extracted:       1,245 images with metadata\n\n  Tagged Evidence:\n    Critical:     12 items\n    Supporting:   34 items\n    Review:       67 items\n\n  Timeline Events:  1,234,567 entries (filtered to incident window: 892)\n  Report:          \u002Fcases\u002Fcase-2024-001\u002Freports\u002Fautopsy_report.html\n```\n","# Analyzing Disk Image with Autopsy\n\n## When to Use\n- When you have a forensic disk image and need structured analysis of its contents\n- During investigations requiring file recovery, keyword searching, and timeline analysis\n- When non-technical stakeholders need visual reports from forensic evidence\n- For examining file system metadata, deleted files, and embedded artifacts\n- When building a comprehensive case from multiple disk images\n\n## Prerequisites\n- Autopsy 4.x installed (Windows) or Autopsy 4.x with The Sleuth Kit (Linux)\n- Forensic disk image in raw (dd), E01 (EnCase), or AFF format\n- Minimum 8GB RAM (16GB recommended for large images)\n- Java Runtime Environment (JRE) 8+ for Autopsy\n- Sufficient disk space for the Autopsy case database (2-3x image size)\n- Hash databases (NSRL, known-bad hashes) for file identification\n\n## Workflow\n\n### Step 1: Install Autopsy and Configure Environment\n\n```bash\n# On Linux, install Sleuth Kit and Autopsy\nsudo apt-get install autopsy sleuthkit\n\n# Download Autopsy 4.x (GUI version) from official source\nwget https:\u002F\u002Fgithub.com\u002Fsleuthkit\u002Fautopsy\u002Freleases\u002Fdownload\u002Fautopsy-4.21.0\u002Fautopsy-4.21.0.zip\nunzip autopsy-4.21.0.zip -d \u002Fopt\u002Fautopsy\n\n# On Windows, run the MSI installer from sleuthkit.org\n# Launch Autopsy\n\u002Fopt\u002Fautopsy\u002Fbin\u002Fautopsy --nosplash\n\n# For Sleuth Kit command-line analysis alongside Autopsy\nsudo apt-get install sleuthkit\n```\n\n### Step 2: Create a New Case and Add the Disk Image\n\n```\n1. Launch Autopsy > \"New Case\"\n2. Enter Case Name: \"CASE-2024-001-Workstation\"\n3. Set Base Directory: \u002Fcases\u002Fcase-2024-001\u002Fautopsy\u002F\n4. Enter Case Number, Examiner Name\n5. Click \"Add Data Source\"\n6. Select \"Disk Image or VM File\"\n7. Browse to: \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd\n8. Select Time Zone of the original system\n9. Configure Ingest Modules (see Step 3)\n```\n\n```bash\n# Alternatively, use Sleuth Kit CLI to verify the image first\nimg_stat \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd\n\n# List partitions in the image\nmmls \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd\n\n# Output example:\n# DOS Partition Table\n# Offset Sector: 0\n# Units are in 512-byte sectors\n#      Slot    Start        End          Length       Description\n#      00:  -----   0000000000   0000002047   0000002048   Primary Table (#0)\n#      01:  00:00   0000002048   0001026047   0001024000   NTFS (0x07)\n#      02:  00:01   0001026048   0976771071   0975745024   NTFS (0x07)\n\n# List files in a partition (offset 2048 sectors)\nfls -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd\n```\n\n### Step 3: Configure and Run Ingest Modules\n\n```\nEnable the following Autopsy Ingest Modules:\n- Recent Activity: Extracts browser history, downloads, cookies, bookmarks\n- Hash Lookup: Compares files against NSRL and known-bad hash sets\n- File Type Identification: Identifies files by signature, not extension\n- Keyword Search: Indexes content for full-text searching\n- Email Parser: Extracts emails from PST, MBOX, EML files\n- Extension Mismatch Detector: Finds files with wrong extensions\n- Exif Parser: Extracts metadata from images (GPS, camera, timestamps)\n- Encryption Detection: Identifies encrypted files and containers\n- Interesting Files Identifier: Flags files matching custom rule sets\n- Embedded File Extractor: Extracts files from ZIP, Office docs, PDFs\n- Picture Analyzer: Categorizes images using PhotoDNA or hash matching\n- Data Source Integrity: Verifies image hash during ingest\n```\n\n```bash\n# Configure NSRL hash set for known-good filtering\n# Download NSRL from https:\u002F\u002Fwww.nist.gov\u002Fitl\u002Fssd\u002Fsoftware-quality-group\u002Fnational-software-reference-library-nsrl\nwget https:\u002F\u002Fs3.amazonaws.com\u002Frds.nsrl.nist.gov\u002FRDS\u002Fcurrent\u002Frds_modernm.zip\nunzip rds_modernm.zip -d \u002Fopt\u002Fautopsy\u002Fhashsets\u002F\n\n# Import into Autopsy:\n# Tools > Options > Hash Sets > Import > Select NSRLFile.txt\n# Mark as \"Known\" (to filter out known-good files)\n```\n\n### Step 4: Analyze File System and Recover Deleted Files\n\n```bash\n# In Autopsy GUI: Navigate tree structure\n# - Data Sources > evidence.dd > vol2 (NTFS)\n# - Examine directory tree, note deleted files (marked with X)\n\n# Using Sleuth Kit CLI for targeted recovery\n# List deleted files\nfls -rd -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd\n\n# Recover a specific deleted file by inode\nicat -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd 14523 > \u002Fcases\u002Fcase-2024-001\u002Frecovered\u002Fdeleted_document.docx\n\n# Extract all files from a directory\ntsk_recover -o 2048 -d \u002FUsers\u002Fsuspect\u002FDocuments \\\n   \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd \\\n   \u002Fcases\u002Fcase-2024-001\u002Frecovered\u002Fdocuments\u002F\n\n# Get detailed file metadata\nistat -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd 14523\n# Shows: creation, modification, access, MFT change timestamps, size, data runs\n```\n\n### Step 5: Perform Keyword Searches and Tag Evidence\n\n```\nIn Autopsy:\n1. Keyword Search panel > \"Ad Hoc Keyword Search\"\n2. Search terms: credit card patterns, SSN regex, email addresses\n3. Example regex for credit cards: \\b(?:4[0-9]{12}(?:[0-9]{3})?|5[1-5][0-9]{14})\\b\n4. Example regex for SSN: \\b\\d{3}-\\d{2}-\\d{4}\\b\n5. Review results > Right-click items > \"Add Tag\"\n6. Create tags: \"Evidence-Critical\", \"Evidence-Supporting\", \"Requires-Review\"\n7. Add comments to tagged items documenting relevance\n```\n\n```bash\n# Using Sleuth Kit for CLI keyword search\nsrch_strings -a -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd | \\\n   grep -iE '(password|secret|confidential)' > \u002Fcases\u002Fcase-2024-001\u002Fkeyword_hits.txt\n\n# Search for specific file signatures\nsigfind -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd 25504446\n# 25504446 = %PDF header signature\n```\n\n### Step 6: Build Timeline and Generate Reports\n\n```\nIn Autopsy:\n1. Timeline viewer: Tools > Timeline\n2. Select date range of interest (incident window)\n3. Filter by event type: File Created, Modified, Accessed, Web Activity\n4. Zoom into suspicious time periods\n5. Export timeline events as CSV for external analysis\n\nGenerate Report:\n1. Generate Report > HTML Report\n2. Select tagged items and data sources to include\n3. Configure report sections: file listings, keyword hits, timeline\n4. Export to \u002Fcases\u002Fcase-2024-001\u002Freports\u002F\n```\n\n```bash\n# Using Sleuth Kit mactime for CLI timeline\nfls -r -m \"\u002F\" -o 2048 \u002Fcases\u002Fcase-2024-001\u002Fimages\u002Fevidence.dd > \u002Fcases\u002Fcase-2024-001\u002Fbodyfile.txt\n\n# Generate timeline from bodyfile\nmactime -b \u002Fcases\u002Fcase-2024-001\u002Fbodyfile.txt -d > \u002Fcases\u002Fcase-2024-001\u002Ftimeline.csv\n\n# Filter timeline to specific date range\nmactime -b \u002Fcases\u002Fcase-2024-001\u002Fbodyfile.txt \\\n   -d 2024-01-15..2024-01-20 > \u002Fcases\u002Fcase-2024-001\u002Fincident_timeline.csv\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Ingest Modules | Automated analysis plugins that process data sources upon import |\n| MFT (Master File Table) | NTFS metadata structure recording all file entries and attributes |\n| File carving | Recovering files from unallocated space using file signatures |\n| Hash filtering | Using NSRL or custom hash sets to exclude known-good or flag known-bad files |\n| Timeline analysis | Chronological reconstruction of file system and user activity events |\n| Deleted file recovery | Restoring files whose directory entries are removed but data remains |\n| Keyword indexing | Full-text search index built from all file content including slack space |\n| Artifact extraction | Automated parsing of browser, email, registry, and OS-specific artifacts |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Autopsy | Open-source GUI forensic platform for disk image analysis |\n| The Sleuth Kit (TSK) | Command-line forensic toolkit underlying Autopsy |\n| fls | List files and directories in a disk image including deleted entries |\n| icat | Extract file content by inode number from a disk image |\n| mactime | Generate timeline from TSK bodyfile format |\n| mmls | Display partition layout of a disk image |\n| NSRL | NIST hash database for identifying known software files |\n| sigfind | Search for file signatures at the sector level |\n\n## Common Scenarios\n\n**Scenario 1: Employee Data Theft Investigation**\nImport the employee workstation image, run all ingest modules, search for company-confidential file names and keywords, examine USB connection artifacts in Recent Activity, check for cloud storage client artifacts, review deleted files for evidence of data staging, generate HTML report for legal team.\n\n**Scenario 2: Malware Infection Forensics**\nAdd the compromised system image, enable Extension Mismatch and Encryption Detection modules, examine the prefetch directory for execution evidence, search for known malware hashes, build timeline around the infection window, extract suspicious executables for further analysis in a sandbox.\n\n**Scenario 3: Child Exploitation Material (CSAM) Investigation**\nImport image with PhotoDNA and Project VIC hash sets enabled, run Picture Analyzer module, hash all image files against known-bad databases, tag and categorize matches by severity, generate law enforcement report with chain of custody documentation.\n\n**Scenario 4: Intellectual Property Dispute**\nImport multiple employee disk images as separate data sources in one case, perform keyword searches for proprietary terms and project names, compare file hashes between sources, build timeline showing file access and transfer patterns, export evidence for legal review.\n\n## Output Format\n\n```\nAutopsy Case Analysis Summary:\n  Case:           CASE-2024-001-Workstation\n  Image:          evidence.dd (500GB NTFS)\n  Partitions:     2 (System Reserved + Primary)\n  Total Files:    245,832\n  Deleted Files:  12,456 (recoverable: 8,234)\n\n  Ingest Results:\n    Hash Matches (Known Bad):  3 files\n    Extension Mismatches:      17 files\n    Keyword Hits:              234 across 45 files\n    Encrypted Files:           5 containers detected\n    EXIF Data Extracted:       1,245 images with metadata\n\n  Tagged Evidence:\n    Critical:     12 items\n    Supporting:   34 items\n    Review:       67 items\n\n  Timeline Events:  1,234,567 entries (filtered to incident window: 892)\n  Report:          \u002Fcases\u002Fcase-2024-001\u002Freports\u002Fautopsy_report.html\n```\n",{"name":5,"tags":24,"author":31,"domain":32,"license":14,"version":33,"nist_csf":34,"subdomain":38,"description":7,"mitre_attack":39},[25,26,27,28,29,30],"forensics","autopsy","disk-analysis","sleuth-kit","file-recovery","artifact-analysis","mahipal","cybersecurity","1.0",[35,36,37],"RS.AN-03","DE.AE-02","RS.MA-01","digital-forensics",[40,41,42,43],"T1005","T1074.001","T1070.004","T1083","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fanalyzing-disk-image-with-autopsy","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill analyzing-disk-image-with-autopsy",{"tool":56,"command":57},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill analyzing-disk-image-with-autopsy",{"tool":59,"command":60},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill analyzing-disk-image-with-autopsy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fanalyzing-disk-image-with-autopsy\u002FSKILL.md",true,[64,68,74],{"path":65,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fapi-reference.md","REFERENCE","参考文档",2908,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fanalyzing-disk-image-with-autopsy\u002Freferences\u002Fapi-reference.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Fagent.py","SCRIPT","脚本",7729,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fanalyzing-disk-image-with-autopsy\u002Fscripts\u002Fagent.py",[81,89,96,103,110,117],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]