SHINDO3

Saison Technology

Customer records1,214records

EXPOSEDPhone number / Full nameMisconfiguration · Closed (final report)

Open in the live monitor ▶
Disclosed
Feb 24, 2026
Detected
Jan 21, 2026
Detection to disclosure
34 days
Leak
Exposed, access unknown
Type
Misconfiguration
Status
Closed (final report)
Security spend
Not checked yet
Compensation
Not announced

What leaked

Business dataCompany name and address
IdentityContact name
Employment & HRDepartment
ContactPhone number, Email address

How many

  • Customer records 1,214 records

Who is affected

  • Client company contacts

Cause

Cloud service misconfiguration

Timeline

  1. Exposure began
  2. Exposure ended
  3. Found by a security management tool
  4. Reported to authority
  5. Security NEXT report date

Response

  • Config review

Reviewed the cloud settings and made the files unreachable from outside

What you should do

  1. Don't open links in emails from this company. The apology email itself may be fake
  2. Treat refund or apology calls and texts as scams. Call back only on the number from the official site
  3. Check the company's notice to see if you're affected

Lessons for companies

  1. Two-person review and pre-release tests for sharing and cache changes; monitor cloud config (CSPM)
  2. Report to the PPC: preliminary in 3–5 days, final in 30 (60 if malicious)
  3. Run red teaming and AI-assisted hardening, and publish how much you invest

Sources