Getting Started With IAM

By Ashwin Venugopal -

 





Creating Your First IAM Admin User & User Group

As we all know, we must not use the AWS account root user when it's not necessary, instead a new IAM user should be created for everyone who needs an administrator access.  After that these users will be made Administrators by simple putting them into an "Administrators" user group attached with an AdministratorAccess policy. 

Now these users can set up the user groups, users, etc. for the AWS account to help with all the future interactions via their own keys not via root user. However, you will still require to login via root user credentials for certain accounts and service management tasks.

Creating an Administrator IAM User & User Group (Console)

In order to do so, you will have to follow these steps:

  • Sign in to the IAM console via root user and insert your AWS account email address and password.
  • Now, enable access to the billing data for the IAM admin user that can be created as follows:

  1. Select you account name and account on the navigation bar.
  2. Choose Edit present next to the IAM User and Role Access to Billing Information. However, you must be signed in as the root user for this one to appear on screen.
  3. After that you can Activate IAM Access and select Update.
  4. Now, you can choose Services and then IAM under Security, Identity, & Compliance to go back to the IAM console on the navigation bar. 

  • Choose users and Add users on the navigation pane.
  • Perform the following tasks on the Details page:

  1. Type Administrator for User name.
  2. Choose AWS Management Console Access, Custom Password, and then type your new password in the text box.
  3. As by default, AWS insists the new user to create a new password for first sign in, you can also choose to clear the check box next to User must create a new password at next sign-in to permit the new user to reset their password after signing in.
  4. Choose Next:Permissions.

  • Perform the following tasks on the Permissions page:
  1. Select Add User to Group.
  2. Choose Create Group.
  3. Now type Administrators in the Create Group dialog box for the Group name.
  4. Select the AdministratorAccess policy.
  5. Choose Create Group.
  6. Select your new user group on the page having a list of user groups.
  7. Select Next:Tags.

  • Now add metadata to the user by attaching tags as key-value pairs. (optional)
  • Select Next:Review, verify the User Group Memberships, and then choose Create User.
  • You can also download a .csv file on the Complete Page, along with the login information for the user or send email having login instruction to the user.

This same process can also be used to create more user groups in order to give the users access to your AWS account resources.

Creating an IAM User & User Group (AWS CLI)

Performing the following tasks will help you in achieving the goal:
  • Create a user group and give it a name (like Admins).
  • Now attach a policy that can offer user group administrative permissions like access to all the AWS actions and resources.
  • Finally, add at least one user to the user group.

























































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