Managing IAM Users (part 1)

By Ashwin Venugopal -

 




To read part 2, please click here 






View User Access

Reviewing a user's recent service-level activity is very important before doing anything to it as it might delete an access from a principal (person or application), who is still using it.

Listing IAM Users

You can easily list the IAM users in your AWS account or in a specific IAM user group, and list all the user groups that a user is in, as described below.

To list all the users in the account

  1. AWS Management Console shows the users in your AWS account and you can choose Users from the navigation pane.
  2. AWS CLI: aws iam list-users.
  3. AWS API: ListUsers.

To list the users in a specific group

  1. You can select the User groups, their name, and the Users tab from the navigation pane of the AWS Management Console.
  2. AWS CLI: aws iam get-group.
  3. AWS API: GetGroup.

To list all the user groups that a user is in

  1. Select the Users, user name, and then, the Groups tab from the navigation pane of the AWS Management Console.
  2. AWS CLI: aws iam list-groups-for-user.
  3. AWS API: ListGroupsForUser.

Renaming an IAM User

As the console doesn't have an option for renaming or change a user's name or path, you must use the AWS CLI, Tools for Windows PowerShell, or AWS API and this change leads to the following things:
  1.  All the policies attached to the user stay with the user under the new name.
  2. The user stays in the same user groups under the new name.
  3.  The unique ID for the user remains the same. 
  4. All the resources or role policies that refers to the user as a principal will be automatically updated to use the new name or path. However, this doesn't happen when the user is referred as a resource, it should be done manually.

To rename a user

  1. AWS CLI: aws iam update-user.
  2. AWS API: UpdateUser.









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