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

By Ashwin Venugopal -

 





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










Azure RBAC Roles & Azure AD Administrator Roles

How the roles are related?

Before, access to the resources are managed with the help of only three administrator roles namely- Account Administrator, Service Administrator, and Co-Administrator but later on RBAC was added. Hence, Azure RBAC is the latest authorization system providing fine-grained access management to Azure resources including various built-in roles, can be assigned at different scopes, and help you to create your own custom rules. Several Azure AD administrator roles are available to help you manage the resources in Azure AD like users, groups, and domains.

There are following types of roles:

  • Classic Subscription Administrator Roles- As stated above, there are three types of classic subscription administrator roles in Azure, they are- Account Administrator, Service Administrator, and Co-Administrator. They have full access to the Azure subscription and can manage resources with the help of Azure portal, Azure Resource Manager APIs as well as the classic deployment model APIs. After automatically setting up the signed up account used for Azure as both the Account and Service Administrator, extra Co-Administrators can be added (both the administrators have equal access of the users who have assigned the Owner role i.e. an Azure RBAC role at the subscription scope).

  • Azure RBAC Roles- It's an authorization system built on Azure Resource Manager that offers fine-grained access management to Azure resources, like compute and storage. There are over 70 built-in roles in which following are the fundamental RBAC roles- 

  1. Owner has full access to all resources and delegates access to others.
  2. Contributor can create as well as manage all types of Azure resources but can't grant access to others.
  3. Reader can view Azure resources.
  4. User Access Administrator can manage user access to Azure resources. 

      The other built-in roles helps in the management of specific Azure resources. 

  • Azure AD Administrator Roles- They are used to manage Azure AD resources in a directory like creating or editing users, assigning administrative roles to others, resetting user passwords, managing user licenses, and managing user domains. Few Azure AD administrator roles are:

  1. Global Administrator manages access to all administrative features in Azure AD as well as services and can reset the password for any user.
  2. User Administrator creates as well as manages all aspects of users and group.
  3. Billing Administrator can make purchases and manage subscription.    












To read part 1, 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