NEW

Halo PSA Integration

Automate ticket creation from WithSecure™ Elements to Halo PSA and learn how to configure the integration.

The WithSecure™ Elements integration with Halo PSA automatically forwards security activity from Elements into Halo PSA as tickets. This lets MSPs manage WithSecure detections and notifications inside the same PSA tool they already use for service delivery, without manual ticket creation.

What this integration does

  • Automated ticketing — WithSecure™ Elements creates tickets in Halo PSA when there is relevant activity for a mapped customer.
  • Per-customer routing — Tickets are routed to the correct Halo PSA customer using the customer’s Halo PSA reference ID.
  • Automated subscription provisioning — WithSecure™ products are synced to Halo PSA, and subscriptions are provisioned automatically from a customer’s recurring invoice.
  • Deep links back to Elements — Each ticket includes basic information about the Elements Security Center activity, along with a deep link to the full details in WithSecure.
  • Native and multi-tenant — The integration is built into Elements, supports multiple customer tenants, and is configured entirely from the Elements Security Center.

Before you begin

You will need:

  • A Halo PSA account with permissions to create API applications.
  • Access to the WithSecure™ Elements Security Center as a WithSecure Partner.

Step 1: Create API credentials in Halo PSA

  1. Log in to your Halo PSA account.
  2. Go to Configuration > Integrations from the navigation menu on the left-hand side.
  3. Select Halo PSA API, then under Applications click View applications.
  4. From the top-right corner, click +New and configure the application:
    1. Enter an application name, e.g. WithSecure Elements.
    2. Make sure the Active checkbox is selected.
    3. Under Authentication method, select Client ID and secret.
    4. Copy the Client ID and Client secret — you will need these in the Elements Security Center.
    5. Under Login type, select Agent.
    6. From the Agent to login in as dropdown, choose an agent. Tickets created by WithSecure use the identity of this agent.
    7. Open the Permissions tab and select the all permission. The application can only do what is selected on this tab and what the chosen agent is allowed to do. If no permission is selected, Connect in the Elements Security Center still succeeds, but loading ticket types and companies, ticket creation, and provisioning fail.
    8. Click Save.

Step 2: Configure the integration in Elements Security Center

In the WithSecure™ Elements Security Center, go to the Management > Integrations section and locate the Halo PSA integration.

Click Configure. The configuration dialog has four steps: Connection details, Data configuration, Result, and Test (optional). The configuration is saved on the Result step. Until then, go back to an earlier step with Previous or by clicking its name at the top of the dialog, and use Cancel or the X in the top-right corner to close the dialog without saving.

Connection details

The Connection details step of the Halo PSA configuration dialog, with the HaloPSA URL, Client ID, and Client Secret fields

  1. Set the HaloPSA URL of your Halo PSA tenant (e.g. https://yourcompanytenant.halopsa.com).
  2. Enter the Client ID and Client Secret copied from Halo PSA.
  3. Click Connect to validate connectivity. When the connection succeeds, the dialog moves on to Data configuration.

When you open an integration that is already configured, the dialog shows that it is already configured and fills in the saved values. The Client Secret is masked; leave it as it is to keep the saved secret. If you change the HaloPSA URL, enter the client secret again. Click Connect to continue to the settings.

Data configuration

The Data configuration step of the Halo PSA configuration dialog, with the event types, severity thresholds, ticket types, and the override for category, urgency, and impact

  1. Under Event types that create tickets, leave Endpoint BCD (Broad Context Detections on endpoints), Identity and Cloud BCD (Azure identity, Azure workload, and AWS workload incidents), and XM (Exposure Management Recommendations) selected, or clear a type that should not create tickets. All three are selected by default.
  2. Under BCD, set Minimum risk for tickets. It applies to both Endpoint BCD and Cloud BCD tickets. The default is High and above. Other choices are Info and above, Low and above, Medium and above, and Severe only. A threshold below Medium can create a large number of tickets. Waiting-for-customer, elevation, and risk-change updates can still create or update tickets.
    • Under Endpoint BCD, select a Ticket type, or leave it empty to use the default type Incident. The form shows the workflow name for the selected type.
    • Under Identity and Cloud BCD, select a Ticket type, or leave it empty to use the same ticket type as Endpoint BCD. If Endpoint BCD is cleared, an empty ticket type uses the default type Incident.
  3. Under XM, set Minimum severity for tickets. The default is all severities (Info and above). Other choices are Warning and above and Critical only. Closed or accepted-risk recommendations never create tickets. Then select a Ticket type, or leave it empty to use the default type Incident.
  4. Leave Override category, urgency, and impact off unless you have configured your Halo instance to require them. When you turn it on, Category, Urgency, and Impact are each optional. Halo recomputes ticket priority only when both urgency and impact are set. Elements still sends its own mapped priority. Leaving the override off omits those fields when the ticket is created.
  5. Click Next.

If a list cannot be loaded from Halo PSA, the error is shown next to the field. Next stays unavailable until the list loads or you turn off the option that needs it, for example Override category, urgency, and impact.

Note: To enable automated WithSecure subscription provisioning, turn on Enable provisioning on the Data configuration step. See Automated WithSecure subscription provisioning for how to use it.

Result

Review the settings and click Save. To change a setting first, click Previous to go back to Data configuration.

Test (optional)

The Test (optional) step of the Halo PSA configuration dialog, with the company selector and the test ticket buttons for Endpoint BCD, Cloud BCD, and XM

After you save, you can create a test ticket to check that Halo PSA accepts tickets from Elements with these settings. A test ticket shows problems such as a mandatory field that Elements does not fill in, a ticket type that cannot be used, or missing API permissions, before the first real ticket fails.

  1. Select the Company for the test ticket. The list shows the companies in your Halo PSA; no company mapping is needed yet.
  2. Click Create Endpoint BCD test ticket, Create Cloud BCD test ticket, or Create XM test ticket. There is one button for each selected event type, because each can use its own ticket type.
  3. Check the result:
    • Test ticket created shows a link to the ticket in Halo PSA. This is a real ticket, so you can close or delete it in Halo PSA.
    • Test ticket could not be created shows the error message from Halo PSA. Click Edit settings to go back to Data configuration, change the settings, click Next and Save again, and create a new test ticket.
  4. Click Close. Creating a test ticket is optional; the configuration is already saved.

Step 3: Enable ticketing for a customer

Map your Halo PSA companies to the corresponding WithSecure™ Elements companies. Ticket creation starts automatically for each mapped company.

  1. In the company mapping view, match each Halo PSA company to its WithSecure™ Elements company.
  2. Click Save Mappings.

Mapping Halo PSA companies to WithSecure Elements companies

Monitor tickets

Monitor the tickets you configured the integration to create in Halo PSA. Each ticket contains basic information about the Elements Security Center activity and a deep link to the full details in WithSecure.

Automated WithSecure subscription provisioning

When Provisioning is enabled in the integration configuration, the integration provisions WithSecure™ subscriptions for your customers directly from recurring invoices in Halo PSA. You no longer need to create subscriptions manually in the WithSecure partner portal.

How it works

Once Provisioning is enabled in the integration configuration, the integration automatically syncs the available WithSecure™ products to the Halo PSA tenant of the partner. These products become available in Halo PSA so you can add them to a customer’s recurring invoice. When a recurring invoice that includes a WithSecure™ product is enabled for a customer, the integration provisions the corresponding subscription for that customer automatically.

Note: If the customer’s organization does not yet exist under your partner account in WithSecure, the integration creates it automatically as part of provisioning.

Prerequisites: required customer details

Before a subscription can be provisioned automatically, the customer record in Halo PSA must have the following fields defined:

  • Address
  • Accounts first name
  • Accounts last name
  • Accounts email address

These billing details fields are mandatory. They are sent to WithSecure as the account’s contact information, so provisioning fails until they are filled in for the customer.

Provision a subscription with a recurring invoice

To provision a WithSecure™ subscription for a customer, add a recurring invoice in Halo PSA:

  1. In Halo PSA, go to Recurring Invoices and click New, then New Recurring Invoice.

  2. Click Add Recurring Item and select the WithSecure™ product(s) you want to provision.

  3. Set the quantity to 1 or more. The quantity sets the maximum number of seats available for the WithSecure™ subscription. You can change it later from the subscription if needed.

    Note: You can set the price to whatever you want. This is the price the MSP bills their customer and has no effect on the WithSecure™ subscription itself.

  4. Click Select.

  5. From the panel on the right-hand side, click Set Schedule and set the Start date to today or to a later date.

  6. Click Save to save the schedule.

  7. Click Save again to save the recurring invoice.

A completed recurring invoice in Halo PSA with a WithSecure product added and the schedule set, ready to be saved

If the customer’s billing details are correctly set, Elements will automatically provision the new customer/subscription within 15 minutes. To change the number of seats later, update the quantity on the recurring invoice.

Tip: To provision the subscription immediately instead of waiting, go to Management > Integrations in the Elements Security Center, open the active Halo PSA integration, and click Sync sites.

Troubleshooting

If tickets are not created as expected, open the integration with Configure, click Connect, Next, and Save, and create a test ticket on the Test (optional) step. It shows the error message from Halo PSA directly.

If Connect succeeds but Elements cannot load data from Halo PSA, for example Failed to fetch ticket types, Failed to load companies from your PSA, or a Failed to load company mapping data notification, check the Permissions tab of the API application in Halo PSA (Step 1).

You can also review the integration logs in the Elements Security Center:

  1. Go to the Management > Integrations section.
  2. Open the active Halo PSA integration.
  3. Select Logs to review recent integration activity and error details.

If a subscription is not provisioned after enabling a recurring invoice, review the integration logs to check for any missing customer details required for provisioning. After completing the missing details for the customer in Halo PSA, you can manually trigger provisioning by going to Management > Integrations in the Elements Security Center, opening the active Halo PSA integration, and clicking Sync sites. Then, review the integration logs again—please note that processing may take up to 1 minute.

Availability

This integration is available to WithSecure Partners in the Elements Security Center. It is not available for free trials or company-managed subscriptions. To access dedicated partner features, contact WithSecure.