Security Engineer

Job Description Security Engineer

Location: Gurugram, Haryana
Experience: 2–5 Years
Employment Type: Full-Time
Department: Cybersecurity

About the Role

The role involves creating and validating IDPS signatures, Application Control rules, and DLP rules that protect customers against network attacks, malicious applications, data leakage, and emerging security threats.

You will work hands-on in a security lab, analyze real-world attack traffic, research vulnerabilities and applications, and ensure that security rules are accurate, effective, and production-ready

What you'll do

Write security rules

• IDPS signatures — detections for exploits, malware, command-and-control traffic and network attacks, with the right severity, action (alert / block / reject) and protocol scope.
• Application control rules — rules that identify and control applications on the network: social media, streaming, file sharing, remote access, unsanctioned SaaS and AI tools.
• DLP rules — rules that detect sensitive data leaving the network: personal and financial data, confidential documents, source code, across web, email and file transfer channels.

Test and validate — the bigger half of the job

• Set up test scenarios in our security lab and generate the traffic yourself using browsers, command-line tools, packet captures and safe proof-of-concept exploits.
• Confirm each rule actually triggers, and that the resulting log shows the correct rule, severity, action and source.
• Hunt for false positives against normal, everyday traffic before a rule is allowed to ship — a rule that blocks a legitimate banking site is worse than one that misses an attack.
• Build and maintain a repeatable test set so rules keep working after product updates.

Research and document

• Track newly disclosed vulnerabilities (CVEs), exploit techniques and emerging applications, and turn them into working detections.
• Study widely used public rulesets to learn coverage patterns and identify where we have gaps.
• Write a short validation note for each batch: what it detects, how it was tested, and what it doesn't cover.