CORS Misconfiguration: What Access-Control-Allow-Origin Actually Permits
A CORS header decides which other websites may read your responses with your users' cookies attached. Reflecting the Origin header, matching it with …
Category
Securing applications, APIs, webhooks, secrets and the software supply chain, from code review to CI pipelines.
A CORS header decides which other websites may read your responses with your users' cookies attached. Reflecting the Origin header, matching it with …
Most OAuth implementations follow the happy-path tutorial and skip the parts of the spec that exist specifically to stop token theft. Here's what the …
SameSite cookies reduce cross-site request forgery but do not end it. Here is what each defense stops, where each one fails, and a header check you …
A leaked API key isn't automatically compromised, but you often can't prove it wasn't used. Here's how to find exposure fast and rotate without …
Use Argon2id for new systems, keep bcrypt if you already have it and handle its 72-byte limit, and use PBKDF2 only when FIPS requires it. The harder …
Any feature that fetches a URL on a user's behalf lets that user borrow your server's network position. Here is how SSRF works, why URL filters keep …
Vulnerability backlogs grow faster than teams can patch because most programs measure the wrong thing: total count instead of exploitability and …
Most supply-chain security advice assumes you can afford to review every dependency by hand. Here's a tiered approach that scales with a normal …
Image scanning in CI catches known CVEs in base layers, but most pipelines still ship vulnerable configs and secrets that scanners aren't tuned to …
Secrets scanning tools have gotten good. The breaches keep happening anyway, mostly for three preventable reasons.