Creating an IAM user in your AWS account (part 1)

By Ashwin Venugopal -

 




To read part 2, please click here




Creating IAM Users (Console)

If you want to create on or more IAM users (console), then, you have to-
  • Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.

  • Select Users and Add users in the navigation pane.

  • Now you can type the user name for the new user (i.e. sign in name for AWS) and you can also add up to 10 users at a time by choosing Add another user for each additional user.

  • After that you can pick any of the following types of accesses for the set of users:

  1. Programmatic Access helps the users to get access to the API, AWS CLI, or Tools for Windows PowerShell creating access keys for each one them that can also viewed or downloaded at the Final page.
  2. AWS Management Console Access enable the users to acquires access to the AWS Management Console creating a password for each user. 

  • Now you can choose Next: Permissions.

  • Next, the Set permissions page will allow you to specify permissions for the new users with the help of following options: 

  1. Add user to group helps you to assign the users to one or more groups already having permission policies.
  2. Copy permissions from existing users enable you to copy all the group memberships, attached managed policies, embedded inline policies, and any existing permissions boundaries from an existing user to the new ones.
  3. Attach existing policies directly will show you a list of the AWS managed and customer managed policies in your account.  

  • Now, you can set a permission boundary, which is an advanced feature and optional too.

  • Choose Next: Tags.

  • You can also add metadata to the user by attaching tags with key-value pairs. (optional)

  • If you want to view all the choices made till now, you can select Next: Review and then Create user.

  • Choose Show next to each of the user's password and access keys if you want to see them and Download.csv in order to save them to a safe location.

  • Now each user can be provided with his or her user credentials. Send email can be chosen on the final page and the template includes details of the user name and URL to the account sign-in page for each user.






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