Skip to main content
availability

Package: Invicti AppSec Core (on-demand), Invicti AppSec Enterprise (on-premise, on-demand)

Salt Security DAST/API Integration

Salt Security is an API security platform that uses AI to detect and prevent API attacks by analyzing API traffic patterns and behavior. This integration allows Invicti AppSec to connect to Salt Security and import API vulnerability findings.

Prerequisites

FieldDescription
Salt Security URLThe URL of your Salt Security tenant (e.g., https://app.salt.security)
Access TokenAn API access token from your Salt Security account

Get an Access Token (on Salt Security Side)

  1. Log in to your Salt Security tenant dashboard.
  2. Navigate to Settings in the left sidebar.
  3. Select API Access or Integrations.
  4. Click Generate Token or Create API Key.
  5. Copy the access token — it may be shown only once.

Step 1: Navigate to Integrations

From the left sidebar menu, click on Integrations.

Integrations sidebar

Step 2: Select the DAST/API Tab

On the Integrations > Scanners page, click on the DAST/API tab.

DAST/API tab

Step 3: Find and Activate Salt Security

Scroll through the list of DAST/API scanners to find Salt Security.

  • If Salt Security is not activated, you will see an "Activate" button. Click it to enable the integration.
note

The scan method badge on the Salt Security card shows KDT, which means scans are triggered through the Kondukto CLI tool (KDT).

Step 4: Configure Connection Settings

Click on the gear icon on the Salt Security card to open the configuration panel. Fill in the required fields:

  1. Token: Paste the access token from your Salt Security account.
  2. Base URL: Select your Salt Security API endpoint (https://api.secured-api.com for US or https://api.secured-api-eu.com for EU).
Salt Security settings

Step 5: Test the Connection

Click Test Connection. A green Connection successful message confirms the token and URL are valid.

Summary

StepAction
1Navigate to Integrations from the sidebar
2Select the DAST/API tab
3Activate Salt Security
4Enter URL and Access Token
5Test the connection

Create a Scan

  1. Open a project in Invicti AppSec.
  2. Go to Settings > Scanners.
  3. Click Add Scanner.

Add Salt Security Scanner

  1. Select DAST/API as the scanner type.
  2. Choose Salt Security from the scanner list.
  3. Click Add to open the scan configuration drawer.

Scan Configuration Fields

FieldDescriptionRequired
EnvironmentSelect the environment for the scanNo
Bind ToSalt Security API project to bind toYes
BranchSource code branch associated with this scanNo
Meta DataAdditional metadata for the scanNo
Scan TagTag to identify the scanNo
Salt Security scan creation

Scheduler

Enable the Scheduler toggle to regularly sync findings from Salt Security.

Webhook (Optional)

Add a webhook URL to receive notifications when new findings are available.

KDT Command

kdt scan -p <project_name> -t saltsecurity -b <branch_name>

Troubleshooting

Connection Fails

IssueResolution
Invalid access tokenRegenerate the token from Salt Security settings and update the integration
Wrong tenant URLVerify the exact URL of your Salt Security tenant
Token expiredGenerate a new access token and update the integration
Network accessEnsure Invicti AppSec can reach the Salt Security tenant URL on port 443

Scan Issues

IssueResolution
No APIs listedVerify the service account has access to the target API assets in Salt Security
No findings importedEnsure Salt Security has detected and analyzed API traffic for the target APIs
Empty resultsSalt Security requires live API traffic to generate findings; static applications may yield no results
Permission deniedThe access token must have at minimum read permissions for API findings

Best Practices

  • Use a service account with read-only access to Salt Security API findings for the integration.
  • Rotate the access token periodically and update the integration.
  • Ensure Salt Security is actively monitoring API traffic before expecting findings in Invicti AppSec.
  • Review Salt Security's API catalog regularly to keep tracked APIs up to date.
  • Use severity-based filters in Invicti AppSec to prioritize high-risk API vulnerabilities from Salt Security.

Limitations

  • Salt Security is a passive API traffic analysis platform; findings are based on observed traffic patterns, not active scanning.
  • Applications must have Salt Security sensors deployed and actively routing traffic for findings to be generated.
  • The number of monitored APIs depends on your Salt Security license.
  • Real-time finding sync frequency depends on Salt Security's detection pipeline and your Invicti AppSec polling schedule.

Need help?

Invicti Support team is ready to provide you with technical help. Go to Help Center

Was this page useful?