Creator Account Takeover Defense for Beginners: 2FA, Permissions, and Request Email Checks

Creative & Goals

Creator Account Takeover Defense for Beginners: 2FA, Permissions, and Request Email Checks

Beginner | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)

Beginner: No technical terms. Just answer the whiteboard's questions, following the examples, and it takes shape.

Help creators, streamers, and their team prepare for channel and social media takeovers by reviewing logins, 2-step verification, permissions, and request email checks. List the current settings of four accounts (channel, social media, email, payout account), starting with the email that gets notices for the other three. SMS codes beat nothing, but an authenticator app or passkey is stronger. Change passwords after a leak or when worried, not on a schedule. Check request emails with 5W1H before opening, and if in doubt, reopen from the official app or a bookmark instead of clicking. Common slip-ups are opening attachments, sharing passwords, giving everyone owner access, and leaving an old recovery email. In services with invitations, have teammates join with their own accounts, and note the takeover response and official procedures in advance, checking the latest guidance. The whiteboard has 4 A4 pages; the task board has 5 columns, 4 parent tasks, and 12 subtasks.

0 Likes 0 Copies Author: WeProcess
account takeover 2-step verification creators streamers security
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

Creator Account Defense for Beginners

How to use (4 pages): ① Write the goal and list the 4 accounts and your team (blocks①–⑤) → ② Decide how to check request emails and audit the traps (blocks⑥–⑨) → ③ Map each person's access and set the fix order (blocks⑩⑪) → ④ Plan the takeover response, owners, review dates, and recovery contacts (blocks⑫–⑭)

1/4 List accounts to protect

① What to protect (start here)

  • What to protect e.g. A channel built over 3 years and the monthly income
  • Current worry e.g. I log in with the same password as my editor
  • Where we want to be e.g. This month, all 4 accounts use an authenticator app or passkey, and teammates join by invitation

② The 4 accounts to protect (fill from the settings screens)

What you log in with 2-step verification method Concerns
Channel e.g. Email address and password e.g. SMS code (weaker than an authenticator app) e.g. My editor logs in with the same password
Social media e.g. Same password as other services e.g. Not set up e.g. Our former editor Casey may still have access
Email e.g. Password (not reused anywhere) e.g. Authenticator app e.g. Confirmation notices for the other 3 arrive here, so this is the key
Payout account e.g. Bank app e.g. Passkey e.g. Notices go to the manager's personal email

③ Editing teammates

  • e.g. Alex, who edits videos for me (3 a week)
  • e.g. Works on = video drafts and uploads
  • e.g. How they get in now = I gave them my password

④ Teammates who help run things

  • e.g. Bailey, the manager who handles sponsor requests
  • e.g. Handles = receiving request emails and checking income
  • e.g. How they get in now = a shared email address receives the requests

⑤ Former collaborators and outside vendors

  • e.g. Casey, who edited until six months ago
  • e.g. An outside vendor who makes thumbnails
  • e.g. I do not know if their access is still active

2/4 List what to check

⑥ 5W1H before opening (check the requests that reach the email in ②)

  • Work request email
    • What What is asked e.g. Do the request and the attachment type match what we discussed before?
    • Why Why this e.g. Why me, and why these terms? Stop if the reason does not match earlier talks
    • Who Who sent it e.g. Is the sender someone you have dealt with? For a new sender, check through the contact page on their company site
    • When When it came e.g. Does it rush you to act by today? Did an attachment arrive out of the blue when you had no recent contact?
    • Where Where to open e.g. Do not click links asking you to log in. Reopen from the official app or a bookmark
    • How How to act e.g. If in doubt, do not open it. Forward it to the manager in ④ and check together

⑦ Trap: opening a request attachment as is

  • What happens: e.g. Login data is stolen from the computer that opened it, and someone gets into the channel
  • How to check: e.g. Read the 6 in ⑥, and if even one does not fit, pass it to a teammate unopened
  • Prevention: e.g. Decide that attachments from new senders are opened only after confirming with the sender another way
  • Audit result: e.g. 1 of this week's 2 requests is unconfirmed. Check with the sender

⑧ Trap: sharing a password with teammates

  • What happens: e.g. Nobody knows who did what, and people who left can still get in
  • How to check: e.g. In the table in ②, mark every account where 2 or more people know the password
  • Prevention: e.g. Where a service has invitations, invite teammates from the admin screen so each uses their own account (conditions differ by service, so check the latest guidance)
  • Audit result: e.g. The channel password was shared with Alex in ③. Switch to an invitation on page 3

⑨ Trap: recovery email on an old address

  • What happens: e.g. After a takeover, notices go to an unused address and you cannot get the account back
  • How to check: e.g. Look at the recovery email and phone number in each settings screen
  • Prevention: e.g. Update them to your current address and number, and write "Checked" in the Concerns column of ②
  • Audit result: e.g. The channel recovery email was a student-days address. Fix today

3/4 Choose what to fix

⑩ Access by person (from the teammates in ③–⑤ and the result of ⑧; check that not everyone has owner access)

Work needed Access needed Current access How to fix
You e.g. Manage all settings and income e.g. Owner (can do everything) e.g. Owner e.g. Keep yourself as the only owner. If everyone is an owner, one takeover can cost everything
The editor in ③ e.g. Video drafts and uploads e.g. Editor (cannot manage permissions; whether they can publish differs by service, so check the latest guidance) e.g. Can do everything with the shared password e.g. Invite as editor and change the password
The manager in ④ e.g. Receive requests and check numbers e.g. View only e.g. Owner e.g. Lower to view only
The former helper in ⑤ e.g. None (no longer working together) e.g. None e.g. Still an editor e.g. Remove from members

⑪ Order of fixes (place the fixes from ⑩ and the results from ⑦–⑨)

Vertical axis: Impact (top = bigger damage if taken over) / Horizontal axis: Ease of fixing (right = quick to fix)

  • Plan the fix Big impact, takes effort. e.g. change where the payout account notices go (needs a bank procedure)
  • Fix today Big impact, quick to fix. e.g. remove the former helper in ⑤ and set up 2-step verification on social media
  • Think about later Small impact, takes effort. e.g. close an old social media account you no longer use
  • Fix in spare time Small impact, quick to fix. e.g. remove access for connected apps you do not use

4/4 Run it with your team

⑫ 4 steps after a takeover (use the table in ⑩ and write who acts)

  1. Notice Tell a teammate right away if something looks wrong e.g. If you see a login notice you do not know or a post you do not remember, call the manager in ④
  2. Stop it Protect the accounts you can still get into e.g. Change passwords, sign out other devices, remove unknown connected apps, and check that the recovery contacts and 2-step verification were not changed. Scan the device that opened the attachment with security software
  3. Get it back If you are locked out, use the official procedure e.g. Apply through the takeover procedure in the official help noted in ⑭
  4. Tell people Let viewers and partners know e.g. Warn viewers on another social network not to click links in suspicious posts, and contact your partners too

⑬ Owners and review dates (keep what you fixed in ⑩⑪)

Owner What to review Review date
2-step verification e.g. Me e.g. Is it on for all 4 accounts, and is any still on SMS? e.g. First Monday of each month
Permissions e.g. The manager in ④ e.g. Does the table in ⑩ match current access, and has anyone who left kept access? e.g. The day someone joins or leaves, and every 3 months
Recovery contacts e.g. Me e.g. Are the recovery email and phone number current? e.g. Every 3 months

⑭ Recovery contacts (open this first in an emergency)

  • Where the official procedures are e.g. The takeover procedure page in the official help of the channel, social media, and email. Bookmark them and write their names here (check the latest guidance)
  • Another way to reach teammates e.g. Phone numbers of the teammates in ③④, so you can reach them without the taken-over account
  • Bank and agency contacts e.g. The bank desk for the payout account, and the contact person at your agency

Task board contents

Unchecked 16 items

Map your accounts

On page 1, write the goal, tabulate the login method and 2-step verification of the 4 accounts (channel, social media, email, payout account), and list the teammates who work with you. This table feeds every page after it. Press Ctrl+F (⌘F on a Mac) and type 3/4 to jump to page 3.

Check email 2FA

Open the settings of the email account you use every day, look under security for the 2-step verification (2FA) method and the recovery email and phone number, and write them in the email row of block ②. Notices for your other accounts arrive here, so check it first. It is one account, so it fits between streams.

Set goal, fill rows

On block ①, write what you want to protect, your worry, and the finished picture, then fill the channel, social media, and payout rows of block ② from each settings screen. Done when all 4 rows are filled.

List your team

On blocks ③–⑤, write the editors, the helpers who run things, and former collaborators or outside vendors, and how each logs in today. They become the rows of the permissions table on page 3.

List what to check

On page 2, decide with 5W1H what to check before opening a request email, and test whether the 3 traps apply to you. The results become the material for choosing what to fix on page 3.

Set your 6 checks

For each of the 6 questions on block ⑥, write one thing you will check. Done when reading the 6 from the top is enough to decide when a request email arrives.

Audit the 3 traps

Read what happens, how to check, and how to prevent it on blocks ⑦–⑨, compare with the table on block ② and the settings screens, and write the result on the last sticky note. Fix whatever applies on page 3.

Brief your team

Tell the teammates on blocks ③–⑤ the 6 checks from block ⑥, and decide whom to ask instead of opening when in doubt. Done when everyone says they heard it.

Choose what to fix

On page 3, compare the access each teammate needs with what they have, write how to fix it, and set the order by impact and ease. Narrowing the fixes here makes owners and review dates on page 4 easier to set.

Map team access

In each service admin screen, check members and permissions, and fill the table on block ⑩ with the work needed, the access needed, the current access, and the fix. Also check that nobody but you holds owner access.

Rank the fixes

Place the fixes from block ⑩ and the results from blocks ⑦–⑨ in the 4 groups of block ⑪. Done when every fix sits in a group.

Fix the quick wins

Fix the items placed in "Fix today" on block ⑪ from each settings and admin screen. Move finished ones to the Fixed column of the task board.

Run it as a team

On page 4, decide what to do if an account is taken over, list owners and review dates, and note the recovery contacts. Share what you decide with your team and track it in the Awaiting review column until the review date.

Plan the 4 steps

On block ⑫, add who does what in each of the 4 steps. Done when every teammate can explain what happens from noticing to telling people.

Owners and dates

On block ⑬, write the owner and review date for 2-step verification, permissions, and recovery contacts. Done when the review dates are in everyone's calendar.

Note recovery info

On block ⑭, write where each service has its official takeover procedure in its help pages, another way to reach teammates, and the contacts for your payout account and agency. Check the procedure names and steps in the latest guidance.

Checking 0 items

Fixing 0 items

Fixed 0 items

Awaiting review 0 items

← Back to templates

Preview mode Creator Account Takeover Defense for Beginners: 2FA, Permissions, and Request Email Checks

Whiteboard preview

① What to protect (start here) ② The 4 accounts to protect (fill fro... ③ Editing teammates ④ Teammates who help run things ⑤ Former collaborators and outside ve... ⑦ Trap: opening a request attachment ... ⑧ Trap: sharing a password with teamm... ⑨ Trap: recovery email on an old address ⑩ Access by person (from the teammate... ⑪ Order of fixes (place the fixes fro... Plan the fix Fix today Think about later Fix in spare time ⑫ 4 steps after a takeover (use the t... ⑬ Owners and review dates (keep what ... ⑭ Recovery contacts (open this first ... Creator Account D... How to use (4 pag... What to protect a... Current state and... Traps and worries Prevention and re... 1/4 List accounts to ... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 List what to check ↙ 3/4 What to protecte.g. A channel built over 3 years and the monthly income Current worrye.g. I log in with the same password as my editor Where we want to bee.g. This month, all 4 accounts use an authenticator app or passkey, and teammates join by invitation What you log in with 2-step verificati... Concerns Channel e.g. Email address and password e.g. SMS code (weaker than an authenticator app) e.g. My editor logs in with the same password Social media e.g. Same password as other services e.g. Not set up e.g. Our former editor Casey may still have access Email e.g. Password (not reused anywhere) e.g. Authenticator app e.g. Confirmation notices for the other 3 arrive here, so this is the key Payout account e.g. Bank app e.g. Passkey e.g. Notices go to the manager's personal email e.g. Alex, who edits videos for me (3 a week) e.g. Works on = video drafts and uploads e.g. How they get in now = I gave them my password e.g. Bailey, the manager who handles sponsor requests e.g. Handles = receiving request emails and checking income e.g. How they get in now = a shared email address receives the requests e.g. Casey, who edited until six months ago e.g. An outside vendor who makes thumbnails e.g. I do not know if their access is still active ⑥ 5W1H before ope... Work request email WhatWhat is asked e.g. Do the request and the attachment type match what we discussed before? WhyWhy this e.g. Why me, and why these terms? Stop if the reason does not match earlier talks WhoWho sent it e.g. Is the sender someone you have dealt with? For a new sender, check through the contact page on their c… WhenWhen it came e.g. Does it rush you to act by today? Did an attachment arrive out of the blue when you had no recent cont… WhereWhere to open e.g. Do not click links asking you to log in. Reopen from the official app or a bookmark HowHow to act e.g. If in doubt, do not open it. Forward it to the manager in ④ and check together What happens: e.g. Login data is stolen from the computer that opened it, and someone gets into the channel How to check: e.g. Read the 6 in ⑥, and if even one does not fit, pass it to a teammate unopened Prevention: e.g. Decide that attachments from new senders are opened only after confirming with the sender another way Audit result: e.g. 1 of this week's 2 requests is unconfirmed. Check with the sender What happens: e.g. Nobody knows who did what, and people who left can still get in How to check: e.g. In the table in ②, mark every account where 2 or more people know the password Prevention: e.g. Where a service has invitations, invite teammates from the admin screen so each uses their own account (conditions differ by service, so check the latest guidance) Audit result: e.g. The channel password was shared with Alex in ③. Switch to an invitation on page 3 What happens: e.g. After a takeover, notices go to an unused address and you cannot get the account back How to check: e.g. Look at the recovery email and phone number in each settings screen Prevention: e.g. Update them to your current address and number, and write "Checked" in the Concerns column of ② Audit result: e.g. The channel recovery email was a student-days address. Fix today 3/4 Choose what to fix → 4/4 4/4 Run it with your ... Work needed Access needed Current access How to fix You e.g. Manage all settings and income e.g. Owner (can do everything) e.g. Owner e.g. Keep yourself as the only owner. If everyone is an owner, one takeover can cost everything The editor in ③ e.g. Video drafts and uploads e.g. Editor (cannot manage permissions; whether they can publish differs by service, so check the latest guidance) e.g. Can do everything with the shared password e.g. Invite as editor and change the password The manager in ④ e.g. Receive requests and check numbers e.g. View only e.g. Owner e.g. Lower to view only The former helper... e.g. None (no longer working together) e.g. None e.g. Still an editor e.g. Remove from members Vertical axis: Im... Big impact, takes effort. e.g. change where the payout account notices go (needs a bank procedure) Big impact, quick to fix. e.g. remove the former helper in ⑤ and set up 2-step verification on social media Small impact, takes effort. e.g. close an old social media account you no longer use Small impact, quick to fix. e.g. remove access for connected apps you do not use NoticeTell a teammate right away if something looks wronge.g. If you see a login notice you do not know or a post you do not remember, call the manager in ④ Stop itProtect the accounts you can still get intoe.g. Change passwords, sign out other devices, remove unknown connected apps, and check that the recovery contacts and 2-step verification were not changed. Scan the device that opened the attachment with security software Get it backIf you are locked out, use the official proceduree.g. Apply through the takeover procedure in the official help noted in ⑭ Tell peopleLet viewers and partners knowe.g. Warn viewers on another social network not to click links in suspicious posts, and contact your partners too Owner What to review Review date 2-step verification e.g. Me e.g. Is it on for all 4 accounts, and is any still on SMS? e.g. First Monday of each month Permissions e.g. The manager in ④ e.g. Does the table in ⑩ match current access, and has anyone who left kept access? e.g. The day someone joins or leaves, and every 3 months Recovery contacts e.g. Me e.g. Are the recovery email and phone number current? e.g. Every 3 months Where the official procedures aree.g. The takeover procedure page in the official help of the channel, social media, and email. Bookmark them and write their names here (check the latest guidance) Another way to reach teammatese.g. Phone numbers of the teammates in ③④, so you can reach them without the taken-over account Bank and agency contactse.g. The bank desk for the payout account, and the contact person at your agency → 2/4 List what to check ↙ 3/4 Choose what to fix → 4/4 Run it with your ...
100%

Drag to move, scroll to zoom