Identity & Access Management (IAM)

By Ashwin Venugopal -

 








What's IAM?

It is a kind of web service that can help you in accessing AWS resources securely by controlling the overall authentication and authorization. When creating an AWS account, a one sign-in account called root user (having total access over all the AWS services and resources available in the account) is accessed via the email address as well as the password used while creating the account. However, it is strongly recommended to use the root user credentials for the tasks that can only be performed by it. 

IAM Features

Some of the important features are as follows:
  • Shared Access to Your AWS Account- Other people can also be given the permission to administer as well as use resources available in an AWS account without sharing any information regarding the access key or password.

  • Granular Permissions- Different permissions can be granted to different people for different resources.

  • Secure Access to AWS Resources for Applications that Run on Amazon C2- IAM features can also help in securing the credentials that run on EC2 instances as they can grant permissions for accessing the other AWS resources to your applications. 

  • Multi-Factor Authentication (MFA)- MFA can also be applied to your account to your account as well as the individual users for additional security as it will always demand a password, access key, or a code from a specially configured device, to further work with an account.

  • Identity Federation- The users having passwords elsewhere can also be allowed temporary access to an AWS account.

  • Identity Information for Assurance- While using AWS CloudTrail, the log records containing the information regarding requests for an AWS account resources are provided which is based on IAM identities. 

  • PCI DSS Compliance- IAM readily supports the processing, storage as well as transmission of the credit card data by a merchant or service provider, and also has been validated as being compliant with Payment Card Industry (PCI) Data Security Standard (DSS).

  • Integrated with Many AWS Services- There is a whole list of services that can easily work with IAM.

  • Eventually Consistent- As the name suggests, IAM is eventually consistent as it can achieve high availability by replicating data across multiple servers within Amazon's data centers around the world and if a request for changing a small amount of data is successful, that change is committed and safely stored; including the change should be replicated across IAM along with the creating or updating all the users, groups, or policies. However, it is not recommended to introduce such IAM changes in the critical, high-availability code paths of an application, rather, it should be done in a separate setup routine that runs less frequently.

  • Free to Use- The features of an AWS account like AWS Identity and Access Management (IAM) as well as AWS Security Token Service (AWS STS) are offered at no additional charges, and one can only be charged if they access the other AWS services via IAM users or AWS STS temporary security credentials.    





































































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