BlokSec
BeyondTrust Endpoint Privilege Management for Windows and Mac pairs powerful least privilege management and application control capabilities to provide preventative endpoint security. Implement zero trust controls and benefit from advanced protection against lateral movement, ransomware, malware, and insider threats.
BlokSec provides BeyondTrust users with a frictionless experience using no password or response code, while also providing the highest levels of authentication and identity assurance through the use of zero-knowledge proofs to further complement the zero trust controls provided by BeyondTrust Endpoint Privilege Management for Windows and Mac. BlokSec also provides the benefit of tamper-proof audit logging through the use of an immutable ledger allowing system administrators to confidently review elevation request history.
For more information about BlokSec, see https://bloksec.com/.
Prerequisites
- BeyondTrust Endpoint Privilege Management (EPM) instance
- BlokSec instance
- Users enrolled with BlokSec mobile app
EPM includes in-policy multifactor authentication or step-up authentication, which needs to be configured to point to a BlokSec instance.
Create an EPM app from a template
- Create a new app from template.
- Select the BeyondTrust Endpoint Privilege Management template.
- Set the Token Endpoint Auth Method to None, and then click Submit.
- Click the Generate App Secret button.
- Make note of the Application ID. This is the Client ID used in the EPM's identity provider settings.
Configure EPM
- Access the Messages tab in the Policy Editor and click Identity Provider Settings.
- Provide the BlokSec Issuer ID and Application ID as the Client ID.
- Click Save the Settings.
- Select the message you want to configure for BlokSec and check the box Verify their identity through an Identity Provider.
Test the integration
Now we can use the test user and a test workstation to make sure the integration is properly configured.
- When a user is requesting elevation, they are redirected to a browser (the default set by the user) to authenticate through BlokSec, using their saved credentials on the workstation.
- A push notification is sent to the mobile app to authenticate the user.
- The user can click OK on the Reason Required message after BlokSec authentication.
- Next the requested elevation (printer driver .msi) is approved, and the executable starts with elevated permissions. The user is never elevated.
Updated 3 days ago