Overview of access management: Permissions and policies

By Ashwin Venugopal -

 







Policies & Accounts

If a single account is managed in AWS, then, the permissions can be easily defined via policies, whereas, it's very difficult to manage permissions for multiple accounts and might require IAM roles, resource-based policies, or Access Control Lists (ACLs) to manage the cross-account permissions. However, it's recommended to allow the use of AWS organizations service to manage the multiple accounts' permissions. 

Policies & Users

IAM users are actually the identities in the service and once created, they can't access anything until they are given permissions to do that via a created identity-based policy attached with the user or a group to which the user belongs. Hence, the actions or resources that are not permitted are denied by default.

Policies & Groups

Another way is to organize the IAM users into IAM groups and then attach a policy to it, which will allow the individual users to have their own credentials as well as all the permissions attached to that group. You can also attach multiple policies with different permissions to a group that can calculated according to the combination of policies. However, the initial rule of granting permissions for an action stays same.

Federated Users & Roles

As federated users doesn't have the benefits of permanent identities like an IAM user, an entity should be created to assign permissions to them which can be termed as role and capable of defining the permissions for that role. Hence, a federated user is linked with the role and will get the permissions that are defined to the role.

Identity-based & Resource-based Policies

As the name suggests, identity-based polices are the permission policies attached to an IAM identity, like, an IAM user, group, or role, and controls the actions, resources, and conditions in which the identity can perform  whereas, the resource-based policies are the permission policies attached to a resource, like, an Amazon S3 bucket or an IAM trust policy, and controls a specified principal's actions that can be performed on a particular resource under certain conditions. 

However, the IAM services supports only role trust policy which is a type of resource-based policy attached to an IAM role, hence, identity-based policy and trust policy both should be attached to an IAM role (it's both the identity & resource that supports resource-based policies). 













































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