Why Zero Trust Matters: A Successful Login Should Not Be Enough
An employee signs in with a valid company account. The password is correct. The device connects.
Should that be enough to access company data?
The laptop might not have checked in with device management for weeks. The user might still have permissions from a previous role. Someone else might be using the session.
A successful login doesn’t answer any of those questions.
That’s where Zero Trust comes in.
NIST describes Zero Trust as an approach that removes implicit trust based solely on network location or device ownership. Being in the office, connected through a VPN, or using a company laptop shouldn’t automatically grant access.
Access needs to be justified.
Microsoft defines three core Zero Trust principles:
Verify explicitly. Check identity, device condition, the resource being requested, and the context.
Use least privilege. Give people only the access they need, for as long as they need it.
Assume breach. Plan for an attacker already being inside. Limit what they can reach and the damage they can cause.
These principles should influence daily IT decisions.
Does this user need permanent admin rights? Should an unmanaged laptop download sensitive files? Why does a contractor still have access after the assignment has ended?
Those are practical questions. Answering them is part of implementing Zero Trust.
Consider an employee account compromised through phishing. What can the attacker reach?
Old group memberships, broad permissions, and unrestricted connectivity can expose far more than the employee needs for their job. Access scoped to individual resources helps contain that exposure. NIST’s reference architecture emphasizes protecting those resources and limiting access to what users, applications, and systems need.
If this account were compromised today, how far could someone get?
The number of security products you’ve installed won’t answer that.
Device management helps fill in another part of the picture. Identity identifies the account requesting access. Endpoint management provides information about the device making the request.
You might require a managed laptop, encryption, and supported software before allowing access to sensitive data. But creating the policy is only the beginning.
Someone needs to maintain enrollment, investigate failed checks, resolve exceptions, and confirm that the policy applies to the right users and applications.
A laptop appearing in the management console doesn’t mean its information is current or that it meets your requirements. Access controls need reliable device information.
IT Asset Management belongs in this work too:
Who owns the device?
Who is responsible for it?
Is it still in use?
Has it been replaced, lost, or retired?
Does the assigned user still need access?
An asset register won’t tell you whether a device is healthy. It can tell you who should have it and where it stands in its lifecycle.
If a laptop is marked as retired but credentials associated with it remain active, someone needs to investigate. Connecting asset records, endpoint management, and identity processes makes those gaps easier to find.
Your last offboarding is a useful test.
Were the accounts disabled promptly? Were active sessions and application access addressed? Was the device recovered or protected through an appropriate process? Did someone confirm that everything was completed?
Role changes need the same attention. Moving to another team shouldn’t mean keeping all the old permissions and adding new ones.
Access that made sense six months ago might be unnecessary today. Departures and role changes should trigger a review and action.
To get started, pick one sensitive application or dataset. Define who needs access, which devices are allowed, what authentication is required, and who approves exceptions.
Test with a small group. Include recovery procedures so you know what to do when someone is incorrectly blocked. Then expand enforcement.
Track what changes: unnecessary privileges removed, unmanaged access identified, and how long it takes to revoke access after someone leaves.
Zero Trust matters because a valid account can still be misused, a company device can still be out of date, and approved access can become unnecessary. The work is in keeping those checks and controls effective as people, devices, and responsibilities change.
Can your IT team explain why a particular user, on a particular device, can access your most sensitive business data today?
If that’s unclear, start there.
ESENEL helps organizations connect IT asset visibility, endpoint management, and practical access governance. To discuss gaps in your environment, contact hello@esenel.eu.
Comments
Post a Comment