What ObfusLabs is right now
ObfusLabs is currently just me, Dan, learning, hacking in labs, and trying to get better at
offensive security and detection engineering. I’m not running a consulting business yet and
I’m not taking on formal client work at this time.
What I’m doing
- Working through web app and cloud security labs, CTFs, and certifications.
- Experimenting with small tooling ideas and ways to visualize security data.
- Documenting what I learn so I can eventually turn it into something useful for others.
If you landed here…
- I’m open to hearing about junior / mid-level offensive security roles or SOC roles with an attacker focus.
- I’m open to low-stakes collaborations, mentoring, or research ideas.
- I’m not going to pretend to offer services I can’t reliably deliver yet.
If you’re curious about my work or just want to say hi:
daniel.gray@obfuslabs.com
Future Idea: SOC-as-a-Service
This is not a real offering yet — it’s something I’d like ObfusLabs to grow into
once there’s a bigger team, more tooling, and more experience behind it.
I’m keeping this here so early supporters can see the long-term vision.
Why even think about a SOC?
A lot of companies want security visibility but can’t afford a giant SOC or a huge vendor.
Long-term, I’d love to build a small, attacker-aware SOC that’s transparent, lightweight,
and human — not a black-box portal full of noise.
What a future SOC at ObfusLabs might look like
-
Human-first monitoring — people who actually understand attacker behavior,
not generic alert processors.
-
Clear, concise escalation — “here’s what happened, here’s what it means,
here’s what to do” instead of giant PDFs.
-
Detection tuning with an offensive mindset — making sure alerts fire for real attacks
while cutting down the noise.
-
Threat-hunting sessions that focus on learning and visibility rather than checkbox exercises.
-
Simple, terminal-friendly tooling instead of flashy dashboards — inspired by my lab projects.
What this is NOT (yet)
- No 24/7 team.
- No SLAs.
- No enterprise onboarding process.
- No compliance mapping or formal IR retainer.
- No polished “product.”
Right now, this is purely a direction I’d like to grow into.
If you’re excited about the idea — or want to help shape it —
feel free to reach out.
Contact: