DriveLock Customer Forum
Information
124 results found
-
MQTT (Port 8883) using an 30years SelfSigned Certificate
MQTT Port 8883 is using an 30years (running time) SelfSigned Certificate, which will be not replaced by ChangeDesCert.exe
Please implement a Feature within ChangeDesCert.exe tool that
MQTT Port 8883 will use the same SSL certificate, used by the other DES Server TCP Ports (6667 and 4568)Our Company Security Audit (vulnerability scan) detected the Port 8883 with this old SelfSigned Certificate behind.
3 votesThis feature request will be part of the 24.2 release
-
Web-Interface - Computer-View - Related Objects - "Alerts" missing
I miss the possibility to see or jump to computer related EDR-Alerts when accessing a Computer object.
Under "Related Objects" or below "Events" it woudl be nice to jump directtly into a view of computer-related alerts.
Shouldn't be too hard to implement - thanks :-)
5 votesPart of 2025.1
-
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 votealready possible
-
Defender management / Send e-mail alert from the server-side
I would like to receive an e-mail alert when a "Severe" Defender-event is fired. This might be possible to be done via SMTP on the agent/client which seems a little odd in 2023.
Such E-Mail-Alerts should be configurable for certain events on the server-side (Web-Interface).
2 votes -
AppControl WhileList rules
New AppControl WhileList rules, created from Events (from DOC Event Report) should not only go
hardcoded into the so called "Permanent unlock policy", but ist should
be also possible to define another (existing) DriveLock Policy as a target for this rule.2 votespart of 24.1
-
Enable Filter/Searching in old Policy
Currently when you open a old Version of a Policy lots of options in a device collection are disabled. You can't filter or export the list.
Either being able to filter the list directly or being able to export it as a csv would help us tremendously to check what devices where in that older version.
Currently our workaround requires exporting the whole policy. Creating a new temporary Policy. Loading the settings from the exported policy. And then searching for our required information. Afterwards deleting the policy.1 vote2024.2
-
Seperate Permissions to Add / Delete Devices from a Device Collection
Currently in depth Whitelist rules can only be set in the Management Console. In there we mostly work with Device Collection. We set a rule with a certain behavior, people it affects, etc. and then connect it with a Device Collection. After that the main effort is in adding new devices to that Device List.
We would like to split the administrative load and have main administrators that set up rules and policies. And then we would like a seperate user group with limited permissions that can only add or remove devices from existing device collections. It is important for…
2 votesThis feature request will be included in the 24.1 release.
-
Would like an order for EDR Responses implemented
While merging two policies, both policies have created a response for the same event, the order in which these responses are actioned are currently at random, we would like to request that the policies be implemented in order.
To do this we would like to request that the policies are:
sorted by Numerical policy position order at RSOP, and for the policies to be executed by their Numerical policy position order.Kind Regards
1 vote23.2
-
Make inventory data acessible via REST API or oDATA interface
It would make it a lot easier to identify gaps between my AD computers and my DriveLock devices if there would be an API interface, either as oDATA or REST API implementation. While there is a way to export all these lists and view to CSV and import them into Power BI, connecting a live data source would be so much easier....
1 voteIt is already possible to get a list of computers by a DL API
In DOC goto Settings, then APIs, then Documentation
-
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 votesThis feature request will be part of the 24.2 release
-
The hardcoded 1440min Defender State Reporting should be configurable by policy
The DriveLock Agent sents the Defender state today (hardcoded) every 1440min to the DES.
We want to have it configurable over Policy Settings, to allow a more frequent Status Report
sent by the Agent to the DES, to get a more sufficient and useful view within the DOC.
Just manual registry Settings are not sufficient for us, we want to rollout a Defender reporting Interval of every 6hours
to all of our clients - configured by policy.5 votesSince version 2023.2, the interval is 6 hours and no longer 24 hours. In addition, the Defender add-on sends messages as soon as something happens on the agent (virus, pattern updated, ...).
-
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.
4 votesPart of 2025.1
-
Need a DriveLock REST API for use with PRTG Network Monitor.
We do need the DOC functionality as a REST API, as we want integrate some
views within our Network Monitor Tool "PRTG".
And once it is implemented, we do need a official REST API documentation.
For example, when we define a DOC View for Computers/Agents with heartbeat was more than4weeks ago, then we want to create a REST API call from it, to view them within our PRTG Monitor tool,
without the needs to login into DOC. Similar like it works with SentinelOne.1 votereleased since 2023.1
-
Want to have the DOC Standard View for "Unknown (>3w)" configurable.
We do need the DOC Standard View for all Clients "Unknown (>3w)" configurable
so we can define also a view for Agents whose last system heartbeat was more than1month, >3month, >6month, >9month and >12month ago; their status is unknown
1 vote2023.1
-
License in use view for cloud customers
We want to have a License in Use view (Cloud) same or similar way as it exist for DriveLock onPrem installations.
2 votesThis feature request will be part of the 24.2 release
-
Get Local Admin Password via DOC (Native Security)
It should be possible to retrieve the password of a user created via the OS management in the DOC and not only via the agent.
Maybe if the Trust to the AD gets lost, the user won´t be able to login to his computer anymore.
5 votes -
Allow multi-factor authentication (2FA/MFA) for DOC login
Drivelock is a security tool connected to the Active Directory.
It should be possible to have consoles with dual authentication (MFA).
For me it is mandatory to avoid an hacker to do what he wants.3 votes23.2
-
Ability to support two password protectors like Encryption2Go
please add for Bitlocker2Go the ability to support two password protectors like Encryption2Go.
Currently the product seems to offer the usage of an administrator password in combination with a user password.
Drivelock Support explained that currently only 1 Passwort Protektor is supported3 votesWith the release 2022.2 publicly available, the status of this idea is updated to "released".
-
operating system security should support conditional settings
Conditional settings cannot be used for firewall rules or local user/group configuration. It should be possible to differentiate definitions through conditional settings.
2 votesConfiguration filters are already available also for local users and groups settings as well as for firewall management settings.
-
Add a column for policy order in the computer config details view
Currently there is no option in the computer config details view of the DOC to have a look at the order of how the policies will be applied on a device.
I would suggest to add a column where you can see the order of the applied policies.2 votesWith the release 2022.2 publicly available, the status of this idea is updated to "released".
- Don't see your idea?