Changing permissions for an IAM user (part 1)

By Ashwin Venugopal -

 





To read part 2, please click here






View User Access

If you want to change the permissions for a user, you must review its recent service-level activity before doing anything as it will prevent you to delete access from a principal (person or application) who is still using it.

Generate a Policy based on a User's Access Activity

An IAM policy can be easily generated according to access activity of an entity to refine your granted permissions. A policy template is generated containing all the permissions used by the entity in your specified data range (based on the IAM Access Analyzer reviews on your AWS CloudTrail logs), that can be used to create a managed policy with fine-grained permissions and attach it to an IAM entity. This allows you to only permit the AWS resources that the user or role needs to interact with for a particular use case.

Adding Permissions to a User (console)

The following ways can help in adding permission policies to a user, but, if the user already has a permission boundary, then, more permissions cannot be added beyond the specified limit.

Adding permissions by adding user to a group

  1. First of all, sign-in to the AWS Management Console and open the IAM console at https:// console.aws.amazon.com/iam/.
  2. Now select Users in the navigation pane.
  3. Review the current group memberships of the users in the Group column of the console and add the column to the users table if necessary.
  4. Select the user name whose permissions you want to modify.
  5. Now you can click the Permissions tab, Add permissions, and then Add user to the group.
  6. Select all the groups that you want the user to join through a list containing each group's name and policies that will be offered to the user if they join.
  7. You can also select Create group if you want to define a new group. (optional)
  8. Now you can select Next: Review to view the list of group memberships to be added to the user and then Add permissions.
  Adding permissions by copying from another user
  1. As stated above, you have to sign-in to the AWS Management Console firstly, and then open the IAM console at https:// console.aws.amazon.com/iam/.
  2. Now select Users, user name whose permissions are to be modified, and Permissions tab in the navigation pane.
  3. Now you can Add permissions, and then Copy permissions from existing user.
  4. Select the button next to the user whose permissions you want to copy.
  5. Now you can select Next: Review to view the list of changes done to the user and then Add permissions.
Adding permissions by attaching policies directly to the user
  1. Firstly, you have to sign-in to the AWS Management Console, and then open the IAM console at https:// console.aws.amazon.com/iam/.
  2. Now select Users, user name whose permissions are to be modified, and Permissions tab in the navigation pane.
  3. Now you can Add permissions, and then Attach existing policies directly to the user.
  4. Select one or more managed policies that you want to attach to the user. A new managed policy can also be created via Create policy.
  5. Now you can select Next: Review to view the list of policies attaching to the user and then Add permissions.

Setting Permissions boundary for a user

  1. Sign-in to the AWS Management Console, and then open the IAM console at https:// console.aws.amazon.com/iam/.
  2. Now select Users in the navigation pane.
  3. Choose the user name whose permissions boundary is to be changed.
  4. Now you can select the Permissions tab and open permissions boundary section to Set boundary (if required).
  5. Select the policy that will be used for the permissions boundary.
  6. Now you can select Set boundary.






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...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
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...
Read more