Identity and access
Managed sign in, workspace membership checks, and role based permissions protect customer access.
Trust center
Security practices described plainly.
Tektory handles important technology context. This page separates protections in the current product from work in progress and future independent assurance.
Current product protections
These controls are part of the present product foundation. Exact customer configuration and deployment readiness must still be confirmed during a pilot.
Workspace separation
Company records are scoped to the active workspace and require explicit membership.
Encrypted connections
Production traffic uses HTTPS and integration credentials are managed as runtime secrets.
Customer approvals
Workspace administrators control members, connected services, exports, retention, and action approvals.
Activity records
Material workspace and action changes create attributed records for review and investigation.
Evidence handling
Private evidence storage can use workspace scoped metadata, review status, retention dates, and activity records.
Security maturity work
- Independent penetration testing
- Documented incident response exercise
- Formal vendor risk management process
- Production monitoring and recovery validation
- SOC 2 readiness assessment
Independent assurance
- SOC 2 Type 1
- SOC 2 Type 2
- Additional customer requested assurance work
Claims only when earned
Product guidance is not certification.
The Tektory control playbook helps customers organize their own programs, but using the product does not create certification or satisfy a legal or regulatory obligation by itself.
Shared responsibility
Customers remain responsible for their environment.
Workspace administrators control what they enter, who they invite, which integrations they connect, and how recommendations are used. Tektory does not replace accountable technical, legal, risk, or compliance review.
Evaluate the current product