Set an Application Control Exception on an Endpoint in BigFix Application Control
The Task: Set Exception on Endpoint applies an application exception — a time-bound Allow rule with additional audit metadata — to a managed endpoint. The task requires four parameters: File_Name, Approved_By, Expiration_Date, and Reason. This task is designed to be triggered exclusively by ITSM applications such as ServiceNow™ as part of an exception approval workflow — it cannot be manually triggered from the BigFix Console.
About this task
As an administrator, you can view the Task: Set Exception on Endpoint to understand the exceptions applied on managed endpoints. Exceptions are Allow rules with additional audit metadata parameters. These parameters are File_Name, Approved_By, Expiration_Date, and Reason.
This task serves as a placeholder that enables the ServiceNow™ exception approval workflow to apply a time-bound application exception on a managed endpoint. When a desktop user raises an exception approval ticket in ServiceNow™, the approved workflow triggers this task to create the corresponding Allow rule — with expiration and approval metadata — on the target endpoint.
The four exception parameters carry the following information:
- File_Name
- The name or path of the application file for which the exception is being granted. This value is used to construct the Allow rule path pattern on the endpoint.
- Approved_By
- The name or identifier of the approver who authorized the exception in the ITSM system. Recorded as audit metadata in the exception rule.
- Expiration_Date
- The date on which the exception expires. After this date, the exception Allow rule is no longer valid and the application is subject to the endpoint's standard Application Control policy.
- Reason
- A description or business justification for the exception, as entered in the ITSM ticket. Recorded as audit metadata alongside the Allow rule.