DonPAPI
Keep the installed revision, collector configuration, and artifact provenance together. The latest GitHub release asset and the current source branch may describe different command layouts.
donpapi --help
donpapi gui --help
Compatibility and evidence
- Check the selected source's Python requirements and subcommand help. Do not combine 1.x examples with 2.x options.
- Map each result to the host, user, application, collector, and collection time.
- Separate collection success from successful decryption. Unsupported artifacts, access failures, missing key material, and empty stores are different outcomes.
- Review existing results through the local GUI or documented exports. Keep the service bound to loopback unless a different deployment is explicitly configured.
- Redact recovered values in reports; retain evidence locations and affected applications.
Avoid false coverage claims
- DPAPI is one protection mechanism. Do not describe the tool as recovering every secret or as equivalent to an LSASS dump.
- Browser support depends on browser build, artifact type, protection scheme, and the selected collector/dependency versions. Do not infer universal App-Bound support.
- The absence of LSASS access is not absence of telemetry; network, service, registry, and filesystem activity can still be observable.
- Use the installed output/database layout. Do not assume per-host JSON/Markdown directories or that task XML contains account passwords.
Sources: upstream documentation, source requirements, published releases.