Security engagement
Rust security audit
Rust removes whole classes of memory bugs at compile time — but unsafe blocks, FFI boundaries, panics, dependency supply chain, and web-facing logic still carry real risk. A Rust audit is not a linter run; it is a threat model plus a hand review of the places the compiler cannot protect you.
from $5,000 · quoted in writing after scope
Who it is for
For Rust services and systems code where a memory bug, a panic-driven outage, or an unsound abstraction has outsized impact — and for teams shipping their first Rust-to-production system.
What is in scope
- unsafe blocks and soundness: invariants, aliasing, Send/Sync, lifetime escapes
- FFI and C-interop boundaries, including pointer/ownership contracts
- panic, unwrap, and error paths that turn into denial-of-service or state corruption
- async correctness: cancellation, backpressure, and shutdown races
- dependency and supply-chain risk in Cargo.lock, plus build/proc-macro surface
- web-facing logic where the audit is for a network service: authz, input handling, resource limits
What you get
- A threat model specific to your system, agreed before testing starts
- Severity-rated findings with proof-of-concept and a clear reproduction path
- Concrete remediation guidance — code-level where possible, with the reasoning
- A live readout call with your engineers so the fixes land
- A retest of your fixes after remediation
Frequently asked
Is a Rust security audit needed if the code is memory-safe by construction?
Safety is only by construction where there is no unsafe. Every unsafe block, every FFI call, every C dependency, and every panic path is a place where the compiler stops protecting you. The audit focuses there, plus the logic bugs that memory safety never covered.
How long does a Rust security audit take?
A fixed one-week deep review is the default for a single service or crate set. Larger workspaces are scoped up front into a fixed number of weeks so the cost is known before you commit.
Do you need write access to our repository?
Read-only access to the code and, where relevant, a running environment for dynamic checks. Everything is covered by a written scope and rules of engagement before the first line is reviewed.
Scope it in one message
Send the targets, the commit and the timeline. You get the rules of engagement and a fixed price.
References available on request. No client names or numbers are published without written consent. Part of an ongoing relationship instead? See the full service list.