Rust Service Security
Use this skill when a Rust service handles identity, credentials, sessions,
cookies, privileged routes, or sensitive user data. Prefer explicit threat
checks and tests over optimistic handler code.
Core Workflow
- Identify the protected asset: account access, admin area, session state,
password change, reset token, private data, or privileged operation.
- Trace the whole flow: request parsing, credential lookup, verification,
session mutation, redirects/responses, logs, and tests.
- Keep secrets out of logs and debug output. Use secret wrappers for passwords,
tokens, signing keys, and session secrets.
- Run password hashing and verification with memory-hard algorithms and move
CPU-heavy work off async reactor threads.
- Prevent user enumeration. Failed login and password reset flows should not
reveal whether the account exists.
- Set cookie and session attributes deliberately:
HttpOnly, Secure,
SameSite, path, lifetime, signing/encryption, and store backend.
- Protect routes at middleware or extractor boundaries, not by repeating
ad-hoc checks in every handler.
- Add tests for happy path, failed auth, missing session, forged cookie or
token, and logout/session rotation behavior.
Password Rules
Read references/password-auth.md before implementing or changing password
storage or verification.
- Store PHC strings produced by Argon2id or the project's chosen password
hasher; never store plaintext or reversible encrypted passwords.
- Generate salts with a secure RNG.
- Use constant, generic responses for invalid credentials.
- Use
tokio::task::spawn_blocking or a dedicated blocking abstraction for
expensive password operations.
- Keep password hash parameters configurable enough to upgrade over time.
Cookie And Session Rules
Read references/cookies-sessions.md when setting, reading, deleting, signing,
or persisting cookies and sessions.
- Never store raw credentials in cookies.
- Prefer opaque session IDs backed by a server-side store for privileged apps.
- Rotate or renew session state after login and privilege changes.
- Delete sessions server-side on logout when using a server-side store.
- Test security attributes on
Set-Cookie headers.
Route Protection
Read references/auth-middleware.md when adding admin routes, extractors,
guards, or framework middleware.
Keep handlers typed:
pub async fn admin_dashboard(user: AuthenticatedUser) -> Result<HttpResponse, AppError> {
// Handler can assume authentication succeeded.
Ok(HttpResponse::Ok().finish())
}
Avoid optional user lookups in handlers that require authentication; make the
missing-user case impossible at the handler signature when the framework allows
it.
Reference Files
references/password-auth.md: Argon2, PHC strings, user enumeration, and
blocking password work.
references/cookies-sessions.md: cookie flags, signed messages, server-side
sessions, and logout.
references/auth-middleware.md: route guards, extractors, and typed session
access.
1---2name: rust-service-security3description: Use when adding, changing, testing, or reviewing security-sensitive Rust web service behavior, especially login flows, password hashing, credential checks, session cookies, flash messages, admin route protection, auth middleware, user enumeration defenses, or moving CPU-heavy password work off async executors.4license: MIT5compatibility: Codex, Claude Code, and other Agent Skills-compatible clients.6metadata:7 source: https://skillmd.com/skills/hashgraph-online/rust-service-security8 version: "0.1.0"9 displayName: Rust Service Security10 category: Rust11 tags: rust,security,authentication,sessions,passwords12---1314# Rust Service Security1516Use this skill when a Rust service handles identity, credentials, sessions,17cookies, privileged routes, or sensitive user data. Prefer explicit threat18checks and tests over optimistic handler code.1920## Core Workflow21221. Identify the protected asset: account access, admin area, session state,23 password change, reset token, private data, or privileged operation.242. Trace the whole flow: request parsing, credential lookup, verification,25 session mutation, redirects/responses, logs, and tests.263. Keep secrets out of logs and debug output. Use secret wrappers for passwords,27 tokens, signing keys, and session secrets.284. Run password hashing and verification with memory-hard algorithms and move29 CPU-heavy work off async reactor threads.305. Prevent user enumeration. Failed login and password reset flows should not31 reveal whether the account exists.326. Set cookie and session attributes deliberately: `HttpOnly`, `Secure`,33 `SameSite`, path, lifetime, signing/encryption, and store backend.347. Protect routes at middleware or extractor boundaries, not by repeating35 ad-hoc checks in every handler.368. Add tests for happy path, failed auth, missing session, forged cookie or37 token, and logout/session rotation behavior.3839## Password Rules4041Read `references/password-auth.md` before implementing or changing password42storage or verification.4344- Store PHC strings produced by Argon2id or the project's chosen password45 hasher; never store plaintext or reversible encrypted passwords.46- Generate salts with a secure RNG.47- Use constant, generic responses for invalid credentials.48- Use `tokio::task::spawn_blocking` or a dedicated blocking abstraction for49 expensive password operations.50- Keep password hash parameters configurable enough to upgrade over time.5152## Cookie And Session Rules5354Read `references/cookies-sessions.md` when setting, reading, deleting, signing,55or persisting cookies and sessions.5657- Never store raw credentials in cookies.58- Prefer opaque session IDs backed by a server-side store for privileged apps.59- Rotate or renew session state after login and privilege changes.60- Delete sessions server-side on logout when using a server-side store.61- Test security attributes on `Set-Cookie` headers.6263## Route Protection6465Read `references/auth-middleware.md` when adding admin routes, extractors,66guards, or framework middleware.6768Keep handlers typed:6970```rust71pub async fn admin_dashboard(user: AuthenticatedUser) -> Result<HttpResponse, AppError> {72 // Handler can assume authentication succeeded.73 Ok(HttpResponse::Ok().finish())74}75```7677Avoid optional user lookups in handlers that require authentication; make the78missing-user case impossible at the handler signature when the framework allows79it.8081## Reference Files8283- `references/password-auth.md`: Argon2, PHC strings, user enumeration, and84 blocking password work.85- `references/cookies-sessions.md`: cookie flags, signed messages, server-side86 sessions, and logout.87- `references/auth-middleware.md`: route guards, extractors, and typed session88 access.