Secret Scanning

the secret scanning connector automates the process of identifying and alerting on potential secrets in text, helping to prevent data breaches secret scanning is a critical tool for identifying and mitigating the risk of sensitive data exposure in text based content this connector enables swimlane turbine users to automatically scan text for potential secrets, such as passwords and api keys, enhancing security posture by integrating with secret scanning, users can configure scans to include detected secrets and raw data for comprehensive analysis, while also controlling spillage risks this functionality is essential for maintaining data privacy and compliance with regulatory standards, making it a valuable addition to any security automation workflow 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 scans provided text for potential secrets like passwords or api keys using secret scanning 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