Services
alg=none, HS/RS key confusion,
weak secrets, broken RBAC — and the bug pattern-matching scanners miss:
IDOR/BOLA, where an authenticated user reaches
another user’s data. I review your authentication and authorization surface,
hand you a report with proof-of-concept and remediation, and re-test it after you patch.
Fixed price, fixed timeline.
One flow, fast read
A single auth flow or endpoint checked against the five JWT classes, claim hygiene, and the most likely IDOR on that route. Proof of value, fast.
Authentication + authorization
The full surface: JWT, sessions, RBAC and OAuth/OIDC config — plus an IDOR/BOLA pass over your Next.js route handlers and Server Actions, where one user reaches another user’s data.
I find it and I patch it
Everything in the Auth & Access Review, then I implement the hardening myself and hand you a reviewed pull request ready to merge.
Prices in USD, paid via PayPal. Remote, worldwide. Engagements run under a written scope and authorization — I only test systems you own or are authorized to test.
How it works
A 15-minute call (or async) to confirm the surface. Fixed price, fixed timeline — no hourly meter, no scope creep.
My own tooling plus manual review: jwt-scan over your tokens, authzscan over your route handlers, and a human read of the auth and access-control logic.
A clear report with severities, proof-of-concept and remediation (Markdown + SARIF for code scanning). One free re-test after you patch so you know it is closed.
Why me
I don't just run a scanner — I wrote two. authzscan reasons about IDOR/BOLA in Next.js code the way pattern-matching SAST can't, and is measured against a seeded benchmark with recall and precision gates. The detection logic comes from reproducing the bugs from scratch. The same rigor goes into your review.
Tell me about your app and I'll reply within a day. Want a free read? Pick Free health check below and send me a token or a public repo. Ready to go? Use the PayPal buttons above to book instantly.