Building toward red-team and security infrastructure work.
I'm Sven: a cybersecurity learner and software builder focused on red-team tooling, secure infrastructure, practical labs, and security engineering habits.
Building toward red-team tooling, secure infrastructure, security labs, and practical engineering work that turns learning into useful defensive and offensive capability.
$ whoami --focus red-team tooling
note[1]: progress recorded
$ build --labs infra detections
note[2]: progress recorded
$ harden --systems repeatable
note[3]: progress recorded
$ ship --security-tools visible-work
note[4]: progress recorded
The work is honest: learn clearly, build consistently, and keep raising the standard.
Early in the field, serious about the craft.
This portfolio is a record of projects, skills, and decisions around red-team practice, secure infrastructure, and security engineering.
Red-team learning
I treat every lab, note, and exercise as a chance to understand attack paths, document evidence, and practice safely with clear scope.
Secure infrastructure
I want the work to include hardening, identity, logging, backups, deployment checks, and the operational details that make systems safer to run.
Useful security tooling
The goal is to build small tools, labs, and workflows that make repeated security tasks easier to practice, review, and improve.
A skill stack for security engineering.
The focus is practical: red-team fundamentals, secure infrastructure, tooling, documentation, and repeatable workflows that turn practice into progress.
Red Team Foundations
Security Tooling
Secure Infrastructure
Security Engineering Habits
Projects that make learning visible.
Each project captures what I built, what I practiced, and how I am turning curiosity into practical security and software skill.
Red Team Lab Automation
A repeatable lab environment for practicing recon, attack paths, detection notes, and cleanup safely.
Why it matters
Shows how offensive practice can be made repeatable, measured, and useful for defensive learning.
Secure Infrastructure Blueprint
A hardened infrastructure pattern for small services with identity, logging, segmentation, and recovery in mind.
Why it matters
Connects software delivery with the operational security controls needed to run it responsibly.
Security Tooling Workbench
A collection of small utilities for security notes, checks, parsing, and repeatable investigation workflows.
Why it matters
Keeps the portfolio centered on useful security engineering habits instead of generic project lists.
Security goals with visible output.
The portfolio is aimed at practical builds: red-team labs, hardened infrastructure patterns, and tooling that makes security work repeatable.
Red-team lab environments
Create controlled environments for practicing recon, exploitation paths, detection notes, and reset workflows without touching real targets.
Secure service infrastructure
Document deployable baselines for identity, secrets, logging, backups, monitoring, and least-privilege operations.
Security tooling and labs
Turn repeated security tasks into small tools, checklists, parsers, and evidence workflows that make practice visible.
Recruiter, mentor, teammate, or fellow nerd?
Send a message about projects, feedback, opportunities, mentorship, or anything worth building and learning from.