Skip to content

DriveLock Product Feedback & Ideas

← DriveLock & idgard Feedback Portal

Share your ideas for DriveLock.

Submit improvement ideas, explore existing ones, and vote on what matters most.

Teilen Sie Ihre Ideen mit DriveLock.

Reichen Sie Verbesserungsvorschläge ein, sehen Sie bestehende Ideen und stimmen Sie ab.

What is missing or could work better in DriveLock?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

6 results found

  1. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Others  ·  Admin →

  2. Richtlinienlöschung nach definierter Offline Zeit

    Hallo zusammen,

    Jetzt habe ich mit dem Parameter "Globale Einstellungen/Netzwerkprofile/Einstellungen/Regelmässige Online-Tet…" nochmal herumgespielt, um herauszufinden welche Richtlinie gelöscht wird.

    Leider wurden ALLE Richtlinien gelöscht. Nicht nur eine unbedeutende LEERE Richtlinie, was ich mir gewünscht habe, weshalb ich diesen Parameter auch extra NUR dort gesetzt habe.
    Somit ist der PC jetzt eigentlich absolut UNGESCHÜTZT

    Meine Frage wäre jetzt, gibt es eine Möglichkeit das löschen auf eine einzelne Richtline zu begrenzen??

    Denn die „Default Policy“ sperrt erstmal ALLES, diese Dürfte NIEMALS entfernt werden.

    Allerdings wäre es praktisch, wenn man z.B. nach 7 Tagen Offlinezeit die Richtlinie „Freigaben“ löschen könnte.
    Indem man den…

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Others  ·  Admin →

  3. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Others  ·  Admin →

  4. Powershell support for drivelock.Exe

    Please fully support (and document) drivelock.exe command line from PowerShell "Start-Process" command along with "ArgumentList". Current the Arguments from ArgumentList Option are not always accepted, for any available Arg. This is very usefull for example for deployment framework like SCCM or PSAPPDeployToolkit.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Others  ·  Admin →

  5. Übertragung des Inventars und der Ereignisse ans Backend

    Aktuell wird das Inventar JSON-formatiert in einem ZIP Archiv Base64 codiert übertragen. Um Manipulation zu vermeiden wäre eine signierte Übertragung sinnvoll

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    released  ·  0 comments  ·  Others  ·  Admin →

  6. 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 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Others  ·  Admin →
    released  ·  AdminAndreas Fuchs (Product Management, DriveLock SE) responded

    Today, 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.

  • Don't see your idea?

DriveLock Product Feedback & Ideas

Categories

Feedback and Knowledge Base

(thinking…)