Managing IAM Users (part 2)

By Ashwin Venugopal -

 




To read part 1, please click here





Deleting an IAM User

If a user quits then you can delete an IAM user from your your AWS account, but, if the user is away only temporarily, then, you can just deactivate the user's access.

Deleting an IAM User (console)

While doing this, the IAM automatically deletes the following information:
  1. The user.
  2. Any user group memberships, i.e., the user is removed from all the IAM user groups where user was a member.
  3. Any password linked with the user.
  4. Any access keys belonging to the user.
  5. All inline policies embedded in the user (however, policies applied via user group permissions remains unaffected).
  6. Any associated MFA devices.
To Delete an IAM User (console)
  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 and the user name you want to delete, in the navigation pane.
  3. Choose Delete at the top of the page.
  4. After this, you can enter the user name in the text input field to confirm the deletion in the confirmation dialog box and select Delete.

Deleting an IAM User (AWS CLI)

  1. Delete the user's password (if any). [aws iam delete-login-profile]
  2. Delete the user's access keys (if any). [aws iam list-access-keys; aws iam delete-access-key]
  3. Delete the user's signing certificate permanently. [aws iam list-signing certificates; aws iam delete-signing-certificate]
  4. Delete the user's SSH public key (if any). [aws iam list-ssh-pubilc-keys; aws iam delete-ssh-public-key]
  5. Delete the user's Git credentials. [aws iam list-service-specific-credentials; aws iam delete-service-specific-credential]
  6.  Deactivate the user's MFA device (if any). [aws iam list-mfa-devices; aws iam deactivate-mfa-device; aws iam delete-virtual-mfa-device]
  7. Delete the user's inline policies. [aws iam list-user-policies; aws iam delete-user-policy]
  8. Detach any managed policies attached with the user. [aws iam list-attached-user-policies; aws iam detach-user-policy]
  9. Remove the user from any user groups. [aws iam list-groups-for-user; aws iam delete-user-from-group] 
  10. Delete the user. [aws iam delete-user]

Deactivating an IAM User

You can easily deactivate an IAM user while they are away temporarily while keeping their credentials in place and still blocking their AWS access. In order to do that, you can simply create as well as attach a policy denying the user's access to AWS and then restore it later. 










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 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