Synthetic demonstration data only. No Tribal, student, or contributor data is used here. Stand-in language content is used, and no Native language is represented. This environment is not a FedRAMP-authorized or production system.
Hosting, security and compliance
Three things are kept apart here: security features of the application, controls inherited from the hosting environment, and the authorization a federal production system would need. Each line states the current status, including what is not held.
Status statement. This demonstration is not presented as a FedRAMP-authorized federal production deployment. We can support an architecture and control-mapping exercise to determine the appropriate federal hosting boundary, inherited controls, agency authorization pathway and deployment model.
Live and demonstrableConfigurable with existing productRequires integrationFuture / pilot developmentNot currently held
Hosting and authorization
| Hosting environment | Microsoft Azure commercial cloud, US region. This demonstration runs on a shared SLS web tier. | Live and demonstrable |
| Federal cloud boundary | Deployment into Azure Government or another FedRAMP-authorized environment, with a dedicated boundary. | Future / pilot development |
| FedRAMP authorization | Not held. The demonstration is not presented as a FedRAMP-authorized or production federal system. | Not currently held |
| Agency ATO | Not held. A control-mapping exercise would define the boundary, the inherited controls and the authorization path. | Not currently held |
| Data residency | United States region. Tenant data stays in that tenant’s tables and private storage. | Live and demonstrable |
Protection of data
| Encryption in transit | TLS for every endpoint, with HSTS and security headers. | Live and demonstrable |
| Encryption at rest | Azure managed-disk server-side encryption using platform-managed keys (inherited from the host). | Live and demonstrable |
| Customer-managed keys | Key Vault-backed customer-managed keys per deployment. | Configurable with existing product |
| FIPS 140-validated cryptography | Not currently configured or documented. It would be required for a federal boundary. | Not currently held |
| No model training | Language, cultural, contributor and learner data are excluded from model training by default, recorded on every consent and xAPI statement. This demonstration sends no tenant data to AI services. | Live and demonstrable |
Identity, access and audit
| Role-based access | Ten least-privilege roles. The platform administrator cannot sign review gates. | Live and demonstrable |
| Attribute-based access | Audience tags (learner, educator, authorized community, restricted) enforced on pages, media and exports. | Live and demonstrable |
| Federated identity and MFA | SAML 2.0 / OIDC federation (e.g. Microsoft Entra ID), with MFA enforced at the identity provider. | Configurable with existing product |
| Application audit log | Hash-chained, append-only event log with verification and CSV export. | Live and demonstrable |
| Central logging / SIEM | Forward application and server logs to the agency SIEM (e.g. Microsoft Sentinel, Splunk). | Requires integration |
Operations
| Backup | Automated daily database backups to Azure Blob Storage with 90-day retention. | Live and demonstrable |
| Recovery objectives | RPO ≈ 24 hours today. RTO has not been formally tested or documented. | Not currently held |
| Vulnerability management and SBOM | Server hardening and intrusion banning are in place. A formal scanning programme and SBOM are not yet documented. | Future / pilot development |
| Incident response | Responsibilities would be defined in the governing agreement and system security plan. | Future / pilot development |
Compliance and accessibility
| Section 508 / WCAG 2.1 AA | This interface is built to WCAG 2.1 AA practices (semantic structure, keyboard operation, contrast, captions where approved). There is no formal conformance report (ACR/VPAT) yet. | Not currently held |
| FERPA / COPPA readiness | Pseudonymous learners, minimum-necessary views and guardian-consent fields. A legal assessment would be needed before any student use. | Configurable with existing product |
| NIST SP 800-53 control mapping | Not yet performed. Offered as the next technical step. | Future / pilot development |
| Privacy Impact Assessment / SORN | Agency-led for a federal system. SLS would supply the system documentation. | Future / pilot development |
| Records retention and deletion evidence | Export-before-exit is live. Retention schedules and deletion certificates would be configured per agreement. | Configurable with existing product |
User interface options
| Responsive web | Learner, teacher, reviewer, administrator and auditor views on any modern browser | Live and demonstrable |
|---|
| Localizable learner interface | Interface strings per tenant and per language | Live and demonstrable |
|---|
| Offline / low-bandwidth app | The SLS offline learning app packages course content for intermittent connectivity | Configurable with existing product |
|---|
| Family / home view | Home practice and family participation features | Future / pilot development |
|---|
| Immersive and 3D | SLS immersive-room, 360° and 3D tour players are live on other SLS sites | Configurable with existing product |