Integration with the tools the team already uses.
They enrich findings and assets. Sync tickets. Notify the team where it already works.
Imports scan results straight into the pentest as findings, with no copy and paste.
InboundEach organization's open vulnerabilities, through the API and filtered by the tag of its assets. Also .nessus exports from Nessus, Tenable.io and Security Center.
ImportEach organization's open vulnerabilities, through the API (VMDR) and filtered by the tag of its assets. Also XML reports from VM and web application scanning.
ImportXML reports with the findings of every host, port and service.
ImportXML reports, exported by hand or through its API.
ImportIssues exported as XML, with their confidence level.
ImportXML alert reports, with their risk level.
ImportXML reports with CVSS and false positives already marked in the scanner.
ImportJSON exports that keep the triage done in the scanner.
ImportOpen ports and services, registered as the pentest's assets.
ImportResults from any code analysis tool that exports SARIF, with file and line. For secret scanners, where the secret is gets stored, never its value.
ImportPackage vulnerabilities with their fixed version, failing configurations and secrets found in images, repositories and clusters.
ImportFailing controls, by account and resource, with the standards each one covers (CIS, ISO 27001, ENS…).
ImportThe domain's risk rules, with their severity from the points they take away.
ImportEvery finding opens its ticket, and the finding hears back when the ticket is closed.
Two-wayTwo-way sync between findings and the work items on your team's board.
Two-wayTwo-way sync between findings and the incidents in your corporate service tool.
Two-wayTakes each pentest's status to the CRM: sales sees progress without entering the platform.
OutboundEvery work request received or updated, with structured data, sent to the system that already manages the customer relationship.
OutboundAlerts on serious findings, reports, work requests and retests, in the team's channel or in one per organization.
OutboundThe same alerts in Slack: one channel for the team and, optionally, one per organization that only gets its own.
OutboundImports the findings your autonomous pentesting operations generate. The platform never launches or controls the tests: it only centralises the result.
InboundThe names mentioned are trademarks of their respective owners. They indicate compatibility, not affiliation or endorsement.
Missing a connector you need?
Tell us what tool you use and we'll weigh it for the roadmap.