secrets

Most candidates start by deleting the commit. The key was copied the minute it went public; the clock starts with revocation.

Static API keys in environment variables are the most common credential leak there is. The answer is platform-issued, short-lived, attested identity.

The app works, the demo is great, and every row in the database is readable from the browser. The scored answer explains the architecture that makes this common and a one-hour review that catches it.

Moving a secret into C changes who can find it in an afternoon, not whether it can be found. The scored answer shows how an analyst would recover it, then replaces the design with one that does not need a shared secret.

The pipeline holds the keys to production and runs code from pull requests. The scored answer separates untrusted from privileged work, pins what it executes, and removes long-lived secrets.

LLM observability quietly becomes the largest copy of customer data in the company. The scored answer minimises what is captured, separates what must be kept, and treats trace stores as production data.

The service receives customers' source code all day. The scored answer protects that code across tenants, keeps secrets out of prompts and logs, and treats suggestions as untrusted output.

Define the compromise scope and secret boundary, map direct and indirect capability paths, and assemble evidence with explicit assumptions. Denial tests and model refusals are useful observations, not universal proofs.