Pause the affected AI workflow, alert the designated legal and security leads, and preserve relevant records without spreading the suspected disclosure. Identify what deal material entered the tool, which account and permissions applied, and who may have received or accessed it. Record confirmed facts separately from unresolved questions. Counsel should assess applicable professional rules, confidentiality and privilege issues, contracts, and notification duties while security personnel investigate and contain the technical exposure. Do not wait for perfect certainty before escalating: ABA guidance calls for reasonable, prompt action when a breach is suspected, although controlling duties depend on jurisdiction and facts. [2] Resume only through a documented human decision after containment and appropriate checks.
1. Open an incident record and assign decision owners
Treat a report of an unexpected AI output, mistaken upload, or unintended shared conversation as a signal requiring assessment, not as proof that an outsider read the material. The first reporter should use the team's approved incident channel and describe the event without attaching the entire confidential document. Capture discovery time, the affected matter, the tool and account, the reported action, and whether exposure appears ongoing.
Name an incident lead and backup who coordinate the response. Assign technical containment and evidence collection to authorized security personnel. Assign legal analysis and notification decisions to designated counsel, with ethics or privacy specialists where needed. The transaction lead should identify affected deal activities and arrange an approved fallback. NIST distinguishes leadership, incident handlers, technology personnel, legal experts, and asset owners rather than placing every decision with one operator. [3]
Keep a decision log stating who authorized each action, when it occurred, and what evidence supported it. Establish the next update time and an escalation route for new material facts. Counsel should define the purpose and handling of legal work; the team should not assume that involving counsel or labeling a record makes everything privileged.
2. Pause the affected path without destroying evidence
Stop new uploads, prompts, output sharing, and downstream use associated with the suspected exposure. The security lead should determine whether containment also requires disabling a shared link, restricting the affected account, suspending a connected data source, or revoking compromised credentials. These are possible responses, not instructions to shut down every system. NIST describes containment as preventing an incident from expanding and supports incident handlers selecting appropriate actions. [3]
Coordinate preservation and urgent containment rather than treating them as competing sequential projects. If a shared link is exposing live material, an authorized responder should address it promptly and document the change. Do not delay containment solely to create an ideal evidence package. Equally, do not clear conversation history, erase accounts, or request deletion as an improvised cleanup before the legal and security leads assess preservation needs.
Redirect affected diligence review or drafting to an approved manual process. Tell users what has stopped and where to report related activity. In an illustrative scenario involving a pasted diligence extract, pause that account's affected workflow and related output circulation while responders determine whether the issue extends to other matters.
3. Preserve a controlled evidence set
The security lead should preserve available prompts, attachments, outputs, conversation identifiers, access records, sharing settings, and relevant account configuration using approved collection methods. Record timestamps with time zones and distinguish the discovery time from the underlying event time. Capture the applicable terms, permissions, and retention settings where ascertainable; today's screen may not establish what applied when the upload occurred.
Retain originals in a restricted evidence location and create working copies only as needed. Document who collected each item, its origin, collection method, subsequent transfers, and any changes caused by containment. NIST recommends preserving the integrity and provenance of incident records and data, safeguarding their confidentiality, and collecting evidence under organizational preservation and retention procedures. Formal chain-of-custody handling is not required for every incident; counsel and qualified responders should determine what this matter needs. [3]
Avoid forwarding a confidential transcript to a broad deal distribution list or uploading it to another AI service for explanation. Provider support requests should follow an approved route with only necessary information. Preserve relevant material proportionately under counsel's instructions rather than collecting unrelated client files indiscriminately.
4. Map the exposed material to source-of-truth records
Build an exposure inventory tied to the original deal records. For each affected input or output, identify its source document and version, matter, owner, information category, and known disclosure restrictions. Include material pasted into a prompt, attached files, and information retrieved from connected sources. Review outputs too: a short summary may still reveal sensitive information even when no original document was shared.
The transaction lawyer should compare the inventory with the authorized deal file, diligence index, engagement terms, confidentiality agreements, and client instructions. Flag legal advice, negotiation positions, employee or customer information, and other sensitive content for the appropriate reviewer without declaring that every item has the same legal status. ABA Opinion 512 explains confidentiality under the Model Rules broadly as information relating to a representation, not merely information marked confidential. Applicable local rules still control. [1]
Label each finding as confirmed, reasonably supported, or unresolved. An upload record can establish that material entered a service without proving another customer saw it. Missing access records do not establish that nobody did. ABA breach guidance calls for reasonable efforts to determine what happened and what information was accessed or lost. [2]
5. Trace possible recipients and provider handling
Separate the possible exposure paths: processing by the provider, access by workspace members, access through a shared link, retrieval across matters, and forwarding of generated output. Establish which paths the actual configuration permitted and which the available records show occurred. Do not collapse provider processing, model training, and public disclosure into a single assumed event.
Have the authorized technical contact ask the provider focused questions about the affected account, relevant retention, access, sharing, and available investigation records. Counsel should review contractual rights and restrictions before requesting preservation, remediation, or confirmations. ABA Opinion 512 recommends understanding a tool's terms of use, privacy policy, and related terms to assess access risks, including risks inside the firm. An account's commercial label alone does not answer those questions. [1]
Record the provider's response and its limits. A confirmation that a link was disabled does not establish whether anyone accessed it earlier or retained a copy. Where evidence cannot resolve recipients or handling, carry that uncertainty into counsel's assessment rather than filling gaps with an AI-generated explanation.
6. Put legal and notification decisions on a separate track
Counsel should identify the relevant jurisdictions, affected clients and other data subjects, applicable professional rules, and contractual commitments. Assess confidentiality and any privilege questions separately from technical containment. Do not announce either automatic privilege waiver or preserved privilege based only on the name of an AI tool. These are fact-specific legal questions for qualified counsel, not software determinations.
ABA Opinion 483 interprets Model Rule 1.4 as requiring notice to affected current clients when a breach involves, or has a substantial likelihood of involving, material client confidential information. It recognizes reasonably suspected access and does not make complete forensic certainty a prerequisite. This is ABA Model Rules guidance, not a universal notice rule; counsel must apply controlling jurisdictional requirements. [2]
Evaluate statutory, regulatory, contractual, and professional obligations separately. The opinion does not impose a general Model Rules notice duty to former clients, but notes that other law or contracts may require it. [2] Maintain a counsel-controlled register of potential recipients, applicable triggers and deadlines, decision owners, approved content, and unresolved facts. Notification assessment should run alongside investigation, not wait until every question is answered. Software must not select recipients or send notices autonomously.
7. Control communications and transaction consequences
Prepare a factual briefing for counsel that explains what is known, suspected, and still being investigated, together with containment steps and affected deal activities. Where client notice is required, ABA Opinion 483 calls for the known or reasonably ascertainable extent of access or disclosure and disclosure of an inability to establish scope after reasonable efforts. It also describes continuing communication about material investigative developments. Local requirements may differ. [2]
Counsel should approve any recipient-facing communication and determine whether protective requests or other legal remedies are appropriate. An authorized person should execute the approved communication through the approved channel. Do not ask a model to contact buyers, negotiate confidentiality undertakings, admit liability, or approve a response.
The transaction lead should identify deadlines or materials affected by the pause and coordinate the approved fallback. Keep operational updates distinct from legal conclusions. Removing a document from a deal workspace may limit further access, but it does not resolve prior exposure, satisfy every notice duty, or establish that copies no longer exist.
8. Limit any AI assistance to a checked, permissioned task
AI assistance is optional during the response. A narrow trial could test whether a tool organizes a synthetic incident timeline into a draft status update. The incident lead owns factual review, counsel reviews legal wording, and neither delegates approval. Before any real record is used, obtain the required authorization, assess the exact service's confidentiality arrangements, and remove unnecessary sensitive details. Sanitization itself requires human checking; removing a client name may leave identifying deal facts.
Require the draft to distinguish facts from assumptions and point to approved record identifiers. The reviewer should compare every event, recipient, timestamp, and claimed containment step with the evidence set. Original records remain the source of truth. ABA Opinion 512 requires appropriate independent verification and warns that AI cannot replace professional judgment. [1]
Stop the trial if it invents an event, changes a material timestamp, implies unverified access, exposes restricted information, loses source references, or proposes an unauthorized action. Return to manual drafting. A successful synthetic test is not permission to upload confidential evidence or proof that the tool is suitable for the live incident.
9. Require a human restart decision and record lessons
Restart only when the designated legal and security owners have documented the necessary containment, corrected permissions or configurations, assessed outstanding obligations, and approved the proposed use. Test the affected sharing and access boundaries with synthetic material before restoring client-data workflows. Keep use paused if material exposure remains unexplained, required permissions are missing, or checks reveal renewed access problems. NIST recommends verifying restoration, addressing root causes before production use, and using criteria to declare recovery complete. [3]
Record lessons in the response plan: clearer reporting channels, updated permissions, narrower permitted inputs, evidence collection instructions, and a named owner for follow-up. Closing the technical incident does not automatically close ongoing legal decisions or client updates. The resulting process should identify an escalation owner, an evidence custodian, counsel-led notification decisions, and explicit restart conditions.
Acquivo is a software platform that delivers the entire sell-side M&A process, valuation, marketing materials, buyer matching, and deal management, on one platform for business owners, M&A attorneys, and boutique investment banks. It is user-operated software with no success fee. This incident-response framework is a recommended team process, not a claim about specific Acquivo security or AI features. Software does not represent clients, decide legal duties, or guarantee confidentiality, privilege, compliance, or incident outcomes.
Key Points
- Escalate suspected exposure promptly and pause the affected workflow without assuming disclosure has been proved.
- Give legal and technical decisions named human owners, and document authorization for containment and recovery.
- Preserve restricted evidence and map inputs, outputs, permissions, and possible recipients to original deal records.
- Run counsel-led notification assessment alongside investigation, applying the relevant jurisdiction, facts, and agreements.
- Use synthetic trials for optional AI assistance, stop on material errors or permission failures, and require human approval before restart.
Sources and references
Source retrieval dates record research access, not article publication. Read our editorial and date policy.
- [1] ABA Formal Opinion 512: Generative Artificial Intelligence Tools, July 29, 2024 · Accessed
- [2] ABA Formal Opinion 483: Lawyers' Obligations After an Electronic Data Breach or Cyberattack, October 17, 2018 · Accessed
- [3] NIST SP 800-61 Revision 3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management, April 2025 · Accessed
Choose your next step
Acquivo is user-operated software. Owners and their professionals remain responsible for decisions, communications, and professional review.
Educational information, not individual legal, tax, or investment advice. Consult qualified professionals for your circumstances. Acquivo provides software, not representation or negotiation on your behalf.