Secure by Design
Defence‑in‑depth, role‑based access; 2FA supported.
We apply secure by design principles and secure development practices. Controls are mapped to integration and deployment needs (cloud or customer environment) without compromising speed.
Data Separation & Provenance
Strict separation of foundational model data and scenario data; SME‑verified sources; human review to mitigate bias/hallucination.
Foundational model data and scenario data are kept separate. Sources are SME‑verified; all entities, events and scripts are labelled with provenance to mitigate bias and reduce hallucination risk while maintaining a clearly accessible audit trail.
Hosting & Integration
AWS/Azure deployment patterns; export support of exercise data to customer systems; customer retains ownership of data generated in exercises.
Deploy to AWS/Azure or approved customer secure environments. Export exercise data back to customer systems; customers retain ownership of their data and control distribution of the scenario truth across multiple systems.
Compliance
Add export control notice (UK/US), classification handling statement, and responsible disclosure mailbox.
We support UK/US export‑control obligations and classification handling. A responsible‑disclosure mailbox is available for reporting security concerns.
Security engineering notes:
Secure‑by‑design
Data separation between foundational model and scenario datasets
Verified sources + SME review
2FA and cloud hosting options (AWS/Azure)