Skip to main content

Tufin

Visualize Tufin-managed firewalls, security policies, firewall rules, network zones, and policy violations, map violations to the rules that triggered them, and monitor firewall policy changes through queries and alerts.

Installation​

info

You will need credentials for a Tufin Orchestration Suite (TOS) user with access to the SecureTrack and optionally SecureChange APIs. See the Tufin user management documentation and user roles documentation for full details.

SecureTrack user setup​

The integration uses SecureTrack to collect firewalls, policies, firewall rules, network zones, and policy violations.

  1. Log in to the TOS web UI as an administrator.

  2. Navigate to Settings → Administration → Users.

  3. Create a dedicated user and assign it the Administrator role in SecureTrack.

    A User role is sufficient for devices, policies, rules, and policy violations, but the Administrator role is required to access network zones via the API.

  4. Assign the user access to all relevant devices.

SecureChange user setup (optional)​

SecureChange is a separate application within TOS and requires independent user configuration. Skip this section if you do not want to ingest SecureChange users or tickets.

  1. Navigate to Settings → Users in the SecureChange UI (or use LDAP group import).
  2. Add the user to SecureChange and assign the appropriate role:
    • Auditor — read-only access to tickets. Sufficient if you only need ticket ingestion.
    • System Administrator — required if you also want to ingest SecureChange users.

To install the Tufin integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Tufin. Click New Instance to begin configuring your integration.

Creating a Tufin instance requires the following:

  • The Account Name used to identify the Tufin account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • Your TOS server Hostname (or IP address), e.g. tos.example.com.

  • Your TOS Username and Password to authenticate with the SecureTrack and SecureChange APIs.

Click Create once all values are provided to finalize the integration.

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.