Technical writing on software engineering, systems design, and the tools that make it possible.
Most inter-VLAN routing in enterprise networks isn't done by a router. It's done by a switch that understands IP. This post breaks down how Layer 2 and Layer 3 switches differ, how SVIs and routed ports work, and why TCAM makes hardware-based routing possible.
ATO isn't a CWE — it's an outcome. This post models account takeover as a composite attack class, maps the five vector families to their root causes, and builds the defense architecture that exploitation checklists leave out.
TLS fingerprinting catches automation tools by their handshake — until the attacker uses a real browser. Part 1 of a series on why client-side bot defense is structurally limited.
HTTP status codes are designed to be informative. That's exactly what makes them dangerous. Part 1 of a series on how RFC-compliant behavior creates exploitable information channels — and when breaking the spec is the right call.
How do you find a user without the server ever knowing who they are? A deep dive into the paradox of zero-knowledge user lookup, why every client-side blind indexing approach collapses, and how OPRF-based truncated bucket routing solves it without leaking identity.
This 70-part series covers everything a network engineer needs to understand—from how devices communicate to how automation is reshaping the field. Structured around CCNA 200-301 objectives, but built on open standards. No vendor lock-in required.