Can zero trust be saved?

Graham Cluley Security News is sponsored this week by the fab folks at Kolide. Thanks to the great team there for their support!

Right now, “Zero Trust” is in serious danger of becoming an empty buzzword. The problem isn’t just that marketers have slapped the Zero Trust label on everything short of breakfast cereal–it’s that for all the hype, we don’t seem to be getting any safer.

At the heart of Zero Trust is a good idea, but the way most companies execute that idea is incomplete. Specifically, most security practitioners forget that device compliance is a crucial element of Zero Trust.

Think about it: your identity provider can ensure that only known devices access your company’s apps, but just because you recognize a device, doesn’t mean it’s in a secure state. A malware-infected laptop running an outdated OS can’t exactly be “trusted.” And you can’t count on MDMs to achieve total compliance. Things like unencrypted access credentials are out of their reach, not to mention Linux devices writ large.

Kolide solves the device compliance element of Zero Trust for companies that use Okta.

Our premise is simple: if an employee’s device is out of compliance, it can’t access your apps.

Kolide’s unique approach works with Okta to make device compliance part of the authentication process. If a device isn’t compliant, users can’t log in to their cloud apps until they’ve fixed the problem. And instead of creating more work for IT, Kolide provides instructions so users can get unblocked on their own.


Device blocked

Kolide works across your Mac, Windows, and even Linux devices, with mobile support coming soon. Our lightweight agent complements your existing tools, brings a lot of compliance issues into scope and under control, and can complete your Zero Trust picture.

>> Learn more and see the product in action.

If you’re interested in sponsoring my site for a week, and reaching an IT-savvy audience that cares about computer security, you can find more information here.