Documentation Index

Fetch the complete documentation index at: https://docs.safe.security/llms.txt

Use this file to discover all available pages before exploring further.

Creating a Ticketing Automation

Prev Next

Balbix Automations allow users to eliminate manual tasks through one-time configuration - including ticketing, exception handling, data exports, inventory tagging, and more. Ticketing Automation enables automatic creation of tickets in third-party systems (e.g., ServiceNow, Jira) whenever matching exposures are detected, helping accelerate remediation workflows.

Follow this procedure to create a ticketing automation.

Step 1: Start a New Automation

Go to Asset Vulnerabilities and click Create Automation.

Enter:

  • A Name for the automation (e.g., "Test Automation ITSM Ticket")

  • Type of Automation: Freeform

  • Element: Asset Vulnerabilities



Step 2: Define Scope Using Filters

Select:

  • Scope of Automation: Use new filter or Asset Vulnerabilities matching Saved Filters

Then:

  • Choose a field like Name

  • Set condition (e.g., "is any of")

  • Enter one or more CVEs (e.g., CVE-2005-2945)

This determines the subset of vulnerabilities the automation will monitor.


Step 3: Set the Trigger Condition

The trigger defines when the automation should run for the selected scope. You can choose:

  • Upon Next Evaluation: Executes automatically during the next system evaluation cycle.

  • Scheduled (Periodic): Runs at regular intervals (e.g., daily, weekly).

  • Scheduled (One Time): Runs only once at a specified time.


This ensures your automation executes at the right moment based on your operational needs.

Choose:

  • Automation Trigger Type: Upon Next Evaluation

This ensures the automation evaluates matching vulnerabilities in the next analysis cycle.


Step 4: Select Action – Create Ticket

From the action dropdown, select:

  • Create Ticket


Then:

  • Choose the appropriate Ticketing Rule (e.g., snow-test-rule1-balbix)


This connects the automation to a preconfigured rule that defines the fields and values populated in the ServiceNow ticket.


Step 5: Define Ticketing Parameters

Populate required ServiceNow fields:

  • Short Description

  • Urgency

  • Impact

  • Contact Type

  • Severity

  • Optional: SLA Choice, Reason for SLA Breach, Release for Test

Fields are pulled dynamically from the connected ServiceNow instance to ensure valid values.


Step 6: Finalize and Activate Automation

Review all inputs and:

  • Check Make this active on creation (optional)

  • Click Create Automation to complete setup

The automation is now live and will create tickets automatically based on your defined scope and trigger.


See Also:

Ticketing Dataflows