- Rules require the same item-level targeting
- Organizing rules into physical groupings for ease of maintenance or review
- Creating rule groups based on abstract terms like department, application, or even denied applications or websites
- Enforcing that all sub-groups or rules inherentthe same action
- Storing obsolete or temporary rules
- Staging rules that are used for testing before inserting them into production. (This works best with Item Level Targeting).
- Operating System Elevations for managing tasks inherent to the OS. Sample rules in this group are for items like modifying the system clock, running defrag.exe, or even adding an ODBC driver.
- Website Explicit Deny rules are for creating Internet Explorer policies that block specific websites. In this example, rules contain the blocking of websites that are against corporate policy. These rules would be processed regardless of whether the user is on the corporate network or logging on remotely.
- The Engineering Department Allowed Collection is an abstract collection of rules that utilizes Item Level Targeting to allowapplications like VMware workstation or AutoCad to operate correctly for specific subnets.
- Discovery is a sample collection with passive rules strictly used to discover applications that are being executed with administrative privileges.
- Within each Group Policy Object (GPO), rules are processed sequentially from highest order number to lowest, and only the first rule that targets an application takes effect.
- When a rule and a collection have the same order number, the individual rule is processed before the collection.
- When a rule collection contains a sub-collection, rules in the parent collection are processed first, and then rules in the sub-collection are processed.
- Rule collections are automatically assigned an order number when they are created. You can change the order number of a collection by selecting the collection in the Group Policy Management Editor and clicking the Move the selected item up or Move the selected item down arrow buttons in the menu bar.
Morey J. Haber, Chief Security Officer at BeyondTrust
Morey J. Haber is the Chief Security Officer at BeyondTrust. He has more than 25 years of IT industry experience and has authored three books: Privileged Attack Vectors, Asset Attack Vectors, and Identity Attack Vectors. He is a founding member of the industry group Transparency in Cyber, and in 2020 was elected to the Identity Defined Security Alliance (IDSA) Executive Advisory Board. Morey currently oversees BeyondTrust security and governance for corporate and cloud based solutions and regularly consults for global periodicals and media. He originally joined BeyondTrust in 2012 as a part of the eEye Digital Security acquisition where he served as a Product Owner and Solutions Engineer since 2004. Prior to eEye, he was Beta Development Manager for Computer Associates, Inc. He began his career as Reliability and Maintainability Engineer for a government contractor building flight and training simulators. He earned a Bachelor of Science degree in Electrical Engineering from the State University of New York at Stony Brook.