A finished survey can leave a trail of contact lists, interview recordings and raw responses.
Market research firm Ipsos disclosed on Nov. 16 that it was investigating a breach of one of its internal information systems. The company said its operations and ability to deliver work for clients were unaffected. Ipsos has yet to say whether anyone accessed or took data.
For security teams, the first step is to find out what Ipsos still holds.
Ipsos filed a complaint on Nov. 11
In its Nov. 16 announcement, Ipsos said it filed a complaint with the relevant authorities on Nov. 11. The company said it activated its incident response procedures, took steps to contain the breach and brought in outside cybersecurity specialists.
The disclosure leaves the affected system, the timing of the breach and any data exposure unspecified. Ipsos said it would contact those concerned directly if the investigation finds that information relating to clients, projects or business partners was affected.
The breach at La Poste subsidiary Maileva shows how much personal information can sit with a provider performing routine business work. For research clients, the equivalent records may sit in the files used to recruit participants, run interviews or process responses.
What security teams should check with Ipsos
Ask the team that commissioned the work to pull transfer records and project agreements for active and recently completed studies. Use that list to make specific requests through your established Ipsos contact.
- Inventory the data you shared. Identify participant contact lists, customer or employee identifiers, recordings and raw responses. Check whether Ipsos retained those files after delivering the findings. If the study used participant codes, find out who holds the file that links those codes to names.
- Ask Ipsos to check specific projects. Send project IDs and transfer dates. Ask whether the affected system stored the files or could access them, and whether investigators can distinguish access to a system from access to individual records. Review the agreement’s incident notice terms with privacy and procurement staff and confirm who should receive updates.
- Match the response to the data. If Ipsos confirms that participant contact lists were exposed, alert study owners to watch for impersonation. SEGA warned of that risk after the breach at its newsletter provider. If shared transfer credentials are implicated, identify who can revoke or rotate them. The Notion response to exposed third-party API keys illustrates why the credential owner matters.
If Ipsos cannot yet confirm whether a project was affected, agree on a date for the next update. Give responders a record of which files were sent, what Ipsos still holds and which questions remain open, so they can act on a project-specific notice as soon as it arrives.
Read more: The Amadeus breach affecting 53,000 Cathay Pacific bookings shows how the details in a vendor’s disclosure can help narrow which records need attention.





