Security Monitoring, SIEM, and Detection Engineering Questions

Building and operating the detection stack: the SOC and detection-engineering practice that answers 'can we see an attack happening.' Covers SIEM platform selection and architecture, use-case and detection-rule query development (for example Splunk SPL, KQL, or Sigma), alert triage and tuning to reduce false positives, detection engineering and closing coverage gaps, mapping detections to the MITRE ATT&CK framework and scoring detection coverage, log analysis and anomaly and baseline development, network and endpoint telemetry sourcing, malware and compromise-indicator recognition, and security operations center (SOC) alert escalation workflows. Distinct from the reactive work of containing, remediating, and communicating during a confirmed incident (incident response and postmortem topics own that ground; this topic stops at 'the alert fired and here is the detection logic', not 'here is how we contained and recovered from it'). Distinct from generic system-reliability monitoring and observability (SLOs, error budgets, uptime dashboards), a separate discipline even when the underlying ingestion mechanics look similar; the anomaly or signal here must be framed as adversarial or security-relevant. Distinct from hardening a software delivery pipeline against supply-chain compromise (SBOM generation, artifact signing, dependency and build-permission controls); this topic only touches the delivery pipeline from the detection side, spotting a compromised build or tainted artifact via telemetry, not the preventive-controls side. Distinct from designing security control architecture and governance (security architecture and cloud security architecture topics own the design-time question of what controls should exist); this topic is the run-time operation of the detection stack once those controls are in place.

MediumTechnical
72 practiced

Write a Sigma rule (YAML-style) that detects suspicious usage of certutil or powershell when invoked with command-line patterns indicating encoding or decoding of content (for example '-EncodedCommand' or 'certutil -decode'). Target Windows ProcessCreate events and include reasonable fields (process_name, command_line, parent_process). Keep the rule generic and explain rationale for key fields.

MediumTechnical
75 practiced

In Python 3.x write a defensive script that reads a CSV export of Windows Security events (columns: Timestamp, EventID, Account, SourceIP, LogonType). Implement logic to flag SourceIP addresses that have 5 or more failed logon attempts (EventID 4625) followed by a successful logon (EventID 4624) from the same IP within 10 minutes. Output flagged records as JSON.

EasyTechnical
125 practiced

Explain how encrypted network channels (TLS/HTTPS/SSH) impact detection of C2 and exfiltration. Describe three metadata-based signals (for example JA3/TLS fingerprinting, SNI anomalies, session timing and volume patterns) that can help detect encrypted malicious communication without decrypting payloads, and discuss limitations.

HardTechnical
108 practiced

With very limited endpoint telemetry (process creation events and summarized netflow only), propose statistical heuristics and feature engineering to detect abuse of LOLBins. Suggest concrete features (for example: process-parent novelty score, command-line entropy proxy, atypical destination score, time-of-day deviation) and describe how you would combine them into a scoring model or anomaly detector.

MediumTechnical
90 practiced

Write a YARA rule suitable for scanning a webroot to detect simple PHP web shells that often include both the functions 'base64_decode' and 'eval', while minimizing false positives against legitimate code that uses one of those functions innocuously. Explain your rationale briefly in comments in the rule.

Unlock Full Question Bank

Get access to all 12 Security Monitoring, SIEM, and Detection Engineering interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.