Using MFA devices with your IAM sign-in page

By Ashwin Venugopal -

 







Signing-in with Multiple MFA Devices Enabled

If this situation happens, then, the user only requires to use one MFA device to sign-in and after authenticating the user's password, they can select the type of MFA device they would like to use to finish it. After that, the user is prompted to authenticate with the type of device that they selected.

Signing-in with a FIDO Security Key

If MFA is used by the users, they have to tap the FIDO security key on the second sign-in page. However, the Google Chrome users doesn't require to choose any of the available options, they have to just tap on the security key and if the FIDO security key is broken or lost, then, the administrators can easily deactivate it.

Signing-in with a Virtual MFA Device

If MFA is used by the users, they have to enter the numeric code provided by the MFA application, in the MFA code box, on the second sign-in page. As the virtual MFA device may go out of sync, the user can be urged to synchronize it if they can't sign-in to the AWS Management Console even after several tries. The on-screen prompts will help the user in synchronizing the virtual MFA device.

Signing-in with a Hardware TOTP Token

If MFA is used by the users, they have to enter the numeric code provided by a hardware TOTP token, in the MFA code box, on the second sign-in page. As the hardware TOTP token may go out of sync, the user can be urged to synchronize it if they can't sign-in to the AWS Management Console even after several tries. The on-screen prompts will help the user in synchronizing the MFA token device .





























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