InterviewStack.io LogoInterviewStack.io
🔐

Security Engineering & Operations Topics

Operational security practices, secure systems implementation, threat modeling, penetration testing, vulnerability assessment, and security operations at production scale. Covers network security, endpoint security, secure architecture implementation, incident response mechanics, and security automation. Distinct from Security & Compliance (which addresses governance, compliance frameworks, and policy) and from Security Research & Innovation (which addresses novel techniques and research contributions).

Security and Data Privacy

Covers design and operational practices for protecting systems and user data. Candidates should be able to explain authentication and authorization models including token based approaches and role based access control, encryption at rest and encryption in transit, key management and secrets rotation, secure application programming interface design and input validation, audit logging and security monitoring, data governance and privacy controls, compliance with data protection regulations such as General Data Protection Regulation and California Consumer Privacy Act, data minimization and anonymization techniques, threat modeling and vulnerability management, incident response and breach notification procedures, and trade offs between security, performance and developer productivity.

0 questions

Mobile App Security and Authentication

Platform specific security practices for mobile applications and clients. Topics include secure storage of credentials and tokens, protecting secrets on device, certificate pinning and secure transport, secure use of OAuth and token refresh flows on mobile, defending against reverse engineering and tampering, permission models and least privilege for mobile apps, privacy and compliance considerations, secure API usage patterns from mobile clients, and strategies for mitigating mobile specific attack vectors.

33 questions

Software Composition Analysis (SCA) & Supply Chain Security

Understand how to identify and manage third-party dependencies and open-source components. Know tools and techniques for detecting vulnerable dependencies, managing license compliance, and responding to supply chain attacks. Discuss how to evaluate third-party security, conduct security reviews of dependencies, and maintain a software bill of materials (SBOM).

0 questions

Mobile Security Fundamentals

Core mobile security practices for protecting user data and application integrity on devices and in transit. Candidates should explain secure credential storage using platform key stores such as the iOS keychain and the Android keystore, secure transport using hypertext transfer protocol over TLS and certificate pinning, safe storage and encryption for data at rest, secure handling of authentication tokens and refresh logic, input validation and safe deserialization, and principles for avoiding sensitive data leakage in logs or debug output. Include reasoning about third party dependency risk, threat modeling for common mobile attack vectors, tamper detection and obfuscation where appropriate, and operational practices such as key rotation and periodic security testing.

0 questions

Authentication and Authorization

Cover core concepts and implementation trade offs for securing backend services. Candidates should demonstrate understanding of token based authentication and server side session strategies, how to securely issue and rotate credentials, techniques for revocation and refresh, secure storage of secrets, use of third party identity providers, common threat mitigations such as cross site request forgery protection and secure transmission practices, and design patterns for role based and attribute based access control. Interviewers will evaluate the candidate ability to reason about scalability and revocation trade offs and to design secure application programming interface permission checks.

0 questions

Code Obfuscation and Reverse Engineering

Techniques and trade offs for protecting application logic and compiled binaries from reverse engineering and tampering, applicable across native software contexts (mobile apps, desktop applications, embedded and firmware binaries, and licensing or DRM enforced components). Candidates should understand code obfuscation approaches such as symbol stripping, control flow obfuscation, string and resource encryption, native library protection, and binary packing, as well as runtime anti tampering and anti debugging measures. Coverage includes platform specific release and signing practices as concrete illustrations of the general problem: for example Android release tooling, application signing, and ProGuard or R8 style shrinkers, or iOS code signing and hardened runtime configuration, alongside equivalent desktop and embedded code signing and packing practices. Also covers secure handling of embedded client secrets and keys, and approaches for protecting native or compiled modules generally. Evaluate how these protections affect crash reporting and diagnostics, testing strategies to validate protections, and the balance between protection strength, performance overhead, maintainability, and recoverability during incidents.

0 questions

Security Testing Fundamentals

Fundamental practices for identifying and mitigating security vulnerabilities in software. Candidates should understand common failure modes described by the Open Web Application Security Project Top Ten and related risks such as injection attacks including structured query language injection, cross site scripting, broken authentication and authorization, insecure direct object references, and security misconfiguration. Coverage includes secure coding patterns such as input validation, output encoding, parameterized queries, secure session handling, least privilege, and secret management. Testing approaches include manual exploratory security testing, threat modeling, dynamic security scanning, static analysis, dependency and composition analysis, fuzz testing, and targeted penetration testing. Candidates should also be able to explain how to integrate security checks into automated test suites and continuous integration pipelines and how to prioritize security fixes by impact and exploitability.

0 questions

OWASP Top Ten and CWE Top Twenty Five

Comprehensive knowledge of the Open Web Application Security Project Top Ten categories and the Common Weakness Enumeration Top Twenty Five weaknesses, focused on identification, exploitation mechanisms, root causes, business impact, and prevention. Candidates should understand each vulnerability class in depth, including injection, broken authentication and authorization, cross site scripting, cross site request forgery, security misconfiguration, insecure design, vulnerable and outdated components, cryptographic and data integrity failures, logging and monitoring gaps, server side request forgery, and related common weakness patterns. Assessment covers how to find these issues in source code and running applications, how attacks are constructed, secure coding fixes and remediation, threat modeling and secure design choices to prevent them, use of static and dynamic analysis and dependency scanning tools, vulnerability prioritization and patching strategies, and runtime detection and monitoring practices. Candidates should be able to explain concrete code examples, demonstrate fixes, and map specific code patterns to CWE entries when relevant.

0 questions

TLS Protocol Security

Deep understanding of transport layer security protocols and their secure deployment. Topics include TLS handshake mechanics, cipher suite negotiation, certificate validation and management, session resumption and key exchange algorithms, forward secrecy, common vulnerabilities and mitigations such as downgrade and padding oracle attacks, practical configuration for servers and clients, certificate revocation and lifecycle management, and compatibility considerations across protocol versions.

0 questions
Page 1/2