SOC 2
Alignment work in progress. We are not certified today and will not describe ourselves as SOC 2 compliant, aligned or equivalent until a report exists that you can read.
In progress. Not held today.
This page exists so that nobody has to infer our certification position from a badge or a carefully worded sentence. We hold none of the certifications below today. Where work is underway we say what stage it is at, and when that changes the revision above changes with it.
Alignment work in progress. We are not certified today and will not describe ourselves as SOC 2 compliant, aligned or equivalent until a report exists that you can read.
Alignment work in progress. The controls we operate can be walked through with your assurance team in the meantime, on the understanding that this is our description rather than an auditor's.
Relevant to the OT side and treated as a design reference, not a claim. We can walk your team through the zones and conduits our architecture assumes, and through the parts of the standard it does not address at all.
Not a certification. Obligations are supported in every deployment model, and the data-residency page states how.
The specification itself, the deployment models, the access posture agreed per connector, and the audit trail. Those are testable during a pilot, which is a stronger basis for a decision than a certificate we do not yet have.
This clause is updated the day a certification is granted, not the day work starts on it. The revision letter above is how you tell.
If your policy requires a certificate before a pilot, tell us now and we will say honestly whether we can meet it.