Search
Close this search box.
SOCReporting Guide

FAQ: Do we need to review an AI feature again when the provider changes the model?

Assess the change against the use case and the risk you accepted. A provider update may alter output quality, available controls, data handling, or how an integration behaves. Keep a record of the versions you can identify, review available change notices, and decide which checks need to be repeated before wider use. If the provider does not offer version control or adequate notice, account for that limitation in your operating plan. Not every change requires a full new audit, but a material change should not pass unnoticed simply because the feature name and subscription stayed the same.

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

SOC 1 or HITRUST?

Choose based on the assurance your customers need. SOC 1 addresses controls relevant to customers’ internal control over financial reporting. HITRUST offers cybersecurity assessments and certifications with different scopes and

Get Our Emails

SOC Reporting Guide