DriveLock Product Feedback & Ideas
Share your ideas for DriveLock.
Teilen Sie Ihre Ideen mit DriveLock.
5 results found
-
Reporting of 651 Events
Even if 651 events are configured to be reported, they do not show up in the Windows Event Log or the central DES-Log. These events only show up in logs once an ABC-Rule rule is created that:
- Monitors the relevant Skript Executions
- Is configured to generate events when DriveLock approves the Skript executionsThis behavior of DriveLock is not documented anywhere.
All other events that I have come across don't work this way and get reported if they are appropriately configured in the "Events & Alerts" section of the policy. The additional ABC-Rule seems to be only necessary…
3 votesThank you for your feedback.
The current behavior is intentional: Events & Alerts defines how an event is handled once it has been generated. For allowed Application Control access, event generation must be explicitly enabled via an ABC rule.
We agree that this behavior is not sufficiently clear in the documentation. Our documentation team will update the relevant documentation accordingly.
We will therefore close this idea.
-
More option for ALF local learning ending time
Actually, the setting for the local learning process time can be configured by days. It would be helpfull to be able to stop the process manually (DOC and drivelock.exe) and to have the option to end the learning process after the first reboot.
The idea behind this is to scan the drive after the OS installation, give some time to the IT departement to install softwares and stop the process before the PC is given to the user either manually or after a reboot.
2 votesThe field 'Duration ...' in the Policy Editor refers to ABC, but not to AC. However, you can start the learning process for the local whitelist for AC later using the setting above: set 'Start learning' to 'Disabled' and trigger the learning process later via a remote task or through the eTray icon (user). This might be the solution for both the UserVoice entry and the incident.
-
Freigabe von Softlinks (via mklink erzeugt)
Bei der Freigabe von Pfaden werden keine Softlinks (via mklink erzeugt) berücksichtigt. Hilfreich wäre eine Ausnahme für Softlinks (via mklink erzeugt) als Ausnahme zu definieren, während der Ursprungspfad per WL Regel gesperrt bleibt.
1 voteThank you so much for your suggestion regarding the allowance of soft links created via mklink.
Our system currently resolves paths upon access, meaning we ultimately only see the resolved path, not the soft link itself. As a result, we're unable to differentiate or specifically allow soft links without impacting existing security mechanisms. Therefore we unfortunately have to reject this request.
We really appreciate your understanding and are here if you have further questions or feedback.
-
DriveLock Linux Agent should be able to send all existing events to other external systems via email
As an administrator I want to let the Linux Agent send all drivelock agent events also to external systems.
It should work similar like DriveLock Agents for Windows OS.
If we can define a priority, we would like to see the following priority order (for implementing):
1) SMTP (email, supporting TLS/SSL)
2) SNMP1 voteplease see comment
-
Policy "Export ..." Button, inside of the "Properties..." Popup
Create an easy policy export button inside of the properties popup
1 voteToday you already can export any opened policy easily:
1. Click on the top-most node on the left side in the MMC
2. Click on the “Export policy…” button on the right side
- Don't see your idea?