Hackuity gives you a complete view of your cyber exposure and the tools to interpret it, so you can detect, anticipate, and protect yourself from vulnerabilities. The platform reinvents Risk-Based Vulnerability Management (RBVM) by aggregating 80+ third-party tools into a single unified view, prioritizing vulnerabilities with a risk-based scoring algorithm, and automating remediation based on your attack surface.
This connector queries the Hackuity API to produce indicators (numerical values tracked over time on a perimeter) about your assets and their vulnerabilities. It can also sync the most critical vulnerabilities as gaps (security flaws recorded in a Tenacy register).
This article is for Tenacy Admins in charge of configuring connectors.
This connector collects the following information:
Vulnerabilities: critical vulnerabilities, open vulnerabilities, open critical vulnerabilities, and vulnerability score.
Assets: number of assets and assets with a critical vulnerability level.
The most critical vulnerabilities as gaps in Tenacy.
Add and configure the connector
To add this connector, go to Catalog > Connectors > Hackuity > Add connector.
After adding it, you must configure:
Operating perimeter: the perimeter that operates and dictates vulnerability management rules. Indicators will be attached here by default.
Frequency: how often the Hackuity API is queried and indicators are updated (daily, weekly, monthly, half-yearly, or yearly).
Once the connector is created, configuration continues with the Hackuity connection credentials:
Namespace: the alphanumeric value identifying your workspace, available in the Hackuity console.
User login: the login of the account used to connect.
User password: the password associated with this account.
Hackuity console URL: the address of your Hackuity instance.
Then, to configure vulnerability synchronization:
Minimum findings score: the score below which vulnerabilities aren't synced, so you can focus on the ones that matter. This threshold only applies to gaps, not to indicators.
Critical threshold: the score above which a vulnerability is considered critical by Tenacy.
Gap register: the register where the most critical vulnerabilities identified by Hackuity are synced.
Maximum number of gaps to sync: the limit of gaps synced per connector run (100 by default if left blank, maximum value: 100).
⚠️ If the Gap register field is left blank, no vulnerabilities will be synced to Tenacy. Only the indicators will keep being updated.
💡 On each sync, Hackuity and Tenacy statuses are compared: gaps still found by Hackuity are reopened if they had been closed, and gaps no longer detected are automatically closed.
You can send differentiated values to several Tenacy perimeters from a single connector by setting up the perimeter mapping.
💡 To retrieve several differentiated values with a single connector, enter the Hackuity perimeter name(s) in the Tenacy perimeter configuration modal.
Run your first test
Once the connector is properly configured, test the integration by running an initial execution.
Go to ⚙️ > Connectors > click on the Hackuity connector > Run now:
💡 Feel free to contact Tenacy support if you have any questions regarding this.
Expected result
Once the test runs successfully, the connector automatically queries the Hackuity API according to the chosen frequency. The Vulnerability score, Assets, Assets with critical vulnerability level, Open vulnerabilities, and Open critical vulnerabilities indicators start updating, and the most critical vulnerabilities progressively appear as gaps in the configured register.
FAQ
What happens if I don't set a gap register?
Vulnerabilities identified by Hackuity are then not synced as gaps in Tenacy. Only the indicators keep being updated.
What's the difference between the minimum findings score and the critical threshold?
The minimum findings score determines which vulnerabilities are synced as gaps, excluding those deemed not relevant enough. The critical threshold determines, among the synced vulnerabilities, from which score they're considered critical by Tenacy.
How does the automatic reopening and closing of gaps work?
On each sync, Tenacy compares statuses between Hackuity and Tenacy: a gap still detected by Hackuity is reopened if it had been closed, and a gap no longer detected is automatically closed.
Can I retrieve differentiated indicators for several Hackuity perimeters?
Yes, by setting up the perimeter mapping with the corresponding Hackuity perimeter name(s), a single connector can feed several Tenacy perimeters with distinct values.
Where can I find my Hackuity Namespace?
This alphanumeric value is available directly in your Hackuity console.