Classic Campus is built for multi-tenant operations with strong tenant isolation, role-based access control, audit trails, and deployment flexibility (cloud or on‑prem).
Below is a practical checklist to help ICT and audit teams evaluate Classic Campus.
• Role-based access (RBAC)
• Department / campus scoping
• Approval workflows for high-risk actions
• Optional SSO (SAML/OIDC) for Enterprise
• Tamper-aware audit trails
• Exportable logs for investigations
• Admin activity visibility
• Alerts for unusual patterns (configurable)
• Encrypted secrets and secure configuration
• Privacy-first defaults for portals
• Controlled exports
• Data retention options (policy-driven)
• Automated backups (cloud) or assisted (on‑prem)
• Restore testing guidance
• Optional standby environment for Enterprise
• Incident playbooks
• Secure headers and transport best practices
• Environment separation (dev/stage/prod)
• IP allowlists (optional)
• On‑prem hardening checklist
• Privacy policy + DPA templates
• Data access logging for audits
• Procurement-ready documentation
• Security review support for ICT teams
Book time with our team to review your requirements (on‑prem, SSO, audit logging, backups, and policies).
Below is a deeper explanation you can share with ICT, internal audit, and procurement. This is written in plain language, not marketing.
Each institution is logically isolated. Data access is always scoped to the tenant, with permission checks on every request and safe defaults for exports.
Roles map to real jobs (registrar, bursar, dean, lecturer, auditor). Sensitive actions can require approvals, and changes are tracked end‑to‑end.
Critical events (fee adjustments, results updates, user changes, approvals) write to audit logs you can export during investigations or annual audits.
Use encrypted secrets for credentials and integrations, rotate keys, and separate environments (dev/stage/prod). Transport security is enforced with modern TLS and secure headers.
Automated backups (cloud) or assisted backups (on‑prem). DR options include restore testing guidance, retention policies, and optional standby environments for Enterprise.
A quick checklist for ICT teams—use it during vendor evaluation and procurement sign‑off.
Send your ICT/security checklist and we’ll respond with architecture notes, controls, and the right deployment option (cloud or on‑prem).