Secret Scanning
Secret Scanning detects sensitive information such as passwords and API keys within provided text to help prevent accidental exposure.
Secret Scanning enables automated detection of sensitive information such as passwords, API keys, and other secrets within text data. This connector allows Swimlane Turbine users to seamlessly scan any text for potential secrets, helping to identify and mitigate accidental exposure of credentials or confidential data. By integrating Secret Scanning with Swimlane Turbine, security teams can automate secret detection in their workflows, reduce the risk of data leaks, and ensure compliance with security best practices. The connector provides flexible options to include detected secrets and raw data in the output, supporting thorough investigation and response within automated playbooks.
Scan For Secrets Task
This task has a flag that will return both the secrets and the text scanned. Be careful when turning this flags on as returning matches might cause further spillage.
Actions
Scan for Secrets
Scan provided text for potential secrets such as passwords or API keys using Secret Scanning and receive a list of detected sensitive information.
Input
Argument Name | Type | Required | Description |
|---|---|---|---|
text | string | Required | Parameter for Scan for Secrets |
include_matches | boolean | Optional | Should include secrets detected. This might increase spillage as secrets are included in the output. |
include_raw_data | boolean | Optional | Should include the raw data analyzed. Returns the entire raw data analyzed. This might increase spillage as secrets might are included in the output. |
Input Example
{"text":"string","include_matches":true,"include_raw_data":true}
Output
Parameter | Type | Description |
|---|---|---|
headers | array | HTTP headers for the request |
headers.file_name | string | HTTP headers for the request |
headers.file | string | HTTP headers for the request |
reason | string | Response reason phrase |
status_code | number | HTTP status code of the response |
secrets | array | Output field: secrets |
secrets.description | string | Output field: secrets.description |
secrets.matches | array | Output field: secrets.matches |
secrets.id | string | Unique identifier |
secrets.keywords | array | Output field: secrets.keywords |
data_analyzed | string | Response data |
Output Example
{"headers":[],"reason":"OK","status_code":200,"secrets":[{"description":"GCP API key","matches":[],"id":"gcp-api-key","keywords":[]},{"description":"Generic API Key","matches":[],"id":"generic-api-key","keywords":[]},{"description":"Slack token","matches":[],"id":"slack-access-token","keywords":[]}],"data_analyzed":"xoxp-144qwerty\n\n\n https://www.googleapis.com/youtube/v3/search?part=snippet&ke..."}
Response Headers
Header | Description | Example |
|---|---|---|
Content-Type | The media type of the resource | application/json |
Date | The date and time at which the message was originated | Thu, 01 Jan 2024 00:00:00 GMT |