Changing Permissions for an IAM User (part 2)

By Ashwin Venugopal -

 







To read part 1, please click here




Changing Permissions for a User (console)

The following methods will help you in achieving the said goal-

Editing a permissions policy attached to a user 

  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. Select the user name whose permissions policy you want to modify.
  4. Now you can click the Permissions tab, and open the Permissions policies section if necessary.
  5. Select the policy name required to be edited to see all the details about the policy and then Used as tab to have a look at the other entities that might be affected after the change.
  6. After that, you can choose the Permissions tab to review the permissions granted by the policy and the Edit policy.
  7. Edit the policy via the Visual editor tab or the JSON tab and resolve any policy validation recommendations.
  8. Lastly, you have to choose Review policy, to review the policy summary, and then Save changes.
Changing the permissions boundary for a user
  1. As done before, you have to 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. Select the user name whose permissions boundary you have to change.
  4. Now you can click the Permissions tab. Open the Permissions boundary section (if necessary), and then Change boundary.
  5. Select the policy required to be used for the permissions boundary.
  6. Choose Change boundary.

Removing Permissions Policy from a User (console)

  1. 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. Select the user name whose permissions boundary you want to remove.
  4. Now you can click the Permissions tab.
  5. If the permissions are revoked by removing an existing policy, then, you have view the Policy type to understand better before actually choosing X to remove the policy.
  • However, if the policy applies via a group membership, then, selecting X will also remove the user from the group along with the access to all the policies received from that particular group membership.
  • Whereas, if it's a managed policy directly attached to the user, then, choosing X will simply detach the policy from the user without affecting the policy or any other entity attached to the policy.
  • But, if it's an inline embedded policy, then, choosing X will remove from IAM as these policies are exist only on that user. 

Removing Permissions Boundary from a User (console)

  1. 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. Select the user name whose permissions boundary you want to remove.
  4. Now you can click the Permissions tab. You can also open the Permissions boundary section and Remove boundary if necessary. 
  5. Finally, you can choose Remove to confirm the removal of the permissions boundary.

Adding & Removing a User's Permissions (AWS CLI or AWS API)

In order to add or remove permissions programmatically, you have to add or remove group memberships, attach or detach the managed policies, or add or delete the inline polices. 








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