Aegis GRC
- Tenant isolation: each workspace is logically isolated, with scoped access
- Encryption in transit and at rest
- Tamper-evident audit logging
The principles that apply across Aegis products, and where to find product-level detail. This page says plainly what it does and does not cover.
These are design principles that guide Aegis products. Product-level implementation detail is kept separate, below.
Security is considered when a feature is designed, not added afterward.
Automation runs inside defined limits, and those limits can be reviewed.
Consequential actions are designed to wait for a person to decide.
Products record what happened, so teams can review it and explain it later.
Access should be scoped to what a role needs, and sign-in should use the identity systems customers already run.
Workflows should use only the data they need, and that data should be protected as it moves and where it is stored.
AI assists people and is not given unchecked authority. Input from untrusted sources is treated as untrusted, and sensitive data is controlled.
Specifics belong to the product that implements them. Here is how each product describes its own controls.
This page does not list certifications, attestations, or audit reports. If your team needs current security documentation for a review, ask us and we will tell you exactly what is available.
Ask a security questionWe are glad to answer them directly.