Salt Security
Connect Salt Security to Radiant Security to forward API attacker and remediation events for AI triage.
Salt Security is an API security platform that detects attackers probing and abusing production APIs, including credential abuse, scraping, business logic abuse, and exploitation of unauthenticated endpoints. Connecting Salt Security forwards Attackers and Remediations events to Radiant Security via webhook. Radiant uses this telemetry to surface anomalous API behavior, correlate it with identity and endpoint activity, and prioritize the alerts that warrant analyst attention.
Prerequisites
Add the data connector in Radiant Security
Log in to Radiant Security.
From the navigation menu, click Settings > Data Connectors, then click + Add Connector.
Search for and select Salt Security, then click Data Feeds.
Under Select your data feeds, select Salt Security (Webhook), then click Credentials.
Under Credential Name, enter an identifiable name for the credential (e.g.,
Salt-Credentials). To reuse an existing credential, select it from the drop-down menu.Under Required Credentials, enter a value in the Connector tag field. This can be any string. Radiant uses this value as salt when generating the authentication token for your connector.
Click Add Connector.
Open the newly created connector. Under Vendor Configuration, copy and save the
Webhook URLandTokenvalues. You will need both when configuring Salt Security.Click Done to save your changes.
Treat the Token value as a secret. Anyone with access to this token can post events to your connector. Do not expose it in client-side code, version control, or shared logs.
Configure the Custom Webhook integration in Salt Security
Salt Security forwards events to Radiant through two Custom Webhook integrations: one for Attackers events and one for Remediations events. Configure each integration separately, reusing the same Webhook URL and Token you copied from Radiant.
For deployment assistance, work with your Salt Security Solutions Engineer.
Configure the Custom Webhook integration in Salt Security
Salt Security forwards events to Radiant through two Custom Webhook integrations: one for Attackers events and one for Remediations events. Configure each integration separately, reusing the same Webhook URL and Token you copied from Radiant.
For deployment assistance, work with your Salt Security Solutions Engineer.
Configure the Attackers webhook
Click Setup on the newly installed Custom Webhook integration and enter the following parameters:
Integration Nickname:
Radiant Security Webhook Integration - AttackersURL: the
Webhook URLyou copied from Radiant.Event Type:
AttackersMethod:
POSTCustom header: name
x-rs-token, value theTokenyou copied from Radiant.Select Trigger Automatically.
Click Install, then click Test Integration to verify connectivity.
Verify ingestion
After saving each Custom Webhook integration in Salt Security, confirm that events are reaching Radiant:
In Radiant Security, navigate to Log Management.
Search for events with the connector type
salt_webhook(rs_connectorType:"salt_webhook").Confirm test events from both the Attackers and Remediations integrations appear in the parsed index.
Allow several minutes for events to be parsed, indexed, and available for search. Events that fail parsing appear in the unparsed index.
Verify ingestion
After Salt Security begins forwarding, confirm events are reaching Radiant.
In Radiant, navigate to Log Management.
Filter by
rs_connectorType:"salt_webhook".Confirm recent events appear.
Allow several minutes for events to be parsed, indexed, and available for search.
Last updated
Was this helpful?