In addition to code enhancements and bug fixes the following features are included:
Application Control now offers even greater control over the access token used when self elevating. Administrators can define custom tokens and these are available for selection from the Self-Elevation Options dialog. Refer to Self-Elevation for further information.
Rule items for files, folders, signatures, and groups can now be configured to prompt the user before elevating application privilege. This allows the user to choose whether to run the application (or item) elevated or normally. Refer to Rules Items for further information.
For auditing purposes, it is recommended the user is prompted to supply a reason for the elevation. Monitoring auditing events enables administrators to easily distinguish between automatic elevations and those initiated by a user.
Administrators can now configure custom tokens to run at medium integrity. Refer to User Privileges for further information.
The Application Control Rules Analyzer now includes a checkbox that allows the filtering out of file overwrite and rename requests. The Rules Analyzer request summary view includes the rules Type field value. This shows at-a-glance the type (or category) of request type made, and prevents the analyst having to open and review individual requests to view the result. Refer to Rules Analyzer for further information.
The UAC Replacement feature complements existing Self-Elevation functionality within Application Control . With UAC Replacement turned on, the standard Windows UAC elevation prompt is replaced with a configurable Application Control consent dialog. This applies if the application is launched from the Start Menu, Explorer, the Desktop, or the command prompt.
See UAC Replacement for further information.
The 2020.2 release introduces a design update for default global styles. The new style uses a larger message box format to accommodate more detailed information; and the default messages no longer use a logo, instead they feature a color-coded banner.
The update is backwards-compatible, enabling you to continue using the previous classic styling, or to apply the style update to your existing configurations as required.
See Message Settings for further information.
Two additional event IDs have been added: 9060 and 9061. By default, both events are disabled. If required, they can enable organizations to differentiate execution requests blocked by Trusted Ownership from those blocked explicitly by a Rule Policy.
See Auditing for further information.
A further event has been added to identify processes started using full admin rights. ID 9062 can be valuable in identifying (and then assessing) the elevated rights required.
See Auditing for further information.
The new Microsoft Edge (Chromium) browser is now supported.
See for Browser Control for further information.
Assigned permissions apply within the Windows 10 Settings Apps and Features view.
See System Controls for further information.
In addition to this online help system, Ivanti provides a wealth of supporting information in the form of online documents, help videos and curated community articles. In the 2020.2 release we have collated these resources into a summary table and made this available via the Release Notes and from the online Help landing page.
In addition to code enhancements and bug fixes the following features are included:
Application Control 2020.1 release has been localized and now supports the following 5 languages:
Selection of the language setting required is described in the Language Settings help topic within User Workspace Manager .
Configurations can grow quite large as groups and rule sets are added. To help you navigate you can carry out a text search to locate where in the configuration a required item is configured.
Management Server, Console, Licensing Console and Agent components are all compatible with Microsoft Windows Server 2019.
For more information on supported software see the Maintained Platforms Matrix.
You can now select to add Folders and Groups to Process Rules. This provides the added benefit of being able to update all rules within the one group rather than having to go through each one individually.
For more information see Process Rules
New option to ignore event filtering for Groups. This now provides the ability to log events for each group item instance, so if a group is used in multiple places each instance has its own setting. This setting overrides any event filtering that has been set.
For more information see Allowed Items and Denied Items
New default setting to deny files on a network share. To allow files, you can either deselect this option, or add specific items to an Allowed list.
For more information see Advanced Settings
Command line arguments included in the Rules Analyzer results for allowed, denied and elevated executables. This is useful for troubleshooting and to create targeted rules.
Changes to Policy Change Requests compatibility now mean that the Application Control Agent and the Application Control Web Services must be at the same version.
New option Do not show access denied message when denied on rule creation. This allows administrators to intentionally block certain executables and perform a 'silent deny' so that the end user does not receive a denied access message.
For more information see Denied Items
New right-click option to Disable a rule, useful for troubleshooting issues and prevents the administrator from having to remove the rule. The option toggles between Disable and Enable so the rule can easily be re-enabled.
When you self-authorize an application exe all subsequent child dlls are now automatically authorized. Whereas in previous versions of Application Control each child dll would need self-authorizing, often causing the application to crash, now self-authorization can be completed in one click.
For more information see Rules
The network port number is now shown in the Blocked Port message box, if applicable. This helps with troubleshooting issues.
For more information see Message Settings
A new option has been added to Ignore Event Filtering. When this option is selected for a specific rule, it means that if an event ID is selected on the Auditing dialog, this event will be raised for this rule regardless of the event filtering settings. So even if no file types have been selected, the event will still be raised for this rule.
For more information see Allowed Items and Denied Items
A new option had been added to User Privileges > Components so that you can now Disable or Suspend BitLocker, and the Enable option has been extended to include Resume. This gives more granular control over the BitLocker component.
The URL Redirection feature is used to automatically redirect users when they attempt to access a specified URL. By defining a list of prohibited URLs you redirect any user attempting to access a listed URL to a default warning page or a custom web page.
This feature has been enhanced in 10.1 FR3 with the ability to whitelist specific URLs to address the following use cases:
For more information about this feature, see URL Redirection.
The 255-character message limit for messages that get displayed to end users has been removed.
In the Message Settings & Application Termination dialogs within the Application Control Console, the administrator can configure the text that gets displayed to end users for the different message types. With 10.1 FR2 and earlier releases, this text was limited to 255 characters. For this release, the limit has been removed so more information can be included.
For more information, see Message Settings.
Additional environment variables can be displayed in the Application Denied message box. From 10.1 FR3, all of the information that is included in the Application Denied log can be used.
For more information, see Access Denied.
In addition to VBScript and JScript, PowerShell scripts can now be created and used within Custom Conditions.
For more information, see Scripted Conditions.
Audit logs now capture details for elevated child processes. If the Apply to child processes option is selected in the configuration, once the primary process has been elevated, this elevation also applies to any child processes. However, in 10.1 FR2 and earlier releases, there was no auditing of those child processes so there was a lack of visibility to the associated activity. 10.1 FR3 audit logs now capture the details for both the primary process as well as any child processes to provide increased audit visibility.
For more information about where the Apply to child processes option is used, see Rules Items and Self-Elevation.
There are no new features in this release.
The Application Manager Console has been updated to reflect the new company name of Ivanti - see here for more details. As well as the change of branding from AppSense to Ivanti, Application Manager is now known as Application Control as of this release.
The Application Control console, as well as components on the endpoint have been updated to reflect these changes.
You may still see the AppSense Application Manager name used in certain areas, such as the registry or services. This is to make the transition as least disruptive as possible for existing users of Application Control.
Having made significant changes to the design of the User Workspace Manager consoles in version 10, we have listened to feedback and added a splash of color back into the consoles by refreshing and updating some of the icons used in the Application Control console.
Application Control Event Logging has been extended to include the following:
For further information about Application Control Auditing, see Auditing.
The Microsoft update model now uses build numbers to identify feature releases and service packs. When you are creating a computer operating system rule, the target build number can be specified and configured to match the specific build number entered or to use it as the maximum or minimum build release.
For more information, see Computer Conditions.
When verifying a file using metadata, administrators can compare the entire certificate to determine the authenticity of the file and whether the metadata can be trusted. The feature also includes real-time certificate verification that helps you diagnose any issues by selecting different combinations or verification settings. As you configure the settings, the certificate status is updated.
For more information, see Metadata and Verify Options.
Self-Elevation has been extended to support all file types. Administrators can also specify that certain file extensions can be elevated only when open with certain applications. For example, you can specify that VBS files can be elevated only with wscript.exe.
For more information, see Self-Elevation.
Application Control can now apply rules based not just on the application being launched, but also any command line arguments. This is useful if full access to an application is not required but specific users need to launch certain files or run applications under certain conditions. Command line arguments can be added for File and Signature rule items.
This feature also includes two new advanced settings - Validate PowerShell scripts and Validate Java archives. When these settings are turned on, powershell.exe, powershell_ise.exe, and java(w).exe are blocked and PS1 and JAR files are subject to trusted ownership checking. Specific files can then be added to rules which do not require a trusted owner. Add powershell.exe or java(w).exe to a rule to allow them for specific users, while blocking them for all other users. For example, you may want to allow powershell.exe for your developers so they can launch any PowerShell script.
For further information, see Rule Items and Advanced Settings.
The System Controls feature of Application Control has been extended to include the protection of processes. Using this enhancement, a specified process - such as antivirus software - can be protected from termination by all users, including administrators.
For further information, see System Controls.
Further support has been added to the control of Windows Store Applications. Applications can be blocked or allowed based on the application's publisher. Using the publisher for sideloaded apps means multiple apps can be controlled. This makes it possible to configure a restriction for all Store Apps while allowing those sideloaded by an organization or IT department.
For further information, see Rule Items.
Administrators can enable the Policy Change Request feature on a per-rule basis. This allows the type of change request and the available request methods to be configured differently for different users or groups of users. Some aspects of the feature, such as specifying the email address and shared key, remain global.
For further information, see Policy Change Requests.
This page refers to an older version of the product. View the current version of the online Help.