Deep Security 11 has reached end of support. Use the version selector (above) to see more recent versions of the Help Center.

Verify that application control is enabled

For an overview of application control, see Lock down software with application control. For initial configuration instructions, see Set up Application Control.

When application control is enabled and has finished its initial software inventory scan:

  • The State field indicates "On" or "On, Blocking unrecognized software".
  • On Computers, the Status field changes from "Application Control Ruleset Build In Progress" to "Managed (Online)".
  • Events & Reports > Events > System Events will record "Application Control Ruleset Build Started" and "Application Control Ruleset Build Completed". (If you don’t see any logs, see Choose which Application Control events to log.)

To verify that application control is working:

  1. Copy an executable to the computer or add execute permissions to a plain text file. Try to run the executable.
  2. Depending on your enforcement setting for unrecognized software, it should be either blocked or allowed. Once application control has built initial allow rules or downloaded a shared ruleset, if any change is detected, it should appear in the Actions tab, which you can use to create allow and block rules (see Monitor new and changed software). Depending on your alert configuration, you will also see an alert if unrecognized software is detected, or if application control blocks software from launching (see Monitor Application Control events). The event should persist until the software change no longer exists, or until the oldest data has been removed from the database.

  3. Add an allow or block rule for your test software and then try again. This time, application control should apply your allow or block rule.
  4. If software is accidentally blocked because you've selected Block unrecognized software until it is explicitly allowed and the software isn't being recognized, the Reason column in application control event logs can help you to troubleshoot the cause.