NGWAF: From Static Rules to Behavioral, API-Aware Protection

From Static Rules to Behavioral, API‑Aware Protection

NGWAFs have been the go‑to shield against the OWASP Top‑10 for years. Back in 2025, most of us were still clinging to static signatures—regexes, hard‑coded SQL‑injection patterns, and a handful of known payloads. Those rules hold up for monolithic sites, but when you start juggling dozens of micro‑services that talk over HTTP/HTTPS, they become a maintenance nightmare and a weak point in the chain.

[Read More]

Using Attack Trees to Prioritize API Endpoint Protection in Microservices

Attack Trees for API Endpoint Prioritization in Microservices

Microservices can expose dozens, sometimes hundreds, of REST or gRPC endpoints. Each one is a potential attack vector. When the budget and bandwidth are tight, you need a systematic way to decide which endpoints deserve the most defensive effort. Attack trees give you a structured, risk‑based view that maps attacker goals to concrete API actions and lets you quantify effort versus impact.

[Read More]

Fixing Session Fixation in a Remember Me Cookie

Rotating session IDs in an e-commerce API

The scenario

Our e‑commerce API was built on a stateless REST layer that delegated authentication to a central identity service. The API accepted a short‑lived bearer token (JWT) and, for convenience, exposed a “Remember Me” feature that let users stay logged in across browser restarts. The implementation was simple: the client stored a cookie named REMEMBER_ME that contained a signed, encrypted token. When the browser sent the cookie back, the API would issue a new JWT and refresh the cookie.

[Read More]

Prioritizing API Rate Limits with Attack Trees

Choosing controls after a DDoS incident

Attack‑Tree‑Driven Rate‑Limiting After a DDoS

We just survived a 2026 DDoS that hammered our public REST gateway. A botnet slammed a handful of endpoints with insane request rates, chewing through CPU and memory until real users hit time‑outs. The fallout was a frantic review of our throttling logic. Attack trees turned out to be the perfect tool to decide which endpoints need the tightest controls and how to enforce them without turning our API into a brick wall.

[Read More]

Is the WAF Obsolete?

No. But the version of the WAF most organizations are running — a signature-matching appliance at the perimeter — is being bypassed in real time by actors who no longer need to be creative. They need to be persistent, and they need an API key.

This post looks at what “obsolete” actually means in 2026, using four specific incidents from the last five months and one academic paper that quantifies the problem.

[Read More]