Backups : verified, not just launched
39 Views •Privileged accounts : the key safe
20 Views •Secrets forgotten in the code
25 Views •Email : the postman who sorts doubtful mail
19 Views •Your online hosting, properly set up
24 Views •Your everyday tools, properly configured
37 Views •Identities : who is really who
21 Views •Container platforms
26 Views •Backups : verified, not just launched
39 Views •Frameworks : measurement and declaration
37 Views •Your everyday tools, properly configured
37 Views •Exclusions : silencing what is normal at your site
35 Views •Who it is for
34 Views •My organisation : companies and licences
33 Views •Risk analysis : a score, and why
32 Views •Declaring a false positive : teaching the tool your habits
32 Views •A machine's detail page
32 Views •Opening a support ticket
31 Views •Choosing your subscription
31 Views •Installing the agent on a machine
29 Views •Users and their permissions
29 Views •Alerts : the list of what was noticed
29 Views •Activity : the running thread of what happens
28 Views •The asset inventory : everything you own
27 Views •Signing in : and what if I lost my password
27 Views •Creating your workspace and accepting the terms
27 Views •Why this tool exists
26 Views •Container platforms
26 Views •Secrets forgotten in the code
"Detected secrets" page
When you build a small in-house tool, a script that sends out quotes, a page that queries the database, you sometimes write a password straight into it, "just for testing". Then you forget it. This page goes and finds them.
What it shows
Each line gives the type of secret found, the file, the line number, the detection date, and a masked value. The secret itself is never shown in full: seeing that it exists is enough to decide.
Four counters at the top: the total number of findings, those still open, those judged critical and needing rotation, and the number of code repositories watched.
Two possible answers
Mark as rotated: you have replaced the password concerned. The line closes. False positive: it was not a real secret, an example in some documentation, a dummy value. The line closes too, and the tool learns.
No blame. Everyone has left a password lying in a file at some point. What matters is not never doing it, but seeing it and fixing it. This page exists for that, not to name a culprit.
Does this concern me?
If your company develops nothing, the page stays empty and displays a message saying so. At Les Ateliers, a former intern had written a small export program; two lines came up, they were dealt with in half an hour, and the page has been empty ever since.
A severity filter and a free search help you sort things once the list grows. Everything exports to a spreadsheet, to discuss with whoever wrote the code.
In closing
A password written "just to test" survives for years. This page finds them; it is up to you to take them out of the code and change them, in that order, because a published secret must be treated as known.
Commenting is not enabled on this course.