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).

Secure Architecture and Design Principles

Designing systems that are secure by construction: defense-in-depth architecture, secure design patterns, fail-safe defaults, security control selection and placement, and reasoning about architectural trade-offs between security, usability, and performance. Covers enterprise-scale security architecture and how security requirements shape system structure. The blueprint layer, distinct from implementing individual controls.

0 questions

Zero Trust, Segmentation, and Service-to-Service Security

Designing network and service-communication trust models where no implicit trust is granted by network location. Covers zero-trust access, microsegmentation and identity-aware perimeters, least-privilege network access, lateral-movement prevention, and segmenting environments to contain blast radius, together with securing service-to-service communication in distributed and microservices architectures: mutual authentication between services, service mesh security, multi-tenancy isolation, east-west traffic, and the security implications of scale and geographic distribution. The architectural trust-boundary pattern and its enforcement across decomposed, high-scale systems, distinct from device-level firewall configuration.

33 questions

Security Fundamentals and Core Concepts

The foundational vocabulary and principles of information security: the CIA triad (confidentiality, integrity, availability) and related properties (authenticity, non-repudiation), defense in depth, least privilege, and the distinction between threats, vulnerabilities, and risk. Establishes the mental model every practitioner reasons from before diving into any specialized domain. Concept-level fundamentals, not tool usage or governance frameworks.

0 questions

Network Security and Defense

Securing networks at the infrastructure layer. Covers firewalls, ACLs and rule design, network device hardening and secure configuration, intrusion detection and prevention systems, VPN and remote-access encryption, network protocols and their security properties, and packet-level traffic analysis. The hands-on network-defense layer, distinct from zero-trust architecture strategy.

100 questions

Vulnerability Assessment and Management

Finding, prioritizing, and remediating vulnerabilities across systems. Covers vulnerability assessment methodologies, scanning and automation, interpreting and validating scan results, vulnerability classification and scoring (CVSS), prioritization based on exploitability and business impact, and driving remediation to closure. The operational vulnerability-lifecycle discipline, distinct from adversarial penetration testing.

0 questions

Penetration Testing Methodology and Execution

Running structured penetration-testing engagements end to end. Covers the pentest lifecycle, reconnaissance and information gathering, network scanning and enumeration (Nmap, service/version detection), tool selection and usage (Metasploit, Burp Suite), engagement scoping and planning, testing across target types, and findings reporting. The methodical offensive-assessment workflow.

0 questions

Threat Modeling and Attack Surface Analysis

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).

4 questions

Incident Response and Containment

Managing security incidents from detection through recovery. Covers incident response process and playbooks, containment and remediation, data-breach investigation methodology, data-exfiltration detection and analysis, root-cause and post-incident analysis, and fraud and complex-attack investigation. The operational 'a compromise is happening, now what' discipline, distinct from broader production-outage incident management.

1 questions

Data Protection and Encryption in Practice

Protecting data at rest and in transit across real systems from an engineering rather than pure-cryptography standpoint. Covers encryption strategy and key management for stored and transmitted data, secrets and sensitive-data handling, tokenization and secure elements for payment and sensitive data, and secure data handling in application code. Applied data-protection controls, distinct from cryptographic primitive design and from privacy-regulation compliance.

0 questions
Page 1/2