ControlIT Secure Access
Turn the internet into your secure enterprise network.
- Overlay Network
- Zero-Trust Access
- Site-to-Site and Cloud
- Application Access
- Connect
- Control
- Extend
Secure access, controlled internet and IT operations, on infrastructure you choose.
No inbound ports, no public IPs, no VPN concentrator. Every endpoint dials out.
Branches, clouds and remote staff on one private network, over the internet you already have.
URL, category and application policy for every user and branch, logged by who asked.
Domain logon, Group Policy and remote domain join from home, a branch or the plant floor. No Entra ID, no connector.
RMM and helpdesk, patch management and remote access, in one console.
Single sign-on and MFA for every app, on the directory you already run.
User plus Device plus Identity plus Policy equals Corporate Network.
The enterprise network is no longer defined by a building. It is defined by secure connectivity, identity and policy.
No inbound ports. No public IPs. No VPN concentrator.
Endpoints dial out to the overlay. Nothing you run has to listen on the internet.
No hybrid join. No directory sync to a vendor cloud.
Your Active Directory stays where it is, and stays yours.
Access, identity and operations in one console.
Windows and Linux endpoints, reached and run from the same place.
Secure Access connects, controls and extends your network over the internet. IT Management runs the endpoints and the sign-ins on the same outbound path.
Connect, control and extend your network over the internet you already have. No VPN concentrator, no Entra ID, no inbound ports.
Turn the internet into your secure enterprise network.
Control and secure internet access for every user, branch and remote laptop.
Your existing Active Directory, over the internet.
Run the endpoints and the sign-ins on the same outbound path, from one console.
Run every endpoint from one console, and reach it without a VPN.
One sign-on and MFA for every app, on the directory you already run.
Everything dials out to one private overlay. Private traffic reaches your directory and applications directly; internet traffic leaves through the Web Gateway, where policy decides.
Every remote user, branch and cloud workload dials out to one private overlay. No inbound ports, no public IPs, no VPN concentrator.
Internet traffic leaves through the Web Gateway, where user and group policy decides what is allowed, and every request is logged by who asked.
Your Domain Controllers answer across the overlay: domain logon, Group Policy and remote domain join, with no Entra ID and no connector.
Every row is a product somebody is already licensing. The right-hand column is what one deployment does instead.
| Module | Capability | What that usually means | ControlIT |
|---|---|---|---|
| ControlIT Secure AccessConnect | Overlay Network | A VPN concentrator on a public address, sized, licensed and patched | A private network over the internet links you already have, nothing published |
| Site-to-Site and Cloud | A tunnel per branch, and another for each cloud | Branches, data centres and cloud on one private network | |
| Application Access | Network-wide VPN access for vendors who need one application | Staff and vendors reach only the applications they are approved for | |
| ControlIT Web GatewayControl | URL and Category Filtering | A cloud web security subscription, or a filtering appliance at head office | URL and category policy for every user, branch and remote laptop |
| User and Group Policies | Separate rules on each branch firewall | One policy per group, applied wherever that group works | |
| Logging and Reporting | A separate reporting tool fed from firewall logs | Every request logged by user, category, policy and verdict | |
| ControlIT AD AnywhereExtend | Remote Domain Access | Hybrid join, or a VPN that has to be up before logon | Domain logon, Group Policy and file shares over the internet |
| Remote Domain Join | A trip to the office for every new laptop's first domain join | Joined to your domain over the internet, from wherever it is | |
| ControlIT Core | RMM and Helpdesk | A separate remote monitoring and management product, plus a separate service desk product | Same agent, same console, tickets beside the device they belong to |
| Patch Management | A dedicated patch management product | Scheduled OS and third-party patching from the same console | |
| Remote Access | A VPN concentrator, plus a remote access tool | Outbound session to the endpoint, nothing published | |
| ControlIT Identity | SSO and MFA | An identity vendor and a separate MFA vendor, each with its own per-user fee | Both on the same identity, no per-user identity fee |
| Identity and Access Management | A separate identity governance product | Group-based access with one audit trail |
Every row above is a renewal someone on your team is already managing.
Internet Is the New LAN
The same product either way. Computer Port configures the deployment around your sites, your directory and your access rules, and nothing about your network has to be published for it to work.
Hand the monitoring, the patching and the first response to the Computer Port operations team.
| Situation | With a VPN and a separate stack | With ControlIT |
|---|---|---|
| A laptop at home | Logon fails before the tunnel is up. | Domain logon from home, with no tunnel to wait for. |
| A laptop in a plant | Group Policy applies only when someone remembers to connect. | Group Policy on a laptop in a plant, on the same outbound path. |
| Reaching a server | RDP behind a port forward, or a jump host on a public IP. | RDP with no port forward, and nothing published. |
| Signing in to applications | An identity vendor, kept fed by a directory sync. | Single sign-on on the directory you already run. No hybrid join. |
| Proving what happened | Access logs collected from four consoles at audit time. | Access, session and admin events in one place, aligned to CERT-In reporting. |
| Internet access for remote staff | Filtered at the office, unfiltered once the laptop leaves it. | The same URL and category policy, wherever the laptop connects from. |
| A vendor who needs one application | A VPN account, and a whole subnet to trust them on. | Access to the one application, with everything else out of reach. |
Four consoles, four vendors, four attack surfaces, or one.
Head office, home, a branch or a plant. One outbound path, the directory you already run, and nothing published to the internet.
Five questions that actually disqualify. Your answers stay in this browser.
Answer all five to see where to start.
You run Active Directory on your own servers today.
Remote or multi-site users need domain resources, not just email.
You rely on a VPN, a port forward or a jump host to reach machines.
You own the IT or the security decision.
You can run a pilot on real endpoints, not a lab.
Three ways in. Each one ends with something written down.
No per-user identity fee. Priced per deployment, so the teardown below is the fastest way to a number.
A pilot with the success criteria agreed first: domain logon from home, Group Policy applied on a remote laptop, a file share that works, RDP with no public port, and MFA on the same identity.
14 days
We add up the VPN, the identity vendor, the MFA vendor and the remote access tool you run today, against one deployment. Your figures, not ours.
60 min
We look at Active Directory, remote access and the branch links, and you leave with a one page verdict: keep the VPN, move to Entra, or run the overlay.
45 min
Kerberos, LDAP and SMB travel from the client to your Domain Controller inside the encrypted overlay, as if both were on the same LAN. Nothing is published, and nothing is handed to a cloud identity provider.
No. ControlIT does not require hybrid join or a directory sync, and it does not replace the directory you run. If you already use Microsoft 365, nothing about that changes.
Wherever you want it to. Computer Port can host the control plane and hand your team the console, or stand it up on infrastructure you nominate so it never leaves your estate. The product and the architecture are the same either way; only the hosting decision changes.
Local users keep local Active Directory, local shares and cached logon. Remote access over the overlay waits for the path to return: the same failure domain as a WAN link today, without a concentrator to fail first.
Access events, admin actions, sessions and configuration changes are recorded against your deployment, with retention you agree, and reporting aligned to CERT-In requirements.
Tell us what your endpoints, sites and directory look like today. We will tell you what the overlay would change, and what it would not.