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

By Ashwin Venugopal -

 



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





Configure RBAC

List Roles

You can list the roles in the portal by following the steps given below:
  1. In the Azure portal, choose All services and then Subscriptions.
  2. Choose your subscription.
  3. Choose Access Control (IAM).
  4. Choose Roles to view a list of all the built-in and custom roles where the number of users and groups that are assigned to each role can be seen. 

List Access

The following steps will help you to list the access for users as well as at different scopes:
  1. Choose Azure AD in the navigation list.
  2. Choose Users to open All users.
  3. Choose an individual user in the list. 
  4. In the Manage section, select Azure resources.
The role assignments for the selected user and selected subscription can be viewed on the Azure resource blade but if you have multiple subscriptions, you can select the Subscription drop-down list to view the role assignments in a different subscription.

List Role Assignment for a Resource Group

  1. Select Resource groups in the navigation list. 
  2. Select a resource group and then choose Access control (IAM).

The Access control (IAM) blade is also known as identity and access management where you can view who has access to this resource group which is either assigned specifically to the resource group or inherited from an assignment to the parent subscription. 

Grant Access

You can grant access at different scopes by following the given steps:

Assign a role at a resource group scope

  1. Select Resource groups in the navigation list.
  2. Choose a resource group.
  3. Select Access control (IAM) to view the current list of role assignments at the resource group scope.
  4. Select Add to open the Add permissions pane, but you won't see this option if you don't have permissions to assign roles.
  5. Select a role like VM Contributor in the Role drop-down list.
  6. In the Select list, select a user, group, or application but if there is no security principal in the list, then, you type in the Select box to search the directory for display names, email addresses, and object identifiers.
  7. Choose Save to assign the role.   

Assign a role at a subscription scope

  1. Select All services and then Subscription in the Azure portal.
  2. Choose your subscription.
  3. Select Access control (IAM) to view the current list of role assignments at the subscription scope.
  4. Select Add to open the Add permissions pane, but you won't see this option if you don't have permissions to assign roles. 
  5. Select a role like VM Contributor in the Role drop-down list.
  6. In the Select list, select a user, group, or application but if there is no security principal in the list, then, you type in the Select box to search the directory for display names, email addresses, and object identifiers.
  7. Choose Save to assign the role.   

Assign a role at a management group scope

  1. Select All services and then Management groups in the Azure portal.
  2. Choose your subscription.
  3. Select (details) for your chosen management group.
  4. Select Access control (IAM) to view the current list of role assignments at the subscription scope.
  5. Select Add to open the Add permissions pane, but you won't see this option if you don't have permissions to assign roles. 
  6. Select a role like Management Group Contributor in the Role drop-down list.
  7. In the Select list, select a user, group, or application but if there is no security principal in the list, then, you type in the Select box to search the directory for display names, email addresses, and object identifiers.
  8. Choose Save to assign the role.   

Remove Access

You can remove an access with the help of following steps:

  1. Open the Access control (IAM) blade for the management group, subscription, resource group, or resource that contains the role assignment you want to remove.
  2. Now, add a checkmark next to the security principal with the role assignment you want to remove in the list of role assignments.
  3.  Choose Remove.
  4. In the remove role assignment message that appears, select Yes.

As the inherited role assignments can't be removed, you have to do it at the scope containing the created role assignment that consists of a link which can take you to the scope where this role was assigned. You can easily remove the role assignment by simply going to the listed scope.







To read part 1, please click here
To read part 2, 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