Website and Online Store Security: Admin MFA, Updates, Plugins, and No Card Data on Your Server

Marketing & Sales

Website and Online Store Security: Admin MFA, Updates, Plugins, and No Card Data on Your Server

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

Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.

Website and online store security starts with one admin account per person, multi-factor authentication, an owner for checking updates, and card numbers kept off your own server. This template helps marketing and e-commerce staff split roles with their web agency, backups included, and turn the check into a monthly routine. Use an authenticator app or passkey for MFA; SMS beats nothing but is weaker. Typical gaps are a login shared with the agency, unused plugins, unverified updates, public test files and unchecked card handling. Check via the admin screen, update record or the agency, then rank findings by impact and ease of fixing, each with an owner and deadline. If unsure where to start, copy down who is in the CMS user list. Confirm payment method names and required steps with your payment provider's latest guidance. The whiteboard's 4 pages list parts, check risks, order fixes and assign roles; the task board has 5 columns, 4 parent tasks and 12 subtasks.

0 Likes 0 Copies Author: WeProcess
website operations online store security checklist multi-factor authentication plugin management
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

Website and Online Store Security

How to use (4 pages): ① On page 1, write the goal and list the site's parts and people (sections①–③) → ② On page 2, check the 5 items and the pitfalls (sections④–⑦) → ③ On page 3, sort what you found and build the fix table (sections⑧⑨) → ④ On page 4, set roles, a monthly check and agreements with the agency (sections⑩–⑫)

1/4 List the site's parts

① Goal and Scope of the Check (start here)

  • Why you are checking e.g. Learn who can sign in to the admin screen and build operating rules
  • Site in scope e.g. The company site and the online store
  • Period and who leads e.g. This month. The web owner leads and checks with the agency

② Parts of the Site (write the provider and contents)

  • e.g. Our online store
    • Domain e.g. The company you contract with and the renewal date
    • Server e.g. The hosting company and who can sign in to its admin screen
    • CMS e.g. A name such as WordPress and who manages it
    • Plugins e.g. How many are installed, who added them and why
    • Payment e.g. The payment provider and the card entry screen
    • Forms e.g. Where inquiries and sign-ups are delivered

③ People and Accounts (copy from the admin user list)

Admin screens they use Permission When to remove
Your own staff e.g. CMS, server, payment e.g. Administrator e.g. The day they move or leave
Web agency e.g. CMS, server e.g. Administrator e.g. Not decided (contract end date unknown)
Outside vendors e.g. Payment provider screen e.g. View only e.g. The day the payment contract ends

2/4 Check the risky spots

④ Check the Parts and Accounts from ②③ Against 5 Items

How to check Result Concerns
Multi-factor authentication In each user's settings in the admin screen (in some CMSs, the multi-factor plugin screen), see whether an authenticator app or passkey is on. Find the screen in your CMS's guide e.g. 2 of 5 people have not set it up e.g. One person uses SMS only. SMS beats nothing but is weak, so move to an authenticator app
Update status On the update screen and update record, see when the CMS core and plugins were last updated e.g. Core updated last month, 3 plugins waiting for updates e.g. Nobody is assigned to update
Test leftovers In the page list, see whether pages marked "test" or "old" are still public e.g. 2 test pages are public e.g. Ask the agency about test files left on the server
Backups In the server admin screen or by asking the agency, see how often backups run, where they are stored and the record of restores e.g. Daily and automatic. Stored only on the same server e.g. If the whole server is lost, nothing can be restored
Payment method In the payment provider's admin screen or contract documents, see whether card numbers are kept off your own server e.g. The card entry screen is the payment provider's screen e.g. Confirm the method name in the provider's latest guidance. Even if card numbers do not reach you, the site that sends people to the entry screen still needs protection (updates, accounts)

⑤ Pitfall: Sharing an Admin Account with the Agency

  • [What happens] e.g. People from a finished contract or who left can still sign in, and nobody can trace who changed what
  • [How to check] e.g. Look in the user list for accounts named just 'admin' or a company name
  • [One step to prevent it] e.g. One account per person, deleted on the day the contract ends
  • [In our case] e.g. One account is shared with the agency → go to ⑧

⑥ Pitfall: Leaving Unused Plugins Installed

  • [What happens] e.g. Deactivated ones tend to drop out of updates, so weak spots stay
  • [How to check] e.g. In the plugin list, mark deactivated ones and ones not updated for a long time
  • [One step to prevent it] e.g. Delete what you do not use, after checking with the agency
  • [In our case] e.g. 4 deactivated, and nobody knows what 2 of them were for → go to ⑧

⑦ Pitfall: Leaving Updates Entirely to the Agency

  • [What happens] e.g. Everyone assumes it was updated, nobody checks, and pending updates pile up for months
  • [How to check] e.g. Compare the record on the update screen with the agency's work report
  • [One step to prevent it] e.g. Ask for the date and what was updated, and have your own staff confirm on screen
  • [In our case] e.g. There is no rule for getting reports → go to ⑧

3/4 Set the fix order

⑧ Sort What You Found in ④–⑦ (impact × ease of fixing)

Vertical axis: Impact (higher = bigger) / Horizontal axis: Ease of fixing (further right = easier)

  • Plan the fix Big impact but takes effort. Set an owner and a deadline. e.g. Also store backups in a second place
  • Fix now Big impact and quick to fix. Start here. e.g. Split shared accounts into one per person and turn on multi-factor authentication
  • Revisit at next check Small impact and takes effort. Revisit at the check in ⑪. e.g. Delete unused themes, keeping one spare, after checking with the agency
  • Fix along the way Small impact and quick to fix. Do it together with other work. e.g. Tidy up drafts that are not published

⑨ What to Fix, Owner, Deadline (pick from the top two zones of ⑧)

What to fix Owner Deadline
First e.g. Split shared accounts into one per person and turn on multi-factor authentication e.g. Web owner e.g. This Friday
Second e.g. Make test pages private and have test files deleted e.g. Agency e.g. This week
Third e.g. Check and delete the 4 deactivated plugins e.g. Agency e.g. Week 2
Fourth e.g. Also store backups in a second place e.g. Agency and hosting company e.g. End of the month

4/4 Assign roles and run it

⑩ Roles for the Fixes in ⑨ and Monthly Work (RACI)

R Does the work A Accountable (one person) C Consulted I Informed
Account management e.g. Web owner e.g. Manager e.g. Agency e.g. Whole team
Running updates e.g. Agency e.g. Web owner e.g. None e.g. Manager
Checking updates e.g. Web owner e.g. Manager e.g. Agency e.g. None
Backups e.g. Hosting company e.g. Web owner e.g. Agency e.g. Manager
Payment and forms e.g. Agency e.g. Manager e.g. Payment provider e.g. Web owner

⑪ Monthly Check Flow

  1. Open Open the admin user list and the update screen e.g. 30 minutes on the first Monday morning of each month
  2. Compare Compare the update record with the agency's report e.g. Are updates still pending? Have unknown people been added?
  3. Ask Ask the agency about what you cannot tell e.g. Is there a record of restoring from a backup?
  4. Record Write the result in the table of ④ and add fixes to ⑨ e.g. For any new fix, set an owner and a deadline too

⑫ Agreements with the Agency

  • Accounts e.g. One account per agency person too. Deleted on the day the contract ends
  • Update reports e.g. Send a monthly summary of the date, what was updated and what was checked
  • Cleaning up after work e.g. Delete test pages and files the day work ends and tell us they are gone

Task board contents

Not checked 16 items

List site parts

On page 1, write why you are checking, then list the parts that keep the site running and the people and accounts that can sign in to the admin screen. The check on page 2 builds on this list, so do it first. Press Ctrl+F (⌘F on Mac) and type "3/4" to jump to page 3.

Copy the user list

Sign in to the CMS admin screen and open the user list (the "Users" screen in WordPress). Sort everyone listed into your own team, the agency and outside vendors, then copy names and permissions into the table in section ③. It takes about 15 minutes. Done when everyone on the list is written in ③.

Set goal and scope

In section ①, write the goal of the check, the site in scope, and the period and people involved. Done when the three notes are filled in.

Fill six branches

In the six branches of section ②, write the provider or content for domain, server, CMS, plugins, payment and forms. Where you do not know, write "ask the agency" and move on.

Check risky spots

On page 2, check the parts and accounts from page 1 against five items, and write whether your site matches the three common pitfalls. What you find here decides the fix order on page 3.

Check the 5 items

Follow the how-to-check column of the table in section ④, looking at the admin screen and the update record, and write the result and anything that worries you. Write "ask the agency" for what you cannot see yourself.

Note the pitfalls

In each frame of sections ⑤–⑦, rewrite the sample for what happens, how to check and the one step to prevent it in your own words, then note on the last sticky whether it applies to you. Done when all three frames describe your situation.

Ask the agency

Gather everything you marked "ask the agency" in sections ④ and ⑤–⑦ into a single message and write the replies into the result column of ④. While you wait, keep the task in the "Waiting for web agency" column.

Set the fix order

On page 3, sort what you found on page 2 by impact and ease of fixing, then turn it into a table of what to fix, who does it and by when. Do not fix everything at once, and start with what has a big impact and is easy to fix.

Sort your findings

Place each point you wrote as a concern in sections ④–⑦ into one of the four zones of section ⑧. Done when every sticky is in a zone.

Build the fix table

Pick four items from "Fix now" and "Plan the fix" in section ⑧ and write what to fix, who and by when in the table of section ⑨. Done when no row is missing an owner or a deadline.

Do the quick fixes

Finish the first row of section ⑨ (in the sample, splitting shared accounts into one per person) by its deadline, then add the date you finished in the deadline column of the same row.

Assign and run

On page 4, decide who does what with a RACI, then write the monthly check routine and the agreements with the agency. Track what you decided in the "In operation" column of the task board.

Fill in the RACI

For each of the five jobs in section ⑩, write who does the work, who is finally accountable, who is consulted and who is informed. Done when the accountable column has exactly one person per row.

Plan monthly check

Pick the day for the check using the four-step flow of section ⑪ and put it in your monthly calendar. After the first check, write the result in the table of section ④.

Agree with agency

Tell the agency the three agreements of section ⑫ and get a reply accepting them. Done when you add the date of the reply to the sticky in ⑫.

Checking 0 items

Fixing 0 items

Waiting for web agency 0 items

In operation 0 items

← Back to templates

Preview mode Website and Online Store Security: Admin MFA, Updates, Plugins, and No Card Data on Your Server

Whiteboard preview

① Goal and Scope of the Check (start ... ③ People and Accounts (copy from the ... ④ Check the Parts and Accounts from ②... ⑤ Pitfall: Sharing an Admin Account w... ⑥ Pitfall: Leaving Unused Plugins Ins... ⑦ Pitfall: Leaving Updates Entirely t... ⑧ Sort What You Found in ④–⑦ (impact ... Plan the fix Fix now Revisit at next check Fix along the way ⑨ What to Fix, Owner, Deadline (pick ... ⑩ Roles for the Fixes in ⑨ and Monthl... ⑪ Monthly Check Flow ⑫ Agreements with the Agency Website and Onlin... How to use (4 pag... Goal and what is ... How to check and ... Risky spots and p... What to fix and n... 1/4 List the site's p... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Check the risky s... ↙ 3/4 Why you are checkinge.g. Learn who can sign in to the admin screen and build operating rules Site in scopee.g. The company site and the online store Period and who leadse.g. This month. The web owner leads and checks with the agency ② Parts of the Si... e.g. Our online store Domain e.g. The company you contract with and the renewal date CMS e.g. A name such as WordPress and who manages it Payment e.g. The payment provider and the card entry screen Server e.g. The hosting company and who can sign in to its admin s… Plugins e.g. How many are installed, who added them and why Forms e.g. Where inquiries and sign-ups are delivered Admin screens the... Permission When to remove Your own staff e.g. CMS, server, payment e.g. Administrator e.g. The day they move or leave Web agency e.g. CMS, server e.g. Administrator e.g. Not decided (contract end date unknown) Outside vendors e.g. Payment provider screen e.g. View only e.g. The day the payment contract ends How to check Result Concerns Multi-factor auth... In each user's settings in the admin screen (in some CMSs, the multi-factor plugin screen), see whether an authenticator app or passkey is on. Find the screen in your CMS's guide e.g. 2 of 5 people have not set it up e.g. One person uses SMS only. SMS beats nothing but is weak, so move to an authenticator app Update status On the update screen and update record, see when the CMS core and plugins were last updated e.g. Core updated last month, 3 plugins waiting for updates e.g. Nobody is assigned to update Test leftovers In the page list, see whether pages marked "test" or "old" are still public e.g. 2 test pages are public e.g. Ask the agency about test files left on the server Backups In the server admin screen or by asking the agency, see how often backups run, where they are stored and the record of restores e.g. Daily and automatic. Stored only on the same server e.g. If the whole server is lost, nothing can be restored Payment method In the payment provider's admin screen or contract documents, see whether card numbers are kept off your own server e.g. The card entry screen is the payment provider's screen e.g. Confirm the method name in the provider's latest guidance. Even if card numbers do not reach you, the site that sends people to the entry screen still needs protection (updates, accounts) [What happens] e.g. People from a finished contract or who left can still sign in, and nobody can trace who changed what [How to check] e.g. Look in the user list for accounts named just 'admin' or a company name [One step to prevent it] e.g. One account per person, deleted on the day the contract ends [In our case] e.g. One account is shared with the agency → go to ⑧ [What happens] e.g. Deactivated ones tend to drop out of updates, so weak spots stay [How to check] e.g. In the plugin list, mark deactivated ones and ones not updated for a long time [One step to prevent it] e.g. Delete what you do not use, after checking with the agency [In our case] e.g. 4 deactivated, and nobody knows what 2 of them were for → go to ⑧ [What happens] e.g. Everyone assumes it was updated, nobody checks, and pending updates pile up for months [How to check] e.g. Compare the record on the update screen with the agency's work report [One step to prevent it] e.g. Ask for the date and what was updated, and have your own staff confirm on screen [In our case] e.g. There is no rule for getting reports → go to ⑧ 3/4 Set the fix order → 4/4 4/4 Assign roles and ... Vertical axis: Im... Big impact but takes effort. Set an owner and a deadline. e.g. Also store backups in a second place Big impact and quick to fix. Start here. e.g. Split shared accounts into one per person and turn on multi-factor authentication Small impact and takes effort. Revisit at the check in ⑪. e.g. Delete unused themes, keeping one spare, after checking with the agency Small impact and quick to fix. Do it together with other work. e.g. Tidy up drafts that are not published What to fix Owner Deadline First e.g. Split shared accounts into one per person and turn on multi-factor authentication e.g. Web owner e.g. This Friday Second e.g. Make test pages private and have test files deleted e.g. Agency e.g. This week Third e.g. Check and delete the 4 deactivated plugins e.g. Agency e.g. Week 2 Fourth e.g. Also store backups in a second place e.g. Agency and hosting company e.g. End of the month R Does the work A Accountable (on... C Consulted I Informed Account management e.g. Web owner e.g. Manager e.g. Agency e.g. Whole team Running updates e.g. Agency e.g. Web owner e.g. None e.g. Manager Checking updates e.g. Web owner e.g. Manager e.g. Agency e.g. None Backups e.g. Hosting company e.g. Web owner e.g. Agency e.g. Manager Payment and forms e.g. Agency e.g. Manager e.g. Payment provider e.g. Web owner OpenOpen the admin user list and the update screene.g. 30 minutes on the first Monday morning of each month CompareCompare the update record with the agency's reporte.g. Are updates still pending? Have unknown people been added? AskAsk the agency about what you cannot telle.g. Is there a record of restoring from a backup? RecordWrite the result in the table of ④ and add fixes to ⑨e.g. For any new fix, set an owner and a deadline too Accountse.g. One account per agency person too. Deleted on the day the contract ends Update reportse.g. Send a monthly summary of the date, what was updated and what was checked Cleaning up after worke.g. Delete test pages and files the day work ends and tell us they are gone → 2/4 Check the risky s... ↙ 3/4 Set the fix order → 4/4 Assign roles and ...
100%

Drag to move, scroll to zoom