Enable a Virtual MFA Device for an IAM User (Console)

By Ashwin Venugopal -

 







To Enable a Virtual MFA Device for an IAM User (Console)

  1. Firstly, just like the others, you have to sign-in to the AWS Management Console and open the IAM console at https:// console.aws.amazon.com/iam/.
  2. Then, choose Users in the navigation pane.
  3. You have to select a username for the intended MFA user in the User Name list.
  4. Select the Security Credentials tab and then Manage next to the Assigned MFA Device. 
  5. Choose Virtual MFA Device and then Continue, in the Manage MFA Device Wizard.
  6. Now open your virtual MFA app. 
  7. Determine whether the MFA app supports QR codes or not and then perform the following actions-

  • Choose Show QR code from the wizard, and then use the app to scan it.
  • Now, choose Show Secret key in the Manage MFA Device wizard, and the type it into your MFA app.

     8.  Now, inside the MFA Code 1 box in the Manage MFA Device wizard, type the OTP occurred in              the virtual MFA device. After that you can type the second OTP (after waiting for at least 30                     seconds) in the MFA Code 2 box. Now, choose Assign MFA.

To Configure & Enable a Virtual MFA Device for Use with your Root User (Console)

  1. Sign-in to the AWS Management Console.
  2. Now, choose your account name and My Security Credentials on the right side of the navigation bar. You can also choose Continue to Security Credentials (if required) and then expand the MFA section of the page.
  3. Choose Activate MFA.
  4. After that, you can select Virtual MFA device, and then Continue in the wizard.
  5. Open the virtual MFA app in the device.
  6. It's way more easier to configure the app by using it to scan the QR code. However, if it doesn't work, you can always manually type the configuration information. 
  7. Enter the first six-digit number displayed by the MFA device of the Manage MFA Device wizard in the MFA Code1 box. The next number can be entered in the MFA Code 2 box after waiting for at least 30 seconds.
  8. Now, you can select Assign MFA, and then Finish.



















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