TrustFlare Access · Problems it solves
Sign-in checks the person.
It does not check the device.
A password and an MFA code prove who signs in. They do not show which computer or phone is used. Here are six problems this causes.
Work laptop
On the listSign-in continues
Other laptop
Not on the listSign-in stops
01
A stolen password works on any device.
Sign-in checks the password and the MFA code, not the device. With both, an attacker signs in from their own laptop.
How Access fixes it
Access stops the sign-in when the device is not on your list.
02
Office network or VPN access says nothing about the device.
An unknown laptop on the office network can open work apps. A VPN user reaches apps with no device check.
How Access fixes it
With Access, apps and VPNs that use your SSO check the device.
03
Personal and contractor devices have no safe way in.
People do not let the company control their own laptops. So these devices get an exception and are never checked.
How Access fixes it
Access checks personal devices without reading files or running commands.
04
A lost laptop forces IT to block the whole account.
IT can block the person, but not one device. Then the employee cannot work from any device.
How Access fixes it
In the console, you remove only the lost device.
05
A device on the list can still have no disk encryption.
The list shows that the device is known. It does not show disk encryption or screen lock.
How Access fixes it
With strict control, you can require disk encryption and screen lock.
06
More security checks make work harder for people.
More passwords and codes slow people down. Then people look for ways around security.
How Access fixes it
Access uses the laptop's security chip, a fingerprint and the employee's phone. Sign-in gets safer and simpler.