Integrations
PlexTrac offers multiple integration points with other tools and applications so that less time is spent managing files and more time is put towards resolving security risks.
Configuration and setup of parsers, third-party tools, and APIs is done by admin users in the Admin Dashboard.
Data parsing is the process of taking data in one format and transforming it to another format for ingestion. PlexTrac can import data from over 20 tools, and all parsers are available without additional licensing.
Parser actions are configured at the admin level on the Admin Dashboard.
Available information (field mappings and instructions) can be accessed by clicking the field mappings or instructions buttons below.
Acunetix
used in
Findings/Reports
accepted file types
XML
Core Impact
used in
Findings/Reports
accepted file types
XML
Mitre Engenuity
used in
Runbooks
accepted file types
YAML
Netsparker (Desktop)
used in
Findings/Reports
accepted file types
XML
Nexpose
used in
Findings/Reports
accepted file types
XML
Nipper
used in
Findings/Reports
accepted file types
XML
Nmap (Stock)
used in
Findings/Reports
accepted file types
CSV, NMAP, XML
Nmap Vulners NSE
used in
Findings/Reports
accepted file types
CSV, NMAP, XML
OWASP ZAP
used in
Findings/Reports
accepted file types
XML
Scythe (Procedures)
used in
Runbooks
accepted file types
CSV, JSON
Scythe Threat Thursday
used in
Runbooks
accepted file types
CSV, JSON
Tenable Nessus Scanner
used in
Findings/Reports
accepted file types
NESSUS
Veracode Platform
used in
Findings/Reports
accepted file types
XML
An API (Application Programming Interface) is a set of procedures and communication protocols that provide access to PlexTrac. PlexTrac has several API integrations, some of which are available immediately while others require a license.
APIs are configured at the admin level on the Admin Dashboard. Click a box below for instructions on setting up an integration.
PlexTrac provides CSV templates and scripts to make the task of importing findings and other data easier, whether importing findings to a specific report or importing data to multiple clients and reports.
Use the following table to determine which solution works best:
Report Findings CSV Import | Python General CSV Import |
|---|---|
Imports to a single report | Imports to multiple reports |
Request is processed on the backend in less than five minutes | Each finding is processed individually and can take up to several hours* |
Must order CSV columns to match template schema exactly | CSV columns are mapped to findings on a finding and sequence is not relevant |
Imports to select finding fields only | Imports to all finding and asset fields |
Does not import client and report information | Imports client and report information |
*Script can create parsed findings in PlexTrac either by sending API calls to create each finding individually that results in a long runtime of the script, or by generating a PTRAC file. Manually importing the generated PTRAC file takes the same amount of time as the PlexTrac Report Finding CSV Template. IMPORTANT: The generated PTRAC only contains report and finding information: Asset information will not be added.
Click the box below for information and access to a downloadable CSV file that can be used as a template for uploading findings into a report. The file has the required fields prepopulated in the CSV file, along with sample values.
Click the box below for information on using a script to import data via the PlexTrac API. The script consists of two CSV files; one with the data to import, and a second that contains field mappings.
This script can be used to import data into multiple clients and reports, and it will parse the CSV to create client, report, finding, and asset objects, then call the PlexTrac API to import/create these in the tenant.
Last modified 2d ago