# Rust formal verification The application of formal methods, including model checking and deductive verification, to prove safety and correctness properties of Rust programs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Developing provably correct Rust code with Verus DevFeed: [Developing provably correct Rust code with Verus]() Original publisher: [Read original article]() Author: Bryan Parno Published: 2026-08-31T15:35:33Z Content type: article Language: en Sources: [Amazon Science homepage]() Topics: [Rust formal verification](), [Vulnerabilities]() Tags: [amazon-elastic-compute](), [automated-reasoning](), [aws-lambda](), [code](), [firecracker](), [formal-methods](), [formal-verification](), [open-source](), [rust](), [security](), [testing]() ### AI overview The article explains how Verus formally verifies Rust code against mathematical specifications, helping establish correctness beyond what Rust safety checks and conventional tests provide. ### Source excerpt How the Verus "program verifier", which automatically checks code against a mathematical specification of its functionality, helps increase security assurance in software projects. ## Verifying Rust cryptography in SymCrypt, from standards to code DevFeed: [Verifying Rust cryptography in SymCrypt, from standards to code]() Original publisher: [Read original article]() Author: Son Ho, Cédric Fournet, Antoine Delignat-Lavaud, Samuel Lee, Jason Fisher, Jessica Krynitsky Published: 2026-07-13T16:00:00Z Content type: article Language: en Sources: [Microsoft Research]() Topics: [Rust](), [Rust formal verification](), [Cryptography](), [Formal verification](), [Post-quantum cryptography](), [Lean](), [toolchain](), [Microsoft]() Tags: [cryptography](), [formal-verification](), [memory-safety](), [microsoft](), [post-quantum](), [research](), [research-blog](), [rust](), [security]() ### AI overview Microsoft Research describes how SymCrypt uses safe Rust, Lean, and the Aeneas toolchain to formally verify production cryptographic implementations. The approach combines Rust's memory-safety guarantees with machine-checked proofs of functional correctness, with initial verified code for SHA-3 and ML-KEM and support from independently verifiable proof-writing agents. ### Source excerpt Cryptographic code supports vital protections in modern computing systems. Learn how a new method helps verify code as developers write it while preserving speed and adaptability as it gets implemented and evolves. The post Verifying Rust cryptography in SymCrypt, from standards to code appeared first on Microsoft Research. ## Rust-proof your code with our new Testing Handbook chapter DevFeed: [Rust-proof your code with our new Testing Handbook chapter]() Original publisher: [Read original article]() Author: "Paweł Płatek" Published: 2026-07-13T11:00:00Z Content type: tutorial Language: en Sources: [The Trail of Bits Blog](), [The Trail of Bits Blog]() Topics: [Rust](), [Security](), [mutation-testing](), [Tooling](), [Test coverage](), [Memory Safety](), [Rust formal verification](), [Concurrency](), [Claude Code](), [Claude]() Tags: [application-security](), [claude-code](), [concurrency](), [measurement](), [memory-safety](), [mutation-testing](), [rust](), [security](), [testing](), [testing-handbook](), [tooling]() ### AI overview A new Testing Handbook chapter presents techniques for security testing Rust programs and systems. It covers Rust security limitations, dynamic and static analysis, undefined-behavior detection with Miri, property testing, coverage and mutation testing, Clippy, manual code review, memory zeroization, model checking with Kani, and dependency supply-chain vetting. The article also announces rust-review, a Claude Code plugin for automated Rust security reviews. ### Source excerpt We've added a new chapter to our Testing Handbook: a comprehensive guide to security testing Rust programs. This chapter covers the tools and techniques we use at Trail of Bits to validate the security of Rust programs and systems. fn main() {(|f:&dyn Fn(u128)->Box< dyn Iterator+'static>|f(*[&( 0x7B736D70683F73u128<<64| 0x7A6A6D7C3F7A667D),&(0x7B736Du128 <<64|0x70683F7073737A77)][((std::hint:: black_box(0.0f64)/0.0).to_bits()>>63)as usize]) .for_each(|c|print!("{c}")))(Box::leak(Box::new(|n: u128|Box::new(std::iter::successors(Some(n),|&n|Some(n>>8) ).take_while(|&n|n>0).map(|n|((n as u8)^0x1F)as char))as _)))} What's in the chapter The chapter starts with a security overview of what Rust's guarantees do and don't cover, including underappreciated issues like unwind safety, nondeterminism, and arithmetic errors. This leads into an overview of dynamic analysis, which covers a range of boosters for unit tests, how to use Miri to detect undefined behavior, property testing with proptest, coverage measurement, and mutation testing. The static analysis section then covers Clippy in depth, including a list of our favorite lints. Beyond tooling, the chapter also covers what we've learned from auditing Rust codebases directly. Our gotchas and footguns checklist is a great reference for manual code reviews, and will help you find subtle issues like a & b == c having different operator precedence than in C. The memory zeroization section offers three solutions to the tricky problem of guaranteeing that secrets are erased from memory. Finally, the specialized testing sections cover tools like Kani (a model checker), and the supply chain section covers the full toolchain for vetting dependencies. Still oxidizing We've also released rust-review, a Claude Code plugin for automated Rust security reviews. Co-built with Aptos Labs, it targets over a dozen bug classes, from memory safety and concurrency hazards to FFI pitfalls and async cancellation issues. It's a fast wa ## EC2's formally verified "isolation engine" provides mathematical assurance of virtual-machine isolation DevFeed: [EC2's formally verified "isolation engine" provides mathematical assurance of virtual-machine isolation]() Original publisher: [Read original article]() Author: Dominic Mulligan; Nathan Chong Published: 2026-06-10T15:00:00Z Content type: article Language: en Sources: [Amazon Science homepage]() Topics: [Amazon EC2](), [Rust formal verification]() Tags: [amazon-web-services-aws](), [autocorrode-library](), [automated-reasoning](), [aws-graviton5-security](), [cloud-and-systems](), [confidentiality-integrity-proofs](), [ec2-virtual-machine-security](), [formal-verification](), [formally-verified-hypervisor](), [isabelle-hol-proof-assistant](), [kernel](), [memory-safety-verification](), [nitro-isolation-engine](), [nitro-system](), [provable-security](), [rust](), [rust-formal-verification](), [security](), [security-privacy-and-abuse-prevention]() ### AI overview Amazon describes formally verifying the Nitro Isolation Engine, a separation-kernel component that enforces isolation between EC2 virtual machines. The verification uses Isabelle/HOL and is deployed as an always-on feature for Graviton5 users. ### Source excerpt Splitting the "separation kernel" off from the rest of the Nitro security system and using only a subset of the Rust programming language to code it enabled its formal verification.