Job Summary

We build Hexnodes XDR endpoint stack - a Windows kernel driver, Windows and macOS agents, and the server and console behind them. The driver and agents already emit a broad telemetry surface: process creation and termination, process access, image load, driver load, thread creation, registry key and value operations, network connections, DNS queries and file activity. We are actively extending the platform with advanced features.

Telemetry on its own catches nothing. This role exists to turn that telemetry into detections that fire on real adversary behaviour, prove they fire, and keep them quiet enough that an analyst trusts them. You will own detection content end to end: write the rule, emulate the technique, verify the telemetry supports it, tune out the false positives, and document what we cover and what we dont.

This is a hands-on engineering role, not an alert-queue role. You will spend your time in a lab with instrumented endpoints, in detection logic, and in the gap between what an attack does and what our sensors see.

Key Responsibilities

- Detection content: Author, tune and maintain detection rules for endpoint threats, and keep coverage mapped to MITRE ATTCK.
- Translate techniques into concrete detection logic against the events our driver and agent emit
- Retire and replace detections that no longer earn their keep.
- Adversary emulation and detection testing: Build benign emulations that reproduce the telemetry signature of a technique without shipping working offensive capability or live C2 into an internal build.
- Telemetry gap analysis: Compare what a detection needs against what the agent and driver emit today, and write up concrete, implementable telemetry requests for the driver and agent teams.
- Contribute to data-model decisions for endpoint events
- Flag where a proposed detection is not implementable with current sensors, early enough to change the plan.




- False positive reduction: Triage alert noise from internal and customer telemetry; assemble false-positive candidates with evidence rather than anecdote.
- Draft exclusion and whitelist filter logic and detection tuning, for review before deployment.
- Help maintain the goodware corpus and prevalence gating that back our release-gate regression runs.
- Research and documentation: Benchmark how competitors implement a given capability and write up the tradeoffs.
- Maintain a living ATTCK coverage matrix - the artifact that answers what do we detect, and how do we know without anyone guessing.

Requirements

- 2-4 years in detection engineering, threat hunting, SOC L2/L3, or endpoint security product engineering.
- Windows internals as they surface in telemetry - processes, threads and handles; services; the registry; scheduled tasks; PE files and Authenticode signing; the Security event log and logon types; common LOLBins.
- Sysmon or equivalent EDR telemetry
- Detection rule tuning - Youd rather say this rule will be noisy, heres its hit rate against our goodware corpus
- MITRE ATTCK fluency - Can go from technique to detection logic to test case without being walked through it.
- Scripting in PowerShell and Python - enough to build own tooling, not just run someone elses.
- Rule authoring, static PE analysis, and similarity hashing - imphash, ssdeep, TLSH.
- Malware triage and unpacking.
- Exposure to Microsofts AV ecosystem - MVI, ELAM, AMSI, ETW Threat Intelligence - or to independent lab testing (AV-Comparatives, AV-TEST).
- macOS endpoint telemetry via the Endpoint Security framework.
- GitLab and Jira in a product engineering workflow.

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.

📌 Detection Engineer/Endpoint Security Engineer (Chennai)
🏢 Hexnode
📍 Chennai