Outbound Policies
Configure rules that filter and route incoming tickets and events for ITSM and Security integrations.
Overview
The Outbound policies are a list of rules which control the incoming tickets based on the defined criteria during their configuration. For example, set your priority to P0 and source to Chronicle — this rule ensures you receive the tickets pertaining to P0 and originating from Chronicle when the defined criteria are met.
The Outbound policies help you enhance the scalability, efficiency, and flexibility of the ITSM and SOAR integration workflow by removing the bottleneck processing at end-point services and by adding custom filters or rules.
In addition, enabling Outbound policies allows you to scan the incoming events, filter, and route the events to the target service associated with the customer integration ID when the defined conditions match the specific events.
Note
The Outbound policies are applicable for ITSM (Jira, ServiceNow) and Security (Chronicle SOAR) integrations.
How Outbound Policies Work
The following sequence of actions takes place during the execution of the outbound policy:
The integration-acton-policy-lookup service consumes data from the Kafka topic, serving as a centralized point of policy-based filtering.
The service references the customer-specific policies established through the integration-acton-subscription-api. If a policy aligns with the incoming data, event filtering occurs, ensuring that only relevant events proceed to the next step.
Filtered events are directed to the appropriate target services (actonIntegrationService or integrationConfigService) based on the customer integration ID.
Outbound Policy Lookup Precedence
For existing integrations, the defined outbound policies lookup for tenant level first, then organization level, and finally domain level. The priority of execution for outbound policies is highest for tenants, followed by organizations, and then domains.
Setting up Outbound Policies
To set up the Outbound policies:
Login to Resolution Intelligence with your credentials.
Click the gear icon at the top (or) hover over the icon at the top left corner. At the bottom of the left menu, click Configurations.
In the left menu, under Data Ingestion, click Integrations.
Navigate to ITSM or Security integrations. For example, Jira.
Enable the integration and complete the details in Authentication and Tenant Mapping.
Click Outbound Policy and then click Add Policy. The Add policy screen opens.
Enter a name and description (optional) for the Outbound Policy.
Under the Specify condition section, construct the condition expression for your outbound policy. Select a field and operator from the drop-down lists. For the value, select a value from the drop-down list or enter it manually, depending on the field type. The condition is used to determine the records to which the rule will apply. A condition expression can consist of several phrases, joined by an And or Or. For each phrase, select a field, operator, and value. Click the button to add an additional row. Use the parentheses and And/Or options to join the phrases together to form a condition expression.
Click Submit.
Viewing an Outbound Policy
To view an Outbound policy:
Click the gear icon at the top (or) hover over the icon at the top left corner.
At the bottom of the left menu, click Configurations.
In the left menu, under Data Ingestion, click Integrations.
Navigate to ITSM or Security integrations. For example, Jira.
Click the Outbound Policy. In the policy listing page, click the desired policy (or) scroll right and click the three dots. A drop-down list opens.
Click View to open your desired outbound policy.