![]() Let’s take an example and use FTP – the FTP executable is only to be used by Administrators, and any users added to an “FTP Allow” Active Directory group. ![]() The commonest use case I see is that people want administrators to be able to run anything, but wish to restrict the use of certain system executables to “whitelist” groups. There are GPOs that can control some of these, but if AppLocker is your approach then it makes sense to leverage that. Think anything in the Windows system folders – the command prompt, Registry editor, FTP, subst, etc., etc. Rather than discuss the ins and outs of each of these technology stacks (or even third-party tools that can extend these capabilities, such as Ivanti Application Control or Citrix WEM), I will simply link you to this article for further reading (which was actually written by me, despite what the author details may have you think!)Ī common requirement for any application management tool is to restrict system applications. It superseded the old Software Restriction Policies and is itself slated to be replaced by Microsoft Defender Application Control, but as of today, it is still the recommended application management solution, particularly within multi-user environments. If AppLocker is used, it is configured through group policy in Computer Configuration > Windows Settings > Security Settings > Application Control Policies > AppLocker.I have been asked about this a few times in the past, so thought I would quickly document it while it is fresh in my memory.ĪppLocker is Microsoft’s GPO-based technology that deals with application execution restriction. AppLocker is a whitelisting application built into Windows Server 2012. Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" under the Microsoft Windows section of the following link:Ĭonfigure an application whitelisting program to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.Ĭonfiguration of whitelisting applications will vary by the program. This will produce an xml file with the effective settings that can be viewed in a browser or opened in a program such as Excel for review. Get-AppLockerPolicy -Effective -XML > c:\temp\file.xml If the AppLocker PowerShell module has not been previously imported, execute the following first:Įxecute the following command, substituting with a location and file name appropriate for the system: If AppLocker is used, perform the following to view the configuration of AppLocker: A deny-by-default implementation is initiated by enabling any AppLocker rules within a category, only allowing what is specified by defined rules. ![]() If an application whitelisting program is not in use on the system, this is a finding.Ĭonfiguration of whitelisting applications will vary by the program.ĪppLocker is a whitelisting application built into Windows Server 2012. Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. This is applicable to unclassified systems, for other systems this is NA. Windows Server 2012/2012 R2 Domain Controller Security Technical Implementation Guide The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting. The organization must identify authorized software programs and only permit execution of authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software.
0 Comments
Leave a Reply. |