DriveLock Customer Forum
Information
9 results found
-
Offer the possibility to remove the "blur" effect in the PBA
It should be possible to remove the "blur" effect in the PreBoot Authentication.
For customers who, for example, store a background image with company data in case the device is stolen / lost, this is not practical.
The "Show Pre-Boot User Information Message" feature is not really useful here, as probably only a few people will click on the small message icon at the bottom right of the screen. Alternatively, of course, this feature could be reworked to make this more present.5 votes -
Persistant File Encryption
As a user I want to have files automatically encrypted when saved into a specific directory, but when I copy or move this file out of this directory it should stay encrypted until an authorized user explicitly stores a decrypted version or manually decrypts it.
4 votes -
BitLocker Protector Status
It should be possible to find / filter clients in the DoC for which the protector status of the BitLocker encryption has been disabled. Currently, clients with this status are displayed as OK / Green, although the devices might be vulnerable.
3 votes -
FDE: Option to remember last used username at PBA
It will be useful to have the possibility in PBA to allow saving/remembering the last used username so that user will only have to type the password. Make this an optional configuration.
3 votes -
Mobile Encryption Application (macOS): Encryption 2 Go Container not visible without enabling hidden files visibility
When a USB flash drive encrypted with DriveLock Encryption 2 Go (container.based) is plugged in on a Mac the encrypted container is not visible on the USB flash drive. Only the DriveLock Mobile App (MEA) for Windows and macOS is visible. So, users cannot add the container to MEA to open it.
Current workarounds:
- Enable hidden files in Finder with the following command: "defaults write com.apple.finder AppleShowAllFiles YES"
- Invoke the MEA via command line and pass the path to the container as argument.Both workarounds are not an option for regular users.
3 votes -
DUO MFA Compatibility
We use Cisco sDUO as MFA for Windows. Unfortunately, the compatibility in connection with the PBA is missing here and thus no users are synchronized automatically.
2 votesWe continue to collect other customer's votes for this idea.
-
Ability to enforce different password when changing BitLocker password
some users may prefer to have the ability to enforce different passwords when changing their BitLocker password. This additional layer of security can prevent unauthorized access to the encrypted data in case the original password is compromised
1 vote -
Support Imprivata credential provider
For synchronization of users/credentials and for a Windows SSO after successful authentication of the user at the DriveLock PBA, a connection of the DriveLock Credential Provider to the Credential Provider of the Imprivata Agent is required (Credential Provider Wrapper).
1 vote -
802.1x support for SSO in the PBA/Win-Login
Currently the Single-Sign-On method for the PBA or for Windows doesn't support port configuration of 802.1x.
That hinder us from using this feature.So I'd like to suggest implementing the support of a port configuration 802.1x to use the SSO in the PBA/Win-Login.
1 vote
- Don't see your idea?