Security Engineering

Offensive Security

RED TEAM — OFFENSE

Recon & Penetration Testing

You can’t fix what you don’t know is broken — and neither can the people attacking you. The cheapest vulnerability you’ll ever patch is the one you find first. I’ll map your attack surface, knock on every open door, and actually prove what’s exploitable. No “high-risk theoretical” filler, no jargon walls.

What that involves:

• External recon — domains, subdomains, exposed services, leaked credentials, takeover candidates
• Infrastructure and web application testing, OWASP-aligned
• Exploits proven to work, so a finding arrives with proof of impact rather than a CVE number
• Custom tooling where the off-the-shelf scanners fall short
• A prioritised report written to be read, not a 200-page PDF nobody opens

So you end up with a map of what you are exposing to the internet, evidence you can reproduce — fix it, then re-test it — and a remediation list your team can work through in order.

Defensive Security

BLUE TEAM — DEFENSE

Monitoring & SOC

Offense is an appointment. Defense is a lifestyle. Between pentests, someone has to watch the perimeter, correlate the logs, and catch the quiet stuff before it becomes a headline. That’s where I live.

That means:

• Metrics, logs and alerting collected centrally, for the whole estate rather than one host at a time
• Detection tuned to intrusions, with honeypots where they earn their place
• Incident response runbooks written before the incident, so the first hour is not improvised
• Alert hygiene — you get woken up when it matters, not when a disk crosses 80%
• Tabletop exercises and post-incident reviews

You find out before your users do, you can see who knocked and whether anyone got in, and the telemetry is still there afterwards for forensics, tuning and capacity planning. Defences that get reviewed and tightened on a schedule hold up better than ones added only after an incident.