SkillVaultskills Browse all 500 skills

Security · Version 1.5.0 · Reviewed 2026-08-02

CSRF & CORS Configuration Reviewer

Find and prioritize exploitable risk in origin policy and CSRF defense with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Reviews cross-origin policy and CSRF defenses for correctness rather than permissiveness.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Origin policy
  • CSRF defense
  • Credentialed request handling

How CSRF & CORS Configuration Reviewer works

You provide

Code, configuration, and the deployment trust model

It inspects

Reachable input-to-sink paths for origin policy

It decides

A CSRF defense finding ranked by blast radius

You verify

Re-attempt the exploit path after remediation

What it checks first

CSRF & CORS Configuration Reviewer reviews cross-origin policy and CSRF defenses for correctness rather than permissiveness. Use it when the work involves Origin policy, CSRF defense, Credentialed request handling.

  1. Trust boundaries and every point where untrusted input crosses one.
  2. Where authorization is enforced relative to where data is accessed.
  3. Secret handling: creation, storage, transmission, rotation, and revocation.
  4. What an attacker gains at each step, which determines whether a finding is material.

Failure modes it recognizes

  • Authorization enforced at the perimeter while internal callers reach the same data unchecked.
  • A single unparameterized query path among many parameterized ones.
  • Sensitive values written to logs or error responses.
  • A dependency vulnerability that is reachable in one code path and unreachable in the rest.

Answers it will reject

  • Reporting theoretical findings as exploitable without a demonstrated path.
  • Blocking a payload signature instead of removing the vulnerability class.
  • Treating obscurity as a control, which delays discovery without preventing exploitation.

Decision rules it applies

  • Prioritize by reachability and blast radius, not by scanner severity.
  • Fail closed on any ambiguity in an access decision.
  • Prefer eliminating the capability over sanitizing input into it.

Evidence it asks for

  • Trace input to sink and name every file and function on the path.
  • Verify the fix by attempting the original exploit path.
  • Check logs for prior exploitation before closing a finding.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to origin policy.
  2. Trace concrete failure or abuse paths for CSRF defense; do not report checklist items without a mechanism.
  3. Prioritize credentialed request handling findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Origin policy assessment
  • CSRF defense decision and action plan
  • Credentialed request handling verification checklist

Evidence requirements

  • Code, configuration, data flows, and trust boundaries
  • Identity, authorization, and deployment context
  • Threat model, controls, and known assumptions

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We set our CORS policy to reflect the request origin with credentials allowed because it fixed a bug.

Expected output

Reflecting the origin with credentials effectively disables the same-origin policy for every site, which is a serious vulnerability rather than a configuration choice. Use an explicit allowlist, and pair it with SameSite cookies and a CSRF token for state-changing requests...

Boundaries and compatibility

Ideal for

  • Origin policy: produce a decision or artifact grounded in supplied evidence.
  • CSRF defense: produce a decision or artifact grounded in supplied evidence.
  • Credentialed request handling: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Authorizing offensive actions against systems without permission
  • Reporting theoretical issues as exploitable without a path

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.