Named ownership
Every engagement has a clear technical owner, approval path, and escalation route.
Every engagement has a clear technical owner, approval path, and escalation route.
Automation handles consistent transformations; engineers review exceptions and document decisions.
Runbooks, monitoring, access, maintenance, failure behavior, and rollback are part of the design.
Perimeter One is a wholly US owned and operated company focused on security and network segmentation, led by practitioners who have run security programs from all three sides of the industry: as the provider, as the channel, and as the enterprise buyer. That is why the engagements here are scoped like operations work, not slideware.
Jason has spent 25 years in enterprise security, infrastructure engineering, and managed service delivery. He founded and ran Type-X Networks and SecNoc for thirteen years, building a multi-tenant detection and response platform that secured healthcare, government, financial services, and commercial clients under one program. He then led the solutions research and development organization at Cloud Harmonics, an Ingram Micro company, where he built an authorized support center and a professional services practice from the ground up for the Palo Alto Networks and Check Point partner ecosystem.
Most recently he has served as a vice president of network security engineering at a global financial institution, owning firewall, proxy, cloud edge, and email security for an estate under continuous regulatory scrutiny. There he led the move from legacy perimeter security to a cloud delivered SASE and SSE model and re-architected flat networks into segmented, policy driven zero trust environments. The same playbook, the same runbooks, and the same insistence on rollback paths are what Perimeter One brings to a conversion.
He is a certified instructor for Palo Alto Networks, Check Point, and Google Cloud, has sustained clean SOX and PCI DSS audit outcomes as the primary liaison to internal audit, and has built compliant programs against SOC 2, ISO 27001, NIST 800-53, FedRAMP, HIPAA, and HITRUST. His current work also covers AI security governance, including data boundary controls and alignment to the NIST AI Risk Management Framework and the EU AI Act.
Tell us what you run, what needs to change, and which constraints cannot move. We will help define a practical next step.