Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Identity Hub
    • All guides
    • Subscribing a user to notifications
      • Creating an MFA policy
      • Applying an MFA policy to users
      • Updating an MFA policy
      • Activating or deactivating an MFA policy
      • Deleting an MFA policy
      • Removing an MFA factor and resetting the verification date
    • Syncing users and groups with Active Directory
    • Billing management in Identity Hub
  • Access management
  • Pricing policy
  • Terraform reference
  • Audit Trails events
  • Release notes
  1. Step-by-step guides
  2. Managing MFA
  3. Creating an MFA policy

Creating an MFA policy

Written by
Yandex Cloud
Updated at November 29, 2025

Note

This feature is at the Preview stage.

MFA policies enable configuring multi-factor authentication (MFA) for federated and local user accounts.

To create an MFA policy:

Cloud Center UI
CLI
  1. Log in to Yandex Identity Hub.

  2. In the left-hand panel, select Security settings.

  3. Navigate to the MFA policies tab.

  4. In the top-right corner, click Create policy and in the window that opens:

    1. In the Name field, enter a name for the new policy. Follow these naming requirements:

      • It must be from 1 to 63 characters long.
      • It may contain lowercase Latin letters, numbers, and hyphens.
      • It must start with a letter and cannot end with a hyphen.
    2. Optionally, enter a policy description in the Description field.

    3. If you do not want to activate the policy upon creation, disable Policy active.

    4. In the Factor types field, select additional authentication factors required for users from the policy's target groups to verify their identity:

      • Any. This option allows users to select one of the following additional authentication factor standards:

        • WebAuthn (FIDO2). The acceptable additional authentication factors may include hardware keys such as Rutoken or YubiKey, Passkeys authenticators, platform authenticators such as Windows Hello, etc.

          Warning

          Browser extensions with password input control may cause errors when entering additional factors. We recommend disabling such extensions in case of errors.

        • TOTP. This standard enables using one-time codes generated by dedicated authenticator apps as an additional authentication factor.

      • Phishing-resistant. This option enforces the WebAuthn authentication factors as the most secure ones.

    5. In the Creation deadline field, specify the period in days during which the user must add a second authentication factor after registration.

    6. In the Lifetime field, set the credential validity period, in days.

      Upon expiry of the specified timeout, the user will need to authenticate with the additional factor again.

    7. Click Create policy.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

  1. See the description of the CLI command for creating an MFA policy:

    yc organization-manager mfa-enforcement create --help
    
  2. Create an MFA policy by running the command:

    yc organization-manager mfa-enforcement create \
      --organization-id <organization_ID> \
      --acr-id <authentication_factor_type> \
      --ttl <lifetime> \
      --status <policy_status> \
      --apply-at <activation_time> \
      --enroll-window <creation_deadline> \
      --name <policy_name> \
      --description <policy_description>
    

    Where:

    • --name: Policy name. Follow these naming requirements:

      • It must be from 1 to 63 characters long.
      • It may contain lowercase Latin letters, numbers, and hyphens.
      • It must start with a letter and cannot end with a hyphen.
    • --organization-id: Organization ID.

    • --acr-id: Authentication factor type.

    • --ttl: Credential validity period in days.

    • --status: Policy status, active (status-active) or inactive (status-inactive).

    • --apply-at: Time after which the policy will become active. This is an optional parameter.

    • --enroll-window: Period in days after registration during which the user must add a second authentication factor.

    • --description: Policy description. This is an optional parameter.

  3. Optionally, run the following command to activate an inactive MFA policy:

    yc organization-manager mfa-enforcement activate \
      --id <policy_ID>
    

Note

For an MFA policy to apply to specific user accounts, add the users in question or the groups they are members of to the policy's target groups.

See alsoSee also

  • Updating an MFA policy
  • Applying an MFA policy to users
  • Activating or deactivating an MFA policy
  • Deleting an MFA policy
  • Removing an MFA factor and resetting the verification date
  • Multi-factor authentication in Identity Hub

Was the article helpful?

Previous
Deactivating and deleting an app
Next
Applying an MFA policy to users
© 2025 Direct Cursus Technology L.L.C.