PhilSIEM monitoring
A personal OpenCanary honeypot and alerting environment, with a separate proposed v2 architecture documented as a design study.
INDEPENDENT CYBERSECURITY PORTFOLIO
I build practical security labs, investigate suspicious activity and turn technical learning into documented defensive projects.
01 / HANDS-ON WORK
Practical work, documented decisions and lessons learned. These are independent learning projects, not commercial security products.
A personal OpenCanary honeypot and alerting environment, with a separate proposed v2 architecture documented as a design study.
A documented network segmentation and centralised monitoring design. Security Onion, Cowrie, Suricata and Zeek are proposed components, not claimed deployments.
Walk through evidence-led simulated cases and try a browser-based SSH event triage exercise. Clearly labelled training data, not live incidents.
02 / INVESTIGATION MINDSET
Security operations is not just spotting an alert. It is understanding the context, documenting findings and knowing what the evidence actually supports.
Review alerts, logs and relevant context.
Identify patterns, scope and potential impact.
Separate confirmed facts from hypotheses.
Refine detections and record lessons learned.
Evidence-first approach. Any public case studies will use sanitised lab data or clearly labelled simulations. Sensitive systems, credentials and personal information stay private.
03 / TOOLKIT
Tools and subjects explored through practical labs and ongoing study. Familiarity varies by tool; this is not a claim of expert proficiency.
Alert triage · Event analysis · Incident documentation · Detection concepts
Wireshark · Nmap · Network protocols · Traffic investigation
Ubuntu Linux · OpenCanary · Virtual machines · Remote lab access
Security+ studies · Defensive research · Practical exercises · Technical write-ups
04 / THE PERSON BEHIND THE LAB
I'm developing my career in cybersecurity by building hands-on projects, studying security fundamentals and investigating how defensive systems work in practice.
PhilSIEM is where I document that journey: what I built, what I tested, what went wrong and what I learned. The goal is to develop the judgement and technical foundations needed for security operations work.
05 / CONNECT
Explore the code and project notes on GitHub. More documented investigations and technical write-ups will be added as the portfolio develops.
Portfolio-ready learning evidence: practical lab documentation, proposed architecture, fictional SOC case studies and an interactive training environment.