Distributed Systems Security and Trust Questions

Security problems that exist because a system is distributed: keeping trust state correct while it propagates across many services, clusters and regions. Covers credential, token and certificate revocation under eventual consistency and network partitions; fleet-wide rotation of signing keys, secrets and trust anchors without outages (key rollover and grace windows, canary rotation, recovery from a compromised root); distributed authorization (replicated policy decision points, cached decisions, fail-open versus fail-closed when an auth dependency degrades); propagating caller identity and permissions through service call chains; tamper-evident audit trails across services and regions (hash chains, Merkle proofs, ordering events with imperfect clocks); Byzantine and partially trusted participants; cross-cluster and cross-organization trust federation; securing shared distributed components such as caches and message brokers against injection, replay and cross-tenant access; protecting data in transit across region boundaries; and tenant isolation as a security blast-radius boundary. Steady-state mTLS, service-mesh identity and network segmentation mechanics are covered by zero-trust service-to-service security; single-system cryptography and KMS basics by applied cryptography.

EasyTechnical
46 practiced

Why are tamper-evident and append-only audit logs important for a distributed system? As an SRE, describe how you would design audit logging across services and regions so logs can't be silently altered or deleted, how you'd keep events correctly ordered per entity, and what operational controls you would put in place to preserve logs during an incident.

HardSystem Design
33 practiced

Design authentication and authorization propagation across hundreds of microservices. Discuss token formats (JWT vs opaque tokens), token exchange patterns for internal services, token refresh and revocation strategies, minimization of token bloat in headers, and patterns for enforcing fine-grained permissions in downstream services (authorization middleware, PDP/PAP, or policy-as-a-service).

HardSystem Design
37 practiced

Your organization runs across 4 Kubernetes clusters, 3 cloud providers, and several third-party SaaS integrations, and needs a zero-trust architecture spanning all of them. Requirements: per-service identity, cross-org trust federation, least-privilege access, full auditability, and the ability to revoke cross-org access within 30 seconds. Describe your trust model (federated vs centralized CA), certificate issuance and attestation flows, policy enforcement points, and the SRE operational model for rotation, emergency revocation, and audits.

HardSystem Design
36 practiced

You need to build a tamper-evident, globally-consistent audit trail for security events that supports efficient range proofs and legal requests. Requirements: per-region append-only chains, a way to verifiably merge them across regions with proofs, efficient queries for time ranges and per-entity history, and operational tooling for SREs to generate proofs for auditors. Walk through the data structures and storage backends you would use, your indexing strategy, and how you'd manage retention and proof generation.

MediumSystem Design
45 practiced

Design a multi-region TLS termination strategy for a global API gateway with three goals: low latency for users, compliance with region-specific key residency rules, and the ability to provide end-to-end encryption when required. Describe where to terminate TLS (edge vs origin), your key management approach, and the SRE operational model for certificate issuance, rotation, and emergency key compromise.

Unlock Full Question Bank

Get access to all 12 Distributed Systems Security and Trust interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.