What If an MFA Device is Lost or Stops Working?

By Ashwin Venugopal -

 







Recovering a Root User MFA Device

If you have lost, damage, or unresponsive MFA device for AWS account root user, then, you can sign-in via alternative methods of authentication by verifying your identity with the help of the email and the primary contact number registered with your account.

To Sign-in Using Alternative Factors of Authentication As An AWS Account Root User

  • Firstly, sign-in to the AWS Management Console as the account owner by choosing Root user, and entering your AWS account email address as well as password on the next case.

  • Now, select Having problems with your authentication device? Click here; on the Amazon Web Services Sign-in With Authentication Device page.

  • You can also type your password again and Sign-in, if required.

  • After that, you have to select Sign-in using alternative factors in the section with same name.

  • Click on Send Verification email if you want to authenticate your account via email address.

  • You have to check the email linked with your AWS account for a message from Amazon Web Services and follow its directions. However, if you don't see it, then either check your spam folder or choose Resend the email.

  • After successfully verifying the above, you can also verify your phone number by choosing Call me now.

  • Answer the AWS' call and enter the 6-digit number from the AWS website on your phone keypad, if prompted.

  • After verifying everything, you can sign-in to your account by picking Sign-in to the console.

  • Now, for this one, you have to continue according to the type of MFA being used:

  1. For a virtual MFA device, you have to remove the account from your device and delete the old virtual device entity before creating a new one.
  2. In a FIDO security key, you have to deactivate the old FIDO security key before activating a new one on the AWS Security Credentials page.
  3. For a Hardware MFA device, you have to take help of the third party provider to fix or replace the device.
  • However, you must also change your AWS password if your MFA device is lost or missing, so that an attacker cannot use it for the other malicious purposes.

Recovering an IAM User MFA Device

For this one, you have to contact an administrator to deactivate the device (as you cannot recover it by yourself), so that you can enable a new one.

To Get Help for an MFA Device as an IAM User

  • Firstly, contact your AWS administrator or other person who gave you the username and password, to deactivate the MFA device, so that you can sign-in.

  • Next, you can continue further according to the type of MFA device in use:

  1. Virtual MFA device allows you to remove the account from your device.
  2. The FIDO security key one allows you to contact the third party provider for help in  replacing the device.
  3. Similarly, the Hardware one also allows you to contact the third party provider for fixing or replacing the device.

  • You should also change your AWS password if your MFA device is lost or missing, so that an attacker cannot use it for the other malicious purposes.










































































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