You got handed the computers on top of a real job. Do these eleven things in this order. When one of them does not fit how your shelter actually works, tell me and I will fix the list, because I am still learning your side of this.

1. Turn on two-step sign-in everywhere

Why. Most break-ins start with a stolen or guessed password. A second step, usually a code on your phone, stops almost all of them, and it costs nothing.

The free way. It is built into Google Workspace and Microsoft 365 and into most software you rent online. Turn it on for email first, then the shelter software, payroll and the bank.

How long. An afternoon to switch it on, about a week for everyone to enroll their phone.

Who. Whoever manages your email accounts flips the switch. Each staff member enrolls their own phone.

2. Keep one list of who has accounts, and close them the day someone leaves

Why. Volunteers and seasonal staff come and go. Accounts nobody closed are the most common way records leak.

The free way. Use one sign-in system for everything you can, through the nonprofit programs of Google Workspace or Microsoft 365, so turning off one account turns off the rest. Write a one-page leaving checklist: email, shelter software, door codes, shared passwords.

How long. A morning to write the checklist. Ten minutes per person after that.

Who. The office manager or whoever already handles new staff and volunteers.

3. Back up your records, and prove you can get them back

Why. Ransomware is criminals locking your files and demanding money to unlock them. It closes small organizations that have no second copy. A backup you have never restored is a hope, not a plan.

The free way. Turn on the version history and backup that come with your cloud file storage. Ask your shelter-software vendor how to export your data and do it quarterly. Keep one copy somewhere that cannot be changed or deleted by the same account. Once a quarter, restore one file to prove it works.

How long. A day to set up, an hour each quarter after that.

Who. Whoever looks after the computers, with the vendor’s help desk on the phone.

4. Write down every computer, tablet and camera you own, and who has it

Why. You cannot protect, update or recover what you do not know you have.

The free way. A spreadsheet is fine. When it gets painful, free inventory software (Snipe-IT, on the Resources page) does the same job with a search box.

How long. An afternoon walking the building with a clipboard.

Who. Anyone careful. This is a good volunteer job.

5. Keep every device updated, from one place

Why. Out-of-date laptops are the door attackers walk through. Updates close the doors; central management means you can see that they did.

The free way. Device management is included in the nonprofit editions of Microsoft 365 and Google Workspace. Turn on automatic updates and require a screen lock.

How long. A day to enroll the devices you listed in step 4.

Who. Your email administrator, or a volunteer who is comfortable in settings menus.

6. Remove remote-control tools you do not manage

Why. Programs that let a helper take over a screen from afar (TeamViewer is the common one) let attackers do the same thing, and they are a favorite target.

The free way. Uninstall them. When someone needs to help with a screen, use the remote-help feature built into the productivity suite you already pay for, where access is logged and ends when the session ends.

How long. An hour per machine.

Who. Whoever looks after the computers.

7. Keep visitors, building controls and card readers off the staff network

Why. A visitor’s phone, the thermostat and the card terminal should never be able to reach adopter records. Put them on separate lanes of your network, so a problem stays in one lane. Your router calls these lanes VLANs.

The free way. The firewall or router you already own almost certainly supports it. Your internet provider or a local IT shop can set it up in one visit: a guest lane, a building-systems lane, a payments lane, a staff lane.

How long. Half a day with someone who knows your router.

Who. A volunteer or a paid technician, once. After that it needs no attention.

8. Keep a record of what your systems are doing, and name someone who looks

Why. When something goes wrong, the record of what each computer did is what tells you how bad it is and what to fix. Without that record you are guessing.

The free way. Turn on your firewall’s logging and have it email alerts to a shared inbox. When you have a person with time, free software (Wazuh, on the Resources page) collects alerts from every computer in one place. Do not install it until someone is named to watch it.

How long. A day to set up. The ongoing part is the attention, not the software.

Who. A named person, even if that is a volunteer who checks on Friday afternoons.

9. Teach staff what a scam email looks like, and give them one place to report it

Why. Your staff and volunteers see the suspicious email first. If they know what to look for and where to send it, they are your alarm system.

The free way. CISA, the federal cybersecurity agency, runs a free fake-email test and offers free training content. Create one shared inbox for “this looks odd” and thank everyone who uses it.

How long. One hour in a staff meeting, repeated once a year.

Who. The director. Nothing about this is technical.

10. Write a one-page plan for a bad day, and practice it once a year

Why. The first hour of an incident matters most, and nobody thinks clearly under stress. A page with names, phone numbers and the first six steps turns panic into a checklist.

The free way. Start from the first-hour list below. Add who to call, including your shelter-software vendor and your insurer. Once a year, spend an afternoon talking through the scenario you fear most, step by step, as if it were happening.

How long. An afternoon to write it, an afternoon a year to practice.

Who. The director plus whoever looks after the computers.

11. Pick a checklist and measure yourself against it once a year

Why. A yearly check against a published list turns “are we safe?” into a short answer the board can read, and it tells you what to do next.

The free way. Two checklists are written for organizations your size: CISA Cyber Essentials, from the federal cybersecurity agency, and the basic tier of the CIS Controls. Pick one. The guide Answering the insurer, the board and the grant officer walks through it.

How long. A day a year.

Who. The director with a board member who is comfortable with technology, or with me.

One more thing that is not a step. If you take card payments for adoption fees or donations, use your payment processor’s hosted page or terminal so card numbers never touch your computers or your paper. That one choice removes most of the card-security rules from your plate.

The first hour when something is already wrong

If you are reading this because a computer is acting strangely right now, do these in order, then call for help.

  1. Unplug the affected computer from the network or turn off its Wi-Fi. Do not power it off; evidence in its memory disappears when you do.
  2. Write down what first looked wrong, when, and on how many machines. Keep adding to that timeline.
  3. Check whether any building system, camera system or card terminal shares the same network. If so, assume it is involved.
  4. From a clean device, change the passwords for email and the shelter software, and turn on two-step sign-in if it is not already on.
  5. Tell whoever is responsible for the organization. If it is serious, report it to CISA; it is free and nobody will bill you.
  6. Only then start cleaning up. Wiping and reinstalling a machine is almost always better than trying to clean it.

The questions I ask when an organization calls, so you can have the answers ready: what looked wrong and when; how many systems; is any building-control device on the same network; what antivirus you have and who manages it; whether logs are collected anywhere; what remote-access tools exist; whether there are backups or a way to reinstall; whether two-step sign-in is on for everyone or only administrators; which systems matter most; and what legal or funder obligations apply.

Your first three months, if you have just been handed “the computers”

First 30 days: look around. Agree with your director on what good looks like. Read whatever documentation exists. Meet the people who own the data: operations, fundraising, finance, medical. Learn the systems in use. List the rules you have to follow (card payments, state privacy law, grant terms, insurance questions). Keep a running list of what you notice.

Days 31 to 60: early wins. Decide which system is the official record for each kind of data. Fix one visible problem. Turn on two-step sign-in where it is missing. Draft the plan. Start telling staff what is changing and why.

Days 61 to 90: make it stick. Get the plan approved. Write down who owns which data. Run one short training session. Write the one-page bad-day plan. Write a one-page summary of what was done and what comes next.

Free software, in the order I would add it

Free to download is not free to run. Every program you host yourself needs updates, backups and someone who notices when it breaks, and a neglected security tool becomes a way in. For most shelters with no IT staff, nonprofit-priced software that a vendor runs for you beats hosting your own for everything except a password manager and an inventory. The test: who updates it, who reads what it produces, and what it costs in staff hours a month compared with the subscription.

  1. Sign-in and devices are not free-software problems. Start with Microsoft 365 or Google Workspace through their nonprofit programs.
  2. Bitwarden, a password manager, for every shared login: shelter software admin, social accounts, vendor portals.
  3. Snipe-IT for the inventory from step 4.
  4. Zammad, a help desk, once requests outgrow a shared inbox.
  5. Wazuh on one small server for alerts, only when someone is named to watch it.
  6. OpenVAS, a scanner that finds out-of-date software, run quarterly.
  7. Everything else only at a larger organization with in-house IT.

Links for all of these are on the Resources page. If you want to talk any of this through for your organization, write to me. It is free.