Niagara Region, Ontario

Akash Raj

Security Analyst II, Cyber Defense Purple teaming | Threat hunting | Adversary emulation | Detection engineering

Hi, I'm Akash. I'm a security analyst in the Niagara Region of Ontario, and I work across cyber defence: purple teaming, threat hunting, adversary emulation, and detection engineering.

The work I keep coming back to sits on the seam between offence and defence. I would rather run the attack myself, watch what the detections do about it, and fix the ones that stayed quiet than wait for a real adversary to find out for me.

Resume (PDF) | LinkedIn |

attack in, detection out
$ whoami
akash raj | security analyst ii, cyber defense
$ cat focus.txt
purple teaming | threat hunting | adversary emulation | detection engineering
$ cat purple.txt
emulate the attack, measure the detection, close the gap
$ cat stack.txt
moved: the full breakdown is under "What I work with"
$ 
  • Adversary emulation Monthly breach and attack simulation, plus retesting penetration test findings
  • Threat hunting Hypothesis-driven hunting across endpoint and network
  • Detection engineering Detection rules tuned down to the ones worth waking someone up for
  • Incident response Tier III escalation from detection through containment and review
4 yrs
in cyber defence
150+
penetration test findings retested
+25%
more control gaps surfaced
-30%
false positive alert volume

Threat radar

Live from open feeds. Each dot is a threat recorded in the last few days, drawn where it happened and at its true bearing and distance from you. Nothing here is fetched by your browser.

Threat radar: threats plotted by bearing and distance from your location
Reading the feeds…

Newly exploited

    Newest malicious URLs

      Loading sources…


      About

      I came to security sideways. I was building websites, kept finding the bugs more interesting than the features, and worked my way onto a security team.

      Now I'm the Tier III escalation point on Intact's Cyber Defense team. When an alert is ambiguous enough that nobody wants to call it, it lands with me.

      I like the unglamorous work: quiet a rule that fires all day, then attack it. Playbooks I like least, which is why I've written twelve. At 3 a.m. nobody remembers who to call.

      How I got here
      1. now Tier III escalation
      2. 2022 First security team
      3. 2019 Conestoga College
      4. 2012 B.Tech, Computer Science
      5. before IT support

      What I work with

      Purple team and adversary emulation

      • Run the attack myself, then watch what the detections did about it
      • Test coverage against real technique rather than assumed coverage
      • Retest every finding instead of trusting the remediation ticket

      Threat hunting and detection engineering

      • Start from a hypothesis, not from whatever the queue happens to hold
      • Tune rules down to the ones worth waking somebody up for
      • Enrich and triage what the rules surface, so the next hunt starts warmer

      Incident response and investigation

      • Take the Tier III escalations nobody else wants to call
      • Contain first, then work back to the root cause
      • Write it up so it does not arrive the same way twice

      Vulnerability management

      • Prioritise by what is actually being exploited, not by score alone
      • Get patching to the point where it mostly runs itself
      • Reassess inside a day when a public disclosure lands

      Identity and access management

      • Review privileged access and enforce least privilege
      • Audit access control and handle exemptions properly rather than quietly

      Platforms and tooling

      • Keep the path from raw telemetry to a rule that fires working end to end
      • Own the detection platform, not only the content sitting in it

      Cloud and infrastructure

      • Harden cloud and endpoint baselines, then prove they hold
      • Work across the security and infrastructure teams instead of throwing tickets over the wall

      Scripting and automation

      • Automate recurring work until it stops needing a person
      • Mostly in service of detection and patching, which is where the hours go

      The stack, grouped by what it is for

      • SIEM Microsoft Sentinel NGSIEM, detection rule authoring and tuning
      • Endpoint and XDR Defender XDR Defender for Endpoint, CrowdStrike Falcon
      • Adversary emulation Cymulate Breach and attack simulation across network and endpoint
      • Exposure Qualys VMDR, Patch Management, CSAM, plus Rapid7
      • Cloud and identity Microsoft Azure AZ-500, AZ-104, Intune and Group Policy
      • Threat intelligence Enrichment VirusTotal, MISP, Recorded Future, GreyNoise
      • Malware triage Sandboxes any.run, Joe Sandbox, Hybrid Analysis
      • Automation Scripting PowerShell, Python, Bash and shell
      • Workflow Jira and Confluence Incident coordination, knowledge base authoring

      Experience

      Security Analyst II, Cyber Defense

      Intact | Mississauga, ON | January 2026 to Present

      Promoted from Security Analyst after 10 months.

      • Tier III escalation point for the incidents other analysts cannot close. I take them from detection through containment and remediation, then write the post-incident review.
      • Retested 150+ penetration test findings and confirmed every high and critical issue was closed before it reached production.
      • Run monthly Cymulate breach and attack simulations across network and endpoint, which surfaced 25% more control gaps than our alert-driven process did.
      • Tune Microsoft Sentinel (NGSIEM) detection rules. False positive volume is down 30% and the rules that matter fire more reliably than they did a year ago.
      • Triage emerging vulnerabilities when public disclosure lands. 40+ so far, each with a risk reassessment inside 24 hours.
      • Wrote and ran 5 cross-functional tabletop exercises covering detection, containment, and remediation. Simulated MTTR dropped 15%.
      • Wrote 12 incident response playbooks and SOPs. Junior analyst onboarding time is down 40% since they went in.

      Security Analyst, Cyber Defense

      Intact | Mississauga, ON | March 2025 to December 2025

      • Worked rotating 24/7 shifts on the escalation ladder, triaging and containing incidents and handing advanced cases up with the evidence, timeline, and impact already documented.
      • Rolled out Azure security baselines across 70+ affiliates, tightening compliance posture and reducing incident risk across the organization.
      • Built PowerShell and batch automation for recurring security work, saving 20+ hours a month.
      • Managed the CrowdStrike Falcon endpoint inventory, improving visibility into stray and unmanaged assets and holding protection coverage at 99%.
      • Wrote 50+ knowledge base articles in Jira and Confluence, which cut resolution time on repeat tickets.
      • Coordinated cross-functional incident response through Jira, which cut response times by 15%.

      Information Technology Security Analyst

      Intact Public Entities | Cambridge, ON | June 2022 to February 2025

      • Rewrote the security policies into something people could follow. Unauthorized access dropped 75% and we saved about $20K a year in breach costs.
      • Engineered patch management scripts that cut patching time by 90% and hardened the endpoints they touched.
      • Ran 200+ vulnerability tests through Qualys VMDR, lowering risk exposure by 30% and remediation times by 40%.
      • Built the security training programme. Compliance went up 25% and phishing incidents fell by half.
      • Investigated and resolved security incidents in Microsoft Sentinel, consistently meeting SLA targets.
      • Ran quarterly audits of privileged access, special permissions, and control groups to enforce least privilege.

      Technical Support Analyst L2

      Cineplex Digital Media | Waterloo, ON | April 2021 to June 2022

      • Monitored the health of Linux-based digital signage networks and worked customer issues through to resolution against SLA.
      • Ran remote diagnostics and repairs over SSH and VNC.
      • Built API integrations and scripts to automate the delivery process.
      • Validated each deployment before handing it to the Day 2 customer success team, so nothing arrived broken.
      • Managed dispatch of technicians, spare parts and equipment to sites.

      Flow Operations Clerk

      Loblaw Companies Limited | Kitchener, ON | July 2019 to November 2020

      Worked here while completing my post-graduate diploma at Conestoga College.

      Web Developer

      B-GHUD Academy of Information Technology | Mavelikkara, Kerala, India | July 2017 to March 2019

      • Built and maintained the institution's website and web applications in JavaScript, PHP, and SQL.
      • Owned the security and privacy of the institution's site and data.
      • Managed the content management system and other web tooling.
      • Provided technical support and training to faculty and staff.
      Time in role
      • Analyst IInow current role
      • Security Analyst10 mo
      • IT Security33 mo
      • Tech Support L215 mo
      • Flow Operations16 mo
      • Web Developer20 mo

      Selected work

      Four things I've done that I can talk about in detail. Anything specific to my employer's environment or detection logic stays off this page, so if you want the methodology, ask me and I'll walk you through it.

      attack it, then fix what missed it
      1. 01 Emulate Monthly Cymulate simulations across network and endpoint, plus retesting penetration test findings. Find the gap ourselves.
      2. 02 Detect Which rules fired, which stayed quiet, and how long the alert took to surface. A control nobody tested is a guess.
      3. 03 Investigate Tier III escalation from detection through containment, then the post-incident review and the root cause behind it.
      4. 04 Tune Rewrite the rule, cut the false positives, and re-test it against the next simulation rather than assuming it improved.

      The loop runs continuously, and each pass through it should make the next one quieter.

      Emulating the attack to test whether the detection actually fires

      I run monthly Cymulate breach and attack simulations across network and endpoint, and I retest penetration test findings rather than trusting the remediation ticket. Both are the same idea from opposite ends: the only honest way to know a control works is to trigger it on purpose and watch what happens. The point is to find the gaps ourselves, before someone finds them for real.

      Surfaced and closed 25% more control gaps than alert-driven review alone, and confirmed every high and critical penetration test finding was closed across 150+ retests.

      Control gaps surfaced +25%
      Pentest findings retested 150+

      Cutting false positives without losing signal

      I tune Microsoft Sentinel detection rules with one goal: fewer alerts nobody acts on, and better coverage where it counts. Reducing noise is only useful if the detections that matter keep firing, so every tuning change gets re-tested against the next simulation run rather than assumed to be an improvement.

      30% reduction in false positive alert volume, with higher fidelity on critical attack vectors.

      False positive volume -30%

      Security policies and training people actually followed

      Policy documents are easy to write and easy to ignore. I rewrote ours around what people could realistically do, then built the training that went with it and ran 200+ vulnerability tests to check whether any of it was working.

      Unauthorized access down 75%, about $20K a year saved in breach costs, compliance up 25%, phishing incidents halved.

      Unauthorized access -75%
      Security compliance +25%
      Phishing incidents -50%

      Patch automation that gave the team its week back

      Patching was slow, manual, and inconsistent. I wrote scripts to handle the repeatable parts and left humans to make the judgement calls. Remediation times dropped by 40% and risk exposure by 30%.

      Patching time down 90%, remediation time down 40%.

      Patching time -90%
      Remediation time -40%

      Certifications and education

      Certifications

      • Microsoft Certified: Azure Security Engineer Associate (AZ-500)
      • CompTIA CySA+ ce (CS0-003)
      • Microsoft Certified: Azure Administrator Associate (AZ-104)
      • Qualys Vulnerability Detection and Response (VMDR)
      • Qualys Patch Management
      • Qualys CyberSecurity Asset Management (CSAM)

      Credential IDs available on request.

      Education

      • Post Graduate, Enterprise Content Management | Conestoga College, Kitchener, ON | 2019 to 2020
      • B.Tech, Computer Science | University of Kerala, Kerala, India | August 2012 to March 2016

      Contact

      If you're hiring for a cyber defence, purple team or threat hunting role, or you just want to argue about detection tuning, my inbox is open. LinkedIn is the fastest way to reach me.

      LinkedIn | | Resume (PDF)

      Private details (password required)

      Phone number and certification credential IDs, encrypted with AES-256-GCM and a 600,000-round PBKDF2 key. The password is not stored anywhere on this site. If you need these details and do not have it, message me on LinkedIn and I will send them.