Strengthen Your Authentication Security With Secfense Microauthorizations. Protect access on every stage of the application journey with enforced authentication by either the user or the supervisor.


Modify Your Authentication/ Authorization Rules On Every Stage Of The User Journey Within The Application

Microauthorizations from Secfense make it possible to force the user to authenticate again every time he or she accesses some specific resources or wants to perform some specific actions within the protected application.

If Microauthorizations are in place Secfense takes over the communication and triggers one of two scenarios. In the Owner scenario, Secfense asks the user to re-authenticate. In the Supervisor scenario, Secfense asks the third party for authorization.

Two-factor authentication is known to be one of the best ways to protect against phishing however implementation was always a difficult part. Secfense being a security broker helped us solve the implementation problem. We were able to introduce various 2FA methods at once to work with our web applications.

Dariusz Pitala Head of IT, MPEC S.A.


Invisible Security Layer

Since User Access Security Broker from Secfense works as an invisible security layer, microauthorizations can be added and triggered anywhere within the application journey.

Microauthorizations in the Owner scenario

Microauthorizations in the Owner scenario introduce an increased level of granulation under the Principle of Least Privilege. This means the additional protection against attacks on a stolen active session or other attacks against an already logged-in user (including real-time phishing or malware).

Microauthorizations in the Supervisor scenario

Microauthorizations in the Supervisor scenario leave authorization of particularly sensitive resources requests in the hands of selected and trusted users.


Effortless Triggering And Use Of Microauthorizations

Microauthorizations only make sense when they are effortless for the user. That is why the recommended Microauthorizations setup is with the use of FIDO2 - the open web authentication standard.

In the case of microauthorizations in the owner scenario, the access to the protected resource requires the user to simply touch the cryptographic key or another local authenticator (like a smartphone with a fingerprint sensor or a laptop with infrared camera).

In the case of microauthorizations in the supervisor scenario, access to the protected resource within the application also requires extra authentication but this time it needs to be performed by the privileged user with higher authority (therefore = microauthorizations).

All events related to microauthorizations are logged in the secfense event log (or streamed to an external login system) and can be analyzed to detect anomalies.

Want to test out User Access Security Broker on your Testing Environment?

Testing enterprise solutions has never been easier. You can deploy and test a UASB demo within one day and learn all its mechanisms. Schedule your discovery call and learn how to register for your commitment-free demo.

Schedule Discovery Call