Gleen AI is Now SOC 2 Type 2 Compliant

Another week, another milestone at Gleen: we've received our SOC 2 Type 2 attestation from Sensiba LLP, and we're now (officially) SOC 2 Type 2 compliant.  (See http://www.aicpa.org/soc4so.)

For any generative AI solution, SOC 2 Type 2 attestation is incredibly important. Here's why.

No generative AI solution survives without customer trust.  

In generative AI, trust is necessary at 2 different levels. Every generative AI customer should be asking themselves these 2 basic questions:

1 - Can I trust the responses of the generative AI solution?  i.e., Does it hallucinate?

Gleen AI is the leader in no-hallucination generative AI. Over 80% of Gleen AI's tech stack is focused on preventing hallucination.

No hallucination is absolutely necessary in generative AI solutions in customer service and sales.  But it's not sufficient.

2 - Can I trust the generative AI solution with all my proprietary data?

A generative AI solution can touch and/or create a lot of proprietary data, including:

• The knowledge used to train the generative AI
• The guidelines used to shape the tone and behavior of the generative AI
• The questions entered by customers and employees into the generative AI
• The access to internal systems granted to the generative AI, like order management or payment processing
• The generative AI's actual responses, especially if the AI is responding in a private channel
• The feedback provided to the generative AI, both by customers and by admins

With all this proprietary data, prospective generative AI customers have the following concerns:

Concerns specific to generative AI:

• Will the solution leak sensitive information (like response guidelines) to the public?
• Does the solution prevent prompt jacking or jailbreak prompts?  (i.e., hackers using the generative AI as an attack vector into the rest of my environment)
• Will the solution train on my proprietary data, and will other customers benefit from this training?

General SaaS concerns (not specific to generative AI)

• Will the solution intermingle my data with other customers' data?
• Will the solution share my data with other sub-processors that are less secure?
• Will the solution introduce vulnerabilities into my production environment?
• Will the solution preserve the integrity of my data?
• Does the solution provider have sufficient data security controls?
• Are they trying to detect security incidents?
• Can they quickly repair damage and restore functionality in the event of a data breach or system failure?

Customers considering Gleen AI can rest assured. We've been hard at work for several months, and we are now officially SOC 2 Type 2 compliant.

Kudos to Nagendra, Gleen Co-Founder and CTO, for taking the lead on making Gleen AI SOC 2 Type 2 compliant. Thanks also to Drata (compliance automation firm) and Sensiba (audit firm) for helping us achieve this milestone as well.

Onwards & upwards,

Ashu