Google Cloud 는 고객에게 가장 강력한 보안을 제공하기 위해 노력하고 있습니다. Google Cloud에서는 계정 및 민감한 정보를 안전하게 유지하기 위해 사용자의 ID를 보호하는 데 주력하고 있습니다. 이 약속을 지키기 위해 Google에서는 모든 Google Cloud 고객이 계정에 다중 인증(MFA)을 사용 설정해야 한다는 요구사항을 단계적으로 적용하고 있습니다.
2단계 인증(2SV)이라고도 하는 MFA는 중요한 보안 조치입니다. 비밀번호 외에도 MFA를 사용하려면 계정에 로그인하는 데 인증 요소라고 하는 또 다른 신원 증빙 자료가 필요합니다.
추가 인증을 요구하면 해커가 계정을 도용하기가 훨씬 더 어려워집니다. 비밀번호를 도난당하더라도 해커가 계정에 액세스할 수 있으려면 여전히 추가 인증이 필요합니다.
Google 계정을 사용하고 있으며 이미 MFA를 사용 설정한 경우에는 추가 조치를 취하지 않아도 됩니다. Google 계정 설정 페이지의 보안 탭을 열어 계정에 MFA가 사용 설정되어 있는지 확인할 수 있습니다. 2단계 인증 설정은 Google에 로그인하는 방법 섹션에 표시됩니다.
서드 파티 ID 공급업체(IdP)를 사용하여 Google Cloud에 대한 싱글 사인온(SSO)을 관리하는 경우 해당 IdP에서 제공하는 MFA를 사용하여 Google CloudMFA 요구사항을 준수할 수 있습니다.
Google Cloud MFA 시행은 서비스 계정에 영향을 미치지 않습니다. 사용자 계정만 영향을 받습니다. 하지만 Google 계정을 사용하여 서비스 계정을 가장하고 계정에 MFA가 시행된 경우 Google Cloud 콘솔에 로그인하려면 MFA를 사용 설정해야 합니다.
다음 인터페이스 및 서비스에 대한 액세스는Google Cloud MFA 시행의 영향을 받지 않습니다.
Gmail, Google Drive, Google Sheets, Google Slides를 포함한 Google Workspace. 그러나 Google Workspace에는 별도의 MFA 설정 요구사항이 있습니다. 자세한 내용은 Google Workspace 관리자에게 문의하세요.
YouTube.
IAP(Identity-Aware Proxy)로 보호되는 애플리케이션을 포함하여 Google Cloud에서 실행되는 애플리케이션과 워크로드는 MFA 시행에 의한 영향을 받지 않습니다. 하지만 개발자는Google Cloud 콘솔을 사용하여 이러한 애플리케이션을 관리할 수 없습니다. 즉, 컨트롤 플레인은 MFA 시행에 의한 영향을 받지만 데이터 플레인은 영향을 받지 않습니다.
MFA 시행 거부
Google Cloud 에 사용되는 Gmail 계정에서 MFA 요구사항을 거부할 수 없습니다.
MFA를 구현할 수 없는 특정 사용 사례의 경우 회사 계정 및 리셀러 계정에 대한 예외가 적용됩니다. 자세한 내용은 Cloud Customer Care에 문의하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eGoogle Cloud is mandating Multi-Factor Authentication (MFA) for all users to enhance account security, as MFA reduces the likelihood of hacking by 99%.\u003c/p\u003e\n"],["\u003cp\u003eMFA enforcement will require users to have it enabled to access the Google Cloud console, Google Cloud CLI, and Firebase console, but it will not affect other services such as Google Workspace or YouTube.\u003c/p\u003e\n"],["\u003cp\u003eThe timeline for MFA enforcement varies by account type, with personal Google Accounts required to implement it by May 12, 2025, and other enterprise accounts varying after this date.\u003c/p\u003e\n"],["\u003cp\u003eUsers will receive reminders in the Google Cloud console and via email at least 90 days before enforcement, or 60 days for reseller accounts, and various methods are available to set up MFA, including prompts, security keys, and authenticator apps.\u003c/p\u003e\n"],["\u003cp\u003eService accounts and user access to applications running on Google Cloud are not impacted, but if you use your account to impersonate a service account you will be required to use MFA.\u003c/p\u003e\n"]]],[],null,["Google Cloud strives to provide its customers with the strongest security\npossible. We prioritize protecting your identity, to help keep your account and\nsensitive information safe. To help keep this commitment, Google is phasing in\nthe requirement that all Google Cloud customers enable\n*multi-factor authentication* (MFA) for their accounts.\n\nMFA, also known as *2-step verification* (2SV), is an important security\nmeasure. In addition to your password, MFA requires another proof of identity,\nknown as an *authentication factor*, to successfully sign in to an account.\nRequiring an additional factor makes it much harder for your account to be\ncompromised by hackers. Even if your password is stolen, hackers still need an\nadditional factor to be able to access your account.\n\nIf you're using a Google Account and have already [enabled MFA](#enable-google),\nyou don't need to take further action. You can check whether MFA is enabled for\nyour account by opening the **Security** tab of your\n[Google Account settings page](https://myaccount.google.com/security). The\n**2-Step Verification** setting is displayed in the\n**How you sign in to Google** section.\n| **Note:** Accounts with passkeys still must enable MFA and add an authentication factor. If someone gets access to your password, and tries to sign in from an [untrusted device](https://support.google.com/accounts/answer/2544838) that doesn't have a passkey configured, Google requests this second factor, preventing unauthorized access.\n\nIf you're using a third-party identity provider (IdP) to manage single sign-on\n(SSO) in to Google Cloud, you can use the MFA provided by that IdP to\ncomply with Google Cloud's MFA requirement.\n\nIf you have questions that aren't answered in this document, contact\n[Cloud Customer Care](https://cloud.google.com/support-hub).\n\nTimelines for MFA enforcement\n\nThe timeline for MFA enforcement for Google Cloud depends on your account\ntype, as shown in the following table.\n\n| Account type | Description | Enforcement start date |\n|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|\n| Personal Google Accounts | User accounts you created for your own use, including Gmail accounts, that are used as [principals](/iam/docs/principals-overview) in Google Cloud. | On or after May 12, 2025 |\n| Enterprise Cloud Identity accounts (not using SSO) | User accounts with usernames and passwords created and managed by your Google Workspace administrator in Cloud Identity. | During or after Q4 2025 |\n| Enterprise accounts using federated authentication | User accounts created and managed by your Google Workspace administrator that use Google Workspace SSO, [Cloud Identity](/identity/docs/overview) SSO, or [Workforce Identity Federation](/iam/docs/workforce-identity-federation). | During or after Q1 2026 |\n| Reseller accounts | User accounts created and managed in a Google Cloud reseller domain. End users of the reseller are not affected. | On or after April 28, 2025 |\n\nIf you don't have MFA enabled, the Google Cloud console displays reminders to\nenable MFA at least 90 days before, and leading up to MFA enforcement. In\naddition, an email is sent with an MFA requirement reminder at least 90 days\nbefore MFA enforcement.\n\nFor resellers and their users, the Google Cloud console displays reminders to\nenable MFA at least 60 days before, and leading up to MFA enforcement.\nSimilarly, an email reminder is sent at least 60 days before MFA enforcement.\n\nWhen the requirement is enforced for your account, you must have MFA enabled to\nsign in to the Google Cloud console or the Firebase console.\n\nScope of MFA enforcement\n\nWhen the Google Cloud MFA requirement is enforced for your account, if you\ndon't have MFA enabled, you won't be able to use the following Google Cloud\ninterfaces:\n\n- The [Google Cloud console](/cloud-console)\n\n- The [Firebase console](https://console.firebase.google.com/)\n\nGoogle Cloud MFA enforcement doesn't affect service accounts. Only user\naccounts are affected. However, if you use your Google Account to impersonate a\nservice account, and MFA is enforced for your account, you must have MFA enabled\nto sign in to the Google Cloud console.\n\nAccess to the following interfaces and services is **not** affected by the\nGoogle Cloud MFA enforcement:\n\n- Google Workspace, including Gmail, Google Drive, Google Sheets,\n and Google Slides. However, Google Workspace has a separate MFA\n requirement. Contact\n [your Google Workspace administrator](https://support.google.com/a/answer/6208960)\n for more information.\n\n- YouTube.\n\nYour applications and workloads running on Google Cloud, including\napplications secured by Identity-Aware Proxy (IAP), aren't affected by MFA\nenforcement. However, your developers won't be able to use the\nGoogle Cloud console to manage those applications. In other words, your\ncontrol plane is affected by MFA enforcement, but not your data plane.\n\nOpt out of MFA enforcement\n\nGmail accounts used for Google Cloud can't be opted out of the MFA\nrequirement.\n\nExemptions for enterprise accounts and reseller accounts are available for\nspecific use cases where implementing MFA is not feasible. For more information,\ncontact [Cloud Customer Care](https://cloud.google.com/support-hub).\n\nEnable MFA for Google Accounts\n\n\nYou can enable MFA, also known as _2-step verification_ (2SV), on the **Security** tab of your\n[Google Account settings page](https://myaccount.google.com/security). For\nstep-by-step instructions, see\n[Turn on 2-Step Verification](https://support.google.com/accounts/answer/185839?sjid=8549799716107395240-NC).\n\n\nIf you don't see the **2-Step Verification** option for your account, your administrator might\nhave disabled it. Contact [your administrator](https://support.google.com/a/answer/6208960) for assistance.\n\n\u003cbr /\u003e\n\nAdditional factors for Google Accounts\n\nPersonal Google Accounts and enterprise accounts that use Google as their\nidentity provider (IdP) can use any of the following additional factors with\nGoogle Cloud:\n\n- **Authenticator apps** : you can set up an authenticator application, such as\n [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2),\n or [Authy](https://www.authy.com/), on your mobile or desktop device to act as\n your second factor.\n\n- **Backup codes** : you can create backup codes and use them as your second\n factor. Backup codes must be stored securely, and can be used only once, so\n this method should be used only when you have no other method available. For\n more information, see\n [Sign in with backup codes](https://support.google.com/accounts/answer/1187538).\n\n- **Google Prompts** : if you are signed into your Google Account on another\n device, you can receive a prompt on that device asking you whether it is you\n signing in. You can confirm that it's you in a browser, on a tablet, or your\n phone. For more information, see\n [Sign in with Google prompts](https://support.google.com/accounts/answer/7026266).\n\n- **Physical security key** : you can touch a physical security key to provide\n your second factor. For more information, see\n [Use a security key for 2-Step Verification](https://support.google.com/accounts/answer/6103523).\n\n- **SMS codes**: you can use a code sent to your phone number as a second\n factor. Before you can use SMS as a second factor, your phone number must be\n associated with your Google Account.\n\nEnable MFA for third-party identity providers\n\nRefer to your third-party IdP's documentation to learn how to enable MFA.\n\nRecover account access if a factor is lost or stolen\n\nSee [Fix common issues with 2-Step verification](https://support.google.com/accounts/answer/185834)\nfor steps to recover your account."]]
