Trust begins with claims that match the product.
This Trust Center distinguishes locally verified controls, deployment responsibilities, design partner capabilities, expansion architecture, and capabilities that are not currently available.
Verified control. Explicit deployment scope.
TracePoint is currently available through design partner implementations. Production scope, integrations, security controls, deployment model, and service commitments are agreed for each implementation.
The Operational Change Authorization workflow returns canonical ALLOW, DENY, or ESCALATE outcomes from pinned authority and policy versions.
Configured authority and policy profiles
External identity and durable decision storage
Authority Envelopes express actor, accountable principal, actions, resources, purposes, limits, validity, and review rules.
Enterprise authority source
Administrative workflow, approval controls, and durable version history
Defined exceptions create a pending review that can resolve to approval, denial, or expiry.
Named accountable reviewer
Enterprise reviewer identity and separation of duties
Permitted decisions produce an expiring authorization with issuer, audience, target, operation, nonce, and action fingerprint.
Server controlled issuer
Durable authorization state and managed signing keys
Payload mutation fails the action fingerprint check before execution.
Canonical action serialization
Connector conformance and portable verification
A consumed authorization cannot execute again in the current product environment.
Single process authorization state
Transactional persistence across instances and regions
Execution creates an Action Receipt connected to its Decision Record and authorization.
Conforming execution connector
External receipt signing and reconciliation
The product environment links bounded reversal context to the original decision and receipt.
Target system recovery operation
External compensation and reconciliation controls
Anonymous product sessions use high entropy HttpOnly tokens and isolated expiring process memory.
Single application process
Tenant scoped durable storage and session governance
Current state is stored in process memory and expires with the session or process.
Transactional database and retention policy
Backup, recovery, migration, and reconciliation testing
No general multitenant production isolation claim is made.
Selected deployment model
Tenant boundaries, encryption context, and isolation tests
TracePoint accepts external actor and principal references but does not establish enterprise identity.
Customer identity provider and workload identity
Authentication assurance, lifecycle, and revocation integration
No public SSO implementation is present in the repository.
Enterprise identity provider
Federation, session controls, and administrator recovery
The product environment does not implement production role enforcement.
Enterprise identities and role model
Separation of duties, access review, and privileged administration
The included connector controls only the local Operational Change Authorization workflow.
Target system owner and enforceable integration point
Connector authentication, conformance, failure, and bypass testing
The current server controlled fingerprint is not a portable signature and does not provide non repudiation.
Key management and verifier trust model
Signing, rotation, revocation, and verification profiles
Connected evidence is available in the product environment, but no production audit export service is claimed.
Customer evidence destination and retention rules
Durable export, access controls, integrity checks, and delivery monitoring
No public production SLA or availability commitment is claimed.
Agreed hosting and support model
Monitoring, incident response, redundancy, recovery objectives, and service agreement
NIST is a reference language, not the product category.
TracePoint maintains a NIST CSF 2.0 reference mapping to help security teams discuss relevant evidence and responsibilities. It does not claim certification, endorsement, adopted control effectiveness, or compliance.
Review the NIST reference map ↗Deployment boundaries are explicit.
Processing location, tenancy, retention, integration access, and shared responsibilities are defined in the enterprise architecture and governing agreement.
Tenant model
Multi-tenant or isolated enterprise environment
Identity boundary
Customer-controlled identity and access
Restricted deployment
High-sensitivity operating environment
Regional residency
Jurisdiction-specific processing location