Cyber Security Cloud GitHub breach sparks customer data leak concerns
A third party gained unauthorised access to the development environment of Japan's Cyber Security Cloud after one employee's GitHub credentials were leaked. The company is investigating the possible exposure of some customers' company names, names, email addresses and information relating to service communications. Limitations in the logs meant the full period of access could not be established, and the company said it would work to prevent a recurrence and rebuild trust.
Key facts
- Affected organisation
- Cyber Security Cloud
- Incident type
- Data breach
- Occurred / detected
- Not confirmed
- Scale of damage
- Possible exposure of some customer information
- Cause / method
- Unauthorised access to the development environment using leaked employee GitHub credentials
- Location
- Japan
If your data was exposed
Exposed dataNameEmail
- Don’t tap links in texts, calls or emails that mention this incident and offer compensation, refunds or breach checks. Check directly on the organisation’s official website or app.
Timeline
- Unauthorised access to the GitHub development environment and a possible customer data leak were disclosed.
- The investigation continued into the possible exposure of some customers' company names, names, email addresses and information relating to service communications.
9 related reports
- サイバーセキュリティクラウド：開発用GitHubの認証情報流出による個人情報の漏えいのおそれ
- サイバーセキュリティクラウド－後場急落 開発環境において情報漏えいのおそれがあることが判明(トレーダーズ・ウェブ)
- セキュリティサービス提供会社が個人情報漏洩おそれ「再発防止と信頼回復に向けて全社を挙げて取り組む」（ABEMA TIMES）
- サイバーセキュリティクラウド、開発基盤GitHubに不正アクセス 従業員認証情報1件流出で顧客情報に漏えい懸念
- Japan's Cyber Security Cloud reports unauthorized access to GitHub development platform; one employee credential leaked, raising customer data breach concerns
- セキュリティ企業が不正アクセス受ける サイバーセキュリティクラウド – Quebee キュエビー
- セキュリティ企業が不正アクセス受ける サイバーセキュリティクラウド（テレビ朝日系（ANN））
- 認証情報が漏洩、GitHub環境に不正アクセス - CSC
- サイバーセキュリティクラウド、GitHubから顧客情報流出か 「セキュリティ企業として重く受け止め」
The summary and key facts are written by AI from related reports and may contain errors. Check the original articles and the organisation’s official statements for accurate details.