SSL 정책 목록에서 TLS 1.2 이상(최신 암호화)을 선택합니다.
이 선택은 최신 암호화 스위트가 적용된 TLS 버전 1.2 이상만 허용합니다. 1.0 이상의 보안 수준이 낮은 TLS 버전을 허용하려면 TLS 1.0 이상(사용되지 않음)을 선택합니다. 하지만 최신 지원되는 TLS 버전을 사용하도록 애플리케이션을 업데이트하는 것이 좋습니다.
저장을 클릭합니다.
gcloud
애플리케이션을 만들거나 업데이트할 때 --ssl-policy 플래그를 사용하여 허용되는 최소 TLS 버전을 지정합니다.
앱을 만드는 동안 최소 TLS 버전을 설정하려면 다음 단계를 따르세요.
gcloud app create --ssl-policy=TLS_VERSION
앱을 업데이트하는 동안 최소 TLS 버전을 설정하려면 다음 단계를 따르세요.
gcloud app update --ssl-policy=TLS_VERSION
TLS_VERSION를 TLS_VERSION_1_2로 바꿉니다. 이렇게 하면 최신 암호화 스위트가 있는 TLS 버전 1.2 이상만 허용됩니다. 1.0 이상의 보안 수준이 낮은 TLS 버전을 허용하려면 TLS_VERSION를 TLS_VERSION_1_0로 대체하세요. 하지만 최신 지원되는 TLS 버전을 사용하도록 애플리케이션을 업데이트하는 것이 좋습니다.
커스텀 TLS 버전 및 암호화 사용 중지
TLS 버전 1.2 이상을 사용하도록 애플리케이션 설정을 업데이트하면 App Engine에서 TLS 버전 1.1 이하를 사용하는 모든 보안되지 않은 트래픽을 자동으로 차단합니다.
Cloud Load Balancing 및 서버리스 NEGS를 사용하여 트래픽을 App Engine 애플리케이션으로 라우팅하는 경우 SSL 보안 정책을 정의하여 TLS 버전 또는 암호화를 사용 중지할 수 있습니다. HTTPS 또는 SSL 연결에서 사용할 수 있는 TLS 버전 및 암호화를 지정합니다.
[[["이해하기 쉬움","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\u003eThis feature is currently unavailable.\u003c/p\u003e\n"],["\u003cp\u003eThe feature will be launched in the near future.\u003c/p\u003e\n"]]],[],null,["# Secure your app with minimum TLS (standard environment)\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nTo increase security, starting in March 2025, support for Transport Layer\nSecurity (TLS) version 1.1 and earlier is deprecated. [Update your application settings](#update-tls) in the App Engine standard environment to use TLS version 1.2 and later, along with a\ncorresponding secure set of cipher suites.\n|\n| **Preview\n| --- Secure your app with minimum TLS**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nWhen you select the latest TLS version, App Engine automatically\nblocks insecure traffic, without requiring you to\n[configure](/load-balancing/docs/https/setting-up-https-serverless) a\nglobal external Application Load Balancer to route requests to your application.\n\nTo upgrade your existing applications to use\nonly TLS version 1.2 and later, follow the [instructions](#update-tls) in this\nguide.\n| **Note:** If you update your application settings to enforce TLS version 1.2 and later, App Engine automatically rejects incoming requests that attempt to use older, less secure TLS versions 1.1 and earlier. Before March 2026, this rejection causes a `400 Bad Request - The request was malformed` error, after a successful TLS handshake, meaning the connection is established, but the request itself is denied. External SSL-checking sites might only verify a successful TLS handshake, and incorrectly imply that TLS version 1.1 and earlier are still supported. After March 2026, App Engine ensures stricter security compliance by preventing the TLS handshake itself for connections using TLS version 1.1 and earlier.\n\nSupported TLS versions and cipher suites\n----------------------------------------\n\nThe security of TLS connections depends on the negotiated cipher suite, a\ncombination of cryptographic algorithms. These cipher suites are identified by\nIANA values, as detailed in the following table:\n\nIf you need to use a different or a less restrictive cipher suite, we recommend\nthat you use a global external Application Load Balancer. For more information, see [Set up a classic Application Load Balancer with App Engine](/load-balancing/docs/https/setting-up-https-serverless) and [SSL policies for SSL and TLS protocols](/load-balancing/docs/ssl-policies-concepts#defining_an_ssl_policy) in the Cloud Load Balancing documentation.\n\nUpdate the TLS versions allowed for your app\n--------------------------------------------\n\nYou can update the TLS version using the Google Cloud console or the\ngcloud CLI. For tool-specific steps, click the tab for your preferred\ntool: \n\n### Console\n\n1. In the Google Cloud console, go to the App Engine **Settings** page:\n\n [Go to Settings](https://console.cloud.google.com/appengine/settings)\n2. In the **Application settings** tab, click **Edit application settings**.\n\n3. From the **SSL Policy** list, select **TLS 1.2+ (Modern ciphers)** .\n This selection only allows TLS version 1.2 and later, with modern cipher\n suites. If you want to allow less secure TLS versions,\n such as 1.0 and later, select **TLS 1.0+ (Obsolete)** . However, we\n recommend that you update your applications to use the latest [supported](#supported-versions) TLS version.\n\n4. Click **Save**.\n\n### gcloud\n\nWhen you create or update your application, use the `--ssl-policy` flag to\nspecify the minimum permitted TLS version.\n\nTo set a minimum TLS version while creating your app: \n\n gcloud app create --ssl-policy=\u003cvar translate=\"no\"\u003eTLS_VERSION\u003c/var\u003e\n\nTo set a minimum TLS version while updating your app: \n\n gcloud app update --ssl-policy=\u003cvar translate=\"no\"\u003eTLS_VERSION\u003c/var\u003e\n\nReplace \u003cvar translate=\"no\"\u003eTLS_VERSION\u003c/var\u003e with `TLS_VERSION_1_2`. This only allows TLS version\n1.2 and later, with modern cipher suites. If you want to allow less secure TLS version,\nsuch as, 1.0 and later, replace \u003cvar translate=\"no\"\u003eTLS_VERSION\u003c/var\u003e with `TLS_VERSION_1_0`. However, we recommend that you update your\napplications to use the latest [supported](#supported-versions) TLS version.\n\nDisable custom TLS versions and ciphers\n---------------------------------------\n\nIf you update your application settings to use TLS version 1.2 and later, App Engine automatically blocks all insecure traffic using TLS version 1.1 and earlier.\n\nIf you use\n[Cloud Load Balancing and serverless NEGS](/load-balancing/docs/negs/serverless-neg-concepts)\nto route traffic to your App Engine application, you can disable a TLS\nversion or cipher by defining an [SSL security policy](/load-balancing/docs/ssl-policies-concepts). Specify the TLS versions and ciphers that HTTPS or SSL\nconnections can use.\n\nWhat's next\n-----------\n\n- To verify and manage SSL certificates, see [Secure custom domains with SSL](/appengine/docs/standard/securing-custom-domains-with-ssl).\n\n- To enable Cloud Load Balancing to manage incoming requests to your custom domain, see\n [Migrate App Engine custom domain to Cloud Load Balancing](/appengine/docs/standard/custom-domain-to-cloud-load-balancing)."]]
