Key takeaways
- Coles disclosed a cybersecurity investigation on November 16 and says it has found no evidence of compromised customer, employee, or supplier data so far.
- Nulab separately confirmed unauthorized access involving Cacoo and approximately 792 exposed inquiry records; Cacoo remains suspended.
- IT leaders should check vendor dependencies, support-ticket data, escalation contacts, and approved alternatives for interrupted services.
Original source
Coles Group and Nulab incident disclosuresWhat does the Coles cybersecurity incident mean for retail and supplier IT leaders?
Coles disclosed a cybersecurity investigation on November 16, saying it had found no evidence so far that customer, employee, or supplier data was compromised. Separately, Nulab confirmed exposed Cacoo support records. The practical priority for IT leaders is to check vendor dependencies, data exposure, and continuity plans without assuming both incidents have the same impact.12
These are separate disclosures. Coles has not announced a confirmed data theft; Nulab has. For organizations that depend on outside platforms, that distinction should shape both the response and the message employees receive.
What has Coles confirmed about its cybersecurity incident?
Coles is investigating with the Australian Cyber Security Centre and external specialists. Its November 16 stock-exchange announcement says experts are working to “contain and secure the Coles IT environment.” Stores and online shopping continue. The announcement does not identify the entry point, attacker, or detection date.1
Coles’ customer update acknowledges problems affecting a small number of Liquorland click-and-collect customers. It says it has no indication that Flybuys accounts were affected and warns customers to watch for suspicious messages. The company promises further updates through its official website.3
The operational lesson is to distinguish an investigation’s current findings from its final conclusion. An IT team should communicate what it knows about its own exposure, the evidence behind that assessment, and when it will revisit the decision. A vendor’s preliminary reassurance is useful information; it does not replace checking whether your organization relies on the affected service.
For a supplier, that check might involve confirming whether orders, invoices, or customer communications are still moving through the expected channel. For an internal security team, it means identifying the relationship owner who can obtain an authoritative update. Avoid changing payment details or granting emergency access merely because a message refers to a real incident.
What is the Cacoo data breach, and what does it mean for teams using online whiteboards?
Nulab’s November 16 disclosure says it detected misuse of company credentials in Cacoo’s operating environment on November 14. It disabled credentials, blocked attacker access, and suspended Cacoo at 18:45 Japan Standard Time that day. The previously announced emergency maintenance was part of its incident response.2
Approximately 792 Cacoo inquiry records were exposed, according to Nulab’s initial count. The records include personal information such as names, email addresses, telephone numbers, and addresses; some contain the last four digits of credit card numbers. That figure counts records, not necessarily unique people, and remains under review.2
Nulab says it has not confirmed unauthorized access to customer data in Backlog or its other services. It describes Cacoo and Backlog as operating in separate environments. Its 16:00 JST update on November 16 says individual notifications are underway and a report to Japan’s Personal Information Protection Commission has been completed.2
The English maintenance notice states, “All Cacoo features are unavailable during the maintenance period.” It also says Backlog and Nulab Flowbase remain available. Nulab’s status page supplies the ongoing service updates.45
For a team using an online whiteboard to document workflows, system diagrams, or project decisions, availability deserves attention alongside confidentiality. Identify the work that cannot proceed without the platform. Use an approved alternative and an authorized existing export where available; avoid moving sensitive diagrams into an unapproved personal account simply to keep a meeting on schedule.
Why should the Cacoo disclosure prompt a review of support-ticket data?
A support conversation can become a separate store of sensitive business information. The Cacoo disclosure makes inquiry records the immediate concern. For healthcare, education, and municipal IT teams, the practical question is what employees have shared with vendors while asking for help, and who owns the review of those submissions.
Datapath recommends including support channels in a vendor data inventory. Look beyond the application’s main workspace: review the categories of information sent through help forms, email threads, and attachments. A screenshot intended to explain a problem may include names, account identifiers, or operational details that the sender did not intend to disclose.
Start with the people who actually open support cases. Ask them to identify the system owner, the approved support channel, and the process for removing unnecessary details before sending an attachment. Where your team identifies a secret or other sensitive material in an affected record, route it to the incident lead for an exposure assessment and coordinated remediation.
This recommendation is about your organization’s handling of support information. It is not evidence that passwords, complete payment-card numbers, or every Cacoo user’s diagrams were exposed. Keep the incident record tied to the vendor’s confirmed scope and any direct notification your organization receives.
What should IT leaders check after the Coles and Cacoo disclosures?
Start with service ownership and business impact. Determine whether your organization uses either affected service, whether a vendor has contacted you, and which essential activities would suffer if access became unavailable. NIST’s incident-response guidance includes supplier coordination, asset inventories, and recovery planning as parts of managing cyber risk.6
For a focused review, assign an owner and a concrete output to each step:
- Identify the dependency. Record the service, business owner, administrator, and affected workflow. Include departmental subscriptions that may not appear in the central procurement list.
- Collect the relevant evidence. Save the vendor notice and any direct customer notification with its timestamp. Preserve your organization’s relevant logs and correspondence in the approved incident workspace.
- Assess your own exposure. Distinguish a service interruption, confirmed disclosure of your records, and an unanswered scope question. Escalate uncertainty to the person authorized to make containment decisions.
- Approve a continuity option. Identify an acceptable temporary workflow, the data it needs, and the person authorized to activate it. Test whether staff can use it without access to the unavailable platform.
- Set the next update. Give employees a named contact and a time for the next status message. Coordinate supplier questions through one owner so conflicting answers do not circulate.
NIST also recommends verifying the integrity of backups and other restoration assets before using them. An exported document is useful only if it is accessible, sufficiently current, and appropriate for the work that must continue.6
A practical exercise is to pick one essential vendor and walk through an interruption with its business owner. Determine who can authorize a workaround, which records must be available, and how the team will return to normal operations without losing changes made during the interruption. Record unresolved decisions as assigned work rather than treating attendance at the exercise as proof of readiness.
How should regulated organizations communicate about the Coles and Cacoo incidents?
Communicate your organization’s verified situation and the actions staff should take. A useful internal update identifies the service, the affected work, the approved alternative, and the next review time. Route questions about sensitive records and external notifications to your established security, privacy, and legal owners before making commitments.
For example, a team that cannot access Cacoo can tell employees where to find approved project documents and who is coordinating with the vendor. A team assessing a possible exposure can explain that review separately. Avoid assigning a confirmed breach label to an organization solely because its services are interrupted.
Use Datapath’s cyber incident communications plan template to define those communication responsibilities. For longer-term improvements, the vendor risk questionnaire provides a starting point for discussing escalation, service dependencies, and provider accountability before the next urgent notice arrives.
Datapath helps regulated and mid-market organizations connect security planning with operational responsibilities through managed cybersecurity services and vendor risk management services. A useful next step is to review one critical supplier’s access, data handling, and outage plan with the people responsible for keeping that service usable.
Can your team act on a vendor security notice?
Review your critical vendor dependencies, sensitive support data, and response responsibilities with Datapath.
Sources
Footnotes
-
Coles Group, Coles investigating cyber security incident, ASX release, November 16, 2026. ↩ ↩2
-
Nulab, Unauthorized access involving Cacoo: initial report, November 16, 2026, updated at 16:00 JST (Japanese). ↩ ↩2 ↩3 ↩4
-
Coles Group, Cyber Security Incident: statement and customer and supplier FAQs, November 16, 2026. ↩
-
Nulab, Important: Notice Regarding Emergency Maintenance for Cacoo, November 15, 2026. ↩
-
Nulab, Service status and Cacoo maintenance notice, maintenance beginning November 14, 2026. ↩
-
Alex Nelson, Sanjay Rekhi, Murugiah Souppaya, and Karen Scarfone, Incident Response Recommendations and Considerations for Cybersecurity Risk Management, NIST SP 800-61 Rev. 3, April 2025. ↩ ↩2
Disclaimer: This news summary is intended for informational and marketing purposes only, and nothing presented here is contractually binding or necessarily the final opinion of the authors.