Classification Strategy
On this page
Best Practices
Start broad, classify entire spaces first. Classify spaces as Internal for most, Confidential for spaces containing sensitive projects. Then add page overrides for individual documents that are more or less sensitive than the space default.
Restrict by exception. It is more practical to classify most spaces as Internal and add Restricted overrides to specific pages than to classify every page individually.
Align with your data governance policy. Use the same terminology your organization’s data classification policy uses. If your policy uses “Confidential” for what Aegis calls “Restricted”, map accordingly and document the alignment.
Cover all spaces. Classifying all spaces ensures every page’s exposure score reflects its actual sensitivity.
Re-review quarterly. Classifications can go stale as space content evolves. Schedule a quarterly review of Confidential and Restricted spaces to ensure the labels still reflect the actual sensitivity of the content.
Recommended Starting Configuration
| Space Type | Recommended Classification |
|---|---|
| Public-facing product docs | Public |
| General internal knowledge base | Internal |
| HR, legal, finance spaces | Confidential |
| Security ops, incident response, credentials | Restricted |
| External contractor workspaces | Confidential |