Security tools for an ordinary user
An ordinary user needs six categories of security tool and no more: a password manager, a two-factor app, automatic updates, backup, DNS filtering and breach alerts; every one of the six has a free and acceptable option. The order you set them up in matters more than which brand you pick, because the first two together are worth more than the other four.
- Lesson 12 of 12
- Beginner
- Free, no signup
The six categories of tool an ordinary user needs
All six categories have an acceptable free option. No name on this page is an advertisement and there are no affiliate links anywhere in it.
Last checked: Facts and tool names in this lesson are re-checked against their sources on this date.
How many tools does an ordinary user actually need?
Six categories, and the figure above the page is those six. Category first, example second; do it the other way round and you install a tool whose job you do not know while leaving undone a job whose tool you have not heard of.
The order we suggest, by which two together do the most work: a password manager and a two-factor app. Those two between them neutralise almost every automated attack that reaches an ordinary user, because both rest on one thing: something only you have. Then automatic updates, which is not a tool but a setting and asks nothing of you. Then backup, which prevents no attack at all and is simply the only thing that works after the event. And last, the two least known: DNS filtering and breach alerts.
Our position, which differs from the usual shopping lists: all six categories have an acceptable free option, and for an ordinary user none of them carries a clear reason to spend. What is usually sold is a multi-seat security suite doing three of these six jobs together, generally none of them better than its free counterpart.
And what is not on the list although you expect it: a separate antivirus. Not because it is useless, but because on an up to date operating system that job is already done, and the full answer sits in the lesson on malware and its kinds. There is also a seventh layer that is no tool at all yet matters more than all six, and that is the habits set out in the lesson on browsing safely.

Which password manager? The three things that actually differ
Why length matters more than complexity, and which second factor is safer, is the subject of the lesson on strong passwords and two-factor, where it is set out in detail. The question in this section is a different one and nobody answers it: out of ten programs that all look alike and all say they are secure, which do you install.
Three things actually differ, and the rest of the differences are cosmetic.
First, where the encryption happens. The vault must be encrypted on your own device before it leaves it, so that what sits on the server is a meaningless file. Checking is simple enough: that service own security page must say so in those words. If it does not say it, do not assume it.
Second, and almost nobody looks at it: export. A program you cannot get your own data out of is holding you hostage. Before you put a hundred passwords into it, find the export button once and confirm it exists. It is the only feature you can no longer add at the moment you need it.
Third, the reuse and breach report. This is the only feature that, instead of holding your passwords, shows you your problem: which password you have repeated in several places and which of them have appeared in public breaches. A program without that report is an archive, not a security tool.
And three things that look like they matter and do not: how the program looks, how many features it has, and its rating in the store. What matters instead is that it works on every operating system you actually use, and that its free tier is honest; a free tier limited to a single device destroys the whole point of a password manager.
Our position, which differs from the usual comparison lists: the manager built into your browser is a perfectly defensible choice for most people. Somebody who spends six months looking for the best program while reusing one password everywhere during those six months is worse off than somebody who switched on their browser manager on day one.
The order for one evening: four moves that lay the base of all six
-
1
The main email
Two-factor switched on and the recovery codes saved in that same moment. If you only do this one, most of the work is done.
-
2
The password manager
Install it, import the passwords you already have, then open the reuse report. That report tells you where to start tomorrow.
-
3
Automatic updates
On the phone, on the computer, and on the router. Almost nobody switches on the third, and that is the one that stays unpatched for years.
-
4
Backup, and one test restore
One copy off the device, and then bringing one file back from it. It is the second move that turns a hope into a backup.
DNS filtering and breach alerts are deliberately not among these four: each is a five minute job, and if these four are undone they add nothing for you.
The two-factor app: what must you save at the very start?
The recovery codes. That one sentence prevents most of the harm people take from two-factor, and the harm does not come from an attack, it comes from losing the phone. At the moment you switch two-factor on, the service shows you a few one-time codes and most people close that screen. Save them into your password manager right there; it takes thirty seconds and it is the only way back into the account once the phone is gone.
After that, choosing the app itself. The comparison of which method is safer is in the lesson on strong passwords and two-factor; here only one practical criterion matters: pick an app that can move its keys to a new phone. An app without that turns the day you change phones into a whole evening of manual work.
And here there is a genuine choice with a cost on both sides, which ought to be said honestly. Apps that synchronise the keys are more convenient and make losing a phone harmless, but those same keys now also sit somewhere else. For most people the trade goes in favour of convenience, because losing a phone is far likelier than that sync account being broken into. It has one exception though: your main email, which is the recovery key to every other account you hold, is better off with a second factor that does not live with the rest.
The same point applies to the password manager itself: most managers today can also hold two-factor codes. It is convenient and entirely sensible for ordinary accounts, but note that doing it puts both factors behind one lock. For the accounts that matter, keep them apart.
And the rule that sits above all of this comes from the FBI public guidance: never give a verification code to anybody, not by email, not by SMS, not in an encrypted messenger. That same guidance warns that attackers use social engineering to get you to disclose the code, and says in the same place to set up two-factor on any account that allows it and never to disable it. No company, no bank and no support desk asks you for that code.
Backup and updates: why do the dullest have the most effect?
Automatic updating is not a tool but a setting, and on our list it is the only item that asks nothing of you beyond switching it on once. Its effect is also greater than any tool named on this page, because most of the holes that reach an ordinary user had their patch published weeks earlier.
Backup is the only thing on this list that prevents no attack at all. Its use lies elsewhere: it is the only thing that still works after the event, whether the event is ransomware or a phone left in a taxi.
Its rule fits in one sentence: three copies of anything that matters to you, on two different kinds of medium, one of them somewhere else. For an ordinary user that means the file on the phone, one in cloud storage, and one on an external drive that is not always plugged into the computer. That "not always plugged in" matters: ransomware that encrypts your computer encrypts any disk attached at that moment too.
And now the thing we learned ourselves and have not seen said this plainly in any backup guide: a backup is finished when the copy has been verified, not when the upload has finished. The plugin that puts this site backups into cloud storage takes the fingerprint of the file from the destination side after the transfer ends and weighs it against the local copy; in that system, the state "done" means precisely that the fingerprint was read and matched. Nine backup jobs are logged there to date and all nine finished by that same measure; the latest was a file of close to three hundred and fifty megabytes whose transfer took a little over a minute and a half.
Translated for you, whose tools differ although the rule does not: a backup you have never once tried to restore is not a backup, it is a hope. Once a year, bring one file back from the backup and open it. That one small test makes plain the difference between having a backup and believing you have one. The method and its tools are in the lesson on taking backups.
The difference between having a backup and believing you have one
It is finished when
- the transfer ended and the copy was verified as well
- one copy sits somewhere not always attached to the device
- one file has once been brought back from it and opened
- you know where it is and can reach it without help
It is not finished when
- the progress bar went green and you left it there
- every copy lives on the disk that is always plugged in
- no file has ever been brought back from it
- it is on a service whose password you no longer hold
The second column holds things we have lived through ourselves. Our backup system deliberately separates a verification failure from ordinary errors, because that mistake once cost us.
DNS filtering and breach alerts: the two you hear about least
Every time you open an address, your device must first ask which server that name belongs to. DNS filtering works at exactly that moment: if the name is on a list of known malware or fraud domains, no answer comes back and the page never opens at all. Its advantage is that it happens before the browser and before any extension, and it covers every device in the house from one setting on the router. Services such as Quad9 and the family edition of the Cloudflare DNS service do this for free. The mechanism underneath is opened up in the lesson on what DNS is.
Let us state its boundary honestly too: DNS filtering only catches domains already on a list, so it does nothing about a domain registered this morning. And because it works at the level of the domain name, a bad page on a reputable domain slips past it. Which means the very example we gave in the safe browsing lesson would have gone through this filter as well.
The sixth tool is the simplest of all and returns the most for the least work: breach alerts. There are services that gather the list of public breaches and tell you which ones your email appeared in. What you have to do is a one-off: enter your address and, if you wish, switch on the alert so that they tell you about the next breach.
And what you must do afterwards is the thing most people do not: changing the password on that one service is not enough. If you had the same password anywhere else, all those places have to change too. Which is why the reuse report in a password manager, mentioned in the second section, is the natural partner of this tool.
And if we are to turn this page into a single action: go and count how many of these six categories you already have. Our experience is that most people have four switched on without knowing it, and the two that are missing are almost always the same two: a backup nobody has tested, and recovery codes that were never saved. Counting comes before reading.
The fast path, with AI
The ordinary way is to assume you have none of the six and start from zero, which is exhausting and usually abandoned half done. The fast way is to see where you already stand. Most people have four of the six switched on without knowing it, and what is genuinely left is two. Finding those two with a coverage table is twenty minutes of work.
- Write six lines, one per category, and against each put only your real state today: what is installed, when it last ran, and if you do not know, write that you do not know. Those "do not know" lines carry the most value.
- For the two items nobody usually knows the answer to, go and look once yourself: the date of the last backup in the phone settings, and when the last operating system update was installed. Both are found in two minutes.
- Give the recipe below to a fast model along with those six lines. The job is comparing a state against a fixed list rather than judgment, so a cheap model is enough.
- From the output take only the "missing" and "partial" rows and close one of them tonight. Do not go at all six together; somebody who closes one gap is ahead of somebody who draws up a six stage plan.
Copy-ready recipe
I am giving you six lines about my current security state. Each line is one category.
The categories: password manager, two-factor, automatic updates, backup, DNS filtering, breach alerts.
Build a table with these columns:
1. Category.
2. State: have it, partial, missing, unclear. "Partial" means it exists but is incomplete, for example a backup that only lives on the same device.
3. The sentence of mine that shows this state. If there is no such sentence, write not stated.
4. The smallest move that raises this category one step from where it is, in one sentence.
After the table, list only the missing, partial and unclear rows in order of importance. Let the criterion for the order be which absence also neutralises the others.
Rules: do not assume anything I did not write. Do not recommend any specific product name and name only the category. If a line is ambiguous, write unclear and ask right there what you would need in order to settle it.
The six lines:
{state of each category}
Before you trust the output: The coverage table is only as honest as the six lines you wrote; if you put "have it" somewhere you are not sure about, the model confirms it and the gap stays hidden. This is why writing "unclear" is worth more than guessing. And do not ask the model for product names: its answer comes out of its memory, and in security the service that was best last year may have had a leak this year. Take the category from this table and take the choice of product from that service own security page.
AI in this kind of work
Here a language model does two jobs well and both are clerical: it holds your current state up against a fixed list and shows you the gaps, and it compares the features of several tools faster than reading three marketing pages. And there is one job it must never be given: creating or holding anything that is a secret. A security tool should do its own job, and a language model is not a security tool.
Tools that actually help
- Gemini Enough for exactly this six row coverage table, and a fast model beats an expensive one here because the work is matching against a fixed list. Google own page says the Gemini app works in more than 230 countries and territories, and Iran is not on that list.
- Claude For when you want to set the policies of two password managers against each other and see what each claims precisely about client-side encryption, which is reading two long texts. Iran is not on Anthropic list of supported countries, so there is no official route to sign up or pay.
- ChatGPT It serves the same two jobs equally well. On reaching it from Iran we write nothing: the OpenAI supported-countries page returns 403 to this server, so we have not checked it and we do not make a claim with nothing behind it.
Where it backfires
The risk specific to this lesson is that a language model plays the part of a security tool very readily without being one. Ask it for a password and it will make one; but a language model is not a cryptographic random number generator, and more to the point that string now sits in text the service retains. Google own help for Gemini says plainly not to enter confidential information you would not want a human reviewer to see, because some conversations are reviewed to improve the service. That one sentence removes passwords, recovery codes and password manager export files from the list of things that can go into a chat. And a second, subtler risk: ask a model which password manager is better and it constructs an answer from its memory, and its memory belongs to the past; in security, the service that was best last year may have had a leak this year. Leave the feature comparison to the model and leave the final choice to that service own security page and to the date of its last independent review. For what paying for these tools looks like from Iran, see the buying guide.
Sources: Google: Gemini Apps privacy notice and data Google: where Gemini Apps are available Anthropic: supported countries
Where this advice stops
This list was written for an ordinary user and is not sufficient for a business: there the discussion also covers staff access, separating accounts and event logging, and none of that appears here. The second boundary we placed deliberately: on this page we put categories ahead of names and called no brand the best, because names move every year and a service recommended this year may itself leak next year; what does not go stale on this page is the six categories, not six names. And the third boundary is the place where no tool works at all: if somebody talks you into reading out a verification code yourself, all six tools are neutralised at once. That one is the subject of the lesson on AI security risks and the phishing lesson in this same track.
From our own work
Two things from our own systems, both with numbers. First, backup: the plugin that puts this site backups into cloud storage does not consider a transfer finished until it has taken the fingerprint of the file from the destination side and weighed it against the local copy; in that code, the state "done" means exactly that equality, and a failure of the verification is deliberately separated from ordinary errors and never retried, because that mistake once made the system check a file it had already deleted twelve times in a row. Nine backup jobs are recorded in its history to date and all nine reached the state "done" by that same measure; the latest was a file of close to three hundred and fifty megabytes whose transfer and verification took a little over a minute and a half. Second, login lockouts: the lockout table of this site held three rows over the window we read, two of them from repeated password guessing and one from failing the bot check. It is a small number and that is what we wanted to show: when an automatic defence is working properly it leaves nothing to see, and this is why nobody notices its absence until it stops.
Real follow-up questions
If I only have a phone and no computer, which of them do I need?
All six, but three of them are already on the phone and only need switching on: automatic updates, the operating system own cloud backup, and the built-in password manager. What you genuinely have to add is two-factor and saving the recovery codes. DNS filtering can also be set on the phone itself, though on the home router it is set once and covers every device.
Does DNS filtering not slow the internet down?
The filtering itself costs nothing noticeable, because it is a lookup in a list. What may change the speed is your distance to that service server; if it sits further away than your operator own, opening each new domain takes a few milliseconds longer and after that the answer is held in cache. The right approach is not to guess: try it for a week and go back if you feel a difference.
Does installing several security tools together cause problems?
The six categories on this page do not interfere with each other, because each stands at a different point of the route. Interference arises where two tools do the same job: two active antivirus engines on one Windows is the classic case and it produces slowness and strange errors. The rule is simple: one from each category, not two.