Your submitted response
1026 wordsFrom: Incident Response Lead (SOC on-call)
To: IT Leadership · Privacy/Legal · Support Ops · Identity/Endpoint Admin · On-call SOC
Subject: [SEV-3][INC-CYB-AI42] Customer records pasted into unsanctioned public AI chatbot — containment and privacy review in progress
Incident: INC-CYB-AI42 · SEV-3 / P3
Status: Investigating — containment and exposure assessment in progress
Classification: Cybersecurity · Shadow AI · Sensitive Data Exposure
Affected asset: 42 customer records + internal helper script via `jordan.kim@acme-corp.com`
Data owner: Support Ops / Privacy
Detected: 2026-05-04 14:18 UTC
SITUATION & SUMMARY
DLP and web proxy telemetry indicate that `jordan.kim@acme-corp.com` used a personal account on an unsanctioned public AI chatbot, `chat.example-ai[.]com`, from the corporate workstation `JORDAN-WKS`.
At approximately 13:47 UTC, the endpoint DLP agent detected clipboard paste activity into the browser. The DLP rule matched approximately 42 rows of customer PII containing name, email, phone, and account ID fields, plus approximately 60 lines of an internal helper script. The web proxy confirms a POST to `chat.example-ai[.]com/api/conversation`. The request body was not inspected due to TLS, but the endpoint DLP event provides enough evidence to treat this as a likely sensitive-data exposure.
The AI chatbot is not approved, is not in the corporate app catalog, was accessed using a personal login, and has no enterprise data-retention configuration or DPA/contract in place.
SEVERITY & PRIORITY
This is rated SEV-3 / P3 at this time because the exposed dataset appears limited to 42 customer records and one internal code snippet, but it involves regulated customer PII and an unsanctioned public AI service with no contractual data-protection controls.
The privacy and data-exposure assessment should be handled urgently because customer PII may have been submitted to a third-party consumer AI platform outside approved channels.
IMMEDIATE CONTAINMENT
* Contact Jordan and instruct them to stop using the chatbot immediately.
* Instruct Jordan not to delete browser history, chatbot history, local files, screenshots, or any related evidence until SOC and Privacy approve.
* Preserve the endpoint DLP alert, including timestamp, host, user, rule hits, and redacted sample metadata.
* Preserve web proxy logs showing the connection and POST to `chat.example-ai[.]com`.
* Block or temporarily restrict `chat.example-ai[.]com` at the web proxy / DNS layer while the exposure assessment is in progress.
* Confirm whether any additional uploads to the same chatbot occurred from `JORDAN-WKS` or Jordan’s account.
* Do not wipe or reimage Jordan’s workstation unless separate evidence of malware or endpoint compromise appears.
INVESTIGATION
* Interview Jordan to determine exactly what was pasted, why it was pasted, whether the chatbot retained the conversation, and whether the output was copied or shared elsewhere.
* Ask Jordan to preserve the chatbot conversation and account context. If accessible, collect screenshots or an export through an approved evidence-handling process.
* Identify the source of the customer export report and determine whether it was generated legitimately within Jordan’s Support role.
* Confirm the exact fields exposed: names, emails, phone numbers, account IDs, and whether any additional sensitive fields were included.
* Determine whether the 42 customer records are real production customer records, test data, or mixed data.
* Identify whether the internal helper script contains secrets, API keys, credentials, internal URLs, business logic, or security-sensitive implementation details.
* Search DLP and proxy logs for other users accessing `chat.example-ai[.]com` or similar unsanctioned GenAI tools.
* Review Jordan’s recent browser/proxy activity for additional POSTs to the same service before and after the detected event.
* Review whether approved enterprise AI tools were available and whether policy banners, training, or technical controls were missing.
PRIVACY / LEGAL REVIEW
* Engage Privacy/Legal to determine whether this meets internal incident-reporting or external notification criteria.
* Provide Privacy with the minimum necessary facts: number of affected records, data elements involved, vendor/tool name, timestamp, user, and whether the data can be deleted or controlled.
* Determine whether the public AI provider’s terms allow retention, model training, human review, or downstream processing of submitted content.
* If possible, request deletion of the submitted conversation/data through the provider’s account or privacy process, coordinated by Privacy/Legal.
* Do not send raw customer PII in email, chat, or tickets while coordinating the review.
EVIDENCE PRESERVATION
* Preserve the DLP alert metadata and redacted sample summary.
* Preserve web proxy logs for `JORDAN-WKS` and `chat.example-ai[.]com`.
* Preserve endpoint telemetry around the clipboard paste event.
* Preserve Jordan’s browser history and relevant local artifacts, if policy permits.
* Preserve screenshots or exports of the chatbot conversation only through approved evidence-handling procedures.
* Preserve a list of the potentially affected customer record IDs in a restricted evidence location.
RECOVERY & NEXT STEPS
* Complete the data exposure assessment with Support Ops and Privacy.
* Confirm whether the internal script contains secrets or sensitive logic. If secrets are found, rotate them immediately.
* Remove or delete the chatbot conversation if the provider/account supports deletion and Privacy approves the action.
* Restrict or block unsanctioned GenAI services until an approved governance path is in place.
* Provide Jordan with targeted coaching on approved AI tools and prohibited data types.
* Review whether DLP should block, not only alert, on customer PII pasted into unsanctioned GenAI websites.
* Update acceptable-use guidance for public AI tools, especially for customer records, internal code, and ticket exports.
STAKEHOLDER COMMUNICATION
* Notify Support Ops that 42 customer records may have been exposed through an unsanctioned public AI service.
* Notify Privacy/Legal for exposure assessment and notification determination.
* Notify Endpoint/Web Security to preserve logs and apply temporary access controls.
* Notify Jordan’s manager after initial fact-gathering, avoiding unnecessary disclosure of raw customer data.
DO NOT
* Do not ask Jordan to paste the chatbot conversation or customer records into email or chat.
* Do not share raw PII in the incident ticket unless the ticket is access-restricted and approved for sensitive evidence.
* Do not delete the chatbot conversation before evidence is preserved and Privacy/Legal approves deletion.
* Do not treat this as malware or wipe the workstation without evidence of endpoint compromise.
* Do not assume the exposure is harmless because only 42 records were involved.
* Do not close the incident after blocking the website; complete privacy review, data scoping, and control improvement actions.