2 results found

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

2. SB Freigabe auf konkrete Regeln in AC beschränken

   Die SB-Freigabe sollte für die Module mehrfach hinzufügbar sein und in AC sollte dies auf konkrete Regeln eingrenzbar sein, damit z. B. nur eine Regel, die z. B. den Datei-Upload von Browser verbietet deaktiviert werden kann und nicht die komplette AC.
   Weiterhin wäre die Umbenennung der SB-Freigabe im Taskbar-Informationsbereich für ein besseres Verständnis der Endnutzer sinnvoll, so dass man dies z. B. als „Upload entsperren“ oder ähnlich benennt. Wer dies selten nutzt, wird nicht wissen was mit SB-Freigabe gemeint ist, da Anleitung beim Endnutzer auch oft nicht gelesen werden…

   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  ·  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
   on the roadmap  ·  AdminAndreas Fuchs (Product Management, DriveLock SE) responded

   I don’t think a temp unlock based on a rule is a good idea. The end user does not know what else is allowed or blocked when a rule is temporarily disabled.

   If we are able to support temp unlocks for binaries at some point, the Unlock UI could also show applications that were unable to perform certain actions because of ABC, which could then be temporarily allowed.