Back to course

F1 Cyber Basics for Public Service

0% done: 0 of 8 lessons

Lesson 4 of 8 · Video

Shared accounts and who has the keys

Progress is saved on this device only. Keep it across devices with a free LFW account.

Curriculum0 of 8 done
2 minutes 18 seconds. Captions are on. Narrated slides, with the Users screen of a fictional city site in WordPress Playground (fictional people). The narration is a synthesized voice; a recorded voice replaces it later.

Make every shared login belong to the institution, not to whoever set it up, with two people who can get in and a recovery address that outlives any one job.

Notes

Step 1 of 5

Start here

Small public institutions run on shared logins: the website admin, the town's social media pages, the email newsletter, the domain registration, vendor portals, the camera system. Each one was set up by someone, years ago, often with their own email address.

When that person leaves, retires or stops answering, the institution can lose its own voice. This lesson is about making sure every account belongs to the institution.

Step 2 of 5

How institutions lose their own accounts

  • The recovery email is a former employee's personal address. Password resets go to them.
  • Only one person ever knew the password, and it lived in their head or their phone.
  • Two-step sign-in is tied to one person's phone number.
  • Domain renewal notices go to a volunteer who moved away. The domain lapses, and the website and email stop working.
  • A vendor set up the account in the vendor's own name, and the contract ended.

None of these needs a hacker. They are housekeeping failures, and they are fixable on a quiet afternoon.

Step 3 of 5

The rules for every institutional account

1. The institution owns it. The login and recovery addresses are institutional, ideally a role mailbox such as webmaster@ or clerk@ that more than one person can read. Never a personal Gmail.

2. Two named people can get in. An owner and a backup. Where the platform supports it, give each person their own login with a role, instead of one shared password. Most social media and website platforms let you add several administrators.

3. It lives in the password manager. Where a password must be shared, keep it in a shared vault in the institution's password manager, not in email, text messages or a notebook.

4. It has two-step sign-in that does not depend on one phone. Use each person's own second step where accounts are individual. For a truly shared login, use a method the backup person can also reach, such as a code stored in the shared vault or a second security key.

5. Someone knows it exists. An account nobody remembers cannot be protected or recovered.

Step 4 of 5

Your web address deserves special care

Your domain name, the part after "www," carries both your website and usually your email. Whoever controls the registrar account controls both.

If your institution is a U.S. government organization, you may be eligible for a .gov domain. CISA manages .gov, and .gov domains are free for eligible U.S.-based government organizations. Whatever your domain, know which registrar holds it, which email gets its renewal notices, and when it expires.

Step 5 of 5

The day someone leaves

Offboarding is the same day, not "when we get to it":

  1. Remove their personal access to every system.
  2. Change every shared password they knew.
  3. Move any account in their name to the institution.
  4. Update recovery emails and phone numbers that pointed to them.
  5. Collect devices and security keys.

A kind departure still gets this list. It protects them as much as the institution: nobody can later claim they did something with an account they no longer had.

Sources

Transcript

Synthesized narration; a recorded voice replaces it later.

  1. 0:00Small public institutions run on shared logins: the website, the social media pages, the newsletter, the domain, vendor portals.
  2. 0:08Each one was set up by someone, years ago, often with their own email address.
  3. 0:13When that person leaves, the institution can lose its own voice.
  4. 0:18None of these needs a hacker.
  5. 0:20The recovery email is a former employee's personal address.
  6. 0:24Only one person knew the password.
  7. 0:26Two-step sign-in is tied to one phone.
  8. 0:28Renewal notices go to a volunteer who moved away.
  9. 0:31A vendor set up the account in its own name.
  10. 0:35The rules for every institutional account.
  11. 0:37One: the institution owns it, with a role mailbox such as webmaster@ or clerk@, never a personal Gmail.
  12. 0:44Two: two named people can get in.
  13. 0:48Where the platform supports it, give each person their own login with a role, instead of one shared password.
  14. 0:54Here, on a fictional city site, everyone has a named account, and two people are administrators of the city's own.
  15. 1:02The role column shows who can do what.
  16. 1:04An outside firm with an administrator account is worth a question: is the contract still running?
  17. 1:11Three: where a password must be shared, it lives in the institution's password manager, not in email or a notebook.
  18. 1:18Four: two-step sign-in that the backup person can also reach.
  19. 1:22Five: someone knows the account exists.
  20. 1:25Your web address deserves special care.
  21. 1:28Whoever controls the registrar account controls your website and usually your email.
  22. 1:33Eligible U.S. government organizations can get a .gov domain at no cost from CISA.
  23. 1:38Know your registrar, which email gets renewal notices, and when it expires.
  24. 1:44The day someone leaves, the same day: remove their access, change every shared password they knew, move accounts in their name, update recovery details, and collect devices and keys.
  25. 1:56Your task.
  26. 1:57List five institutional accounts.
  27. 2:00For each: what it controls, the login and recovery emails, the two people who can get in, and whether two-step sign-in is on.
  28. 2:08Keep the list in an access-controlled place.
  29. 2:10Any account with one person, a personal recovery email or no two-step sign-in goes to your supervisor.

Task

Your task at your institution

Make a list of five institutional accounts you know about. For each, write down:

Keep the list in the password manager or another access-controlled place, never on a public shared drive. Any account with one person, a personal recovery email or no two-step sign-in goes to your supervisor as a fix.

Quiz

4 questions. Choose one answer for each, then check them. Each answer shows its reason.

1. The town's social media page was set up with a former clerk's personal email as its recovery address. What is the risk?
2. How many named people should be able to get into each institutional account?
3. Someone who knew a shared password leaves. When should that password change?
4. Where should the list of shared accounts be kept?
Show the answers
  1. B. Whoever controls that email can take the page back. Recovery goes to that inbox. If it belongs to someone who left, so does the account.
  2. B. At least two. One person is a single point of failure. Two named people, each with their own access where possible, is the minimum.
  3. A. The day they leave. Offboarding happens the same day: remove their access and change every shared password they knew.
  4. B. In the password manager or a locked, access-controlled place. The list is a map for an attacker. Keep it where only the people responsible can see it.