About the author
FwChange is not a product written by people who read about firewalls. I built it after seventeen years inside enterprise security operations, and after watching the same migrations fail the same preventable way. The software encodes the method I already used by hand.
The background
I have spent my career as a hands-on network security architect: migrating firewall estates, rationalizing rule bases, and standing in front of auditors who want to know who changed what, when, and why.
Across 280+ firewall migration projects I worked inside Tier-1 European and KRITIS-regulated environments: banking, insurance, enterprise software, automotive, chemicals, payments, energy, consumer goods, heavy machinery and telecommunications. Names stay anonymized; the patterns do not. The same preventable failures repeat at every scale: shadow rules nobody finds, manual translation errors between vendor syntaxes, and compliance evidence reconstructed under deadline because no system captured it as the change happened.
FwChange exists because I got tired of solving those problems by hand. It encodes seventeen years of field-tested method into software, so the analysis that used to live in my head is now a step in the workflow.
Credentials
Six industry credentials across network security, enterprise architecture, cloud security and AI engineering, plus four vendor certifications across the firewall platforms FwChange actually speaks to.
Where the work happened
Client names stay under NDA, but the regulated sectors that shaped the method are the same ones FwChange now serves. The migrations behind the platform sit across these industries.
Specialization
The work sits where regulated infrastructure meets multi-vendor firewall estates, the place where a wrong rule is both a security incident and an audit finding.
FwChange was born from one observation repeated across 280+ projects: enterprise firewall migrations fail the same preventable way: undetected shadow rules, manual translation errors between vendor syntaxes, and compliance evidence that has to be reconstructed after the fact. The platform turns each of those into a step the software handles, not a thing a senior engineer has to remember.
The platform is the proof. The methodology page walks the thinking behind every part of it, the same reasoning I used in the field before any of it was code.