Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
A penetration test names what you want to protect as a goal, and checks from an attacker's position whether that goal can actually be reached. It is also called an intrusion test. The question is not "is there a hole?" but "do holes link up to reach what matters?"
Cyber Shield's penetration test is from JPY 498,000 (excl. tax). Below we cover how it differs from a vulnerability assessment, which companies it suits, how it runs and what it costs. We do not publish attack steps or strings that can be abused.
How does a penetration test differ from a vulnerability assessment?
The difference lies in what each one looks at. A vulnerability assessment lists the holes in a defined scope, without gaps. A penetration test sets a goal first and checks whether the goal can be reached.
An assessment tells you, for example, "this screen has three weaknesses." A test tells you "weaknesses A and B, linked together, reached the customer list." Holes that look minor one by one can become serious in combination, and that is why this view is useful.
IPA's Information Security Service Standard Conformity Service List treats penetration testing (intrusion testing) as an option of vulnerability assessment services. It is a more goal-driven test that extends the assessment.
| Point | Vulnerability assessment | Penetration test |
|---|---|---|
| The question | What holes are in the scope? | Can the chosen goal actually be reached? |
| Method | Tools scan broadly and a person checks | A person works back from the goal and links holes |
| Result | A list of holes and how to fix them | The path that reached the goal, and where to stop it |
| When it fits | Before launch, after changes, regular checks | After the defenses are in place, to confirm their strength |
| Price | from JPY 49,800 (excl. tax) | from JPY 498,000 (excl. tax) |
NIST SP 800-115 is a guide to security testing and assessment. It treats penetration testing as a technique separate from checking for vulnerabilities. For web applications, the OWASP Web Security Testing Guide is a public document that organizes testing viewpoints.
Which should come first, an assessment or a penetration test?
Usually the assessment. A test run while many holes remain tends to repeat the assessment's findings, and it yields fewer new discoveries for the money.
We suggest this order. Fix the holes an assessment found, confirm the fixes with a re-assessment, and then use a test to ask whether the goal can still be reached. Assessments are available as the web application assessment and the e-commerce assessment.
Which companies is a penetration test suited to?
It suits companies that know what they want to protect and have finished their basic measures. These are typical cases.
- Companies that handle customer or payment data, and whose business partners or auditors ask whether an intruder could really get in
- Companies that let contractors or outside vendors into internal systems
- Companies that have fixed what an assessment found and want a final confirmation that the defenses work
- Companies that want to review their preparation against stolen admin rights or spread into the internal network
In the organization list of IPA's Top 10 Information Security Threats 2026, "attacks targeting the supply chain or contractors" is second and "attacks that exploit system vulnerabilities" is fourth. Both are attacks that spread from one hole to another place. A test that follows the path can suit these cases better than an assessment that looks at holes one by one.
If basics are still missing, such as parts that are no longer updated or an admin screen anyone can open, an assessment and fixes come first. In that case, tell us your situation in the free consultation. We will say plainly whether starting with an assessment makes more sense.
What goals can a test aim at?
Goals are set for each company. The goals you choose decide the scope and the price.
| Example goal | What we confirm | Related vulnerability |
|---|---|---|
| Reaching customer data | From an ordinary member's position, whether another person's data or the whole data set can be reached | Broken access control |
| Gaining admin rights | Whether ordinary rights can be raised to admin rights | Privilege escalation |
| Entry through a contractor | How far into your systems an entrance handed to a contractor leads | Contractor intrusion |
| Spread into internal systems | Whether getting into one machine leads to others | Measures against hacking |
A test uses the same kinds of holes as an assessment. What it reports is what each hole reached. If you cannot decide on a goal, name the one thing you cannot afford to lose, and we set the goal from that.
How does a test run, and what do you keep afterwards?
A test starts by fixing the goals and the scope. Starting without that can affect the live system or leave the report off target.
First, the goals and targets are agreed in writing. Alongside them we settle which areas may be tested, which data must not be touched, which functions must not stop and in which hours testing may run. Testing someone else's system without permission may break Japan's Unauthorized Computer Access Law, so a signed consent form comes first.
Then an analyst tests toward the goal. The work does not stop at a broad tool scan. The analyst links holes and judges whether the goal is really reached.
What you keep is a report in Japanese. It says whether the goal was reached, and if so, which holes were linked and where the path can be closed. One re-assessment after the fixes is free. It confirms the holes are closed, and the result goes into the report.
Our limits are as follows. We test only the agreed scope and touch nothing outside it. We do not promise that passing a test means you are safe.
What does it cost, and what changes the amount?
A penetration test is from JPY 498,000 (excl. tax).
| Item | Price | Included |
|---|---|---|
| Penetration test | from JPY 498,000 (excl. tax) | Agreeing goals and scope, the test, a report, one re-assessment after fixes |
Three things raise the amount. The first is the breadth of the target, because more screens and devices mean more to check. The second is the number of goals, because each added goal means more paths to try. The third is the depth of the scope, meaning whether it includes screens behind login or internal systems.
The amount is fixed once the goals and scope are set. A test takes more human work than an assessment, so it costs more. The formal quotation follows the free assessment.
For the other plans, see the pricing page. If you want to start from an assessment, plans begin from JPY 49,800 (excl. tax). To see what is visible from outside before you decide, use the free URL check. If you are unsure about goals or scope, contact us.
How does a request go from first contact to delivery?
A test adds one step to the standard flow from first contact to after-delivery support: setting the goals and scope.
- In the free consultation we ask what you want to protect and whether you have had an assessment before.
- Before any test or work begins, we sign a non-disclosure agreement (NDA). It costs nothing.
- After you sign the consent form, we run the free assessment, a quick tool scan plus a person's review, and hand over an issue report on the current state.
- We agree the goals, the scope and what must not be touched, and then present a quotation.
- After you place the order, we run the test and close the holes that were found.
- A PDF of what we changed and how reaches you before delivery.
- You confirm the behavior yourself on the real screens.
- Delivery follows, with free support for one month.
Common objections
Will you teach us the attacker's methods?
The report states where each hole is and how to fix it. Specific procedures and strings that can be abused stay out of the report. We keep what you need in order to fix the problem, and we keep the report from becoming a guide for misuse.
Is an assessment alone not enough?
It depends on your goal. An assessment lists holes in a defined scope. A test is for the stage after you have fixed them, when you want to confirm that an attacker still cannot reach your goal. If the basics are not done, begin with the assessment.
Can our own staff run a test like this?
Your staff's checks are a foundation. A person who built a system tends to use it the way they planned. Someone in a third party's position looks for the path nobody expected.
Frequently asked questions
What is a penetration test?
It is a test in which you name what you want to protect as a goal and check, from an attacker's position, whether that goal can actually be reached. Unlike a vulnerability assessment, which lists holes, it looks at whether several weaknesses link up to reach the goal.
How does it differ from a vulnerability assessment?
An assessment lists the holes in a defined scope without gaps. A penetration test fixes a goal, such as reaching customer data, and checks whether it can be reached. One produces a list, and the other shows whether the goal can be reached.
How much does it cost?
It is from JPY 498,000 (excl. tax). The amount depends on the breadth of the target, the number of goals and whether the test goes behind login or into internal systems. The formal quotation follows once the goals and scope are set.
Can the test stop a live system?
Operations that could have an effect run only inside the scope and time window agreed beforehand. Functions that must not stop and data that must not be touched are fixed in writing first. We sign an NDA and a consent form before the test.
Should we start with a penetration test?
Usually it is better to run a vulnerability assessment first and fix the holes, then take the test. With many holes still open, the test results tend to repeat the assessment's findings.
Next step
If you want to see how your site looks today, use the free URL check. Type in a URL and it looks only at publicly visible information. It does not run attacks.
If you cannot tell whether an assessment or a penetration test fits, contact us by form, phone or online meeting. The NDA is free and is signed before any test.
Written by Mio Kanzaki (AI security analyst). Supervised by 千葉圭介. Updated 19 November 2026.
Frequently asked questions
What is a penetration test?
It is a test in which you name what you want to protect as a goal and check, from an attacker's position, whether that goal can actually be reached. Unlike a vulnerability assessment, which lists holes, it looks at whether several weaknesses link up to reach the goal.
How does it differ from a vulnerability assessment?
An assessment lists the holes in a defined scope without gaps. A penetration test fixes a goal, such as reaching customer data, and checks whether it can be reached. One produces a list, and the other shows whether the goal can be reached.
How much does it cost?
It is from JPY 498,000 (excl. tax). The amount depends on the breadth of the target, the number of goals and whether the test goes behind login or into internal systems. The formal quotation follows once the goals and scope are set.
Can the test stop a live system?
Operations that could have an effect run only inside the scope and time window agreed beforehand. Functions that must not stop and data that must not be touched are fixed in writing first. We sign an NDA and a consent form before the test.
Should we start with a penetration test?
Usually it is better to run a vulnerability assessment first and fix the holes, then take the test. With many holes still open, the test results tend to repeat the assessment's findings.