iboss
“Being on the network should not prove anything about you.”
iboss Zero Trust SASE puts data, applications and services out of reach of attackers, while trusted people reach what they need from anywhere.
The model
NIST defined the architecture in Special Publication 800-207 and published a full implementation guide, SP 1800-35, in June 2025. This is settled territory now, not a trend.
Icon
No implicit trust, from anywhere
Being inside the network stops counting as evidence. Every user is verified before being granted access to any resource, every time.
Icon
The perimeter stopped existing
People work from anywhere and the applications moved too. A model built around a building and a VPN concentrator describes somewhere you no longer are.
Icon
Out of reach beats well defended
The useful distinction. Resources an attacker cannot see or route to are a different problem from resources they can reach but should not get into.
Icon
Verified per request
Access is a decision made continuously against current signals, not a door someone was let through at nine in the morning.
The platform
One platform covering the controls that used to be four separate products and three vendors, applied to traffic rather than bolted to devices.
Zero trust cloud security
The secure web gateway, applied to every user wherever they are working, with the same policy and the same logging as if they were sitting in the office.
Security Service Edge
The category name for delivering these controls from the cloud rather than from appliances you backhaul traffic to. SSE is the part of SASE that does security.
CASB
Visibility and control over the cloud applications in use, including the ones that arrived without anyone asking IT first.
Browser isolation
Risky content rendered somewhere that is not the user’s device, which also makes it a credible replacement for a VDI estate that exists only to contain a browser.
Data loss prevention
Control over what leaves, including exact data matching for the records you genuinely cannot afford to have walk out.
Malware defense
Inspection applied in the path rather than at the endpoint alone, so the decision is made before the file reaches the device.
A thing worth knowing
NIST is explicit that zero trust architecture is a set of concepts and principles, not a set of technical specifications that can be complied with. No product makes you zero trust, and anyone selling you one is telling you something NIST does not. What a platform like this does is make the architecture practical to implement.
The architecture
Most of this category requires you to send all traffic to the provider. If you still run applications on your own floor, that is a real cost worth understanding before you commit.
In the cloud
For the traffic that belongs there
Users working anywhere reach the service rather than your network, across a global footprint iboss puts at more than a hundred points of presence.
In your datacenter
For the traffic that does not
This is the part that distinguishes iboss from most of the category. The enforcement points are containerized, so the same service can run on your own floor.
Where it fits
Zero trust matters most where the network is flat, the users are scattered, or somebody outside the organization needs access to part of it.
Icon
Government and public safety
Federal agencies are directed to move to zero trust, and state and local bodies are being held to the same expectation by the people who fund them.
Icon
Credit unions and financial services
Members, staff and third parties reaching the same systems from different places, with examiners who will want the access decision explained.
Icon
Healthcare
Clinicians, contractors and connected devices on one network, where flat connectivity is exactly the condition an attacker needs to move sideways.
Icon
Education
Open by nature and impossible to lock down at the perimeter, which makes verifying the request the only control that actually holds.
Icon
Construction and distributed operations
Sites, trailers and partner firms that need access to some things and nothing else, for the length of a project.
Icon
Aviation and logistics
Workforces spread across locations and carriers, connecting from networks you do not own and cannot inspect.
Why LKMethod
The technology is the straightforward part. Deciding what gets verified, in what order, without stopping people from doing their jobs, is where these programs are won or abandoned.
Zero trust is an architecture project
It touches identity, the network path, the endpoint and the applications at once. That is the work we do, and it is why these programs stall when they are run as a product rollout.
We map the traffic before we change it
Which flows go where, what still lives on your own floor, and what breaks if it is suddenly inspected. Finding that out afterwards is how these projects earn a bad reputation.
We run it afterwards
Policy, exceptions and the steady drift that follows any rollout, managed by the people who designed it rather than handed to whoever has least on.
We are an architecture practice before we are a reseller. If the first useful step for you is identity or segmentation rather than an edge platform, that is what we will tell you to do first.
Start with what is reachable
If a single laptop on your network were taken this afternoon, how far could it get. We will map that with you and come back with the sequence we would follow, starting with whichever step buys the most.