Current public version published on the date shown.
AuraOne / Trust / Security
Enterprise security and data isolation
Enterprise security architecture, access controls, data protection, and vulnerability disclosure across the AuraOne platform.
Public version 1.0 · Effective October 10, 2026
Document record
- Version
- Public version 1.0
- Effective
- Effective October 10, 2026
Document summary
Overview
- Enterprise security architecture, access controls, data protection, and vulnerability disclosure across the AuraOne platform.
- Security controls, data handling, and deployment governance for enterprise AI programs.
Scope and shared responsibility
AuraOne security controls are tailored to the selected product, deployment model, customer environment, data classifications, identity provider, and governing agreement. Customer and AuraOne responsibilities are documented during architecture and security review.
Each deployment defines explicit tenant isolation, network egress, and encryption boundaries aligned to your security requirements.
Identity and access
Identity, authentication, authorization, service accounts, privileged actions, and offboarding are scoped to the deployment. Access follows least privilege and separation of responsibilities across operators and reviewers.
Enterprise security reviews cover identity architecture, role mappings, and audit logging for your target deployment.
- Human and service identity inventory
- Role and permission boundaries
- Privileged access and approval records
- Credential rotation and offboarding
Data protection
Data classification, ingress, processing, storage, retention, export, deletion, encryption, region, and transfer assumptions are agreed for each program during security review.
Restricted source material should move only through approved product and support paths. Public forms must not contain credentials, private datasets, protected health information, or other customer-confidential content.
Data licensing and consent
Data used for model training or evaluation comes from a source with a stated right to supply it. The source and its permitted uses are recorded before a task is built from it.
- Public software fixes. Only code under a permissive license, with the license and its notices kept.
- Owner-licensed records. Work history that an owner licenses to us in writing, for the uses that license names.
- Expert-created data. Work made for a program by qualified people under an agreement that covers the use.
Model-provider output restrictions are checked before any model output enters a dataset. Training examples and sealed holdouts are kept in separate partitions. Retention, region and transfer terms are set in each signed scope.
Read how the work is delivered on the Data Partnerships and agent training data pages.
Application and change security
Every source path has assigned code owners. Dependency updates are proposed weekly by an automated bot. Secrets, tests, deployment approval, rollback, and vulnerability handling are covered in security review.
- Change review and protected delivery paths
- Dependency and vulnerability management
- Secret-management and configuration review
- Release approval and rollback
Monitoring, recovery, and incidents
Logs, metrics, traces, audit events, alerts, backup, restore, recovery, and incident handling are agreed for each product and environment during review. Monitoring should preserve useful evidence without exposing restricted source content.
Customer communication, support coverage, response timing, recovery objectives, and notification duties are defined by the governing agreement and incident context.
Framework and procurement posture
AuraOne's public posture does not claim SOC 2 certification or Type II attestation. Security, availability, and confidentiality materials are scoped for buyer review, and any current report is shared through the security review process.
AuraOne's public posture does not claim formal HIPAA compliance. Administrative, technical, and physical safeguards are scoped for sensitive-data workflows, and regulated responsibilities are established during procurement.
AuraOne's public posture does not claim formal GDPR compliance. Data processing, regional scope, transfer, and request-support responsibilities are established through buyer review and executed program documents.
AuraOne's public posture includes ISO 27001 as a control-mapping and buyer-review topic. AuraOne does not claim ISO 27001 certification; certification status, certificate, scope, and dates would be established by current verified evidence.
Open the compliance posture page for the current public framework labels.
Report a security issue
Report a security issue through the contact form. Include a short description, the affected product or route, the observed impact, and a reply address. Do not place exploit instructions, credentials, private data, or customer identifiers in the public form.
Change history
Procurement review
Security review materials
The exact materials depend on your product, deployment, and review scope.
- Architecture
- Data flow, identity, and regionsCustomer deployment scope
- Controls
- Relevant control owners, procedures, and evidenceSecurity review materials
- Operations
- Logging, recovery, and incidentsOperating and contractual record
- Limitations
- Excluded systems, assumptions, and customer dutiesShared-responsibility statement