Backups : verified, not just launched
23 Views •Privileged accounts : the key safe
14 Views •Secrets forgotten in the code
14 Views •Email : the postman who sorts doubtful mail
14 Views •Your online hosting, properly set up
14 Views •Your everyday tools, properly configured
24 Views •Identities : who is really who
14 Views •Container platforms
15 Views •Risk analysis : a score, and why
25 Views •Opening a support ticket
25 Views •Your everyday tools, properly configured
24 Views •Exclusions : silencing what is normal at your site
23 Views •Declaring a false positive : teaching the tool your habits
23 Views •Choosing your subscription
23 Views •Activity : the running thread of what happens
23 Views •Backups : verified, not just launched
23 Views •Frameworks : measurement and declaration
23 Views •My organisation : companies and licences
23 Views •Who is watching while you work
15 Views •Secrets forgotten in the code
14 Views •The asset inventory : everything you own
15 Views •Container platforms
15 Views •Alerts : the list of what was noticed
14 Views •Vulnerabilities : the updates that are missing
14 Views •Creating your workspace and accepting the terms
14 Views •The equipment list : your machines
14 Views •Installing the agent on a machine
14 Views •The vocabulary, once and for all
14 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.
Commenting is not enabled on this course.