target-dossier-system

A target dossier system maintains persistent memory for complex pentesting workflows by tracking targets, request maps, and exploit chains in structured markdown notes. It solves fragmented context by ensuring critical findings like object families and state transitions persist across different agent sessions.

To track exploit chains and state transitions, you initialize a target dossier that records discovered vulnerabilities and attack vectors in standardized markdown notes. This allows subsequent attack attempts to build upon verified previous findings rather than repeating work.

Yes, the dossier system requires local file system access to manage campaign-specific markdown notes and traffic analysis artifacts. It operates entirely through file-based repository management without external database dependencies.

Yes, the dossier system is designed to map and store discovered GraphQL global IDs and admin panel subdomains during security reconnaissance. It maintains these findings as evidence within a structured repository for ongoing reference.

The best way to organize offensive security findings is using a standardized file-based dossier that categorizes targets, hypotheses, and evidence. This prevents losing track of verified hypotheses by maintaining a structured repository of campaign plans and request maps.