Search
Close this search box.
SOCReporting Guide

FAQ: How should AI-related mistakes fit into incident response?

Use the existing reporting route, but make sure it recognizes AI-specific problems such as unintended disclosure, unsupported customer-facing statements, or an agent taking an unauthorized action. Record the use case, affected data or users, relevant version and configuration, and what happened. Preserve necessary evidence with appropriate access restrictions. Assign responsibility for containment, investigation, communication, and safe restoration. A mistaken output is not automatically a reportable breach, but it still needs assessment against your commitments and applicable obligations. Feed lessons back into approvals, testing, and training instead of treating each event as an isolated prompt-writing problem.

Related: SOC 2 audit and compliance hub.

Further reading: NIST Generative AI Profile.

Additional FAQs

What should happen after we approve a vendor?

Assign an owner to keep the review current and follow up when circumstances change. Triggers can include: Set a review schedule that fits the risk and applicable obligations. Review sooner

How often is a SOC 2 audit required?

The timing depends on customer and contractual requirements, not a universal certificate expiry date. Ask customers what report age and coverage period they accept, and check contractual requirements. Then agree

What is fourth-party risk?

Fourth-party risk is the risk to your organization from a supplier your vendor relies on. For example, your payroll provider may use a separate hosting company. An outage or security

Get Our Emails

SOC Reporting Guide