01
Tenant Isolation
Every customer and MSSP client operates within its own logical tenant boundary, with separate data stores, encryption context and access scopes. Cross-tenant access requires explicit, auditable authorization.
Security & Trust
We Hold Ourselves to the Same Standard We Audit You Against.
Tenant isolation, encryption, and disclosure practices for the platform itself.
This page is maintained by AlexoCloud AI and describes current platform practices. It is not an independent certification.
Pillars
Platform data protection
02
Encryption At Rest & In Transit
Data in transit is protected with modern TLS between clients, collectors and the platform. Data at rest is encrypted using industry-standard algorithms managed through the platform's key management workflow.
03
Least-Privilege Access
Scanners and connectors request the minimum permissions needed for a read-only security assessment. Internal platform access follows role-based controls, review workflows and access logging.
04
Independent Testing
The platform is subject to periodic third-party security testing and internal review cycles. Findings feed the same remediation workflow customers use inside the product.
Responsible disclosure
Found a security issue?
We welcome coordinated reports from security researchers. If you believe you have found a vulnerability in the AlexoCloud AI platform, please contact our security team directly. Include reproduction steps, affected components and any supporting artifacts. We aim to acknowledge new reports within one business day and provide status updates through remediation.
Security contact
security@alexocloud.aiCompliance posture
Specific certifications, audit reports and control attestations for the AlexoCloud AI platform are made available under NDA to qualified enterprise customers on request. We intentionally do not publish certification badges or audit outcomes on this public page. Contact your account team, or write to us, for the current compliance package.