Veracode
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Connect Veracode to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Connect Veracode with an API service account's API ID and secret key, generated under Account settings → API credentials in the Veracode Platform. Requests are signed with Veracode's HMAC scheme.
The service account needs the Results API and Applications API roles to read the application portfolio and findings. Pick the region your Veracode account lives in — data is isolated per region.
Configuration
| Option | Type | Required |
|---|---|---|
API ID | password | Yes |
API secret key | password | Yes |
Region | select | Yes |
Linking Veracode to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Veracode
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
applications | An application profile in the Veracode portfolio, including its policy-compliance state and scan history. | Incremental, Full refresh | modified | — |
sandboxes | A development sandbox belonging to an application, used to scan code before it is promoted to a policy scan. | Full refresh | — | — |
findings | Static, dynamic, and manual security findings for an application, with severity, CWE, and remediation status. | Full refresh | — | — |
sca_findings | Software Composition Analysis findings for an application: vulnerabilities in open-source and third-party components. | Full refresh | — | — |