Trust Is Not Granted.
It Is Continuously Earned.
Authentication determines whether access begins. SAFE continuously evaluates whether trust should continue.
Three different questions.
SAFE continuously evaluates whether the combination of user, device, session, application, network and behavior should still be trusted.
Answered once, at the start of a session, and then inherited by everything that follows it.
Answered against a checklist, and true until the next time something checks.
Answered continuously across identity, device, session, application, network, behavior and enterprise context.
Not the advertising kind.
The word carries baggage. In the consumer web, fingerprinting usually means covertly identifying an individual across sites in order to track and monetize them. That is not what SAFE does, and the distinction is worth being explicit about.
SAFE builds a security-oriented, continuously evolving trust representation from the unique combination of device, user, application, network, session and behavioral conditions present in an enterprise environment. Its purpose is to answer one question — should this combination still be trusted right now — for the organization that deployed it.
Seven domains, evaluated in combination.
Who the user is, how they authenticated and whether that assertion still holds.
Integrity, posture, configuration and management state of the endpoint itself.
Whether the active session still behaves like the session that was authorized.
What is running, what it is doing and whether it should be permitted to.
The path the device is using and how much that path can be trusted.
Deviation from the pattern established for this user and this device.
Policy, role, data sensitivity and the wider organizational context.
From signal to protection.
See Autonomous Endpoint Defense in Operation.
Protect every endpoint. Continuously establish trust. Respond at machine speed.