Project title — to be added
A short description of a real project or lab will go here: what it was, why it was built, and what it demonstrated.
Security • Curiosity • Continuous Growth
Security Engineer Trainee
I'm learning security by doing it — building labs, investigating what I see, and writing down what each one teaches me. This is where that work lives as it grows.
Scroll to explore↓
Projects & Labs
Environments built and broken on purpose, to understand them.
In progress
Technical Writing
Investigations and lessons written up as they happen.
In progress
Certifications
Structured study, verified where verification exists.
To be added
Continuous Learning
The part of the work that never gets a final number.
Ongoing
01About
I'm Roshinni — a security engineer trainee who learns by taking things apart carefully and writing down what happens.
My route into security came from curiosity about how systems fail quietly: the log line nobody reads, the alert that looked routine, the small misconfiguration that becomes a story later. That curiosity is still the engine.
Right now my attention is on operations and investigation — building labs I can break, following evidence rather than assumptions, and documenting each step so the reasoning survives longer than the memory of it.
PlaceholderPersonal details, background and goals to be expanded with Roshinni's own words.
More about me02Focus
Areas I work in, learn about and explore — labelled honestly rather than scored.
Day-to-day monitoring work: triaging what comes in, separating noise from signal, and understanding how alerts become decisions.
Working with log sources, queries and dashboards to see what a system is actually doing rather than what it claims to.
Building the habit of a careful, documented investigation: scope it, evidence it, contain it, and record what was learned.
Reading indicators and reporting with a critical eye, and turning that context into something operationally useful.
Writing and testing detection logic in a lab, then studying where it fires, where it misses and why.
Understanding traffic at the packet and flow level — what normal looks like before deciding what abnormal means.
How hosts behave, what they record, and how endpoint telemetry supports an investigation.
Scripting the repetitive parts of analysis so attention stays on the parts that need judgement.
03Work
Hands-on projects, labs, investigations and practical security work — written up as case studies rather than thumbnails.
A short description of a real project or lab will go here: what it was, why it was built, and what it demonstrated.
A short description of a real project or lab will go here: what it was, why it was built, and what it demonstrated.
A short description of a real project or lab will go here: what it was, why it was built, and what it demonstrated.
04Writing
Technical writeups, investigations and lessons learned — the record of the thinking, not just the result.
A short summary of a real writeup will appear here once the article is written.
A short summary of a real writeup will appear here once the article is written.
A short summary of a real writeup will appear here once the article is written.
05Experience
Dates to be added
Organization to be added
A description of the current role, its responsibilities and the work carried out will go here.
Dates to be added
Organization to be added
An earlier step in the journey will be described here.
06Achievements
Moments that marked real progress — certifications, training and recognition, in the order they happened.
Date to be added
Issuing organization to be added
What this milestone involved and why it mattered will be described here.
PlaceholderDate to be added
Issuing organization to be added
What this milestone involved and why it mattered will be described here.
Placeholder07Learning
What I'm working through right now — stated as status, never as a percentage.
What this is being learned for will go here.
What this is being learned for will go here.
What this is being learned for will go here.
How I work
08Connect
I'm always up for a conversation about security work — investigations, labs, things you've broken and fixed, or where to look next. Collaboration, learning and opportunities all welcome.