Security-minded systems builder working on telemetry, defensive tooling, automation, and trustworthy AI-assisted workflows.

I build small, practical projects that sit between systems, security, and operational data.

My current direction is shaped around:

• Linux, networking, and core systems understanding
• detection-oriented security engineering
• telemetry, monitoring, and signal processing
• public-safe technical writing and sanitized security notes
• AI-assisted workflows with explicit human verification and scope boundaries

C++20 defensive log analysis CLI for Linux authentication logs.

• parses both legacy syslog and journalctl --output=short-full style input
• normalizes authentication evidence before detection
• applies configurable rule-based detections
• emits deterministic Markdown and JSON reports
• includes CI, CodeQL, and repository hardening

Small telemetry and monitoring prototypes for detection-oriented workflows.

• builds sliding-window features from timestamped event streams
• generates alerts, summaries, and reusable local demo outputs
• explores the bridge between logs, signals, and security operations
• keeps scope explicit: prototype-first, reproducible, inspectable

Public, sanitized security write-ups from authorized labs and training platforms.

• focused on methodology, reasoning, and reusable patterns
• designed for safe publication instead of copy-paste exploitation
• organized as a maintainable public knowledge base
• includes publication boundaries and sanitization rules

• building finished defensive / telemetry-oriented tools
• strengthening Linux and networking depth
• improving public project presentation and documentation quality
• preparing an English-first technical portfolio for international applications

• clear scope over inflated claims
• reproducibility over demos that only work once
• defensive and public-safe by default
• documentation, testing, and repository hygiene matter

Most repositories here are learning-driven engineering artifacts: small enough to finish, structured enough to review, and honest about their boundaries.

• GitHub: @stacknil