Security
HCL BigFix AEX implements layered security controls to protect data, identities, and platform operations.
- Data encryption: TLS 1.2/1.3 for data in transit and AES-256 encryption for data at rest across all storage layers.
- Data protection: Strong access controls, encryption, and configurable retention protect customer and AI-related data.
- Identity & access management: SSO via SAML 2.0 with enterprise IdPs and role-based access controls enforce least-privilege access.
- Platform architecture & isolation: Secure-by-design architecture with network isolation, encrypted integrations, and authenticated APIs.
- Availability & disaster recovery: High availability design with redundancy, backups, and defined recovery processes.
- Logging & monitoring: Continuous logging and 24×7 monitoring of access, application, and AI activity.
- Secure development & testing: Security embedded across the SDLC with threat modeling, testing, and GenAI-specific safeguards.
- Incident response: Structured vulnerability management and incident response led by our PSIRT
- Edge & network protection (SaaS): Uses a web application firewall (WAF) and DDoS protection at the edge to protect the platform from common web threats and volumetric attacks.
- Session security: Interactive sessions are automatically terminated after 15 minutes of inactivity.
- API & service security: Platform APIs require authentication (for example, API keys and OAuth 2.0). Service-to-service communication uses secure channels and mutual TLS where applicable.
- Backups: Storage snapshots and component backups are maintained, including (e.g.) Cloudant weekly (30 days), VectorDB daily (35 days), Redis daily (30 days), and Postgres daily (30 days).
- Security monitoring: Security events are aggregated into a SIEM for 24×7 monitoring, supported by service heartbeat monitoring.
- Log Retention: Application logs are retained up to 30 days and access logs up to 1 year (subject to policy and deployment scope).
- GenAI Threat Testing: Includes testing aligned to OWASP guidance for LLM application risks (for example, prompt injection and data leakage).