Fireworks and Notion: scoping data at a provider
The Fireworks and Notion notices show why supplier reviews must trace data and credentials by function. Establish the affected dataset before deciding what recovery requires.
Leer en portuguésBy Pentesty
Scope follows the function
The initial Fireworks notice records activity identified on October 6, 2026. The November 9 update describes another route: an incident at a cloud provider on October 23 and access to development machines on October 24. These are distinct points in the timeline; this analysis is dated November 10.
The expanded findings cover metadata and billing information, plus subsets of datasets and incomplete weights for certain accounts. Calling an environment a research system does not, by itself, confine the consequences to employees. Establish which customer data could reach the affected application.
Notion limited its disclosure to fewer than 1% of workspaces and transcripts used for Insights. For most affected workspaces, it described transcripts without user or workspace labels and without tool call results. This does not establish exposure of every conversation, feature or category of Notion customer data.
Map the data paths
For a customer organization, the first useful deliverable is a specific map of the integration. Identify which feature sends data, under which identity and for what purpose. This review complements the analysis of application secrets by connecting each credential to the data it can reach.
- Origin and purpose: connect each submitted field to the approved feature, an internal owner and the reason for using real data in that processing step.
- Retention and copies: examine uploaded datasets, temporary files and diagnostic artifacts. These are paths to investigate in your integration, not additional claims about this incident.
- Effective permission: check what the identity can read, change and export. Record exceptions and differences between the stated configuration and the access you observe.
Test the route with synthetic data
With authorization and in a test environment, place a marker such as CLIENTE-SIMULADO-47 in a request containing no personal information or real credentials. Follow the approved processing stages. Record whether the text reaches the expected service, remains in intermediate storage or appears in a diagnostic artifact. When a stage cannot be observed, document that limitation and who can supply the evidence.
Repeat the route with the feature disabled and the identity restricted. Compare timestamps, destinations and authorized outcomes, retaining enough identifiers to reproduce the assessment. This test establishes the behavior observed within that scope. Deletion of historical copies at the provider requires separate evidence from the people responsible for those systems.
Revoke access and record what remains
For accounts identified in notifications, follow the official instructions for reviewing the affected dataset. Connect any secrets found there to their issuer and the application that uses them. Removing a stored value does not invalidate the corresponding credential. For an authorized test account, confirm revocation at the issuer and operation of the replacement, without copying secret values into the report.
The decision to close the assessment should combine the account notification, data flow inventory, test results and exceptions accepted by a responsible owner. The review of trust between cloud accounts can complement this work for cloud integrations. A conclusion about one product must respect the notice’s product name, period and scope; it does not automatically settle questions about other data paths.
Frequently asked questions
How do we establish whether our workspace is in scope?
Use the official communications addressed to the account. Record when you checked and retain the follow-up channel specified by the provider. Local investigation should work from the data identified for your organization.
Does removing origin labels make a chat non-sensitive?
Not automatically. The text can contain names, plans or secrets. Classification should consider the content authorized for review, even when account attributes are absent.
Does deleting a secret remove access?
No. The credential remains valid until its issuer revokes or changes it. Identify the integration that used it, confirm revocation and validate a replacement with appropriate permissions.
What supports closing the assessment?
A responsible owner accepts the demonstrated scope, authorized test results and open exceptions. The record separates local recovery from conclusions that depend on the provider’s investigation.
Sources and references
- Fireworks: initial October notice
- Fireworks: expanded scope and response
- Notion: scope of the supplier incident
- BleepingComputer: consulted reporting
- The Hacker News: consulted reporting
- The Record: consulted reporting
Original Pentesty analysis, published November 10, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.