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

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.
- Cyber security means protecting computers, smartphones, networks (the systems that connect things), and the information inside them from malicious attacks
- What is being protected is information in three qualities: “only the people who are allowed to see it can see it,” “it has not been altered,” and “it can be used when it is needed.” Protecting information means keeping all three of those qualities intact
- The scope is wider than the machines themselves. It includes how systems are built, the rules for handling information, how you recover when something happens, and how you explain safe habits to the people who use the systems
- Most incidents do not begin with a weakness in a machine. They begin with a person — an attachment opened without thinking, a password reused in several places. That is why “educating the users” is part of the protection, too
- No protection is perfect. So the protection itself includes being ready to notice an incident, respond to it, and get back on your feet — what is called cyber resilience
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.
- Confidentiality: only the people who are allowed to see it can see it. Think of the contacts on your smartphone: they sit behind a locked screen that only opens with your own finger or face
- Integrity: the contents have not been quietly changed. The balance in your bank book, or the figures in a shop’s ledger, are exactly as they should be — nobody has altered them without you knowing
- Availability: you can actually use it when you need it. Your contacts open when you want to make a call, and the reservation list is there in the morning when the shop opens
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.
- Network security: protecting the entrances to your connections. At home, this is the gate and the front door — deciding who gets in and who does not. A firewall is the guard at that gate
- Application security: protecting the way the tools themselves — apps and software — are built. Was the app that takes your reservations built safely from the start? For the checks that look for weak spots in a tool before someone else does, see the article on vulnerability assessment
- Information security: protecting the information itself, both while it is stored and while it is being carried. In terms of a letter, it is both keeping it in a locked drawer and sealing the envelope when you send it. Encryption plays the role of that seal
- Operational security: the rules for handling things. Who is allowed to see what, where things are kept, and how they are handed over. In a shop, it is the decision about who holds the keys and where the customer list is stored
- Disaster recovery and business continuity: the readiness to restore things and keep the work going when something has happened. In the Ashikaga City funeral hall case, even after the system stopped, reservations continued to be taken by telephone. That was “keeping things going” in real life
- End-user education: telling the people who use the systems how to avoid dangerous handling. Do not plug in an unknown USB stick. Do not open a suspicious attachment. However thick the technical protection is, the last entrance is a person
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.
- The Funeral Hall Reservation List Was Targeted — Unauthorized Access to Ashikaga City’s Funeral Hall Reservation System, and How to Protect the Information of the Deceased and Chief Mourners: the protection of information (personal information), and the readiness to keep going — after the system stopped, reservations were taken by telephone
- The Flower-Offering Order Information Was Targeted — Unauthorized Access to the Official Website of Funeral Company Tamanoya, and the Protection of Sending the Payment Outside: a weak spot in how the system was built (application security), and how handing payments to an outside service kept the damage contained
- You Can Find the ‘Weak Spots’ Yourself, Before Someone Breaks In — The Basics of Vulnerability Assessment and How to Protect a Small Site: the checks that find weak spots in advance. It connects directly to “application security” in this article
Scope — the boundaries of this article
- This article is a foundational explainer rebuilt for this laboratory’s readers: it is based on Kaspersky’s explainer, checked against Japanese law (the Basic Act on Cybersecurity) and public standards (JIS Q 27000 and NIST’s CSF 2.0). It is not a copy of the original explainer’s text
- The way the areas are divided differs between explainers and standards. The six areas in this article follow Kaspersky’s explainer; in NIST’s framework, the division is by function
- No specific product or service is being introduced. Kaspersky is treated as one of the sources
- The figure (62%) is based on Verizon’s published DBIR 2026. The subjects of the research and the way of counting belong to the report itself
- This article is based on public information available as of November 21, 2026
Sources
- Kaspersky, “What is cyber security?” https://www.kaspersky.co.jp/resource-center/definitions/what-is-cyber-security
- Basic Act on Cybersecurity, Article 2 (e-Gov law search) https://laws.e-gov.go.jp/law/426AC1000000104?occasion_date=20221118
- NIST, “Cybersecurity Framework (CSF) 2.0” https://www.nist.gov/cyberframework
- Verizon, “2026 Data Breach Investigations Report,” Executive Summary https://www.verizon.com/business/resources/executivebriefs/dbir-2026-executive-summary.pdf
- The three qualities of information (confidentiality, integrity, and availability) are based on the definitions in JIS Q 27000 (vocabulary for information security management systems)
- The meanings of the terms can be looked up in the Security Laboratory glossary: Security Glossary — malware (S-44), file-infecting virus (S-49), Trojan horse (S-26), spyware (S-14), ransomware (S-45), worm (S-47), botnet (S-43), phishing (S-39), man-in-the-middle attack (S-23), DDoS attack (S-24), social engineering (S-20), backup (S-35), vulnerability and zero-day (S-17), and more
Entrance (other languages)