View all

Earning trust through action: Our SOC 2 Type 2 milestone

As IndyKite’s Security Lead, I know firsthand how crucial it is to demonstrate strong, consistent security practices. In today’s digital world, trust is everything - and achieving our SOC 2 Type 2 certification marks a major milestone in earning and maintaining that trust with our customers.

What trust means to us

At IndyKite, trust goes beyond secure infrastructure. It means being accountable for the data customers entrust to us - through reliable systems, clear processes, and independent verification. This certification helps demonstrate that commitment in a measurable, third-party validated way.

From Type 1 to Type 2: Raising the bar

Last year, we were proud to complete our SOC 2 Type 1 audit - it validated the structure and intention of our security practices. But Type 2 is where the real work happens.

SOC 2 Type 2 confirms we’re not just putting security on paper, but actively implementing and maintaining it across the entire organization. Security claims are easy to make. SOC 2 Type 2 gives our customers independent assurance that their data is protected, and that we’re serious about our responsibilities. The audit process helps us identify gaps before they become issues. It’s not just a checkbox - it’s an opportunity to improve and strengthen our defenses.

Security isn’t optional - it’s foundational. At IndyKite, our SOC 2 Type 2 journey reflects a deep and ongoing commitment to doing things the right way. At the end of the day, security certifications are about more than just checking a compliance box. They are about proving to our customers that we truly follow through on our commitment to security.

A continuous journey

Security isn’t something you achieve once and forget. It’s an ongoing journey. And at IndyKite, that journey is driven by one goal: earning your trust - and keeping it.

For more details on the announcement, check the press release here and for more information on IndyKite’s approach to security and privacy here.

In this article

Keep updated

Subscribe

More from the Blog

Enforcing user intent across AI tool calls

Learn how to enforce user intent across AI agent tool calls using OpenID AuthZEN, COAZ-MCP mappings, and gateway-driven Intent-Based Access Control (IBAC).

Intent based access control: Whose Intent is it anyway?

Intent-based access control checks agent actions against the user’s original goal. Learn why Subject intent beats Agent intent and how AuthZEN formalizes it.

Meta's Muse and the enterprise risk of AI agent access you can’t see

When AI agents borrow a user’s identity, their actions become harder to trace. Explore what Muse reveals about enterprise visibility, delegated authority, and control over agent actions.

Resources

Blog

Enforcing user intent across AI tool calls

Next

Guides & Whitepapers

The Enterprise Guide to EU AI Act Compliance

Next

News

IndyKite launches Intent-based access control that limits every AI agent to the task

Next
News