DriveLock Customer Forum
Information
90 results found
-
Nicht beenden Modus bei SW-Verteilung
Wir würden gerne den nicht beenden Modus aktivieren, damit keine User oder Admins lokal die Drivelock Dienste beenden können. Da wir eine Software Verteilung nutzen, ist dies aktuell nicht möglich. Wäre es möglich diese Option so zu erweitern, dass die Agent Updates trotzdem funktionieren, ohne dass wir gezwungen sind die Verteilung von Drivelock zu nutzen?
1 voteToday, you can configure the unstoppable mode as a conditional setting in the policy. To do this, proceed as follows, for example: Define a dynamic group to a registry value. Create a config filter in the policy that filters for this dynamic group. Then configure the unstoppable mode as a conditional setting based on this config filter. On the DriveLock side, that's it.
The software distribution can now control the unstoppable mode and stop the DriveLock service by temporarily setting the registry value followed by an UpdateConfig.
In addition, DriveLock Application Behavior Control can ensure that only the software distribution is allowed to set this registry value. The latter requires the AC module.
-
Freigabe von Skripten in der Application Control
Es sollte möglich sein, bestimmte Skripte durch die Application Control freizugeben. Rein generell soll es Usern ja lieber nicht möglich sein die cmd.exe oder Powsershell.exe auszuführen. Teilweise ist dies aber für einige Programme erforderlich, sodass bestimmte Skripte ausgeführt werden müssen. Diese Skripte liegen unter fest definierten Pfaden auf Servern oder lokal) und können durch die User im Normalfall nicht bearbeitet werden. Zudem wäre es möglich, Powershellskripte zu signieren und das dazugehörige Zertifikat + Pfadangabe würde so zu einer erhöhten Sicherheit bei der Freigaberegel beitragen. Also eigentlich wie bei einer Datei-Eigenschaftsregel oder meinetwegen eine Erweiterung der Datei-Eigenschaftsregeln durch Angabe von Skripten
1 voteWhat is already possible today is authorization for individual scripts. In addition, you can build rules that check whether a parameter following PowerShell, for example, is permitted or not. This is possible with AC or Application Behavior Control (ABC).
-
DOC Companion should be part of ALF special rule DriveLock
Even if a "DriveLock" special rule is created to allow drivelock components to runf doc-companion is blocked by AC. DOC-copanion online and offline installer should be include into the special Drivelock-Rule.
3 votesSince 2023.2 the installed doc companion (not the one downloaded by the user) is now included in the "installed drivelock components" special ac rule
-
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 -
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
-
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, ...).
-
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
-
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".
-
DriveLock Bitlocker with PBA - Autologon without a user
After the DriveLock Bitlocker installation with PBA, the PBA screen also appears if no user has previously logged on.
The DriveLock PBA should be skipped until the first Windows User has logged on.
2 votesWith the release 2022.2 publicly available, the status of this idea is updated to "released".
-
Preinstall DOC Companion for All Users on a computer
Currently the DOC Companion can only be installed, when the user is also local admin on his machine.
But it's a really good security recommendation to separate users internet activities from admin tasks.
So we'd suggest to have an install procedure, that can be started from an admin command line or via a software distribution system.Add a configuration option to prevent the download/start of DOC_Companion.exe.
2 votesWith the release 2022.2 publicly available, the status of this idea is updated to "released".
-
SSO to DOC for legacy AD accounts
Windows with pass-through authentication.
Either using NTLM / Kerberos or SAML / ADFS (SSO)2 votesWith the release 2022.2 publicly available, the status of this idea is updated to "released".
-
Anonymization of personal data in DOC views
Data related to a single person (for example, user names or computer names) should only be visible in any DOC view, if the anonymization has been manually deactivated and if either the current user has a special permission which is allowing to view this data or a second user with appropriate permissions has logged in additionally (four-eyes principle).
0 votesWith the release 2022.2 publicly available, the status of this idea is updated to "released".
-
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 votesThe DriveLock backend already has a very comprehensive API and is extensively documented. We are constantly working on the extension.
- Don't see your idea?