Our Technology & Security
Enterprise-Grade Infrastructure. Designed for Clinical Trust.
Axonix is built on Microsoft Azure under Microsoft’s HIPAA Business Associate Agreement (BAA). Our platform incorporates layered identity controls, encryption safeguards, private networking, and continuous monitoring to support compliance with the HIPAA Security Rule.
​
Security is not an add-on. It is foundational to how Axonix is architected.
Secure Cloud Architecture Axonix operates entirely within Microsoft Azure’s secure cloud environment. Our infrastructure includes: - Dedicated Azure Virtual Network - Private endpoints for storage and service access - No publicly exposed storage containers - HTTPS-only endpoints (TLS 1.2+ enforced) - Encryption at rest and in transit All production resources are protected by Microsoft’s enterprise-grade physical and logical safeguards.
Encryption & Data Protection Axonix enforces encryption across all data handling. - Data encrypted at rest using Azure-managed encryption - All communications encrypted in transit (TLS 1.2+) - Secure certificate management through Azure Key Vault - No anonymous public access to storage resources PHI is protected both during transmission and while stored within the platform.
Logging, Monitoring & Audit Controls Axonix uses Azure Monitor and centralized logging services to maintain visibility and auditability. Monitored events include: - Authentication attempts - Privilege and role changes - Administrative configuration updates - Secure key access events - Storage and infrastructure activity These controls support operational oversight and incident response readiness.
Responsible AI Safeguards Axonix AI services operate under Microsoft Azure’s HIPAA Business Associate Agreement. Our safeguards include: - PHI is not used to train foundation models - AI communications occur over secured Azure endpoints - No external public AI endpoints are used - Human validation is required prior to final report completion
Identity & Access Management Strong identity governance is central to our platform. Axonix uses Microsoft Entra ID (Azure External ID) to manage authentication and authorization. Security controls include: - Mandatory Multi-Factor Authentication - Role-based access controls - No shared user accounts - Restricted administrative privileges - Periodic access reviews - Managed identities for secure service-to-service communication These controls ensure that only authorized individuals can access protected health information (PHI).
Secure Application Development Security is integrated into our development lifecycle. Axonix employs automated security testing and validation processes including: - Static Application Security Testing (SAST) - Dependency vulnerability scanning - Secret and credential scanning prior to code deployment - Secure session management (HTTPS) - Logging configurations that exclude PHI Security checks are enforced prior to deployment to prevent unsafe code from entering production.
Backup & Resilience Axonix incorporates Azure-native backup and recovery protections. - Encrypted backups - Soft-delete protection for storage - Role-restricted backup access - Azure recovery processes for production services
Ongoing Security Program Axonix maintains an evolving security program that includes: - Continuous monitoring and improvement - Periodic access reviews - Secure development lifecycle documentation - Disaster recovery program expansion - Enterprise-level key management options