Security FAQ

Security & Compliance

Security, privacy, and compliance questions for AgenixChat deployment in regulated industries

What security certifications does AgenixChat have?

AgenixChat is built on a security-first architecture ready for enterprise certifications: SOC 2 Type II Ready: Architecture designed to meet SOC 2 requirements for security, availability, processing integrity, confidentiality, and privacy. ISO 27001 Ready: Information security management system (ISMS) aligned with ISO 27001 standards. HIPAA Compliant: HIPAA-ready deployment options with Business Associate Agreement (BAA) available for healthcare customers. GDPR Compliant: Data processing practices aligned with GDPR requirements including data minimization, purpose limitation, and user rights. PCI DSS: Infrastructure supports PCI DSS requirements for customers processing payment data. FedRAMP Pathway: Architecture designed for FedRAMP authorization for government deployments. Certification status varies by deployment model. Contact us for specific certification documentation.

Is AgenixChat HIPAA compliant?

Yes, AgenixChat supports HIPAA-compliant deployments for healthcare customers: Technical Safeguards: Encryption at rest (AES-256) and in transit (TLS 1.3), access controls with role-based permissions, audit logging of all PHI access, automatic session timeouts, secure authentication (MFA supported). Physical Safeguards: Deployment on HIPAA-compliant infrastructure (AWS, Azure, GCP), data center security controls, disaster recovery and backup procedures. Administrative Safeguards: Business Associate Agreement (BAA) available, security policies and procedures, workforce training requirements, incident response plan. PHI Handling: Database-level encryption, secure data transmission, configurable data retention, secure deletion capabilities, audit trail for all PHI access. Healthcare customers should deploy on VPS or on-premises for maximum control. BAA execution required before processing PHI.

How is data encrypted?

AgenixChat implements encryption at multiple layers: Data at Rest: Database encryption using AES-256, encrypted backups, API keys encrypted before storage, user passwords hashed with bcrypt (12 rounds), file storage encryption (if applicable). Data in Transit: TLS 1.3 for all HTTPS connections, encrypted WebSocket connections for real-time features, encrypted database connections, secure API communication with AI services. Key Management: Encryption keys stored in secure key management service, key rotation supported, separate keys per tenant (multi-tenant isolation), hardware security module (HSM) support for Enterprise Plus. Application-Level: Sensitive fields encrypted at application layer, tokenization for payment data (if applicable), secure session management. All encryption uses industry-standard algorithms and follows NIST guidelines.

What authentication methods are supported?

AgenixChat supports multiple enterprise authentication methods: Built-in Authentication: Email/password with bcrypt hashing, JWT-based session management, multi-factor authentication (MFA) via TOTP, password complexity requirements, account lockout after failed attempts. Single Sign-On (SSO): SAML 2.0 (Okta, Azure AD, OneLogin, Google Workspace), OAuth 2.0 / OpenID Connect, LDAP / Active Directory integration, custom SSO providers supported. API Authentication: API key authentication for programmatic access, JWT tokens for user-context API calls, OAuth 2.0 for third-party integrations, webhook signature verification. Session Management: Configurable session timeout, automatic logout on inactivity, concurrent session limits, secure cookie handling (HttpOnly, Secure, SameSite). Enterprise customers can enforce SSO-only access and disable password authentication.

How do you handle data privacy (GDPR, CCPA)?

AgenixChat is designed for privacy compliance: GDPR Compliance: Data minimization (collect only necessary data), purpose limitation (use data only for stated purposes), user consent management, right to access (data export), right to erasure (data deletion), right to rectification (data correction), data portability, privacy by design and default. CCPA Compliance: Consumer rights support (access, deletion, opt-out), do not sell personal information, privacy notice requirements, data inventory and mapping. Data Processing: Data Processing Agreement (DPA) available, sub-processor list maintained, data transfer mechanisms (Standard Contractual Clauses), data residency controls (EU, US, custom regions). User Rights: Self-service data export, automated deletion workflows, consent management, privacy settings per user. All data processing documented and auditable.

Can we deploy in an air-gapped environment?

Yes, AgenixChat supports air-gapped deployments for maximum security: Deployment Model: Complete on-premises installation, no internet connectivity required, all components self-contained, offline license management. Requirements: Enterprise Plus tier, dedicated infrastructure (32+ cores, 96GB+ RAM), PostgreSQL database on-premises, your AI service (on-premises or within air-gap), offline update mechanism. Use Cases: Government agencies (classified networks), financial institutions (trading floors), healthcare (PHI isolation), defense contractors, research facilities. Support: Offline documentation package, on-site installation assistance, dedicated support channel (secure email/phone), quarterly on-site reviews. Updates: Offline update packages, manual deployment process, security patches delivered via secure channel. Air-gapped deployments require Enterprise Plus tier and custom implementation.

What audit logging is available?

Comprehensive audit logging for compliance and security: User Activity Logs: Login/logout events with IP and device, user actions (create, read, update, delete), permission changes, failed authentication attempts, session management events. Data Access Logs: Message access (who viewed what), conversation history access, user data exports, API access logs, file access (if applicable). System Logs: Configuration changes, space creation/modification, role and permission changes, integration configuration, AI service interactions. Security Events: Failed login attempts, permission denied events, suspicious activity detection, API rate limit violations, encryption key usage. Log Retention: Configurable retention (30 days to 7 years), tamper-proof log storage, log export to SIEM (Splunk, ELK, etc.), real-time log streaming, compliance reporting. All logs include timestamp, user ID, IP address, action type, and result.

How are API keys and secrets managed?

Secure secrets management following best practices: API Key Storage: Encrypted at rest using AES-256, stored in secure database with restricted access, never logged or displayed in plain text, separate encryption keys per tenant. Key Generation: Cryptographically secure random generation, configurable key length and format, automatic key rotation support, key expiration policies. Access Control: Role-based access to key management, audit trail for key creation/deletion, key usage tracking, rate limiting per key. Secret Management: Integration with HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, environment variable injection, secure configuration management. Best Practices: Keys never committed to version control, secure key distribution to services, automatic key rotation (optional), revocation and regeneration workflows. Enterprise customers can integrate with their existing secrets management infrastructure.

What is your incident response process?

Structured incident response for security events: Detection: 24/7 security monitoring, automated threat detection, anomaly detection algorithms, real-time alerting, SIEM integration. Response Team: Dedicated security team, on-call rotation, escalation procedures, communication protocols. Incident Handling: Immediate containment, root cause analysis, remediation actions, evidence preservation, stakeholder notification. Communication: Customer notification within 24 hours (Enterprise), detailed incident reports, remediation timeline, lessons learned documentation. Post-Incident: Security improvements, policy updates, team training, compliance reporting (if required). Customer Responsibilities: Report suspected incidents, provide access for investigation, implement recommended mitigations. Enterprise customers receive dedicated incident response support with custom SLAs.

Do you offer BAA for healthcare customers?

Yes, we offer Business Associate Agreements (BAA) for HIPAA compliance: BAA Availability: Available for Enterprise and Enterprise Plus customers, required before processing PHI, covers all HIPAA requirements, includes required safeguards and breach notification. BAA Terms: Permitted uses and disclosures of PHI, safeguard requirements, breach notification procedures, subcontractor management, termination provisions, audit rights. Technical Requirements: HIPAA-compliant deployment (VPS or on-premises), encryption at rest and in transit, access controls and audit logging, secure backup and recovery, incident response procedures. Compliance Support: HIPAA compliance documentation, security risk assessment assistance, policy and procedure templates, staff training materials. Ongoing Compliance: Regular security assessments, compliance monitoring, breach notification support, audit assistance. Contact our healthcare team to execute a BAA and discuss HIPAA deployment requirements.

Related Resources

Need Security Documentation?

Request our security whitepaper and compliance documentation

Request Security Docs