I'm Ian Dowd — a Lead Security Engineer based in Wethersfield, Connecticut. I'm an information security architect focused on orchestration suites and firewalls, on-premise and in the cloud. Brand agnostic, with a penchant for problem solving. I currently lead security operations engineering at Eversource Energy. See the resume for the full history.
singleventupset.com is my personal journal and research space for notes on
network security engineering. It's not a blog in the traditional sense — more a structured
dump of things learned, patterns recognized, and tools evaluated in the process of doing the work.
Current areas of research and interest: container security, public cloud IAM,
and DevOps for MSSP tool stacks.
The name comes from fault analysis: a single event upset (SEU) is a bit flip caused by ionizing radiation hitting a memory cell, or an unexpected state change induced by a cosmic ray or charged particle. In networking, most interesting problems are SEUs — a single misconfigured route, a single non-compliant resolver, a single open port in the wrong segment. The cascade from one bit to a major incident is the interesting part.
Content focuses on protocol security, network defense engineering,
vulnerability analysis, and tooling. After years deploying Check Point,
Tufin, AlgoSec, and Gigamon across enterprise environments, much of what shows up here is the
view from the policy-orchestration and network-visibility side of the house.
Nothing here is coordinated disclosure without explicit notice. All CVE content references publicly available information unless marked otherwise. Assume all vulnerability analysis is post-patch unless a disclosure status block states otherwise.
All content on this site is TLP:WHITE unless explicitly labeled otherwise. TLP:WHITE may be distributed without restriction, subject to copyright. Content marked TLP:AMBER or TLP:RED will be clearly labeled and scoped accordingly. See CISA TLP definitions for reference.
If something here is wrong, outdated, or dangerous — please reach out via email. If you're doing responsible disclosure and need a reference point, everything cited is available via public sources. For sensitive coordination, use the PGP key.
I don't run ads, analytics, or tracking scripts. No JavaScript, no third-party requests except Google Fonts (CDN). If you want full offline/privacy, block fonts.googleapis.com and the page will fall back to system monospace.