You Can Find the 'Weak Spots' Yourself, Before Someone Breaks In — The Basics of Vulnerability Assessment and How to Protect a Small Site

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.
This time, the story is about the defending side. In the unauthorized access to the official site of the funeral company “Tamanoya,” the cause was announced as a “vulnerability” in the website system. A vulnerability is a “weak spot” in a system. So can those weak spots be found not after someone has broken in, but before? The check for doing that is a “vulnerability assessment.”
The result first
Here is the result first.
- A vulnerability assessment is a check to find the “weak spots” in a site or server before the attacking side does, and to fix them. The assessment itself is not the protection — finding, fixing, and checking again are all part of one continuous process
- Assessments fall broadly into two types. A “web application assessment” looks at systems such as order forms and login screens, and a “platform assessment” looks at servers, operating systems, and open doors (ports)
- Even with free tools, there is a range you can check yourself. However, reading the results and doing the fixing are your own responsibility
- Systems that handle personal information or orders and payments are in the range to leave to specialists. Tamanoya’s ordering system was exactly that kind of example
- This is the most important caution. You may only point assessment tools at things you manage yourself and things you have permission for. Assessing someone else’s site may not be allowed
What does a vulnerability assessment actually check?
Think of it like a house. How well the locks engage, whether the windows close properly, aging pipes, a back door left open. An inspection does not break the house itself — it makes a “list of weak places.” A vulnerability assessment is the same: while imitating an attack, it washes out the weak places in advance.
There are broadly two things it looks at.
- Web application assessment: This covers the systems you use in a browser themselves, such as order forms, inquiries, and login screens. It checks for tricks in input fields (such as SQL injection and cross-site scripting) and for loose settings. In the Tamanoya case, it was a weakness on this side that was exploited
- Platform assessment: This covers servers, operating systems, the parts that run on them (middleware), and network equipment. It checks whether parts have been left old, whether unnecessary doors (ports) are open, and whether there are flaws in the settings
There are also two ways of doing it.
- Tool-based assessment: A method where a tool checks mechanically, matching against known patterns of weakness. It is fast and can look widely. On the other hand, weaknesses the tool does not know, and weaknesses hidden in the flow of a system, can be harder to find
- Manual assessment: A method where a specialist actually operates the site and checks by hand. It takes time, but it can reach weaknesses that are hard for tools to find
What you can check yourself with free tools
First, there is something I want to note before the tools. Keeping the site itself and its parts (such as plugins) up to date is itself the number one measure against known weaknesses. In the Tamanoya case, what was announced as a measure to prevent recurrence was also an “update of the system itself.” An assessment is what comes after that foundation.
On that basis, here are representative tools you can use for free, within the range confirmed in official guidance (confirmed on November 21, 2026).
- ZAP (formerly OWASP ZAP): A scanner that automatically looks for weaknesses in web apps. It is free and open source (its inner workings are published, in a form anyone can check). Its official site describes it as “the world’s most widely used web app scanner.” It is suited as a first tool for checking around the forms on your own site
- Burp Suite Community Edition: A tool for manual work, which catches the exchange between a browser and a server along the way so you can proceed while checking. It can be used for free, but it does not include a scanner that searches automatically. Professional, which comes with a scanner, is paid, on an annual per-user basis (confirmed on the official purchase page. The price varies depending on how you purchase it, so this article does not state it)
- Nikto: A scanner that checks web server settings, old parts, and whether dangerous files have been left in place. It is free and open source
- Nmap: A tool that checks which doors (ports) are open and what kinds and versions of services are running there. It is free and open source. It is used to check “whether unnecessary doors are open”
- Nessus Essentials: The free tier of a full-fledged scanner that matches against known weaknesses. However, the free tier is only for non-commercial use, can check only up to 5 IPs, and the license is limited to 30 days (from Tenable’s official comparison table). Essentials Plus, for continued use, is $199 per year (up to 20 IPs, non-commercial only), and if you use it for shop or company work, you need the commercial Professional (listed as $4,790 in the official comparison table)
What the tools give you is a list of “candidates for weaknesses.” Whether it is a real weakness, which ones to fix first, and how to fix them — that judgment and work remain outside the tools. That is where the line is drawn for free tools.
Where to ask a specialist
So where does the range for asking a specialist begin? As a guide, it is like this.
- There is a system that handles personal information, or order and payment information (Tamanoya’s system for ordering funeral flowers and offerings was that example)
- There is a login or member registration system
- Even after reading the results from free tools, you do not know how to fix them, or there is no one to do the fixing
- An incident or failure has occurred once, and a re-check has become necessary
The cost of an assessment by a specialist company varies greatly depending on the breadth and depth of what is covered. In the comparison in the source column, services starting from 250,000 yen were listed, and it was noted that depending on the scale, the cost can reach several million yen. When looking for someone to ask, one way is to look for a service that conforms to the Ministry of Economy, Trade and Industry’s “Information Security Service Standards” in the list of conforming services maintained by the IPA (Information-technology Promotion Agency).
And an assessment does not end with “I had it done.” Fixing the weaknesses that were found, and checking again whether they were fixed (a re-assessment), are part of the same continuous check.
An important caution — who you may point these tools at is limited
This is what I most want to convey in this article.
Assessment tools send communications similar to an attack to the other side. So who you may point them at is limited.
- Do not point tools at someone else’s site or server without permission: The act of entering someone else’s computer, where access is restricted, by going beyond the original restrictions, is prohibited by the Act on Prohibition of Unauthorized Computer Access (the Unauthorized Computer Access Prohibition Act). The penalty is imprisonment for up to 3 years or a fine of up to 1,000,000 yen (Articles 3 and 11 of the same Act). Even with the good intention of “let me tell them about a weakness,” it is the same if you do not have permission
- Even for your own site, if the place where it sits is managed by someone else, you need permission: A site placed on a rental server or on an external service (SaaS) sits on a foundation managed by someone else. The terms may restrict acts like assessments. First, check with the administrator or provider
- If you point them at a live site, be careful: Assessment communications can make a site run heavily, or stop it. The manner on the defending side is to do it in a test environment, take a backup copy, and do it at a time of low use
Three incident articles to read together
This article, as a story from the defending side, forms a set with the following three.
- Funeral flower order information was targeted — Unauthorized access to the Tamanoya official site, and how separating payments to the outside protected it: This is the incident where the cause was announced as a “vulnerability in the website system.” The starting point of this article is here
- A funeral hall reservation register was targeted — Unauthorized access to the Ashikaga City funeral hall reservation system, and how to protect information about the deceased and chief mourners: In this case, the route of intrusion has not been announced. Precisely because it is an incident where the cause is not known, the story of “a check that looks for weak spots in advance” applies to both
- The Government’s Shared Platform Was Entered — Unauthorized Access to the Digital Agency’s GSS and the Possible Exposure of About 246,000 Items of Personal Information, and How to Protect VPN Weak Spots: The entry point was a known VPN vulnerability, exploited before the correction program could be applied. That is, itself, the teaching of this article
Weak spots can arise in any system. The problem is not that a weakness exists in itself, but leaving it in place without noticing it is there. Move to the side that finds them. The check for doing that is a vulnerability assessment.
The scope of this article
- The prices and forms of provision of tools and services are as confirmed in each official guide on November 21, 2026. They may change. Before using them, check the official source
- “Nothing was found” in an assessment is not proof that there are no weaknesses. That is because a tool checks by matching against the patterns it knows
- This article is not a manual for how to use the tools. For specific procedures, please see each official guide
- This article is based on official guides and columns that could be read as of November 21, 2026
Sources
- Cybersecurity.com, “16 Free and Paid Vulnerability Assessment Tools (Services)! Comparing Prices and How to Choose” https://cybersecurity-jp.com/column/11633
- ZAP official site https://www.zaproxy.org/
- PortSwigger official site, “Burp Suite Community Edition” https://portswigger.net/burp/communitydownload ・ Same, “Subscribe to Burp Suite Professional” https://portswigger.net/buy/pro
- Nikto official repository https://github.com/sullo/nikto
- Nmap official site https://nmap.org/
- Tenable official site, “Nessus Essentials” https://www.tenable.com/products/nessus/nessus-essentials
- Act on Prohibition of Unauthorized Computer Access, Articles 3 and 11 (e-Gov law search)
- For the meanings of terms, you can look them up in the Security Lab glossary: Security Glossary — Vulnerabilities and Zero-Days (S-17)
Entrance (other languages)