Import results from third-party tools (limited availability)
Run external analysis tests to import SAST and SCA issue data from third-party tools into SAST & SCA projects in Polaris.
Overview
With a subscription that permits external analysis tests, you can import SAST and SCA issue data from many third-party tools into SAST & SCA projects in Polaris.
Important: The ability to import results from third-party tools is available on a limited basis, and is not generally available. Please contact your account teams for more information.
Please note:
- Imports can only be run from the Polaris user interface, and run like other tests.
- Issues without a valid severity are ignored.
- You can upload one file (up to 2GB in size) for each external analysis test.
- Each file you upload can only include one type of issue data (SAST or SCA).
- Different file formats are accepted for different third-party tools. Find a list of third-party tools that generate results you can import into Polaris here: Supported third-party tools.
- SCA issues you import only appear on the Issues tab, and do not affect the Components or Licenses tabs.
- Issues you import from third-party tools do not appear in reports and dashboards.
Import results from third-party tools
View and manage issues imported from third-party tools
Issues you import from third-party tools can be triaged and exported (to CSV, JSON, or Jira) like other issues in Polaris, and are subject to issue policies.
Issue deduplication
- Polaris deduplicates issues captured using the same third-party tool (if you run multiple external analysis tests to import results from Clang into a project, Polaris won't duplicate the same issue found in different external analysis tests that import results from Clang).
- Polaris does not deduplicate issues imported from different third-party tools in the same project (if the same issue is captured in external analysis tests using exports from Clang and Coverity, the issue appears twice on the Issues tab).
- Polaris does not deduplicate issues captured in external analysis tests from issues captured in other test types in the same project (if the same issue is captured in a SAST test run with Polaris and an external analysis test, the issue appears twice on the Issues tab).