Senior Quiz: Operations and Architecture¶

Key response spans issuers, verifiers, caches, sessions, and long-lived connections. Routine overlap may be inappropriate during confirmed compromise.

Availability requirements do not silently authorize unverifiable credentials. Cache lifetime, revocation exposure, criticality, and user impact must be explicit.

Attacker-controlled or near-unique labels can exhaust the monitoring system and leak sensitive data. Put bounded classifications in metrics and detailed identifiers only in protected, redacted logs when necessary.

Separate untrusted validation from trusted release jobs. Use short-lived workload identity, environment protections, minimal permissions, and provenance for publishing.

Combine an SBOM with dependency verification, scanning, provenance, patch processes, and risk decisions.

Rate-limiter failures are denial-of-service risks. Security-sensitive paths should fail closed; public or non-sensitive paths may be allowed to fail open if that is an explicit, reviewed policy.

External authorization creates a runtime dependency. Critical operations need explicit failure, caching, audit, and recovery semantics.

Credentials and assertions in logs create a secondary credential store. Diagnose validation stages without retaining reusable secrets or excessive identity attributes.

Server-side fetching creates SSRF risk. Browser CORS does not constrain server egress or metadata/internal-service access.