Role Based Access Control (RBAC) (part 1 of 3)

By Ashwin Venugopal -

 



To read part 2, please click here
To read part 3, please click here 









Plan for RBAC

Role Based Access Control (RBAC) manages users access to Azure resources, what they can do with those resources, and what areas they have access to. It is an authorization system built on Azure Resource Manager that offers fine-grained access management of resources in Azure.

What can I do with RBAC?

The following examples will help you to understand this:
  • Allow one user to manage virtual machines in a subscription and another to manage virtual networks.
  • Allow a DBA group to manage SQL databases in a subscription.
  • Allow a user to manage all the resources in a resource group, like VMs, websites, and subnets.
  • Allow an application to access all resources in a resource group.  

How RBAC works?

You can easily control access to the resources by creating role assignments using RBAC to enforce permissions. Role assignment contains three elements- security principal, role definition, and scope.

Security Principal

It is an object representing a user, group, or service principal that requests access to Azure resources. 
  1. User- It's an individual having a profile in Azure AD and various roles can also be assigned to the users in the other tenants.  
  2. Group- It's a set of users created in Azure AD and if a role is assigned to a group, then, all the users within that group will have that role. 
  3. Service principal- It's a security identity used by applications or services to access specific Azure resources and it may also be considered as a user identity (username and password or certificate) for an application. 

Role Definition

It's a collection of permissions and sometimes called just role. Role definition consists of the operations that can be performed like read, write, and delete. Roles can be either high-level like owner or specific like VM reader. Azure contains following built-in roles and the first three applies to all resource types:

  1. Owner Has full access to all resources including the right to delegate access to others. 
  2. Contributor Can create and manage all types of Azure resources but can't grant access to others.
  3. Reader Can view existing Azure resources.
  4. User Access Administrator Allow you to manage user access to Azure resources.

The other built-in roles helps you to manage specific Azure resources and if they doesn't meet the specific need of your organization, you can create your own custom roles. 

Scope

It's the boundary applied to the access i.e. you can limit the actions allowed by defining a scope while assigning a role which can be helpful to make someone a Website Contributor, but only for one resource group. Scope can be specified at multiple levels- management groups, subscription, resource group, or resource and are structured in a parent-child relationship. When you grant access at a parent scope, those permissions are inherited to the child scopes, for example:

  1. If you assign the Owner role to a user at the management group scope, that user can manage everything in all subscriptions in the management group. 
  2. If you assign the Reader role to a group at the subscription scope, the members of that group can view every resource group and resource in the subscription. 
  3. If you assign the Contributor role to an application at the resource group scope, it can manage resources of all types in that resource group, but not other resource groups in the subscription.  

How RBAC determines if a user has access to a resource?

The following high-level steps used by RBAC tells you about your access to a resource on the management plane:
  1. A user (or service principal) acquires a token for Azure Resource Manager which includes user's group memberships (including transitive group memberships).
  2. The users makes a REST API call to Azure Resource Manager with the token attached.
  3. Azure Resource Manager retrieves all the role assignments and deny assignments that apply to the resource upon which the action is being taken. 
  4. Azure Resource Manager narrows the role assignments that apply to this user or their group and determines what roles the user has for this resource. 
  5. Azure Resource Manager determines if the action in the API call is included in the roles the user has for this resource.
  6. If the user doesn't have a role with the action at the requested scope, access is not granted. Otherwise, Azure Resource Manager checks if a deny assignment applies. 
  7. If a deny assignment applies, access is blocked. Otherwise access is granted.  









To read part 2, please click here
To read part 3, please click here 



Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more