Basics

What Is Cyber Security, and What Does It Protect? — The Definition, the Scope, the Main Threats, and the Ability to Recover

Security Lab — kurashiki-bouzu

Hello, I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. I am a former funeral director, and I now live in an old house in Kurashiki, Okayama, working together with my AI butler, Moka.

In this Security Laboratory, I have been writing about incidents one at a time — the case in Ashikaga City, the case at Tamanoya, cases involving hospitals. But if we only ever talk about incidents, the basic question gets left behind: what is security actually protecting? This article goes back to the foundations and sets that out. It is based on Kaspersky’s explainer, “What is cyber security?”, and I have also checked it against Japanese law and public standards.

The result first

Here is the conclusion, before the details.

The definition — not something you buy, but a state you keep

Kaspersky’s explainer defines cyber security as the practice of defending computers, servers, mobile devices, electronic systems, networks, and data from malicious attacks. What is protected is both the machines and the information, and the key word is “practice” — something you do every day, not something you install once.

Japanese law points to almost the same place. The Basic Act on Cybersecurity phrases it in formal legal language, but put plainly, it means this: measures are in place so that information does not leak, disappear, or get damaged, and so that systems and networks keep running safely — and that state is properly maintained.

Put the two side by side and an important point comes into view. Security is not finished by buying one piece of software. A house with a lock is only a “safe house” if someone keeps locking it and keeps checking the doors and windows. Security is the name of a state you keep maintaining.

The information being protected has three qualities. The standard JIS Q 27000 calls them confidentiality, integrity, and availability. In everyday words, they look like this.

Every incident I have written about in this laboratory was a case where one of these three broke down. Information got out (confidentiality broke down). Data was encrypted and could no longer be used (availability broke down). Seen through these foundations, the separate incidents line up into a single story.

The scope — six areas of protection

Kaspersky’s explainer divides the scope of protection into six areas. They may sound like matters for large companies, but every one of them translates to a small workplace and to daily life.

Different explainers divide this up in different ways. NIST, the American public standards body, organises its Cybersecurity Framework (CSF 2.0) around six “functions”: Govern, Identify, Protect, Detect, Respond, and Recover. The shelves are arranged differently, but the items on them are much the same. In this article, I mainly follow Kaspersky’s six areas.

The types of threats — how the attacking side works

To know what you are protecting against, here are the representative methods. The detailed meanings of the terms are in this laboratory’s glossary; here I will only sketch the shape of each method, briefly.

Malware — the general name for software that does harm

Malware is the general name for malicious software. Its family includes file-infecting viruses, which attach themselves to files and spread; Trojan horses, which slip in pretending to be legitimate software; spyware, which quietly records what the user does; ransomware, which encrypts data and demands a ransom; worms, which spread on their own; and botnets, which bundle hijacked machines together and use them as one. Rather than memorising the names one by one, it protects your daily life better to hold on to this: software and attachments from unknown sources are the entrance. The foundation of the countermeasures is antivirus software and keeping things updated.

SQL injection — slipping an instruction into an input field

An input field on a website is like a reception desk. It is meant to receive a “name” or an “order.” In an SQL injection, the attacker slips in, instead of an order, a sentence that is an instruction — “open the storeroom” — and the side behind the desk (the system) reads it not as information to receive, but as an instruction to follow. Because the place where the information itself is stored (the database) can be opened this way, it can lead to a major leak. The entrance is a weakness on the side that built the site, so it is one of the things checked in advance by vulnerability assessment.

Phishing — pretending to be the real thing, and getting you to hand over the key

Phishing pretends to be a real bank, delivery company, or similar, and gets you to enter your password or card number. Its heart is that it does not break the key to the machine — it makes the owner hand the key over voluntarily. This is why, after every incident, companies call for caution about suspicious emails pretending to be them.

Man-in-the-middle attacks — someone steps into the middle of a conversation

In a man-in-the-middle attack, the attacker steps between two parties who are communicating, and peeks at the contents or changes them. On public Wi-Fi, for example, it is hard to be sure that what you connected to is genuine, so it easily becomes the stage for this attack. It may be easier to picture as someone in the next seat listening in on an important conversation.

Denial-of-service attacks — blocking the entrance so the service cannot be used

These attacks flood a system with access until it can no longer be used. The glossary lists them as DDoS attacks. Picture a crowd surging at a shop’s entrance so that the real customers cannot get in. The aim is not to steal information, but to break the “usable” state — availability.

Incidents begin with people, not machines

This is the point Kaspersky’s explainer places first. Most incidents begin not with a machine, but with a person. Attackers aim not at a hard-to-break lock, but at a person who is easier to deceive. They hurry you, reassure you, frighten you, and get you to press the button. Methods that play on how people’s minds move are called social engineering.

There is evidence behind this, too. According to Verizon’s research report (the 2026 Data Breach Investigations Report, DBIR), a “human element” was involved in 62% of data breaches. Clicking on a convincing email. Reusing a password that has leaked somewhere. Approving a fake request believing it is real. The accumulation of these is what becomes the entrance to an incident.

That is why “end-user education” stands at the end of the six areas of protection. Installing software alone does not close the human entrance. Looked at the other way, the habits of the people who use the systems — checking before you press, not reusing passwords, and asking someone rather than deciding alone when you are unsure — are a form of protection you can add today, without spending money.

Not only preventing — the ability to recover (cyber resilience)

One more idea in Kaspersky’s explainer is cyber resilience. It starts from the premise that not every attack can be prevented, and holds, as one continuous readiness, not only preventing (prevention), but also noticing (detection), responding (response), and restoring things to how they were (recovery).

It becomes clearer if you think of preparing for a fire. Taking care not to start a fire is prevention; a smoke alarm is detection; a fire extinguisher and an evacuation procedure are response; and the copies and insurance that let you rebuild your life after a fire are recovery. No one of them is enough on its own.

For individuals and small workplaces, the heart of recovery is the backup. Even if ransomware encrypts your data, if an intact copy is kept somewhere else, you may be able to restore everything without paying the ransom. In the Tamanoya case, card information was not among what was targeted, because payments were left to a specialised external system and were not held in-house. “Do not hold it,” “keep it separate,” “keep a copy.” The ability to recover is something you build in before an incident, not after.

Reading the incident articles alongside this one

Once the basic shape is in view, reading the incident articles shows you which area each one belongs to.

Scope — the boundaries of this article

Sources


Entrance (other languages)

日本語 中文 Español 한국어 Français Deutsch हिन्दी العربية

Basics / Back to the English top