Ipsos: normal operations still leave a data scope question
Ipsos reported an incident in an internal system and said operations were unaffected. Clients need to connect projects, systems and evidence when assessing shared information.
Читать на португальскомBy Pentesty
What the statement establishes
In its statement dated November 16, 2026, Ipsos reported an incident affecting an internal system, with its investigation continuing. The document records a complaint filed with authorities on November 11, activation of incident response and assistance from outside specialists. The SecurityWeek report appeared on November 17. These dates document communications and actions; they do not establish when the intrusion began or was detected.
The company said operations and client delivery were unaffected. It also linked contact with concerned parties to establishing whether client, project or partner information was affected. The official statement does not confirm exfiltration, a number of affected people or a technical cause. An enterprise assessment should keep those questions open rather than supply assumptions to close the gap.
Availability and scope need separate questions
For a business commissioning research or sharing datasets with a provider, service continuity matters. A decision about information needs different evidence: which datasets passed through the system under investigation, for what purpose and under whose responsibility. Service can continue while that relationship is assessed. This is an analytical distinction, not a conclusion about information held by Ipsos.
Open a record for each potentially relevant project. Connect the contract to its internal owner, the types of information shared and the integrations used. Distinguish supplier confirmations, facts the business can verify and questions awaiting a response. Avoid classifying every project as affected solely because those projects share a supplier name.
Organize evidence around the decision
Build a timeline with the date and origin of each update received. Preserve statements and their versions without treating a news publication date as the incident date. For information under your control, identify transfer records, exports and permissions relevant to the project. Define the review period from established facts and extend it when new evidence warrants doing so.
Questions for the provider should permit a verifiable answer: which system is in scope, which projects were reviewed, what evidence supports the conclusion and when an update is expected. Use established contractual channels. The analysis of breach allegations helps organize that inquiry; the review of supplier deletion complements the inventory of copies and retention.
Rehearse the next update
In an authorized exercise, give the team two simulated updates: one leaves scope undetermined; another identifies a particular project. Observe who reviews the inventory, who approves communications and which evidence changes the classification. Use synthetic information and record the reasons for decisions, without implying these scenarios describe the actual incident.
Assign an owner and a next review for unresolved questions. A general availability response may settle an operational question while leaving the information assessment open. The final record should show that difference. Consider the assessment complete only when each decision has a scope, evidence, an accountable owner and explicit limitations, according to the obligations applicable to that project.
Record dependencies that may delay an answer: incomplete inventories, exports without an accountable owner and missing records for the relevant period. These limitations do not establish exposure. They show where the team needs additional information before giving the business a conclusion it can use.
Frequently asked questions
Did Ipsos confirm data theft?
The statement reviewed leaves the nature and scope under investigation. It does not confirm exfiltration or provide a total number of affected people.
Is November 11 the intrusion date?
It is the reported date of the complaint to authorities. The document does not identify it as the start of the intrusion or its detection date.
Does normal operation close the assessment?
Continuity answers a delivery question. Assessing scope requires connecting systems, projects and information with the evidence available for each decision.
What should a client do first?
Identify the contract owner and projects sharing information with the provider. Preserve updates and record outstanding questions without assuming confirmed impact.
Sources and references
Original Pentesty analysis, published November 17, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.