CSE Roadmap

Core tier · about 9 hours · 17 parts

Part 12 of 17 · 1 min read

How to build it so it holds up

  1. Say which transport and whether authorization applies, because stdio takes credentials from the environment, not OAuth.
  2. Validate every token five ways, because any one skipped check is a specific, exploitable hole, not a general weakening.
  3. Never pass a client's token to an upstream API, because that is exactly what token passthrough and the confused deputy attack both exploit.
  4. Challenge with the minimum scope and step up on demand, because a broad first challenge multiplies a stolen token's blast radius for no benefit to the honest case.
  5. Take the caller from the verified token, never from an argument, because an argument is something the model (or an attacker's text) can set.
  6. Guard every URL a stranger named, because SSRF and DNS rebinding both rely on your own client fetching from your own network position.
  7. Tie approval to data flow, not to wording, because a content-based control has a blind spot a paraphrase will eventually find.