Do you know every site your company has?

Besides the website you manage day to day, are sites or test environments built by other departments exposed without the management department knowing? Environments that slipped out of management are also targets that attackers examine.

Do you have a full view of all the sites and networks exposed across your company?

A campaign site built by the sales department. A test environment set up by the development team. Some are published without going through company approval or management procedures.

Even if they are used for business, if the management department does not know they exist, they may be missed by updates and checks.

Read about sites and systems that slip out of management
Environments not on the management department’s list can still be found from outside
example.jp
Company website
www.example.jp
On the management department’s list
Another department’s campaign site
campaign.example.jp
Not on the management department’s list
Development team’s test environment
dev.example.jp
Not on the management department’s list
External API
api.example.jp
Not on the management department’s list
Even if the management department does not know about them, some environments are accessible from outside.

An illustrative example of exposed environments. It is not an actual discovery result.

Small and medium-sized businesses are being hit, too.

In the first half of 2026, 123 ransomware incidents were reported to the police. Of these, 79 were at small and medium-sized businesses.

Of the 36 cases with an answer on the infection route, 18 were intrusions via VPN devices. You need to check not only websites but also devices connected to the internet.

Reports of data leaks due to unauthorized access are surging.

Reports to the Personal Information Protection Commission (August 2026 – October 16, 2026)

In just over half a month, about 2.7 times the entire previous month.

Ransomware damage, first half of 2026

National Police Agency figures

Damage reports

Small and medium-sized businesses

79 / 123 damage reports

Intrusion via VPN devices

18 / 36 valid answers on infection route

Running does not mean safe.

Pages load. Inquiries arrive. That alone does not tell you whether the software you use is up to date or whether old environments remain.

www.example.jp
EXAMPLE

As usual,
the site is running.

Contact us
Pages loadInquiries arrive

An illustrative example using a fictitious site.

What you cannot tell just by looking at the screen

Is the software up to date?

A site can keep running even on old versions or versions past end of support.

Are old environments left behind?

Test servers or pre-migration sites may be exposed separately from production.

What about connection points other than pages?

Besides the pages you usually see, there are other places that can be reached from outside, such as APIs and admin screens.

A problem with your site can bring work to a halt.

When weaknesses in an exposed system are exploited, information may be stolen or data may be encrypted.

If systems needed for orders and shipping become unavailable, everyday work stops too. Besides recovery, you may also need to explain the situation to customers and business partners.

Needed information is unavailable

Data cannot be accessed and systems cannot be used.

Daily work stops

Orders, shipping, handling inquiries, and other work are disrupted.

Busy with recovery and explanations

Investigate the cause and explain to customers and business partners while recovery proceeds.

An example of what happens when information needed for business becomes unavailable.

What is risky? What should you fix first?

First, find your internet-facing assets from your domain and check for vulnerability candidates. When problems are found, decide the order of remediation based on severity and business impact.

PentaTrail supports this checking and decision-making, and keeps observing after updates and configuration changes.

ASM · Free

Find internet-facing assets

Explore assets starting from your domain and check for known vulnerabilities that may apply.

CTEM · Paid

Decide what to fix first

Review remediation priorities and specific remediation steps based on severity and asset importance.

CTEM · Paid

Remediate with the people involved

Share information internally and with your maintenance provider, and discuss who does what and when.

CTEM · Paid

Check the results of remediation

After updates and configuration changes, check whether vulnerability candidates are no longer detected or are detected again.

Whether a detected candidate affects your environment, and the actual fix, are decided and carried out by your company or your maintenance provider.

See the product screens and report

Even after you check, things change.

You launch a new site. You change a server’s settings. A new vulnerability is published for software you use.

Even if no problems were found when you checked, that may not stay true afterward. A problem you thought you had fixed can reappear with the next update.

Keep checking so you notice these changes and confirm that remediation is complete.

Read about one-time assessments versus ongoing checks

First check

You see the assets exposed at that point and the vulnerability candidates.

Your environment keeps changing
New sites and servers are exposed
Settings or software are changed
New vulnerabilities are published

Keep checking

Check for new assets, new problems, and changes after remediation.

Past results alone cannot tell you whether you are safe now.

An illustration of ongoing checks. It does not guarantee that changes are detected immediately or without omission.

Start checking from your own domain.

Get started