Business & Strategy
Small Business Security: First 5 Steps for Beginners | Updates, Passwords, Sharing, Backups, Help
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.
A small business security template for companies of 10 to 30 people with no IT staff to check five basics, pick what is missing, and set owners and deadlines. The five are software updates, passwords with two-step verification, file sharing, backups, and who to call. Defenses work like Swiss cheese: one slice has holes, but the holes in stacked slices rarely line up (the Swiss cheese model). Common stumbles: relying on antivirus alone, naming no owner, and leaving two-step verification off for executives. Not sure where to start? Open the two-step verification list in your email admin console and count who has it on. Fill in the tables using the "e.g." examples, and each measure gets an owner, deadline, and check date, kept up monthly. The whiteboard has 4 pages: check where you stand, lay out the five measures, choose priorities, set owners and deadlines. The task board has 5 columns, from untouched to monthly check, and 4 parent tasks with 3 subtasks each.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Small Business Security: First 5
How to use (4 pages): ① On page 1, write the goal and tabulate where the 5 measures stand → ② On page 2, check the pitfalls and list what to do → ③ On page 3, pick priorities with MoSCoW and impact vs. effort and write the no-exceptions promises → ④ On page 4, set owners, deadlines and check dates and run the monthly check
1/4 Check where you stand
① Goal and scope (start here)
- Why tighten security e.g. So we can answer right away when a client asks about our measures
- Scope and period e.g. PCs, phones, email and shared folders for 25 employees. One full pass in 2 months
- A view everyone shares Defenses are like Swiss cheese. One slice leaves holes, but stack many and the holes rarely line up (the Swiss cheese model) e.g. Even if an update is missed, a backup lets you restore
② Where the 5 measures stand (check ledgers, settings screens, and vendors)
| Current state | Pain points | Where you checked | |
|---|---|---|---|
| Updates | e.g. Automatic updates are left to each person. Two old PCs | e.g. Worried work software will stop working after an update | e.g. Device ledger and each PC's settings screen |
| Passwords and login | e.g. 10 of 25 people use two-step verification | e.g. Some people reuse the same password | e.g. The list in the email admin console |
| Sharing settings | e.g. Some shared folders are open to "anyone with the link" | e.g. Unsure whether people who left can still see files | e.g. The cloud sharing settings screen |
| Backups | e.g. Only accounting data is saved weekly to an external drive | e.g. Never tested whether it can be restored | e.g. Backup logs and the backup drive |
| Who to call | e.g. Not decided | e.g. Nobody knows who to contact when in trouble | e.g. Maintenance contract and a check with the vendor |
③ Sum up table ② one row at a time (now → what is missing → the goal)
- As-Is Current state e.g. Only 1 of the 5 has an owner. Settings are left to individuals
- Gaps and issues e.g. Two-step verification under half, restore untested, no one to call
- To-Be Target state e.g. All 5 have an owner and check date, kept going by a monthly check
2/4 Expand the 5 measures
④ Pitfall 1 Antivirus alone feels enough (compare with ②)
- What happens: e.g. Installing antivirus feels like enough, so updates and backups stay untouched
- How to check: e.g. Count how many blanks or "not decided" entries are in the 5 rows of table ②
- The fix: e.g. Do not stop at one slice of cheese; stack the 5 measures one by one
- In our company: e.g. It applies. Who to call is "not decided" and updates were left to each person
⑤ Pitfall 2 Naming no owner
- What happens: e.g. Everyone assumes "someone is doing it", so update notices and contract renewal dates get ignored
- How to check: e.g. For each of the 5 measures, try writing the owner next to table ② and see if you can name one right away
- The fix: e.g. Name one person per measure. It can be on top of other work
- In our company: e.g. Only backups had a name
⑥ Pitfall 3 An exception for the boss's account
- What happens: e.g. Two-step verification is turned off for the boss or executives only, leaving a hole where the most important information is
- How to check: e.g. In the two-step list in the email admin console, see whether the executives are turned on
- The fix: e.g. Write that executives are included in promises ⑩–⑫ and have the owner help with setup
- In our company: e.g. 2 of 3 executives were off
⑦ What to do for each of the 5 measures (from pain points in ② and results of ④–⑥)
| What to do | Concrete example | How to confirm it is done | |
|---|---|---|---|
| Updates | e.g. Turn on automatic updates on everyone's PCs and phones | e.g. Put devices the maker no longer supports into the replacement plan | e.g. Write each device's last update date in the ledger |
| Passwords and login | e.g. Everyone uses two-step verification and stops reusing passwords | e.g. Choose an authenticator app or a passkey (logging in with fingerprint, face, or the screen-lock PIN) over SMS codes. SMS is better than nothing but weak | e.g. Everyone shows as turned on in the admin console list |
| Sharing settings | e.g. Change "anyone with the link" to "people inside the company only" | e.g. Remove sharing for people who left or business partners no longer working with you | e.g. Look at the list of external sharing on the sharing settings screen |
| Backups | e.g. Decide which data matters and save it automatically | e.g. Keep one more copy somewhere not normally connected | e.g. Twice a year, pick one file and test restoring it |
| Who to call | e.g. Put the maintenance vendor's contact and contract scope on one sheet | e.g. Check official support desks against the latest guidance and add them | e.g. The contact sheet is posted and everyone can say where it is |
3/4 Pick what to do first
⑧ Sort the actions from ⑦ into 4 (MoSCoW)
Must Required
- e.g. Two-step verification for everyone including the boss, automatic updates for all, automatic saving of important data, and posting the contact list in one place
Should Worth doing
- e.g. Review sharing settings and test whether restore works
Could If possible
- e.g. Bring forward replacing old PCs
Won't Not this time
- e.g. Replace every PC in the company at once (consider next fiscal year)
⑨ Place the Musts from ⑧ by impact and effort
Vertical axis: Impact (bigger toward the top) / Horizontal axis: Effort (more toward the right)
- Do first (high impact, low effort) e.g. Turn on two-step verification for everyone. The owner helps with setup in person
- Plan and do (high impact, high effort) e.g. Decide automatic saving of important data with the vendor
- Fit in gaps (low impact, low effort) e.g. Gather the contact list and post it where everyone can see it
- Rethink the method (low impact, high effort) e.g. Write update manuals for everyone → drop the manuals, and have the owner set up each PC in person
⑩ Promise 1 Same settings for the boss and executives
- Everyone, including the boss and executives, uses two-step verification
- Change passwords when they leak or you are worried (do not change them on a fixed schedule)
- e.g. Install the authenticator app on the boss's phone too, with the owner helping
⑪ Promise 2 Keep company data in company places
- Do not put company data in personal cloud accounts or email
- No exceptions, even when in a hurry or for executives
- e.g. Exchange files with clients through company accounts
⑫ Promise 3 Speak up as soon as something looks wrong
- Do not click links in suspicious emails. Reopen from the official app or a bookmark
- No blame if you clicked. Report it to the help contact right away
- e.g. The boss reports to the same contact. The first contact is the admin staff member
4/4 Set owners and deadlines
⑬ Set owner, deadline, and check date in the order decided in ⑨
| Owner | Deadline | Check date | Backup person | |
|---|---|---|---|---|
| Updates | e.g. Admin staff | e.g. Friday of week 1 | e.g. Monthly check day | e.g. Accounting staff |
| Passwords and login | e.g. Admin staff (also helps with the boss's setup) | e.g. Friday of week 2 | e.g. Monthly check day | e.g. Sales staff |
| Sharing settings | e.g. Sales staff | e.g. Friday of week 3 | e.g. Monthly check day | e.g. Admin staff |
| Backups | e.g. Accounting staff | e.g. End of month 1 | e.g. Every 6 months (restore test) | e.g. Maintenance vendor contact |
| Who to call | e.g. Admin staff | e.g. Friday of week 1 | e.g. Once a year | e.g. The boss |
⑭ Monthly check (e.g. 30 minutes on the first Monday)
- Open Open the ledger and admin consoles e.g. Device ledger, email admin console, sharing settings screen
- Check Check using the methods listed in ⑦ e.g. Are there 0 people without two-step verification?
- Fix Fix gaps or ask the owner e.g. Turn on two-step verification for newcomers on the spot
- Record Write the result and the next check date e.g. Change the check date in ⑬ to next month and leave a one-line note
Task board contents
Untouched 16 items
Check your defenses
On page 1, write the goal and scope, tabulate how each of the 5 measures stands and what is troubling, and sum it up as now → what is missing → target. Once the current state is on the table, you can decide what to add on page 2. Press Ctrl+F (⌘F on Mac) and enter 3/4 to jump to page 3.
Count 2-step users
The first step, and it only takes opening one admin screen and counting. Open the admin console of your email account (e.g. Google Workspace or Microsoft 365), find the list showing the status of two-step verification (a setting that checks who you are with your phone as well as your password), count how many people have it turned on, and write "X of Y" in the "Passwords and login" row of board ②. Where the list is depends on the service and plan, so check your service's help. If there is no admin console or list, ask everyone to check on their own settings screen.
Set goal and scope
On board ①, write why you are tightening security, which devices and accounts are covered, and the period. Done when the 3 notes are filled in.
Map the 5 measures
In the table on board ②, write the current state and pain points you found from ledgers, settings screens, and vendors, then sum each row up on board ③ as now → what is missing → target.
Expand the 5 areas
On page 2, test three common pitfalls against your own company and list everything to do for each of the 5 measures. The more candidates you put out here, the less likely you are to miss something when choosing on page 3.
Review 3 pitfalls
On each of boards ④–⑥, rewrite the examples of what happens, how to check, and the fix in your own words, and on the last note write whether it applies and what you found. Done when the notes in all 3 frames are in your own words.
List what to do
In the table on board ⑦, write what to do and a concrete example for each of the 5 measures, based on the pain points in ② and the results of ④–⑥. Done when every row has at least one.
Note how to verify
In the last column of board ⑦, write whether you can tell it is done from the ledger, admin console, settings screen, or a check with the vendor. You will use it as-is on the check dates on page 4.
Pick the priorities
On page 3, sort the actions from ⑦ into four groups, then rank the must-dos by impact and effort to decide what comes first. Also write the promise of no exceptions, even for the boss and executives.
Sort with MoSCoW
On board ⑧, sort the actions from ⑦ into Must, Should, Could, and Won't this time. Keep Must to 3 to 5 items.
Impact-effort rank
On board ⑨, place the Musts in the four impact and effort quadrants and number them starting from Do first.
Write the 3 pledges
In the 3 promises on ⑩–⑫, write that the boss and executives are held to the same rules. Done when an executive gives a quick okay.
Set owners & dates
On page 4, set an owner, deadline, and check date for each of the 5 measures and decide how the monthly check will run. Track what you decide in the Waiting for check date column of the task board.
Set owner and dates
In the table on board ⑬, write the owner, deadline, check date, and backup person for each of the 5 measures. Done when each measure has two names, an owner and a backup. For how to check, use the last column of ⑦.
Pick the check day
Read the 4-step flow on board ⑭, pick the monthly check day and time, and put it in the calendar.
Run the first check
Run the first check following the flow on board ⑭, and change the check dates in ⑬ to next month. Move finished measures to the Monthly check column.