Export (0) Print
Expand All

Monitor Application Usage with AppLocker

Published: April 19, 2012

Updated: June 1, 2012

Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2



This topic describes how to monitor application usage when AppLocker policies are applied in Windows Server® 2012 and Windows® 8.

Once you set rules and deploy the AppLocker policies, it is good practice to determine if the policy implementation is what you expected.

You can evaluate how the AppLocker policy is currently implemented for documentation or audit purposes, or before you modify the policy. Updating your AppLocker Policy Deployment Planning document will help you track your findings. For information about creating this document, see Creating Your AppLocker Planning Document. You can perform one or more of the following steps to understand what application controls are currently enforced through AppLocker rules.

  • Analyze the AppLocker logs in Event Viewer

    When AppLocker policy enforcement is set to Enforce rules, rules are enforced for the rule collection and all events are audited. When AppLocker policy enforcement is set to Audit only, rules are not enforced but are still evaluated to generate audit event data that is written to the AppLocker logs.

    For the procedure to access the log, see View the AppLocker Log in Event Viewer.

  • Enable the Audit only AppLocker enforcement setting

    By using the Audit only enforcement setting, you can ensure that the AppLocker rules are properly configured for your organization. When AppLocker policy enforcement is set to Audit only, rules are only evaluated but all events generated from that evaluation are written to the AppLocker log.

    For the procedure to do this, see Configure an AppLocker Policy for Audit Only.

  • Review AppLocker events with Get-AppLockerFileInformation

    For both event subscriptions and local events, you can use the Get-AppLockerFileInformation Windows PowerShell cmdlet to determine which files have been blocked or would have been blocked (if you are using the audit-only enforcement mode) and how many times the event has occurred for each file.

    For the procedure to do this, see Review AppLocker events with Get-AppLockerFileInformation.

  • Review AppLocker events with Test-AppLockerPolicy

    You can use the Test-AppLockerPolicy Windows PowerShell cmdlet to determine determine whether any of the rules in your rule collections will be blocked on your reference computer or the computer on which you maintain policies.

    For the procedure to do this, see Test an AppLocker Policy by Using Test-AppLockerPolicy.

For both event subscriptions and local events, you can use the Get-AppLockerFileInformation Windows PowerShell cmdlet to determine which files have been blocked or would have been blocked (if the Audit only enforcement setting is applied) and how many times the event has occurred for each file.

Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.

noteNote
If the AppLocker logs are not on the local computer, you will need permission to view the logs. If the output is saved to a file, you will need permission to read that file.

  1. Open a Command Prompt window.

  2. At the command prompt, type PowerShell, and then press ENTER.

  3. Run the following command to review how many times a file would have been blocked from running if rules were enforced:

    Get-AppLockerFileInformation –EventLog –Logname "Microsoft-Windows-AppLocker\EXE and DLL" –EventType Audited –Statistics

    noteNote
    For an event subscription, specify the path to the forwarded event log for the Logname parameter.

  4. Run the following command to review how many times a file has been allowed to run or prevented from running:

    Get-AppLockerFileInformation –EventLog –Logname "Microsoft-Windows-AppLocker\EXE and DLL" –EventType Allowed –Statistics

When AppLocker policy enforcement is set to Enforce rules, rules are enforced for the rule collection and all events are audited. When AppLocker policy enforcement is set to Audit only, rules are only evaluated but all events generated from that evaluation are written to the AppLocker log.

Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.

  1. Open Event Viewer. To do this, click Start, type eventvwr.msc in the Search programs and files box, and then press ENTER.

  2. In the console tree under Application and Services Logs\Microsoft\Windows, double-click AppLocker.

AppLocker events are listed in either the EXE and DLL log, the MSI and Script log, or the Packaged app-Deployment or Packaged app-Execution log. Event information includes the enforcement setting, file name, date and time, and user name. The logs can be exported to other file formats for further analysis.

See Also

Other Resources

AppLocker Overview

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft