77 results found

1. Cleanup deleted Accounts

   Hi,
   Currently, there is no automatic cleanup within the DOC.
   There are users within the DOC who have the “Active Directory Account” type. As soon as Drivelock's sync with AD detects that this account no longer exists, the account should also be deleted within the DOC, with a corresponding log entry.
   This would help keep the environment clean without the need for custom scripting.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  UX / UI / DOC  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Collect "DLL started" and "DLL blocked" events without blocking them while Application Control Whitelisting of EXE files is still active

   In a customer environment, where only the launch of EXE files is controlled by DriveLock, it is currently not possible to collect information about how Application Control would handle DLLs with the current policy set.
   In order to collect "DLL started" and "DLL blocked" events, you have to change the "Scan- and Block-Mode" to include DLLs. This forces you to choose between Simulation Mode, which also affects the handling of EXE files, or "Active"-Mode, which would block all unknown DLLs immediately.
   We would appreciate a feature that allows us to determine which DLLs would be blocked in our environment before activating the feature and without degrading our security posture by disabling the whitelisting of EXE files.

   In a customer environment, where only the launch of EXE files is controlled by DriveLock, it is currently not possible to collect information about how Application Control would handle DLLs with the current policy set.
   In order to collect "DLL started" and "DLL blocked" events, you have to change the "Scan- and Block-Mode" to include DLLs. This forces you to choose between Simulation Mode, which also affects the handling of EXE files, or "Active"-Mode, which would block all unknown DLLs immediately.
   We would appreciate a feature that allows us to determine which DLLs would be blocked in our environment before… more

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   on the roadmap  ·  0 comments  ·  Application Control  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Reports should also have a Excel export choice.

   I've now seen a few clients who want a report in XLSX format. That they can forward to another department for automating some feature of the rollout software. As far as I know, only PDF is possible, but I could be wrong, of course.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Others  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. SQL-Authentifizierung zwischen DES-Service und AWS-RDS-SQL

   Es sollte eine SQL-Authentifizierung zwischen DES-Service und AWS-RDS-SQL möglich sein. AWS-RDS hat keine Domäne-Anbindung, darum ist Windows-Authentifizierung dort nicht möglich. Aktuell versucht DES Service die Anmeldung bei AWS-RDS-SQL mit Windows-Credentials und verursacht Fehler.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Others  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   planned  ·  AdminAndreas Fuchs (Product Management, DriveLock SE) responded

   Will be part of 26.1 Patch 1 (after upcoming 26.1)

5. Missing Email-Server via Port 465 SMTPS (provide Port 465 as optional)

   Missing Email-Server via Port 465 SMTPS. Solution: provide Port 465 SMTPS as optional. Company-Appmailer requires SMTPS-Protocoll for encrypted mails and doesnt allows STARTTLS via Port 587.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  UX / UI / DOC  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   planned  ·  AdminAndreas Fuchs (Product Management, DriveLock SE) responded

   Will be part of 26.1 Patch 1 (after upcoming 26.1)

6. Automatic alerts for expiring API-Keys and Information regarding last API-Key Usage

   We need the capabilities to send out notifications about API keys which are expiring in X days or weeks.
   Also an overview about the last usage of an api key would be very helpful.
   These two options would help us to fulfill compliance and security standards.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  0 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Verbesserung der Barrierefreiheit von Windows-Toast-Benachrichtigungen in Application Control und Port Control

   Im Rahmen der Barrierefreiheitsanforderungen möchten wir einen Feature Request für DriveLock Application Control und Port Control einreichen.

   Aktuell werden die Windows-Toast-Benachrichtigungen von DriveLock nicht von Screenreadern (z. B. NVDA) vorgelesen, sofern die Benachrichtigung nicht im Fokus ist.

   Dadurch können sehbehinderte oder blinde Anwender sicherheitsrelevante Benachrichtigungen nicht wahrnehmen.

   Wir wünschen uns daher eine Anpassung der Implementierung, sodass die von DriveLock erzeugten Windows-Toast-Benachrichtigungen von gängigen Screenreadern zuverlässig erkannt und vorgelesen werden, ohne vorher durch ein Klick das Fenster in den Fokus gerät.

   Die Umsetzung dieses Anliegens ist für uns von hoher Priorität. Daher würden wir uns über eine Einschätzung freuen, mit welchem zeitlichen Rahmen wir rechnen können.

   Im Rahmen der Barrierefreiheitsanforderungen möchten wir einen Feature Request für DriveLock Application Control und Port Control einreichen.

   Aktuell werden die Windows-Toast-Benachrichtigungen von DriveLock nicht von Screenreadern (z. B. NVDA) vorgelesen, sofern die Benachrichtigung nicht im Fokus ist.

   Dadurch können sehbehinderte oder blinde Anwender sicherheitsrelevante Benachrichtigungen nicht wahrnehmen.

   Wir wünschen uns daher eine Anpassung der Implementierung, sodass die von DriveLock erzeugten Windows-Toast-Benachrichtigungen von gängigen Screenreadern zuverlässig erkannt und vorgelesen werden, ohne vorher durch ein Klick das Fenster in den Fokus gerät.

   Die Umsetzung dieses Anliegens ist für uns von hoher Priorität. Daher würden wir uns über eine Einschätzung freuen, mit welchem… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Application Control  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Feature Request – Native Let's Encrypt / ACME-Integration für automatisierte Zertifikatsrotation (90-Tage-Zyklen)

   Beantragt wird die Implementierung einer nativen oder offiziell unterstützten Automatisierungsschnittstelle für das ACME-Protokoll (z. B. Let's Encrypt) zur automatischen Beantragung, Erneuerung und Bindung von SSL/TLS-Zertifikaten für den DriveLock Enterprise Service (DES) und das DriveLock Operations Center (DOC).

   DriveLock sollte den Prozess durch eine integrierte Automatisierungslogik übernehmen, die im Hintergrund nahtlos mit ACME-Clients wie win-acme interagiert oder einen nativen ACME-Client in den DES integriert.

   Eine robuste Umsetzung sollte folgende Kernfunktionen umfassen:

   Zertifikats-Beantragung & Renewal-Triggering: Ein konfigurierbarer Job innerhalb der DriveLock-Konsole, der (ähnlich wie win-acme per Scheduled Task) rechtzeitig vor Ablauf (z. B. an Tag 60) die Erneuerung anstößt.

   Unterstützung für DNS-01 und HTTP-01 Challenges:
   Da DriveLock-Server oft intern (ohne public Inbound-Traffic auf Port 80) betrieben werden, ist die Unterstützung der DNS-01 Challenge essenziell. Die Integration von API-Hooks (z. B. für Cloudflare, AWS Route53, Infoblox) ermöglicht die Validierung interner Hostnamen.

   Automatisches Service-Binding (Zero-Touch):
   Der kritischste Schritt: Nach dem erfolgreichen Import des Zertifikats in den Windows Certificate Store (Local Machine > Personal) muss DriveLock das Zertifikat automatisch anhand des Thumbprints oder Subject Alternative Names (SAN) identifizieren und an die entsprechenden Ports (DES, DOC, IIS) binden.

   Graceful Service Reload:
   Ein automatisierter, unterbrechungsfreier Neustart oder Reload der betroffenen DriveLock-Dienste, um das neue Zertifikat ohne manuelles Eingreifen des Administrators aktiv zu schalten.

   Alerting & Monitoring:
   Native Events in der DriveLock-Datenbank, falls ein ACME-Renewal fehlschlägt. Dadurch können Administratoren proaktiv über das Control Center oder per E-Mail gewarnt werden, bevor das Zertifikat tatsächlich abläuft.

   Native Integration (Bevorzugt): DriveLock implementiert eine C#-basierte ACME-Bibliothek (z. B. Certes) direkt in den DES. Die Konfiguration (Mailadresse für Let's Encrypt, Domain, Challenge-Typ) erfolgt zentral über eine Policy im DriveLock Control Center.

   oder

   Offizielles win-acme Plugin / Installations-Skript: DriveLock liefert ein offizielles PowerShell-Modul oder win-acme Post-Installation-Skript (.bat / .ps1) aus. win-acme erneuert das Zertifikat und ruft anschließend das DriveLock-Skript auf, welches das Re-Binding in der DriveLock-Konfiguration vornimmt und die Dienste neu startet.

   Nutzen für DriveLock und Endkunden
   Security-by-Default: Förderung von modernen Krypto-Standards mit kurzen Lebenszyklen (90 Tage) und perfect Forward Secrecy, ohne den Betriebsaufwand zu erhöhen.

   Betriebssicherheit: Massive Reduktion von "Outages" durch vergessene Zertifikatswechsel.

   Kostenreduktion: Kunden sparen sich den Erwerb kommerzieller SAN-Zertifikate sowie den personellen Aufwand für die manuelle Pflege.

   Wettbewerbsvorteil: Eine "Zero-Touch"-Zertifikatsverwaltung ist ein starkes Verkaufsargument gegenüber Mitbewerbern im Endpoint-Security-Markt.

   Beantragt wird die Implementierung einer nativen oder offiziell unterstützten Automatisierungsschnittstelle für das ACME-Protokoll (z. B. Let's Encrypt) zur automatischen Beantragung, Erneuerung und Bindung von SSL/TLS-Zertifikaten für den DriveLock Enterprise Service (DES) und das DriveLock Operations Center (DOC).

   DriveLock sollte den Prozess durch eine integrierte Automatisierungslogik übernehmen, die im Hintergrund nahtlos mit ACME-Clients wie win-acme interagiert oder einen nativen ACME-Client in den DES integriert.

   Eine robuste Umsetzung sollte folgende Kernfunktionen umfassen:

   Zertifikats-Beantragung & Renewal-Triggering: Ein konfigurierbarer Job innerhalb der DriveLock-Konsole, der (ähnlich wie win-acme per Scheduled Task) rechtzeitig vor Ablauf (z. B. an Tag 60) die Erneuerung anstößt.

   Unterstützung für DNS-01… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Choose modules/options which are allowed for temporary unlock

   We have a role-based setup in our company that allows the Helpdesk role to grant temporary unlocks in urgent situations. However, certain options and modules should not be accessible to this role.

   In particular, for Application Control, it is critical that the Helpdesk can perform only a standard Application Control unlock. The options under “Executable files to add to the local hash database”, specifically:

   Files written to the computer during the unlock period
   Executables (and DLLs) launched during the unlock period

   must not be available to the Helpdesk role. These capabilities should be restricted exclusively to the Administrator role.

   A possibility to choose which options are available for specific Roles or atleast in general would be great.

   Thanks :)

   We have a role-based setup in our company that allows the Helpdesk role to grant temporary unlocks in urgent situations. However, certain options and modules should not be accessible to this role.

   In particular, for Application Control, it is critical that the Helpdesk can perform only a standard Application Control unlock. The options under “Executable files to add to the local hash database”, specifically:

   Files written to the computer during the unlock period
   Executables (and DLLs) launched during the unlock period

   must not be available to the Helpdesk role. These capabilities should be restricted exclusively to the Administrator role.

   A… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Application Control  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Self Service

    Hi,
    when using Self Service for application control, we have communicated the following settings to our administrative users, when installing software.

    1) Start Self-Service before starting the installation proccess
    2) Disable Application Control during Unlock Period, Add Application launched... (checked), Executable files added to the local hash database: FIles written during unlock period (checked), Require user approval .... (checked)
    3) Timespan and reason given

    AppControl is now unlocked and the software will be installed

    When ending the Self Service of AppControl, a list of files is displayed, where the files can be selected from, which have to be added to the Local Has database.
    This list can be very long as there are not only the installed files included. All files, which Windows writes from system side during the unlock period are also included there.

    In this list, there is no option to
    a) resize the window itselt
    b) filter the list according to path for example
    c) select multiple succeeding entries with Control- or Shift Click

    You are only able to check each list entry one by one, which makes working with this very time consuming.

    I'd like to have the options a)-c) mentioned above added to the list of files, which are to be added to the local hash database.

    Kind regards
    Uwe

    Hi,
    when using Self Service for application control, we have communicated the following settings to our administrative users, when installing software.

    1) Start Self-Service before starting the installation proccess
    2) Disable Application Control during Unlock Period, Add Application launched... (checked), Executable files added to the local hash database: FIles written during unlock period (checked), Require user approval .... (checked)
    3) Timespan and reason given

    AppControl is now unlocked and the software will be installed

    When ending the Self Service of AppControl, a list of files is displayed, where the files can be selected from, which have to be added to… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Application Control  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Customizing Multiple-Line-Chart-Widgets

    Für eine übersichtliche Gestaltung eines Custom Dashboards sollte es möglich sein, Multiple-Line-Charts Widgets zu customizen.
    Beispiel UseCase wäre die Darstellung der Auslastung und Verteilung auf die einzelnen LinkedDES.
    Zweiter UseCase, wie veile Events von einem bestimmten Type oder ID sind über eine Woche aufgetreten.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  UX / UI / DOC  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Nach Beschreiben eines USB Datenträgers Datei sollte Datei lesbar sein

    Hallo,
    nach dem Beschreiben eines zuvor, an einer Index Scanstation gescannten USB-Wechseldatenträgers kann die Datei anschließend nicht mehr geöffnet bzw. angezeigt werden. Dadurch ist es derzeit leider nicht möglich, die eigene Datei auf dem Wechseldatenträger nochmals zu kontrollieren.

    Es sollte möglich sein, dass die Datei nach dem Beschreiben an einem sicheren PC weiterhin lesbar bleibt, solange der USB-Datenträger noch am PC angeschlossen ist.

    Bitte prüfen Sie dieses Verhalten nochmals.

    Vielen Dank im Voraus.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Device/Drive Control  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Direkter Link aus E-Mail-Benachrichtigung zum Event im DOC

    Direkter Link aus E-Mail-Benachrichtigung zum Event im DOC

    Beschreibung:
    E-Mail-Benachrichtigungen zu Sicherheitsereignissen enthalten derzeit keinen direkten Zugriff auf das zugehörige Event in der zentralen Management-Konsole (DOC).

    Anforderung:
    Bereitstellung eines direkten Links in der E-Mail-Benachrichtigung, der Anwender unmittelbar zum entsprechenden Event im DOC führt.

    Nutzen:

    Schnellere Analyse und Reaktion auf Ereignisse
    Reduzierter manueller Suchaufwand im DOC
    Effizientere Bearbeitung durch Support und Administratoren

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Application Control  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Ability to Filter what syslog events I want to forward

    I know I can enable my events to be forwarded to a remote Syslog server, but we're missing an option to filter what events will actually be sent, at the source, in this case our DES tenant.
    That would be important for narrowing the data ingestion in our XDR, and also would enable us to better manage alerts and block incidents directly in MS Defender for example, in our case is only for Blocked Processes, eventId 473.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  UX / UI / DOC  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Erstellung und speichern von eigenen Filter im Inventar

    Ich möchte im DOC unter Inventar/Computer eigene Filter erstellen und abspeichern, damit ich diese bei Bedarf abrufen kann. Die Ergebnisse sollten sich optional als Tabelle exportieren lassen.
    Die vorhandenen Filter sind an dieser Stelle nicht besonders hilfreich.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  UX / UI / DOC  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. temporary unlock

    When a user wants to request unlock of a usb connected device, there are two options, which could be selected from the unlock dialog.

    In the dialog, which appears after selecting "Request unlock" we have either the "Locked drives" or "Locked drives" with a "Request unlock" link on the right side. This requests a temporary unlock.
    With the temporary unlock link selected, no information about the connected device is transferred into the DOC.

    If a device is connected it is shown in one of these two boxes, also with a "Request unlock" link on the right side. When the user clcks on this link on the right side of the device entry, the unlock is requested for this special device.
    Only in this case, the device information is sent to the DOC.

    We do not want our users to request temporary unlocks in DriveLock, we only want the users to request unlocking for the connected device.

    It should be possible either in DOC or DMC to disable the temporary unlock link for the users and only the unlock link near the device should appear.

    When a user wants to request unlock of a usb connected device, there are two options, which could be selected from the unlock dialog.

    In the dialog, which appears after selecting "Request unlock" we have either the "Locked drives" or "Locked drives" with a "Request unlock" link on the right side. This requests a temporary unlock.
    With the temporary unlock link selected, no information about the connected device is transferred into the DOC.

    If a device is connected it is shown in one of these two boxes, also with a "Request unlock" link on the right side. When the user… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Device/Drive Control  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. DOC Berichte selbst anpassen/erweitern - USB Stick Whitelist Regeln

    Ich habe in den Kommentaren jeweils vermerkt, für was der zugelassene USB-Stick genutzt wird.
    Diese Information wollte ich gerne im wöchentlichen DOC Bericht "Kürzlich blockierte Laufwerke" mit ausgeben, damit ich direkt sehe wo welcher Stick genutzt wurde.
    Daher wäre die Anpassung der Berichte, um benutzerdefinierte Spalten hilfreich.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Others  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Unterschiedliche Informationen bei ähnlichen Ereignissen

    Wenn ich in den Ereignissen, z.B. Geräteereignissen die Einträge zu einem System ansehen, fällt auf das die Hardware ID bei Event 130 unter Parameter 2, bei Event 782 unter Parameter 3 eingetragen ist.
    Beim Geräte-Typ sind es Parameter 4 und 2.

    Dies macht eine Sinnvolle Auswertung/Suche eigentlich unmöglich.
    Hier wäre eine Bereinigung/Vereinheitlichung wünschenswert

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Others  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Erstelle Whitelist aus Software Repository

    Es gibt mittlerweile soviel portable Software bzw. Software die keine Installation benötigt.
    Aus diesem Grund kam der Folgende Gedanke auf

    Anbieten eines "Software-Repositorys" d.h. man bietet einen Share an und legt dort die freigegebene Software ab.

    Nun wäre es natürlich Smart wenn man in Drivelock bspw. einen UNC-Path angeben könnte und Drivelock schaut sich in einem einstellbaren Zeitrahmen also z.B. alle 2 Stunden diesen Share an und bildet für alles was dort liegt Whitelist-Regeln. Somit hätte man einen Katalog an Software der ohne Installation genutzt werden kann.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Application Control  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Implement for DOC the Drive Identification Files

    Please implement/migrate the feature “Settings for Drive Identification Files” in the DOC as well.

    https://www.drivelock.help/versions/2025_2/web/de/complete/content/devicecontrol/tasks/task_drivessetvolid.htm?Highlight=SD

    Having a split configuration between DMC and DOC for Device Control is very cumbersome, as it is often unclear where specific settings are configured.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Device/Drive Control  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating