The OWASP Application Security Verification Standard (ASVS) lists what a secure application must do. Sentinel is a gateway, not the application itself, so for each requirement this table says what Sentinel does about it, and what is still the protected app’s job.
Requirement numbers and wording are from ASVS 4.0.3 (summarised).
Status:
Met: Sentinel does this for every app behind it.
Helps: Sentinel adds a layer of defence, but the requirement is about how the app itself is built, so the app still has to meet it.
App: only the app can do this. Sentinel can’t.
Partly: Sentinel does part of it. The note says what’s missing.
Pro: met by Sentinel Pro’s zero-trust features (logins for your apps, access policies, mTLS, risk-based step-up, tamper-evident audit log); the free edition leaves it to the app.
V2 Authentication
ASVS
Requirement (summary)
Status
How Sentinel meets it
2.1.1
Passwords at least 12 characters
Partly
Sentinel’s own accounts are its dashboard administrators, created through the first-run setup. There is no self-service password change yet, so there is no length check at change time.
2.2.1
Anti-automation against brute force and credential stuffing
Met
Rate limit on the login API (/__sentinel/auth/=10/1m, counted per IP), flood bans, and a per-account limit on failed logins from any IP (password spraying). Five wrong 2FA codes end the login attempt.
2.4.1
Passwords stored resistant to offline attacks
Met
bcrypt hashes.
2.4.4
bcrypt work factor as high as practical (min. 10)
Met
Cost 12.
2.8.1
Time-based OTPs have a defined lifetime
Met
TOTP per RFC 6238: 30-second steps, ±1 step tolerance. The MFA token that waits for the code lasts 5 minutes.
2.8.3
Approved algorithms for OTPs
Met
HMAC-SHA1 as RFC 6238 specifies. Secrets come from a CSPRNG.
2.8.4
A TOTP code can be used only once
Met
The last accepted time step is stored per user, and replays are rejected.
2.8.5
A reused TOTP code is logged and rejected
Met
Rejected with “already used”, logged as mfa_failed.
2.10.1
Service-to-service auth doesn’t rely on unchanging passwords or API keys
Pro
mTLS for services (MTLS_ROUTES).
2.10.4
Secrets not in source code
Partly
All secrets come from environment variables, and the 2FA secrets in the database are encrypted with AES-256-GCM. The lab’s docker-compose.yml contains lab-only values, marked as such.
V3 Session management
ASVS
Requirement (summary)
Status
How Sentinel meets it
3.3.1
Logout and expiry invalidate the session token
Met
Tokens expire after 15 minutes. Logout puts the token’s ID on a revocation list in PostgreSQL.
3.3.2
Periodic re-authentication
Met
15-minute tokens. There are no refresh tokens, so users log in again.
3.5.2
Session tokens rather than static API secrets
Met
Short-lived signed JWTs for people, certificates for services.
3.5.3
Stateless tokens protected against tampering, null cipher, key substitution
Met
HMAC-SHA256 signatures. Only HS256 is accepted (alg: none and algorithm switching are refused). The signing key is derived with HKDF and kept separate from the encryption key.
V4 Access control
ASVS
Requirement (summary)
Status
How Sentinel meets it
4.1.1
Access control enforced on a trusted server-side layer
Pro
Access policies checked in the gateway on every request. The free edition protects Sentinel’s own dashboard this way; your app’s access control is the app’s job.
4.1.2
Access control data can’t be manipulated by users
Met
Client-sent X-Sentinel-* headers are removed before the app sees them, so no client can forge an identity header.
4.1.3
Least privilege
Met
Rules give each role only the paths and methods it needs.
4.1.5
Access controls fail securely
Partly
Sentinel’s own checks fail securely (an invalid token is never treated as a login, schema checks don’t depend on Redis); only rate limiting fails open if Redis is down, which favours availability. Default-deny access policies for your app are in Pro.
4.2.1
Protection against IDOR (BOLA)
Pro
Owner rules such as /employees/{username}/salary only for that user, HR or admins.
4.2.2
Strong anti-CSRF
App
Sentinel uses bearer tokens in a header, which aren’t sent automatically. CSRF protection for the app’s own cookie sessions is the app’s job.
4.3.1
Admin interfaces use MFA
Met
require_mfa on admin routes, and the dashboard needs admin + 2FA.
4.3.3
Step-up or adaptive authentication
Pro
Risk-based step-up: medium risk needs a session that passed 2FA, and high risk is blocked.
V5 Validation, sanitization and encoding
ASVS
Requirement (summary)
Status
How Sentinel meets it
5.1.1
HTTP parameter pollution
Helps
The WAF inspects every value of repeated parameters, and the schema validator rejects unexpected parameters.
5.1.2
Mass assignment
Met
Schema validation rejects fields the API spec doesn’t allow (additionalProperties: false).
5.1.3
Positive (allow-list) input validation
Met
OpenAPI schema validation on the APIs it covers (types, formats, lengths, patterns).
5.1.4
Structured data strongly typed and validated against a schema
Met
Same.
5.3.3
Output escaping against XSS
Helps
The WAF and the ML model block XSS payloads on the way in. Escaping output is the app’s job.
5.3.4
Parameterised database queries
Helps
SQL injection is blocked by the WAF and the ML model, and was tested with sqlmap (docs/evaluation.md). Sentinel’s own database access is parameterised.
5.3.7
LDAP injection
Helps
ML model (LDAP family in training).
5.3.8
OS command injection
Helps
WAF rule CMDI-001 and the ML model.
5.3.9
Local/remote file inclusion
Helps
WAF rules LFI-001/002 and NULL-001, and the ML model.
5.3.10
XPath/XML injection
Helps
ML model (XXE family).
V7 Logging and error handling
ASVS
Requirement (summary)
Status
How Sentinel meets it
7.1.1
No credentials or payment details in logs
Met
Passwords, tokens and 2FA codes are never logged. Login failures log only the username.
7.1.3
Security events logged (auth success and failure, access control failures)
Met
One access-log line per request, with Sentinel’s decision: attacks, refusals, bans, dashboard logins and dashboard actions.
7.1.4
Enough detail to investigate
Met
Time, request ID, client IP and country, rule, field, reason and matched text.