DriveLock Customer Forum
Information
25 results found
-
Support für Yubikeys 2FA DOC
Sehr geehrte Damen und Herren,
wir nutzen aktuell Yubikeys als 2. Faktor für unsere Admin PCs.
Das gleiche benötigen wir für das DOC.
Könnten Sie im DOC Support für Smartcards hinzufügen?
Die Yubikeys sind hier sehr viel praktischer, als die Token App.2 votes -
it should be possible to modify custom widget
once a widget is created , it is not possible to modify it. This should be changed
1 vote -
Policy Assignments via DOC should include full path of AD objects
Actually , policy assignment in the DOC only shows f.e the name of the OU but not the AD Path. For organization using the same OU Name but under different path it is not possible to identify which OU to choose. Other objects might have the same problem.
2 votes -
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 votes -
new computer attribut to identify location
thanks to MQTT implementation it is now possible to know in the DOC if computers are alive and to communicate with them whereever they are (LAN, intertnet, home, ...). It would be nice to have a computer attribute available in the DOC computer view to identify where the PC is. The policy definition "network location" could be used for this.
3 votes -
DOC Should integrate AD attributes first- and last-
For company using number as login name it is not easy for DOC admin to identifiy on which PC a user is working. The DOC should integrates in the views operation>computers and operation>users the AD attributes firstname and lastname in order to be able to quickly identify loginname with real user. The column chooser functionallity should of course offers this two new attributes to be shown.
3 votes -
Selectable positioning of the dialog box for user notifications of the agents
It would be helpful for the user if the agent user notification dialog could be moved to a selectable position. Currently, this pops up in the lower right corner.
On devices with visualizations for operation in the plant area, operation and acknowledgement buttons of the UI are blocked in this situation.
It would be convenient to define the positions left-up, left-down, etc. via configuration in the MMC or via integration of the handling of the window position in the agent as last-position-as-default.1 voteWe will pursue this idea further, taking into account the voting in this forum, among other aspects, before including it in the detailed product backlog for the next version.
-
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 voteCreating an API to access DriveLock information via DES is already part of our long-term issues roadmap.
-
Offline scan option for MS defender should be included in the list of actions in DOC
Actually the DOC offers for MS Defender scans: quick, full an drives. An additional option should be add to support the offline scan MS defender supports.
3 votesWe will pursue this idea further, taking into account the voting in this forum, among other aspects, before including it in the detailed product backlog for the next version.
-
DOC deployment installation option should support DriveLock groups
In the new DOC 21.2, it is possible to deploy new agent on computer. It would be very nice to be able to use drivelock groups here instead of a static list of PCs.
2 votes -
Multiselection in white list rules under devices is not possibe
In policy editor, it is possible to multi select WLR under drives in order to move them or delete them but it is not possible to do the very same thing in the devices category. It will be nice to have the same functionality.
2 votes -
API implementation
In order to enhance integration with workflow tools in a company to automate certain processes (f.e. update whitelists in DL policies, etc), it would be interesting to have available an API in DES
3 votesWe have already started to implement first architectural changes in our backend which are mandatory for such a feature set. These changes will be continued and introcuded step by step in the next releases.
-
DOC configuration options for agent status outdated policy
as soon as a new version of a policy is published, the computer status in the DOC change to Warning outdated policy. This should be configurable with either an offset ( policy version is not smaller than actual policy - offset ) or with a number of days ( new policy version exists since X days but still not deploy on the agent)
2 votesWe will investigate how this warning is generated and how and if we can changed this behavior in such way, that a warning for an agent is only shown, when it wasn’t able to update it’s assigned (newer) policy the first time or for a period greater than its heartbeat intervals.
-
DOC: Run commands on groups and multiple computers
Currently running commands can be done only on individual computers under DOC > Computers page. Suggesting to add the ability to issue commands on multiple computers under the same page mentioned above, as well as issue commands on group(s) under DOC > Groups page.
4 votesWe will pursue this idea further, taking into account the voting in this forum, among other aspects, before including it in the detailed product backlog for the next version.
-
DCC/DOC: Restart agent service via remote connection
Occasionally there will be a need to manually restart the main DL agent service (enforce policy update, etc.). Suggesting to add the possibility to perform agent service restart while connected remotely using DCC or DOC. This is to be restricted to specific admins/operators only.
5 votesWe will pursue this idea further, taking into account the voting in this forum, among other aspects, before including it in the detailed product backlog for the next version.
-
DOC: Configurable session timeout
DOC sessions will time out after a period of inactivity. This period should be configurable.
2 votesWe will pursue this idea further, taking into account the voting in this forum, among other aspects, before including it in the detailed product backlog for the next version.
-
DOC: Auto-refresh and auto-toggle dashboard
For SOCs and ability to display on big monitoring screens (SecOps style), DOC dashboards should have auto-refresh feature. Refresh intervals should be configurable (every 1 minute, 10 minutes, etc.). DOC dashboards should also have the ability to toggle between dashboard tabs every X amount of time (configurable).
3 votes -
Delete computers after x days of no activity/connection
Delete computers after x days of no activity/connection in the database (automatically/periodically).
Events should not be deleted.16 votesThis feature request has been estimated and added to the product backlog.
-
When I'm giving a presentation and presentation mode is active, I don't want any DriveLock messages to come up
When I'm giving a presentation and presentation mode is active, I don't want any DriveLock messages to come up. I want to be able to configure this centrally. The default setting is "No messages at all". And this must be a central general setting and not separately for each DriveLock module. With an extended possibility of this feature, the general switch can control the switches below it, if I want certain modules to show messages exceptionally after all, if I consider them important despite the presentation mode.
2 votes -
Identifying a computer using IP address (or some other unique value) vs hostname
In a customer environment where many computers share the same hostname (eg. machines in a large distributed convenience store infrastructure), it would be very useful to be able to register the computer via its IP address or some other unique value, instead of just relying on hostnames/FQDN. Perhaps a feature to allow the customer to select the IP address (or a unique agent registration ID) to be used in our management and operations consoles - without the need for scripting or a convoluted workaround.
7 votes
- Don't see your idea?