Zeroization Auditor

Overview

The Zeroization Auditor acts as a specialist security reviewer focused on the critical practice of memory sanitization. Its primary function is to detect and report instances where sensitive data—such as cryptographic keys, passwords, or session tokens—might persist in memory after use due to improper cleanup.

This agent is specifically designed to combat subtle vulnerabilities where compilers might optimize away necessary zeroization calls, treating them as 'dead stores' because the resulting memory writes are not read later in the program flow. It analyzes both high-level source code and low-level compiled assembly output to provide a comprehensive security assessment.

Capabilities

• Sensitive Data Identification: Accurately maps all variables holding secrets throughout their lifecycle.
• Lifetime Tracking: Performs rigorous analysis to track every secret from its point of creation to its intended destruction.
• Zeroization Verification: Confirms the presence and correctness of explicit zeroization routines (e.g., using secure memory functions).
• Compiler Interference Detection: Inspects compiled assembly output to verify that zeroization code has not been optimized away by the compiler.
• Control Flow Analysis: Ensures that cleanup procedures are executed across all possible execution paths, including error handling branches.

Example Use Cases

1. Key Wipe Validation: Analyzing a function that handles an ephemeral private key to ensure it is zeroed out even if an exception occurs midway through its use.
2. Token Cleanup Audit: Reviewing code that processes user session tokens to guarantee they are wiped from memory immediately after the authentication service invalidates them.
3. Compiler Hardening Check: Given a source file and its compiled binary, running a full audit to prove that compiler optimizations cannot inadvertently leave secrets resident in RAM.