Security is more easily maintained when limiting unnecessary access rather than managing permissions for individual accounts or users. Managing and auditing network access is an essential security aspect which ensures that the right users have access to the right infrastructure components. Role-Based Access Control (RBAC) can control what users can do or cannot do on a granular level. Access is granted on a need to know basis.
With Role-Based Access Control, you can designate roles for users at various levels such as administrator, the specialist user or end-user and align these roles with the permission that the end-users at every level will require. It reduces IT and administrative load as personalized user permissions need not be set for every user and each user automatically gets access to the right data. Managing new users is also easy as the access levels are pre-defined – even before they join the network. Access restriction to certain applications and processes enables cost-effective use of resources such as network bandwidth, memory and storage.
RBAC on apiculus SP administration Console
apiculus Service Provider administration console now supports Role-Based Access Control. With this integration, SP teams can be onboarded with restricted administrative access to their specific resources or areas of work. Being highly flexible, RBAC can be configured differently for each service provider and actions can be specified for the users within an organization.
SP-RBAC currently supports the following features:
- Role-based access maps.
- Single-role association of admin users with any of the available roles.
- Partial and/or complete restriction on availability, viewing and editing capabilities.
What roles can be configured using RBAC on the apiculus administration console?
apiculus can be configured for the following roles:
- Accounts Manager
- Finance Manager
- Marketing Manager
- Product Manager
- Service Manager
Implementing RBAC requires a great deal of consideration. A user should not be assigned privileges beyond their role or expertise. So, it’s essential to analyze your Cloud Infrastructure and determine which resources need to be under access control and understand what types of users would require access to these different categories of resources. Evaluate how the access implementation impacts when user accounts are removed. Further, once implemented, it’s imperative to run periodic audits to understand if a role is found to have unnecessary access to certain systems. This enables SPs to also meet the regulatory and statutory requirements for data confidentiality and privacy.
For more information and consulting on how to set up Role-based Access Control on Apiculus SP Administration Console, contact us.
Comments are closed.