Using ScanSuite

Credentials

Secrets and leaked credentials found by scans, and verifying whether they still work.

Credentials found during static code analysis — secrets detection — and during infrastructure checks such as the OSINT credential-leakage stage or the Bruteforcer scan are saved here and managed from the Credentials page.

The link on each entry refers directly to the code line, so the issue can be checked immediately:

ScanSuite credentials list
The credentials list with source links

Adding credentials manually

Leaked credentials can be entered by hand or uploaded in bulk as a JSON list:

Credentials input form
Adding credentials manually or in bulk

Verifying whether they still work

Credentials matching a login/password pattern can be used by the Bruteforcer scanner to check their validity. Run it from the infrastructure page:

Bruteforcer scan configuration
Running the Bruteforcer scan

Confirmed credentials are alerted in the scan logs:

Bruteforcer scan log
Confirmed credentials in the scan log

And updated in the Credentials tab through the Verified and Details fields:

Verified credentials
Verified credentials in the list

Click a credential name for the full details:

Credential details
Credential detail view

Two different meanings of "verified" meet on this page. A secret found in code is marked verified when the model judges it to be a real credential rather than an example. A login/password pair is marked verified when the Bruteforcer successfully authenticated with it. The Details field records which.

A confirmed working credential is a live compromise, not a scan finding. Rotate it before you file it.

Last reviewed 2026-08-16