The Cyborg Control Centre powers a clear, tiered Roles-Based Access Control (RBAC) Framework across Cyborg ERP. Designed to align with NEP-2020, ISO 27001, and NIST practices, it keeps academic and administrative operations secure, auditable, and easy to govern.
Establish a structured, tier-based policy for user authorisation and access privileges—covering admins, faculty, students, and parents—so data stays confidential, actions are accountable, and governance is visible through Cyborg Control Centre (CCC).
Control Centre — Roles-Based Access Control (RBAC) Framework
Empower your institution with secure, transparent, and policy-driven governance through the Cyborg Control Centre . Manage authorizations, approvals, and audit trails seamlessly — ensuring every action is accountable and every user has the right access.
Ans: CCC governs who can access what across all modules using a tiered RBAC (Roles-Based Access Control) model — ensuring each stakeholder only sees and performs actions allowed by their role.
Ans: Yes. Roles, scopes, and approval chains are fully configurable per campus, college, department, or program — while retaining complete auditability and control.
Ans: CCC supports MFA, SSO (Azure AD / Google Workspace / University LDAP), dynamic IP policies, and role-scoped API tokens (JWT/OIDC) for secure authentication.
Ans: All data is encrypted using AES-256 at rest and TLS 1.3 in transit, and each record is tagged by Institute → Department → Program → Role for traceability. Every action is captured in audit trails.
Ans: Yes. Dual-approval (maker–checker) can be enforced for high-risk operations such as role elevation, bulk updates, or financial/admin changes.
Ans: Scheduled reviews include Daily login/access logs, Weekly workflow status, Monthly role/privilege changes, and Quarterly user audits — aligned with NEP-2020 and ISO 27001 standards.