zeroize-audit

Featured

Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.

Data & Documents 8,273 stars 715 forks Updated 6 days ago CC-BY-SA-4.0

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# zeroize-audit — Claude Skill ## When to Use - Auditing cryptographic implementations (keys, seeds, nonces, secrets) - Reviewing authentication systems (passwords, tokens, session data) - Analyzing code that handles PII or sensitive credentials - Verifying secure cleanup in security-critical codebases - Investigating memory safety of sensitive data handling ## When NOT to Use - General code review without security focus - Performance optimization (unless related to secure wiping) - Refactoring tasks not related to sensitive data - Code without identifiable secrets or sensitive values --- ## Purpose Detect missing zeroization of sensitive data in source code and identify zeroization that is removed or weakened by compiler optimizations (e.g., dead-store elimination), with mandatory LLVM IR/asm evidence. Capabilities include: - Assembly-level analysis for register spills and stack retention - Data-flow tracking for secret copies - Heap allocator security warnings - Semantic IR analysis for loop unrolling and SSA form - Control-flow graph analysis for path coverage verification - Runtime validation test generation ## Scope - Read-only against the target codebase (does not modify audited code; writes analysis artifacts to a temporary working directory). - Produces a structured report (JSON). - Requires valid build context (`compile_commands.json`) and compilable translation units. - "Optimized away" findings only allowed with compiler evidence (IR/asm diff). --- ## Inputs...

Details

Author
trailofbits
Repository
trailofbits/skills
Created
10 months ago
Last Updated
6 days ago
Language
Python
License
CC-BY-SA-4.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

zeroize-audit

Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.

49,938 Updated today
sickn33
Code & Development Listed

crypto-source-audit

Audits cryptographic source code for timing side channels, missing secret zeroization, non-constant-time comparison, and weak randomness. Use when reviewing crypto primitives, key/nonce/PSK handling, TLS or handshake code, signature or KEM implementations, or any function that touches secret key material, including the bare conversational form ("is this constant-time?", "is this key actually wiped?"). Not for confirming that a compiled binary preserved these properties (use binary-crypto-verify) and not for general non-crypto vulnerability hunting (use codebase-security-audit).

1 Updated 3 months ago
Quant-Off
Code & Development Listed

binary-crypto-verify

Verifies in compiled machine code that security properties survived the compiler: that secret zeroization was not removed by dead-store elimination and that constant-time logic did not regain secret-dependent branches. Use when auditing a binary, shared object, static library, or firmware image whose source claims constant-time or wiping guarantees, when a memset on a key may have been optimized away, or when confirming a fix actually landed in the shipped artifact, using Ghidra, objdump, or radare2. Not for source-level crypto review (use crypto-source-audit) and not for general binary exploitation or malware analysis.

1 Updated 3 months ago
Quant-Off