Cleanup, Restoration, Evidence Retention, and Secure Destruction

An authorized penetration test is nearly finished. During the work, the tester created an account, added a scheduled task for persistence, changed a security setting, deployed a tool, started a temporary cloud instance, captured a credential hash, and saved a packet capture. The…
An authorized penetration test is nearly finished. During the work, the tester created an account, added a scheduled task for persistence, changed a security setting, deployed a tool, started a temporary cloud instance, captured a credential hash, and saved a packet capture. The findings are documented, so can the tester simply delete everything and declare the environment clean? This episode explains how tester-created accounts, persistence, configuration changes, tools, temporary infrastructure, evidence, and sensitive working data should be removed, restored, retained, or destroyed. The discussion keeps conclusions tied to the evidence collected and the actions permitted by the engagement rather than treating technical capability as automatic authorization. Visit BareMetalCyber.com for more cybersecurity education, certification preparation, and practical penetration-testing guidance.
Cleanup, Restoration, Evidence Retention, and Secure Destruction

headphones Listen Anywhere

More Options »
Broadcast by