Secure remote access and VPN replacement for your remote sites.
Remote Access Hardening: the Zero Trust Gateway
Know every way into your sites, and trust none of the messengers. Engineers, vendors, and integrators reach your sites through VPN gateways, relays, vendor tools, and cellular and satellite links. We map every way in, engineer one governed path that you own, keep the keys away from every carrier, and retire old cryptography on a dated schedule. Devices on the path that can't change get a compensating-control record.
Engineered by Jeremiah Coakley, Principal Security Architect
In your crypto-agility plan: the access path gets hybrid post-quantum key exchange where both ends support it, and an inventory entry where they don't.
What you're buying
Remote access you can account for.
Teams call us when a deadline, a review, or an insurance renewal asks a question about remote access they can't answer yet.
VPN deadline
Your VPN replaced before it becomes the finding
Fortinet removed SSL VPN tunnel mode in FortiOS 7.6.3, and insurers and auditors now ask how remote access is protected. We move your people onto identity-gated access, most often on the Cloudflare One™ platform, retire the old VPN, and hand over a path that answers the next question.
Vendor access
Vendor sessions you can see and end
Your operator, your customer, or your auditor asks who can reach your systems and how you cut them off. Every vendor gets a named login, a time limit, and a session your team can end from one screen, with logs that answer the question.
Internal apps
Admin panels off the open internet
Staging sites, dashboards, and admin panels move behind your identity provider, reached in a browser with nothing to install. The exposed admin interface finding closes, and the application needs no code change.
Long-lived systems
Post-quantum protection without upgrading every system
On the Cloudflare One platform, connections through the tunnel get hybrid post-quantum key exchange, which covers older consoles and applications that will never get a cryptography upgrade of their own. Your cryptographic inventory records what stays classical, with a date to revisit it.
Cloudflare and Cloudflare One are trademarks of Cloudflare, Inc., named here to identify the platform.
The engagement
Map it, engineer it, evidence it.
One site at a time, scoped by the number of access paths into it. Each path ends the engagement engineered or documented, with evidence attached.
Inventory
Every way into the site
Each interactive and vendor remote access path into the site's systems, mapped end to end: who connects, from where, through what, and over which carrier, including the cellular and satellite links that backhaul remote sites and the forgotten modem nobody listed.
Engineer
One governed way in
Access through your own zero trust gateway, a broker in your tenant tied to your identity provider: one named identity per person, multi-factor authentication, no inbound ports opened at the site, time-boxed sessions, and the ability to see and end an active vendor session. Relays and carriers pass traffic and never hold the keys. Hybrid post-quantum key exchange on the path where both ends support it.
Retire
Old cryptography, on a dated schedule
Every outdated protocol, cipher, and key on the path gets an end date and a replacement, so nobody can stand up a convincing fake gateway or reuse a session that should have expired.
Evidence
A package your auditor can follow
Session logs written to an audit sink in your account and fed into your detection platform, with hunting queries and an incident response playbook for ending a hostile session, plus an evidence package mapped to the framework you are measured against: NIST 800-53 AC-17, IA-2, SC-8, and AU-2, ISA/IEC 62443, and NERC CIP-005 where it applies.
Document
The devices that can't change
A field device on the path that can't take multi-factor authentication or modern encryption gets a risk-acceptance record with compensating controls, an owner, and a review date.
What it reaches
One access layer for every destination.
The same identity-gated path, the same session evidence, whichever system sits at the far end.
Remote sites
Engineers and vendors into operational sites
Consoles, controllers, and the hosts that manage them, reached over cellular, satellite, or wired backhaul with no inbound port at the site. Vendor sessions you can see and end, with evidence mapped to NIST 800-53, ISA/IEC 62443, and NERC CIP-005 where it applies. Moving off FortiGate SSL VPN? See SSL VPN tunnel mode no longer supported. Scanner flagging SSH on your devices? See SSH weak key exchange algorithms enabled.
Internal web apps
Admin panels, staging, and back-office tools
Taken off the open internet and reached in a browser through your identity provider, with no client to install. This closes exposed admin panel findings from a pentest or a customer security review. The public side of the application stays with edge security.
Who holds the keys
The zero trust gateway is yours.
A shared remote-access service that reaches many operators' management networks is a single point of compromise for all of them. The Intermediate System we engineer runs in your own tenant, authenticates against your identity provider, and writes its session logs to your account. Our access during the engagement is time-boxed, and your team can revoke it.
The same rule holds for every carrier on the path. Relays, brokers, and vendor platforms pass traffic along without holding the keys, so if one is taken over, the sessions it carries stay sealed.
What we engineer
The patterns behind the gateway.
Three layers, each one engineered, verified, and documented.
Zero-trust identity
One named person per session
A least-privilege role model mapped to NIST 800-53 access and identification controls, with machine identity handled the same way.
Tunnels
A gateway with no open ports
An outbound-only tunnel in front of SSH and private dashboards, gated by each person's own identity, with no new public ingress.
Mesh
Replacing a self-run VPN
A highly available mesh with hybrid post-quantum key exchange and policy kept as code: devices cannot reach each other, and the protected network is closed by default. The mesh product is in beta, so a fallback path stays in place until it graduates.
The same pattern extends to a partner's engagement: a dedicated node behind an outbound-only tunnel, tiered access policies tied to the partner's own identity provider, SSH trust through a certificate authority, and default-deny network policy. The partner holds the control plane and can revoke our access at any time.
Questions
Remote access, answered
Why does old cryptography matter for remote access?
Every remote connection travels through messengers: VPN gateways, relays, and vendor tools. Cryptography is how the far end knows the messenger is the real one and the session arrived untouched. When that cryptography goes out of date, the sharpest risk is impersonation: a convincing fake gateway, a session reused after it should have expired, or a login from a vendor who left years ago. We retire outdated protocols and keys on a dated schedule so the site can tell the real connection from a copy.
Can you replace our VPN with zero-trust access?
Yes. We replace shared VPN logins and jump boxes with identity-based access: a named person per session, no inbound ports at the site, and a broker in your own tenant. We build with tunnels and a mesh with hybrid post-quantum key exchange, and the client owns the platform afterward. Devices that cannot take the new path keep a documented exception with compensating controls.
Can the same path protect our internal web applications?
Yes. Admin panels, staging sites, dashboards, and back-office tools sit behind the same identity-gated path, reached in a browser with no client to install. Each request is checked against the person and their device, the application stays off the open internet, and the connection through the tunnel gets hybrid post-quantum key exchange with no change to the application itself. For a software company whose customers review its application, this closes findings such as an exposed admin interface and produces the access evidence the reviewer asks for.
Which platforms do you build on?
Most often the Cloudflare One platform, because its Access and Tunnel paths carry hybrid post-quantum key exchange today. Where a cloud intermediary isn't acceptable, such as high- and medium-impact NERC CIP sites without the operator's agreement, we engineer a self-hosted broker inside your boundary. If you already license another zero trust service, we check it against the same design before recommending any change. Whatever the platform, it runs in your tenant against your identity provider.
Does it work with our identity provider?
Yes. The gateway works with Microsoft Entra ID, Google Workspace, and Okta, and with JumpCloud, AWS IAM Identity Center, or any SAML or OIDC provider. People sign in with the accounts and multi-factor authentication they already use.
How do you handle remote sites reached over cellular or satellite links?
The carrier is one segment of the path. The inventory records every backhaul link into a site, and the engineered path encrypts and authenticates end to end across it, so the controls hold whichever network carries the session. Links with high latency or tight bandwidth are scoped for session timeouts and logging that still work over them.
Who owns the zero trust gateway after the engagement?
You do. The gateway runs in your tenant against your identity provider, and the session logs land in an audit sink in your account. Our own access during the engagement is time-boxed and revocable by your team.
We supply software or equipment to an operator. Can you harden our own access into their network?
Yes. Operators ask their suppliers to show how their people reach the operator's systems: a named identity per person, multi-factor authentication, time-boxed sessions, and logs. We engineer that path on your side and map the evidence to the requirement you are answering, such as the NATF supply chain risk questionnaire or the operator's own supplier cybersecurity policy. You answer the questionnaire, and we build and evidence the controls behind your answers.
Who runs it after the engagement ends?
Your team does. We hand over a run pack with the access diagram, the configuration as code, and runbooks for adding people, revoking sessions, and retiring a path. If you want a second pair of hands, FEDLIN support is available afterward as a separate arrangement.
Which frameworks does the evidence map to?
The one you are measured against. The same engineered path maps to NIST 800-53 (AC-17, IA-2, SC-8, AU-2), NIST CSF 2.0, and ISA/IEC 62443, and to NERC CIP-005 R2 and R3 where those requirements apply.
What does NERC CIP-005 require for remote access?
For high- and medium-impact BES Cyber Systems with External Routable Connectivity, CIP-005-7 R2 requires interactive remote access to pass through an Intermediate System, encryption that terminates there, and multi-factor authentication, plus a way to determine and disable active vendor remote access sessions. R3 extends vendor session management to the associated EACMS and PACS. The broker we engineer serves as the Intermediate System, and the evidence package shows each requirement working.
Can you work inside a protected network?
Work inside a protected network runs through your integrator or your team, under whatever personnel and change requirements apply there. We engineer and verify the change and deliver it for them to apply.
How is Remote Access Hardening priced?
At a fixed price set by the number of sites and access paths. After a scoping call and an NDA, we return a fixed scope within one business day. Integrators and primes receive partner pricing to deliver it inside their program.
A remote access audit coming, or a vendor path you can't account for?
Book a scoping call. Once an NDA is in place, we scope the sites and paths over a channel you choose and return a fixed price within one business day.
Book a Scoping CallNot sure where to start? Tell us where you are.
Evaluating your security posture before a funding round, compliance deadline, or enterprise deal?
