Security overview
How Aevum secures what it holds, and how little that is.
This document is being written, and we have published the page now rather than leave you guessing. A school evaluating us should be able to see exactly what is coming, what it will contain, and what has to happen before it is signed off. Treat this page as the plan, not as the finished document.
What this document will contain
- The threat model for data that stays in the building, and how it differs from a cloud one
- Access control, update integrity and the model artefact
- Vulnerability management and testing cadence
- Compatibility with the Cyber Security Standards for Schools and Colleges
What we are doing to finish it
We publish this once the red-team report and an independent review are in hand. Security is the applicable DfE standard we are furthest from, and the mapping says so plainly rather than quietly.
If you need this now
If your procurement timeline needs this document before it is finished, write to hello@aevumfoundry.ai. You will get a straight answer about where the work has got to, and we will never dress it up as further along than it is.