Rust Security Properties.

Rust enforces memory and thread safety at compile time through ownership, borrowing, and lifetimes, eliminating common UB classes such as use-after-free and data races without a garbage collector. It belongs to the Application Security category of cybersecurity.

Rust enforces memory and thread safety at compile time through ownership, borrowing, and lifetimes, eliminating common UB classes such as use-after-free and data races without a garbage collector.

Rust's borrow checker statically verifies that every value has a single owner and that references are either one exclusive mutable borrow or many immutable borrows for a bounded lifetime. This eliminates use-after-free, double-free, iterator invalidation, and most data races by construction. Bounds checks on slices and the Option/Result types remove null-deref and unchecked-error classes. Memory or hardware-level operations live behind explicit unsafe blocks that should be audited and minimized; the standard library and many ecosystem crates encapsulate unsafe behind safe APIs. Adopting Rust does not remove logic bugs, supply-chain risk, side-channel vulnerabilities, or unsafe code review obligations.

Defences for Rust Security Properties typically combine technical controls and operational practices, as detailed in the full definition above.

Common alternative names include: Rust safety, Borrow checker.