security-audit

Auditing unsafe code and FFI boundaries in Rust applications involves inspecting all unsafe blocks, verifying safety invariants, and assessing memory management. This skill automates that review to identify vulnerabilities and ensure secure defaults.

Static analysis for Rust security vulnerabilities covers identifying common vulnerability patterns, reviewing authentication and authorization, checking for injection vectors, and validating cryptographic usage against OWASP guidelines.

Yes, you can use cargo-audit and cargo-clippy to enforce secure defaults in WebAssembly projects. This skill integrates these tools to automate vulnerability assessment, review unsafe code, and generate actionable remediation guidance.

The best way to check Rust crates for OWASP compliance is to automate security auditing across code dependencies and configurations. This skill validates input handling, secret management, and TLS configuration to ensure adherence to secure standards.

You need to run a security audit on Rust and WebAssembly applications during code review, threat modeling, and compliance checks. It identifies vulnerabilities, reviews unsafe blocks, and validates input handling across crates and FFI boundaries.