tag: Forensics · 3 items
- Engineer — Learn: OneNote has been abused as a malware delivery vector; knowing how to extract embedded objects from .one files is useful for analyzing suspicious attachments or artifacts in CI/build pipelines that process user-uploaded documents.
- SOC/IR — Learn: Useful forensic technique for IR scenarios involving OneNote-based phishing lures with embedded payloads; bookmark the method for future triage of .one file artifacts.
- Leader — Skip
- Engineer — Learn: Useful awareness that AI coding assistants (Claude Code, Copilot, Cursor, etc.) leave recoverable chat history and artifacts; relevant for understanding the forensic footprint of tools running in your dev environment, but no patch or config change needed.
- SOC/IR — Plan: New forensic scripts targeting 8 popular AI coding assistants are worth incorporating into IR playbooks — when investigating developer workstations, you can now systematically locate and review AI agent session history to reconstruct what the agent did or was instructed to do.
- Leader — Skip
- Engineer — Learn: Atuin replaces flat shell history files with a SQLite-backed store containing richer metadata (timestamps, exit codes, working directory); useful context if you deploy or encounter Atuin on Linux systems and need to understand its forensic footprint or audit trail quality.
- SOC/IR — Learn: Understanding Atuin’s artifact locations and data schema improves Linux IR investigations on hosts where it is installed — richer command history can surface attacker activity that traditional .bash_history misses due to truncation or in-session collisions.
- Leader — Skip