8. Integrations Configuration
C-PAT offers integrations with STIG Manager and Tenable.sc. While it is possible to run C-PAT independently, to fully realize the benefits of C-PAT it is strongly recommended that C-PAT be configured to run in conjunction with these tools.
8.1. STIG Manager
Note
C-PAT has been tested and configured to work when C-PAT and STIG Manager are housed within the same OIDC realm, therefor, the value set for CPAT_OIDC_PROVIDER will also be used for obtaining a token for STIG Manager.
If you are using the provided RMFTools Keycloak container, the default value for STIGMAN_OIDC_CLIENT_ID can be used.
Variable |
Default |
Description |
|---|---|---|
|
stig-manager |
The OIDC clientId for STIG Manager. |
|
The URL to the STIG Manager API. |
|
|
No default |
String used as a prefix for each STIG Manager scope when authenticating to the OIDC Provider. This will likely match your |
|
No default |
Scopes to request in addition to: |
8.2. Tenable
Tenable Environmenment Variables: Variable
Default
Description
TENABLE_URLNo default
The URL to your instance of Tenable.sc, no trailing slashes or additional paths are necessary. Example:
https://myACASinstance.something.com
TENABLE_ACCESS_KEYNo default
See the tenable documentation for instructions on how to generate API keys. NOTE: The account that an API key is generated for must have permissions to access vulnerability data. e.g.
Security AnalystVulnerability AnalystAuditor
TENABLE_SECRET_KEYNo default
See the tenable documentation for instructions on how to generate API keys. NOTE: The account that an API key is generated for must have permissions to access vulnerability data. e.g.
Security AnalystVulnerability AnalystAuditor
TENABLE_CERT_FILENo default
A file/path relative to the API /tls directory that contains the PEM encoded Client certificate used when connecting to Tenable. Additionally requires setting a value for
TENABLE_KEY_FILE.
TENABLE_KEY_FILENo default
A file/path relative to the API /tls directory that contains the PEM encoded Client private key used when connecting to Tenable. Additionally requires setting a value for
TENABLE_CERT_FILE.
8.3. AI
Warning
AI integration for mitigation statement generation is an experimental feature.
Variable |
Default |
Description |
|---|---|---|
|
|
By default, AI integration will be disabled. Set to |
|
No default |
Valid options include: |
|
No default |
Underlying AI integration is enabled by Vercel AI SDK. For precise model naming instructions, please visit the Vercel docs. |
|
No default |
The API key for your chosen AI provider. This is not applicable when using ollama. |
|
|
URL prefix for API calls. Default will be set according to the providers [CPAT_AI_PROVIDER] documented default. |