On this page

The company described different effects across services

Norwegian sorting-equipment group TOMRA disconnected selected systems during its July 2023 cyberattack. Its timeline said North American reverse-vending (container-return) machines remained connected, while material-recovery services were affected and some remote-service work used manual procedures. Parts access was a practical challenge. A September account described staged restoration after system validation.

These are dated company accounts of distinct services. They do not establish that every customer was unaffected or that the same fallback would suit another business.

Sources: TOMRA: Timeline’s19–20 July 2023 updates: North America machine/material-recovery distinctions, manual remote-service work and spare-parts access TOMRA: 29 September 2023 article: manual workarounds and staged system validation/restoration

Follow a customer problem from first call to completion

For your operation, ask what happens when the normal business system is unavailable. The customer still needs a contact, a supported assessment, any necessary part or technician and an explanation of the next step. A general instruction to work manually leaves those jobs undefined.

Use this ELN continuity map with authorised operational and security leads. It is a responsibility exercise, not a set of technical instructions for handling a cyber incident.

Customer jobOffline capability to establishResponsibility to name
Receive and assess the requestAn approved contact route and access to the minimum necessary product informationPerson who owns the unresolved customer issue
Find a part or technicianA trustworthy source for identity, stock and available capacityDispatch/parts lead and technical escalation
Record work and commitmentsA controlled way to keep decisions and avoid duplicate promisesPerson who reconciles temporary records later
Restore the normal routeEvidence the authorised technical/security team requires before reconnectionPerson who approves the operational switch back

Include the time consumed by the fallback

Fictional example: a team can answer calls but cannot trust the stock screen. Someone must verify the part and available quantity through an authorised alternative before dispatch. That extra job can slow the response even when the equipment itself remains usable.

Test the process with a permitted exercise. Check simultaneous calls, absence cover, information protection and the return of temporary records to the normal system. Do not put passwords, customer data or confidential incident records into the learning worksheet.

Make the continuity claim specific enough to test

Ask management which service continues, with which information, people and limitations. Identify work that must stop until a qualified person can approve it. A successful fallback for one product or customer route does not prove every service is covered.

Use Management dependence to assign the offline jobs, backups and recovery decision. Keep detailed incident and security procedures in your authorised business process.

Scope

  • The dated public account does not establish current operations, private contract terms or a result another company can expect.
  • ELN’s exercise is an original planning aid. The actual product, people, permissions, contract and costs need their own evidence.

Next step

Use Management dependence to assign customer contact, parts/dispatch, temporary records and the recovery decision. Test a specific offline customer journey with the authorised team.

Sources & review notes

Access dates show when a source was retrieved. Review dates show when its meaning was checked. Editing this guide does not recheck the law.

TOMRA’s consolidated 2023 cyberattack timeline

TOMRA

Passage, dates and research notes

company-incident-updates · Timeline’s19–20 July 2023 updates: North America machine/material-recovery distinctions, manual remote-service work and spare-parts access

Accessed: 2026-11-16T10:40:22.420510+00:00 · Meaning reviewed: 2026-11-16T10:48:36.481030+00:00 · Next review target: 2026-12-16

Read timeline context and19–20 July entries, plus later restoration entries. URL slug is not the date of every entry. No no-leakage/no-loss assertion is independently adopted; offline machine operation differs from full digital-service availability.

TOMRA’s September 2023 restoration account

TOMRA

Passage, dates and research notes

company-incident-update · 29 September 2023 article: manual workarounds and staged system validation/restoration

Accessed: 2026-11-16T10:40:22.738048+00:00 · Meaning reviewed: 2026-11-16T10:48:36.481030+00:00 · Next review target: 2026-12-16

Read main article. Used for the stated validation/restoration sequence only; revenue, cost, incident-cause and data-security assurances are not treated as independently proven results.

Your learning

Bookmark this guide or mark it as read.

Learning library
Progress privacy

Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.

This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.