CyberKit

Cookie Security

Also called HttpOnly, Secure Cookie, SameSite.

Cookie flags that limit theft, leakage, and cross-site sending.

What it is

The set of attributes that harden cookies: HttpOnly blocks script access, Secure restricts them to HTTPS, and SameSite controls whether they ride cross-site requests. Together they constrain how and where a cookie is exposed.

Why it matters

Session cookies are prime theft targets, so these flags blunt XSS-based theft and CSRF; their absence on an authentication cookie is a direct, commonly cited weakness.

In practice

An HttpOnly, Secure, SameSite cookie that injected page script cannot read and that won't be sent cross-site.

What to look for

  • Session cookies missing Secure, HttpOnly or SameSite.
  • Long lived session cookies.
  • Cookies scoped to broad domains.

Common mistake

Setting HttpOnly and assuming the session is safe. Stolen cookies can still be replayed.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Burp Suite Commercial

    An intercepting proxy for testing web apps by hand and with its scanner.

  • ZAP Open source

    An open source web app scanner and proxy, often run in CI pipelines.

  • Cloudflare WAF Commercial

    Blocks common web attacks at the edge while the code gets fixed.

Read next

Sources