Alert triage
Validate the trigger, establish context, and identify what needs investigation.
Currently SOC Analyst @ Ensign InfoSecurity
// MUHAMMED IQBAL HAMDZAN · COMPTIA CySA+
> Security Operations Analyst
Behind every alert is a story.
I follow the evidence. Approximately four years investigating security alerts, connecting context, and turning uncertainty into a defensible assessment.
Kuala Lumpur, Malaysia · SOC / BLUE TEAM
01 / ANALYST PROFILE
I’m a SOC analyst with a focus on understanding what actually happened. My work moves from alert context and raw events to historical searches, entity pivots, and evidence-labelled reporting.
I work across Microsoft Sentinel, Splunk, IBM QRadar, and LogRhythm, with EDR and threat intelligence providing the context around the signal.
Outside the queue, I build personal automation tools and develop my detection engineering skills in a lab.
More about my background“Reputation is a reason to look. Evidence is a reason to act.”
MY APPROACH TO TRIAGE
Validate the trigger, establish context, and identify what needs investigation.
Historical searches, related entities, and the security-control outcome.
Use enrichment to test a hypothesis and understand the wider context.
Observations, assessment, uncertainty, and an actionable next step.
02 / EXPERIENCE
A path through security operations, from the first alert to the next investigation.
Ensign InfoSecurity
Alert triage, incident investigation, escalation, and case documentation in security operations.
Establish alert context, inspect parsed fields and raw events, search historical activity, pivot on related entities, and validate control outcomes before documenting an assessment.
Building practical experience in security analysis and investigation.
The starting point of my hands-on security operations journey.
03 / INVESTIGATION WORKFLOW
Six steps. One principle: make every conclusion traceable to the evidence.
Start with the behaviour the alert claims to detect. Identify the source, time window, affected asset, and the condition that triggered it.
A clear investigation question.
Personal methodology, independently reconstructed. Read the full note ↗
04 / TOOLKIT
The platforms behind the investigation, and the skills I’m building next.
// PERSONAL LAB · IN DEVELOPMENTExploring detection engineering and AI-assisted workflows.
05 / SELECTED PROJECTS
Personal tools for the repetitive work, and experiments that sharpen the method.
Python enrichment for IPs, domains, URLs, and hashes. Batch input, API error handling, and structured JSON/CSV output to support analyst judgement.
A browser userscript exploring notifications and audible alerts for new incident IDs. A small experiment in reducing repetitive queue checking.
An autonomous Hack The Box agent exploring enumeration, hypotheses, and structured evidence in sanctioned training environments.
A browser console for comparing the same prompt across AI models. Bring your own API keys and inspect the outputs side by side.
Personal research. Training-platform agents are used within sanctioned or explicitly authorised scopes.
06 / CREDENTIALS
Cybersecurity Analyst
Computer Science · SecurityUniversiti Kuala Lumpur (UniKL)
Diploma · IT NetworkingPoliteknik Mersing
Next on the learning path: eJPT and a tested detection engineering portfolio.
07 / FIELD NOTES
Personal lab work and independently reconstructed investigation methods.
SOC INVESTIGATION · GENERAL METHODOLOGY
THREAT INTELLIGENCE · TRIAGE WORKFLOW
Employer and client data, telemetry, and internal playbooks stay private.
$ connect --analyst iqbal
Conversations about security operations, investigation, detection engineering, and tools worth building.
security@iqbalhamdzan.xyz