Backups : verified, not just launched
127 Views •Privileged accounts : the key safe
115 Views •Secrets forgotten in the code
115 Views •Email : the postman who sorts doubtful mail
115 Views •Your online hosting, properly set up
119 Views •Your everyday tools, properly configured
126 Views •Identities : who is really who
87 Views •Container platforms
88 Views •The cybersecurity dictionary
160 Views •Defence : the blocked addresses
155 Views •Who is watching while you work
147 Views •The crisis room: the button never to press
143 Views •Risk analysis : a score, and why
143 Views •The help centre and the explanation bubbles
140 Views •Opening a support ticket
139 Views •Exclusions : silencing what is normal at your site
137 Views •The dashboard : ten seconds to know
137 Views •Your three habits, and what comes next
136 Views •My organisation : companies and licences
134 Views •Signing in : and what if I lost my password
133 Views •Who it is for
133 Views •Companies : the administrative record
133 Views •Creating your workspace and accepting the terms
133 Views •Vulnerabilities : the updates that are missing
133 Views •The equipment list : your machines
132 Views •Installing the agent on a machine
128 Views •Playbooks : ready-made responses
127 Views •Backups : verified, not just launched
127 Views •Privileged accounts : the key safe
"Privileged accounts" page
Every company has a few accounts that can do anything: the one that administers the server, the one that runs the mail, the one for the management software. Those passwords often end up on a sticky note or in a shared file. This page gives them a proper safe.
What goes in it
Each entry carries a meaningful name, a target address, a username, and the secret itself. They are sorted by nature: local administrator, domain administrator, database, network equipment, online service, application. That classification is not decorative: it tells you at a glance which accounts are the most sensitive.
How the safe opens
To read a secret, two things are asked. First a six-digit code from your authentication app, the very one that protects your login. Then a reason: "work on the quotes server", for example.
The reason is not paperwork. It is recorded with your name and the time. The day someone wonders who touched what, the answer is written down, and it protects the honest person first.
Rotation
A button lets you change a secret and keep a record of it. The simple good practice: when someone leaves the company, rotate the accounts they knew. At Les Ateliers that happens once or twice a year, and takes ten minutes.
This page also counts towards your insurability score: an insurer looks precisely at whether privileged accounts are kept in a safe or not.
In closing
Accounts that can do anything deserve better than a shared file. A vault, regular rotation, and a record of who opened what: those are the three things an auditor will ask for, and the three that will save you.
Commenting is not enabled on this course.