KOMORIManufacturer and technology company

Explore the site

Explore the site

Our workshop in Toyohashi, Aichi
Toyohashi, Aichi

SECURITY · KOMORI

Security report

To protect customer data, KOMORI stacks defenses at the edge, in transit, on the server, in the applications and in backups. This page shows how it works and how many attempts were actually stopped, using automatically collected figures.

Last updated: · refreshed automatically every hour

Last 30 days

Server intrusion attempts blocked
— Being set up
Password-guessing attempts stopped at login
37 Runs of wrong passwords (272 failures) detected and throttled or paused
Malicious requests blocked at the edge
— Being set up
Encrypted traffic (HTTPS)
100% TLS 1.3 and a valid certificate verified on every main domain

Collected since 2026-10-01. Items marked “Being set up” will show figures once collection starts.

Day by day

Login failures detected (per day)30-day total: 272
2026-09-28 : 0 2026-09-29 : 0 2026-09-30 : 0 2026-10-01 : 48 2026-10-02 : 133 2026-10-03 : 1 2026-10-04 : 2 2026-10-05 : 12 2026-10-06 : 1 2026-10-07 : 13 2026-10-08 : 10 2026-10-09 : 4 2026-10-10 : 0 2026-10-11 : 1 2026-10-12 : 3 2026-10-13 : 0 2026-10-14 : 17 2026-10-15 : 4 2026-10-16 : 1 2026-10-17 : 7 2026-10-18 : 0 2026-10-19 : 1 2026-10-20 : 0 2026-10-21 : 3 2026-10-22 : 0 2026-10-23 : 3 2026-10-24 : 1 2026-10-25 : 4 2026-10-26 : 0 2026-10-27 : 3
09-28max 133/day10-27
View as table
DateLogin failures detected (per day)
2026-10-273
2026-10-260
2026-10-254
2026-10-241
2026-10-233
2026-10-220
2026-10-213
2026-10-200
2026-10-191
2026-10-180
2026-10-177
2026-10-161
2026-10-154
2026-10-1417
2026-10-130
2026-10-123
2026-10-111
2026-10-100
2026-10-094
2026-10-0810
2026-10-0713
2026-10-061
2026-10-0512
2026-10-042
2026-10-031
2026-10-02133
2026-10-0148
2026-09-300
2026-09-290
2026-09-280

How our layered protection works

  1. CDN and WAF (edge defense)

    Every web request first passes through a global CDN that stops known attack patterns, malicious bots and volume attacks (DDoS) before they reach the server.

  2. Encryption in transit

    All services are HTTPS-only. Certificates renew automatically and are watched for expiry.

  3. Automatic intrusion blocking

    Failed server logins are watched continuously; persistent sources are automatically blocked at the firewall.

  4. Login protection

    Logins to KOREOS and other systems limit attempts: brute force is paused and slowed down without locking out legitimate users.

  5. File and data isolation

    Attachments are served only after a permission check. Each product and customer runs on separate applications and databases.

  6. Malware protection

    Uploaded files can never run as programs on the server. Automatic antivirus scanning of attachments is being rolled out; figures will appear here once it starts.

  7. Daily off-site backup

    Data is copied every day to a location outside the server (Google Drive) over an encrypted channel, so it can be restored after a failure.

  8. 24/7 monitoring

    All services are monitored automatically; any failure alerts the team immediately, and every incident feeds improvements.

Hosting and responsibility

Our server runs in a data center in the United States (GeHost). Data management and security are designed and operated by KOMORI株式会社 in Japan, under its own responsibility.

No system is “100% unbreakable”. We review our protections continuously and publish these records to stay transparent. If you notice a vulnerability or suspicious behavior, please reach us through our contact page.

Method and notes

  • All figures come from the real records of our defense systems, collected automatically every hour (nothing typed by hand or estimated). Dates are Japan time.
  • To avoid helping attackers, IP addresses are partially masked and configuration or software details are not published.
  • Each block counts one blocking action; the same source may be counted more than once.