Detection Engineer
You build and tune the rules that turn raw logs into alerts worth waking up for.
Competency areas
- Defensive Cybersecurity
- Threat Analysis
- Vulnerability Analysis
Aramis:Current Daily
A short reading list for a Detection Engineer, under 30 minutes per edition.
2026-09-30. 7 minutes in total
French Tax Data Theft Using Stolen Staff Passwords Went Undetected for Seven Weeks
The Hacker News, 2026-09-29. Read, 7 min.
Why it matters for this role: Correlate night logins, VPN or known-bad source addresses, and per-user request counts on business applications, because ANSSI says those signals together could have raised an alert that none raised alone.
Sample questions
Three real questions from this role's assessment, with the answer, the reasoning, and the NICE statement each one measures. The full assessment draws from hundreds like these.
Sample question 1
At Solvent Bank, detection engineer Marcus reviews four deviations that the network anomaly detection pipeline flagged this week for the transaction-processing segment: a database server that began beaconing to a single unrecognized external IP address every 58 seconds three nights ago; a marketing workstation that generated a brief spike in outbound HTTP traffic during a product launch livestream; a backup server pushing its usual large monthly transfer to the offsite replication target on the scheduled date; and a developer laptop resolving DNS lookups for a SaaS tool that IT approved last week. Marcus has time to escalate only one item today. Which one should he treat as anomalous network activity warranting immediate investigation?
- A.The marketing workstation's HTTP spike during the livestream, since any sudden jump in outbound traffic volume from a single host is the strongest signal of compromise the pipeline can surface.
- B.The backup server's monthly transfer to the replication target, since large recurring transfers to an external-facing destination carry more risk than a low-volume connection and deserve priority review.
- C.The developer laptop's lookups for the newly approved SaaS tool, since a domain the environment has not seen before is the clearest indicator that the pipeline has identified something worth escalating.
- D.The database server's regularly-timed beaconing to an unattributed external address, since nothing about its established role or history explains a new, persistent connection to an unapproved destination that appeared this week.
Show the answer and reasoning
Correct answer: D
The database server's beaconing is the only observation that breaks from the asset's established behavioral baseline: a system with no history of initiating outbound sessions has started a new, regularly-timed connection to a destination nobody has attributed to a vendor, partner, or business process, which is what makes an observation genuinely anomalous rather than merely unusual. The marketing workstation's traffic spike is explained by a known, scheduled business event, so volume alone does not make it suspicious. The backup server's transfer matches its documented monthly schedule and destination, so it is expected activity rather than a deviation from baseline. The developer laptop's DNS activity involves a domain IT already approved, so its novelty to the environment does not indicate a security-relevant anomaly.
This question measures: T1084: Identify anomalous network activity
Sample question 2
A detection engineer at a logistics company is triaging four alerts that fired within the same 20-minute window. Alert 1: an email gateway alert that a user received a phishing message with a malicious macro attachment, which the user deleted without opening. Alert 2: an EDR alert, opened two days ago and still unresolved, for a suspicious PowerShell process spawned by Word on a different and unrelated user's machine. Alert 3: a network alert for an endpoint that has been beaconing to a previously unseen external domain every 60 seconds since that morning. Alert 4: an EDR alert, timestamped four minutes ago, that a roughly 2 GB compressed archive was just created in a temp folder on that same beaconing endpoint, coinciding with a spike in outbound traffic to that external domain. Given limited immediate response capacity, which alert should the engineer act on first?
- A.Alert 1, because phishing delivery is the earliest point in the attack chain, and industry guidance generally treats interrupting an intrusion at the earliest available stage as the highest-value response before committing resources elsewhere.
- B.Alert 4, because the archive creation and outbound spike on the beaconing host indicate the attacker has reached the actions-on-objectives stage and data may be leaving the network right now.
- C.Alert 2, because a suspicious PowerShell process spawned from Word indicates initial exploitation, which analysts should generally treat as a higher priority than a network-layer beaconing alert alone.
- D.Alert 3, because a new beaconing pattern represents the command-and-control stage, and stopping a live command-and-control channel is typically the response an analyst should prioritize ahead of other concurrent alerts.
Show the answer and reasoning
Correct answer: B
Only alert 4 places the attacker in the actions-on-objectives stage: a multi-gigabyte archive appearing in a temp folder together with an outbound traffic spike to the same domain the host is already beaconing to is the signature of data staging and exfiltration in progress, the last and most damaging stage of the attack, and it is happening right now. Alert 1 sits at the earliest stage, delivery, but the message was deleted before it was opened, so that particular chain is already closed off; treating a neutralized delivery attempt as the top priority on the theory that earliest-stage interruption is generally the highest-value response ignores that a different, active chain has already progressed to exfiltration. Alert 2 is two days old and concerns an unrelated host; the option's framing, that exploitation-stage evidence should generally be treated as higher priority than a network alert, ignores exactly the kind of recency and relevance context a detection engineer must weigh, since stale evidence on a different machine does not outrank an active exfiltration in progress elsewhere. Alert 3 is a genuine and serious command-and-control indicator that would normally warrant fast action, but it is on the very same host already producing alert 4, meaning the attacker there has already moved past the command-and-control stage; treating that channel as the priority on the general principle that a live command-and-control channel typically outranks other concurrent alerts overlooks that this is the same intrusion already at a later, more damaging stage, so containing the channel is necessary but is subsumed by the more urgent response to the active exfiltration alert 4 represents.
This question measures: K0844: Knowledge of cyber attack stages
Sample question 3
A detection engineer at a regional bank is investigating a suspected account takeover. Identity provider logs confirm the user completed multi-factor authentication successfully from a company laptop in Ohio at 9:02 AM. Two minutes later, the resource server accepts an API request carrying that session's OAuth access token, but the request originates from an IP address in Vietnam with a device fingerprint that does not match the laptop, and the IdP logs show no new sign-in at that time. Which detection rule is best suited to catching this specific technique?
- A.Flag any account with more than five failed MFA attempts inside one minute, because that pattern usually signals brute-force credential guessing rather than a stolen live session.
- B.Flag any account that submits two password-reset requests inside a rolling 24-hour window, because repeated resets often follow a successful credential-stuffing campaign.
- C.Flag access-token use from a device or network context inconsistent with the session that issued it, because that mismatch signals a stolen token being replayed without re-authenticating.
- D.Flag sign-ins that occur from two geographically distant locations within a time window shorter than travel would allow, because that impossible-travel pattern indicates a shared or stolen credential.
Show the answer and reasoning
Correct answer: C
The IdP logs show authentication itself succeeded (valid MFA from a known device), so brute-force detection on failed MFA attempts would never fire here and is not the relevant control for this technique. The real anomaly sits in how the resulting token is used afterward: the same OAuth access token is replayed two minutes later from a mismatched device and network with no corresponding new authentication event, which is the signature of session or token theft. A rule that correlates token use against the device and network context of the session that issued it catches exactly that pattern. Password-reset frequency detects a different technique, credential-stuffing follow-up, and would not fire here since no reset occurred. Impossible-travel detection is a real and useful control, but it operates on sign-in events reported by the identity provider, comparing the locations and timestamps of two authentications to see if both could plausibly belong to the same user. It is built to catch a shared or stolen credential being used to log in from two places at once. This scenario has only one authentication event, the legitimate Ohio sign-in; the Vietnam-based activity never re-authenticates, it simply replays the access token issued to that session. Because impossible-travel logic needs a second login event to compare against, it would not trigger on this technique at all, making it a plausible but non-functional choice here.
This question measures: K0686: Knowledge of authentication and authorization tools and techniques
Job description templates
Three ready-to-edit drafts for hiring managers and recruiters: copy one, replace the bracketed lines, and post it. Responsibilities and requirements are drawn from the same NICE statements this role is measured against.
Statements use the official NICE Framework wording, which is published in English.
Detection Engineer: Junior
We are hiring a junior Detection Engineer. You build and tune the rules that turn raw logs into alerts worth waking up for. At this level you take on well-defined parts of the work, with senior colleagues to learn from, and grow into the rest.
[Company] provides [what you do]. The security function is [size and shape: e.g., a five-person team reporting to the CTO]. Replace this paragraph with your own.
Responsibilities
- Identify anomalous network activity
- Evaluate threat decision-making processes
- Generate requests for information
- Identify cyber threat tactics and methodologies
- Review cyber defense service provider reporting structure
- Determine how threat activity groups employ encryption to support their operations
- Scope analysis reports to various audiences that accounts for data sharing classification restrictions
- Develop cybersecurity risk profiles
- Pair with senior colleagues and grow through structured feedback.
- Document what you do so the team learns with you.
Required knowledge
- Cyber attack stages
- Authentication and authorization tools and techniques
- Intrusion detection tools and techniques
- Fault Detection and Diagnostics (FDD) tools and techniques
- Virtual machine detection tools and techniques
- Intrusion Detection System (IDS) tools and techniques
- Programming language structures and logic
- Malware
Skills
- Performing threat modeling
- Interfacing with customers
- Performing packet-level analysis
- Conducting non-attributable research
- Communicating complex concepts
How to use this template
Copy the draft, replace every bracketed line, cut statements that do not apply to your opening, and add your compensation range and location policy. The statement lists come from the NIST NICE Framework v2.2.0, so candidates can be assessed against the same statements with Aramis:Insight.
Detection Engineer: Mid-level
We are hiring a mid-level Detection Engineer. You build and tune the rules that turn raw logs into alerts worth waking up for. You own this work day to day and work closely with the rest of the security team.
[Company] provides [what you do]. The security function is [size and shape: e.g., a five-person team reporting to the CTO]. Replace this paragraph with your own.
Responsibilities
- Identify anomalous network activity
- Evaluate threat decision-making processes
- Generate requests for information
- Identify cyber threat tactics and methodologies
- Review cyber defense service provider reporting structure
- Determine how threat activity groups employ encryption to support their operations
- Scope analysis reports to various audiences that accounts for data sharing classification restrictions
- Develop cybersecurity risk profiles
- Validate network alerts
- Determine if cybersecurity-enabled products reduce identified risk to acceptable levels
- Determine if security control technologies reduce identified risk to acceptable levels
- Determine the effectiveness of an observed attack
Required knowledge
- Cyber attack stages
- Authentication and authorization tools and techniques
- Intrusion detection tools and techniques
- Fault Detection and Diagnostics (FDD) tools and techniques
- Virtual machine detection tools and techniques
- Intrusion Detection System (IDS) tools and techniques
- Programming language structures and logic
- Malware
- Intelligence fusion
- Cognitive biases
- Computer networking protocols
- Risk management processes
Skills
- Performing threat modeling
- Interfacing with customers
- Performing packet-level analysis
- Conducting non-attributable research
- Communicating complex concepts
- Collaborating with others
- Creating analytics
- Extrapolating from incomplete data sets
How to use this template
Copy the draft, replace every bracketed line, cut statements that do not apply to your opening, and add your compensation range and location policy. The statement lists come from the NIST NICE Framework v2.2.0, so candidates can be assessed against the same statements with Aramis:Insight.
Detection Engineer: Senior
We are hiring a senior Detection Engineer. You build and tune the rules that turn raw logs into alerts worth waking up for. You set the direction for this work, mentor the people who do it, and answer for its results.
[Company] provides [what you do]. The security function is [size and shape: e.g., a five-person team reporting to the CTO]. Replace this paragraph with your own.
Responsibilities
- Identify anomalous network activity
- Evaluate threat decision-making processes
- Generate requests for information
- Identify cyber threat tactics and methodologies
- Review cyber defense service provider reporting structure
- Determine how threat activity groups employ encryption to support their operations
- Scope analysis reports to various audiences that accounts for data sharing classification restrictions
- Develop cybersecurity risk profiles
- Validate network alerts
- Determine if cybersecurity-enabled products reduce identified risk to acceptable levels
- Determine if security control technologies reduce identified risk to acceptable levels
- Determine the effectiveness of an observed attack
- Determine causes of network alerts
- Perform required reviews
- Detect cybersecurity attacks and intrusions
- Distinguish between benign and potentially malicious cybersecurity attacks and intrusions
- Mentor junior team members and review their work.
- Represent this function to leadership and to auditors or clients.
- Set standards, select tooling, and own the roadmap for this area.
Required knowledge
- Cyber attack stages
- Authentication and authorization tools and techniques
- Intrusion detection tools and techniques
- Fault Detection and Diagnostics (FDD) tools and techniques
- Virtual machine detection tools and techniques
- Intrusion Detection System (IDS) tools and techniques
- Programming language structures and logic
- Malware
- Intelligence fusion
- Cognitive biases
- Computer networking protocols
- Risk management processes
- Cybersecurity laws and regulations
- Cybersecurity policies and procedures
Skills
- Performing threat modeling
- Interfacing with customers
- Performing packet-level analysis
- Conducting non-attributable research
- Communicating complex concepts
- Collaborating with others
- Creating analytics
- Extrapolating from incomplete data sets
- Analyzing large data sets
- Creating target intelligence products
How to use this template
Copy the draft, replace every bracketed line, cut statements that do not apply to your opening, and add your compensation range and location policy. The statement lists come from the NIST NICE Framework v2.2.0, so candidates can be assessed against the same statements with Aramis:Insight.
Related roles
Roles with similar work or at a similar career stage. Each has its own job description templates and a free assessment.