HaloPSA · remediation tickets
Vulnerability fixes as HaloPSA tickets, after your review
Every Varaxon Scan Hub report ends in a fix plan. Connect HaloPSA and each fix becomes a ticket draft for the right customer, sent only after you approve it.
What Scan Hub sends
One ticket per fix.
Scan Hub groups findings that share a fix into one ticket, with the affected devices and the evidence, so a technician has what they need.
You approve first.
Drafts wait in Scan Hub's ticket review. Nothing reaches HaloPSA until you approve it, and you can edit any draft first.
Updated, never deleted.
When a later report changes a fix, Scan Hub adds a private note to the ticket it created. It never deletes a ticket.
How to connect HaloPSA
- In HaloPSA, go to Configuration, Integrations, HaloPSA API, View Applications, and add an application using Client ID and Secret (Services).
- On its Permissions tab, allow read:customers, read:tickets and edit:tickets.
- In Scan Hub's ticket settings, enter your HaloPSA address, tenant name, client ID and secret, then choose the ticket type.
- Link each Scan Hub client to its HaloPSA customer.
How tickets work
- Each ticket names the fix, the devices it applies to and the findings it closes.
- Priorities follow the report: known exploited vulnerabilities come first.
- Keys are stored encrypted and never shown again after saving.
Common questions
- Does Scan Hub create tickets automatically?
- It drafts them automatically when a report finishes. They are sent to HaloPSA only after you approve them.
- What HaloPSA permissions are needed?
- read:customers, read:tickets and edit:tickets on an API application that uses Client ID and Secret (Services).
- Can I bill for the fixes?
- Yes. Tickets carry the work in your PSA, so remediation can be tracked and billed like any other job.
Guide
Billable vulnerability remediationHow to turn report findings into scoped, billable work.Read the guide