Threat Modeling and Attack Surface Analysis Questions

Systematically identifying how a system can be attacked and where its exposure lies. Covers structured methodologies (STRIDE, PASTA, DREAD, OCTAVE, attack trees), enumerating and reducing attack surface, mapping trust boundaries and data flows via DFDs, profiling likely threat actors, and prioritizing identified threats by likelihood and impact during design. Includes applying this methodology to specific architectural substrates (cloud-native and serverless, microservices, ML/AI systems, IoT, CI/CD pipelines, cryptographic subsystems) and operationalizing it as a recurring program (SDLC integration, governance, tooling, KPIs). The proactive 'think like an attacker before you build' discipline: distinct from live penetration testing (the adversarial validation of a built system), from runtime detection/monitoring (recognizing an attack already in progress), and from implementing the resulting security controls (a separate design-and-build discipline).

HardSystem Design
40 practiced

Design an enterprise-scale threat modeling program for a multinational organization. Describe program governance (centralized vs federated), roles and responsibilities, toolchain (including automation and the types of tools), workflows for onboarding new systems, integration points with SDLC and vulnerability management, and measurable success metrics you would track.

HardTechnical
36 practiced

Create a security and privacy threat model for enabling corporate invoicing and expense features inside a B2B workplace-collaboration platform. Identify critical assets, threat vectors (data leakage, fraud), and propose architectural controls and processes to mitigate the top 5 risks.

HardTechnical
34 practiced

Threat-model a multi-tenant SaaS platform that uses federated single sign-on (SAML/OIDC), tenant-scoped data isolation, and supports tenant-level custom integrations (webhooks). Identify risks such as token audience confusion, tenant ID misrouting, SSRF via integrations, and tenant admin compromise. Propose specific mitigations, detection signals, and testing approaches for cross-tenant isolation.

MediumTechnical
43 practiced

Scenario: You're threat-modeling a REST API that uses OAuth2 authorization code flow with refresh tokens. Identify key threats specific to token handling, list potential attack paths (token theft, CSRF, redirect-uri manipulation, refresh-token misuse), and recommend mitigations and detection strategies for each threat.

EasyTechnical
33 practiced

Explain the STRIDE threat modeling categories (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege). For each category, provide a concise example vulnerability or attack path in the context of a web-based e-commerce application (authentication, payments, product catalog) and explain why it maps to that STRIDE category.

Unlock Full Question Bank

Get access to all Threat Modeling and Attack Surface Analysis interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.