Using Multi-Factor Authentication (MFA) AWS

By Ashwin Venugopal -

 









What's MFA?

It's a tool to add extra security by providing unique authentication system via an AWS supported MFA mechanism along with their regular sign-in credentials for accessing AWS websites or services. They are as follows:
  • Virtual MFA Devices- It's a software app that runs on mobiles or other devices, and can generate a six-digit numeric code according to a time-synchronized one-time password algorithm. 

  • FIDO Security Key- It's a device that can be plugged-in to a computer's USB port. The enabled FIDO2 security key allows you to sign-in via your security credentials and then simply tapping it not manually entering the code.

  • Hardware MFA Device- Similar to the virtual MFA devices, this one also generates a six-digit numeric code according to a time synchronized one-time password algorithm. Each MFA device assigned to a user should be unique.

NOTE- SMS text message-based MFA- The support to enable an SMS MFA has ended by AWS and it's recommended that customers with users having this type of MFA , should switch to any of the above discussed ones.

Enabling MFA Devices for Users in AWS

The type of MFA device being used, decides the method of their configuration.

General Steps for Enabling MFA Devices

  • Select any one of the MFA devices- a virtual MFA device, a FIDO security key, or a hardware-based MFA device- and you will be allowed to enable only one per AWS account root user or IAM user.

  • Now, IAM users with virtual or hardware MFA devices can enable them either from AWS Management Console, CLI, or the IAM API; while those with FIDO security keys can enable them via AWS Management Console only. However, AWS account root users with any type of MFA device can also enable them via AWS Management Console only.

  • After the above steps, you can easily use the MFA device to log-in to or access AWS resources.

However, in order to access the MFA-protected API operations, the following are required:
  1. An MFA code.
  2. The identifier for the MFA device.
  3. The usual access key ID and the secret access key.
Enabling a Virtual MFA Device (Console)

A phone or any other device can be used as a virtual MFA device having a mobile app compliant with RFC 6238, a standards-based TOTP algorithm. A six-digit authentication code will be generated as they generally run on unsecured mobile devices. Hence, it's highly recommended to use a virtual MFA device while waiting for a hardware purchase approval or hardware to arrive. Although, most of them supports the use of multiple virtual devices allowing you to use the same app for various AWS accounts or users, only one MFA device per user can be enabled.









































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