Skip to content

DriveLock Product Feedback & Ideas


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.

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

7 results found

  1. Inventory Daten dediziert löschen

    DriveLock sollte die Möglichkeit besitzen, Inventorydaten dediziert zu löschen. Hierbei sollten zwischen Drives / Devices / Applikationen usw. unterschieden werden können.
    In Kundenumgebungen die schon über mehrere Versionen hinweg bestehen, ist die Auswertung der Daten derzeit einfach zu unübersichtlich. DIe Möglichkeit den Rechner aus dem Operations Center zu löschen und danach das Inventar neu einzulesen ist m.E. nicht ausreichend.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Syntax-basierte Benachrichtungsregeln - DOC

    Aktuell können Benachrichtigungsregeln (E-Mail) im DOC nur auf Basis der Event ID getriggert werden.
    Sinnvoll wäre die Möglichkeit, innerhalb der ID auf spezifische Syntaxinhalte filtern und alarmieren zu können.
    BSP: EVENT ID 130 - The device HP LaserJet Pro M404-M405 was connected to the computer.;Device type: Media player.
    Alle anderen Events zur ID130 sollen dann keine E-Mail Benachrichtigung im DOC zur Folge haben.
    Filterung im Bereich der Eventgenerierung selbst, würde die ID nur einschränken. Es würden Informationen verloren gehen.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Ability to remove management audit events via Policy

    There are multiple events which are logged in the console, like Event-ID 910 (DriveLock Management Console started) which are not necessary. It would be good to be able to remove them with the DriveLock Management Console like the other events until Event-ID ~750

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Alert frequency based rule

    DriveLock should allow the creation of alert based on frequency and time. Ideally with boolean logic f.e:
    -if event happens (more¦less) X time within Y minutes (most important one)
    -if event happens between X am and Y pm
    -if event does not happen between X am and Y pm
    -if event happened at least X minutes after the last event
    -if event not happened after X minutes of the previous event

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. EDR new responses (email, snmp, ...)

    actually responses definition include Powershell, Batch, Command line, Awareness and taken picture. It should be extend to E-Mail, SNMP Trap and Web-hook. At least E-Mail should be implement. That way one could decide to send E-Mail based on filtered event.

    It is actually possible to send E-Mail for a complete event-type but not to define further condition under which the E-Mail should be sent ( user, folder, computer, etc, ...). Of course it is possible to write script but E-Mail is already there in the solution.

    It sould be although possible to restrict the action repetition if one action (f.e…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Include System Name in Email Alert Subject Line

    Improvement Suggestion: Include System Name in Email Alert Subject Line

    Currently, the subject lines of automatically generated email alerts do not include any indication of which computer system triggered the respective event. In order to identify the affected system, each message must be opened individually, which significantly reduces clarity and efficiency when handling alerts.

    Suggestion:
    It would be very helpful if the subject line of alert emails could be extended to include the name of the affected system. This would make it immediately visible in the email client whether recurring alerts are coming from the same system or if different…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. History diagrams showing the use of devices or applications over a period of time as line graphs

    It would be nice to have a set of diagrams showing the use of devices, applications or even other assets over a period of time, as line graphs. This would support risk evaluation showing trends or values different from an expected or usual trend.

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base