Mock / Demo Documentation
Mock and Demo Environment Operations Guide
Use this guide to run demonstrations safely, isolate non-production data, and keep demo outputs distinct from authorization records.
- Enable demo mode only in sandboxed organizations intended for training or demonstrations.
- Use redacted sample artifacts; never upload controlled or production-sensitive content.
- Apply clear naming labels with `DEMO` or `SAMPLE` prefixes for systems and assessments.
- Disable outbound integrations to production identity or ticketing systems where possible.
- Create a dedicated demo organization and assign least-privilege demo roles.
- Import a reference framework and seed sample assessments.
- Load redacted artifacts and run scoring to demonstrate workflow behavior.
- Export reports with visible draft/demo markings.
- Reset demo records between sessions to avoid stale context.
- State that all displayed data is synthetic or redacted.
- Show RMF phase progression from intake through report export.
- Explain AI scoring as advisory with human approval checkpoints.
- Call out tenant isolation and audit logging controls.
- End by clearing test artifacts and invalidating temporary accounts.
Demo outputs must not be treated as production assessment evidence or authorization package artifacts.
Keep demo reporting exports in dedicated non-production storage locations and retain explicit labels in filenames and metadata.