For example, you have a consultant helping you with your new ERP system (just saying). They need to launch the ERP application but you really don't want them firing up a browser or the RDP client and checking things out on your network.
Getting started with AppLocker is pretty simple:
- Launch the local group policy management tool
- Enable auditing only initially for exe/dll control
- Create the default rules to allow basic or general access (if applicable)
Then you want to create your specific allow / deny rules. The AppLocker rules are going to be a collection of rules saying if they are allow or deny rules, who they apply to, what type of matching they use (path, or publisher), and then actual match. So you might have a rule like
- Program Files\ERP\bin\*
If the consultant only matches this one rule, they will be allowed to launch binaries in the ERP's installation path and will be blocked from anything else.
The first thing to do is set your rules in audit-only which creates event logs for all access that is controlled by AppLocker. You can test out your rules very easily this way as there will be two types of events to look for: "access granted" and "access granted BUT applocker rules will block this when set to enforcing". Once you are satisfied you are not going to can all access to your regular users and that you are locking down the consultant sufficiently, switch to enforcing and you're golden.
Or for another example, maybe you just want to block an out of date version of Acrobat Reader from running on your network. You can set a rule to deny "Acrobat" publisher's "Acrobat Reader" program from running "9.0 or older". Again, easy to test using "audit only" before setting enforcing.
Looks like a dummy apparmor or selinux maybe? Honestly, I never made too much progress selinux. I would figure out how to get something working then wouldn't use it for a while and forget out how to work with selinux and have to start all over again.