Security Tools

Review session controls, token policy, API key age, and integration scope exposure with practical security workflows for engineering teams.

API Key Rotation Planner

Prioritize rotation windows based on age, production exposure, and stale-usage risk before old credentials become incident drivers.

Plan rotation

Session Cookie Auditor

Score cookie flags like Secure, HttpOnly, SameSite, and lifetime controls to catch avoidable session weaknesses.

Audit cookies

CSRF Token Policy Checker

Evaluate SameSite mode, token rotation, origin checks, and SPA controls in one quick review.

Check policy

Secret Scope Matrix Builder

Map integration scopes and find broad permissions that should be replaced with least-privilege alternatives.

Build matrix

Supporting security guides

Security Posture Workflow

Follow a phased hardening order for headers, sessions, CSP, and integrity controls.

Open workflow

Security Audit Checklist

Use a release-ready checklist for periodic or pre-launch security reviews.

Open checklist

CSP vs SRI vs Security Headers

Compare where each control fits so teams choose the right browser-side protection.

Open comparison

Use this cluster as a security hygiene workflow

This cluster is built for operational review loops: start with exposed credentials, verify session controls, confirm CSRF defenses, then tighten integration scope definitions before the next audit cycle.

Signals worth reviewing first

  • Production keys older than your internal rotation target or incident response standard.
  • Session cookies missing Secure, HttpOnly, SameSite, or explicit lifetime controls.
  • CSRF defenses that rely on a single mechanism instead of layered browser and server checks.
  • Integrations carrying broad admin scopes or more permissions than the job actually needs.

Suggested order

  1. Start with the API Key Rotation Planner.
  2. Continue with the Session Cookie Auditor.
  3. Check browser and form defenses with the CSRF Token Policy Checker.
  4. Finish by tightening integration permissions in the Secret Scope Matrix Builder.

Why this cluster matters

These are the kinds of controls that drift quietly until an audit, outage, or incident surfaces them. A quick structured review keeps that drift visible.

  • Reduce credential exposure before forced emergency rotations.
  • Catch session weaknesses that widen account takeover risk.
  • Move integrations toward least privilege instead of inherited convenience scopes.
Browse Tools

Tool Navigation

629+ tools across 43 categories