Skip to slide
138 / 221

CH 12 · Secrets and Bring-Your-Own-Key · 01/11

Read as one page

Secrets and Bring-Your-Own-Key

Bring-your-own-key lets users supply their own model API key, encrypted at rest and resolved by precedence over the operator's.

11 slides · 4 min read

Contour map for Secrets and Bring-Your-Own-Key

In this chapter

  1. 01Two kinds of secrets
  2. 02Why bring-your-own-key
  3. 03Storing user secrets: encryption at rest
  4. 04Saving and clearing
  5. 05Resolution precedence: user beats operator
  6. 06Expose status, never secrets
  7. 07Tie model routing to available credentials
  8. 08Signing secrets and other operator credentials
  9. 09Operational hygiene
  10. 10The summary

Agents depend on credentials: model-provider API keys, integration tokens, signing secrets. Some belong to the operator; some belong to individual users who "bring their own key" (BYOK). Mishandling any of them is a serious breach. This chapter covers how to store secrets safely, how to resolve which one to use, and the BYOK pattern.

Finished this idea?

Your learning progress stays in this browser.