Hosting and security

Where it runs

• Edgent-hosted on Amazon Web Services. This is the production path for customers. Each organization has an isolated data store.
• Your own environment, on a Kubernetes cluster including OpenShift, or on a single Linux host for evaluation.

The public demonstration at acme.lms.vforce360.ai is Edgent's own demonstration environment and holds synthetic data only.

Identity and access

• Sign-in through Keycloak, connected to your identity provider by SAML or OIDC.
• Learner, instructor and administrator roles, with authority granted at an organizational unit reaching that unit and its descendants and nothing above it.
• Every consequential action recorded against the person who took it, exportable to your SIEM.

Data

• Learner records never leave the organization that produced them. Shared course content reaches an organization only when assigned.
• Packaged third-party content runs in a sandboxed, cookieless origin with a content security policy.
• Nightly database backups, kept 30 days daily and 12 weeks weekly, and a weekly automated restore validation.
• Metrics with alert rules, and central logging.
• Your whole estate leaves at any time as an open archive, and a hosted environment is deleted on request after an export exists.

Availability

The current release runs one application instance per environment with no automatic failover. Recovery is by restart or restore from backup.

Attestations

Edgent holds no FedRAMP, StateRAMP or SOC 2 attestation, and no HIPAA attestation. The access, audit and encryption controls are described in the security and accessibility evidence we provide on request.