Security and an audit trail for your deployment
TL;DR
Changes made in your Pantheon workspace are recorded in an audit trail. Each deployment sets its own sign-in and two-factor policy. Credentials for connected accounts are encrypted before they are stored, and your data is never sold or used to train third-party AI models. A detailed security package is available under NDA.
On this page
An audit trail for workspace changes
Workspace changes made through Pantheon's app API, from editing a record to changing a member's role, are recorded with who made them and when. Security and sign-in events are logged too, and those logs fall under the same seven-year default hold as everything else (see records and retention).
Today the audit trail is reviewed by our team on your request. A customer-visible audit view, and an export of those events to your own security-monitoring system, are built on request.
Security settings that belong to your deployment
On a dedicated deployment, the security posture is a setting of your site: which sign-in methods are allowed, whether two-factor sign-in is required, and who may sign up. Settings are checked every time the deployment starts, so they cannot drift quietly from what was agreed. Company sign-in runs through your identity provider (see company sign-in).
How your data is handled
Organization data is isolated, encrypted in transit and at rest, and never sold or used to train third-party AI models. Credentials for the accounts your people connect are encrypted by Pantheon before they are stored. Pantheon staff never become owners of your workspace.
Attestations: where they stand
Some assurances cannot be built on request because an outside party issues them. Pantheon does not yet hold a SOC 2 report or a published penetration-test report, and we will not imply otherwise. Our current posture is on the security overview, and the detailed security package is shared under NDA.
What is standard and what is on request
Standard means it is part of every Pantheon Enterprise deployment today. On request means we build it for your deployment once you ask, and support it from then on.
| Capability | Availability | What it means |
|---|---|---|
| Audit trail of workspace changes | Standard | Who changed what, and when. |
| Per-deployment sign-in and two-factor policy | Standard | Checked every time the deployment starts. |
| Encrypted connected-account credentials | Standard | Encrypted before they are stored. |
| No training of third-party AI models on your data | Standard | Your data is never sold or used for training. |
| Customer-visible audit view | On request | Your admins read the trail directly. |
| Audit export to your security-monitoring system | On request | Events delivered to the tools you already run. |
Is Pantheon SOC 2 certified?
Not yet. Pantheon does not hold a SOC 2 report today. Our current posture is on the security overview, and the detailed security package is shared under NDA.
Does Pantheon keep an audit log?
Yes. Workspace changes are recorded with who made them and when, and security events are logged, under a seven-year default hold. A customer-visible audit view is on request.
Is our data used to train AI?
No. Your data is never sold or used to train third-party AI models.