Supported Data Models
-
Vulnerability Findings V2
- type:
code
- type:
-
Issues (AppSec)
- type:
code
- type:
-
Resources
- type:
repository
- type:
Onboarding Black Duck Coverity
Follow the steps below to onboard your Coverity Connect environment to Leen.Identify Your Coverity Connect Server URL
Locate the URL of your self-hosted Coverity Connect instance (e.g.,
https://coverity.example.com). This will be required as the Server URL during configuration.Prepare a Coverity User Account
Leen authenticates to Coverity Connect using HTTP Basic Auth (username and password). We recommend creating a dedicated read-only service account for this integration.Ensure the account has the following permissions:
- Read access to all relevant projects and streams
- Access to issue search endpoints (
/issueOccurrences/search) - Access to project listing endpoints
- Access to issue search endpoints (
Enter Configuration Parameters in Leen
In your Leen integration configuration, provide the following:
| Parameter | Description | Required |
|---|---|---|
| Server URL | Your Coverity Connect server URL (e.g., https://coverity.example.com) | Yes |
| Username | Coverity Connect username for Basic Auth. | Yes |
| Password | Coverity Connect password for Basic Auth. | Yes |
Data Synced
The Black Duck Coverity integration syncs the following data:- Issue Occurrences: Static analysis findings from all accessible project streams, including checker name, category, impact, triage status, file location, and CWE references
- Projects: Coverity project metadata used as resource records