[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-25。"],[],[],null,["# Enabling FIPS 140-2 level 1 compliance\n\nThe [Federal Information Processing Standard Publication (FIPS) 140-2](https://csrc.nist.gov/pubs/fips/140-2/upd2/final) is a US government computer security standard that is used to approve cryptographic modules. New customer-hosted Looker instances can be created to meet FIPS 140-2 Level 1 standards.\n\nCreating a FIPS 140-2 compliant Looker instance\n-----------------------------------------------\n\nTo create a new FIPS 140-2 compliant Looker instance, include the `--fips` [startup option](/looker/docs/startup-options) when you first start the instance. This puts the new instance in FIPS-compliant mode.\n\nOnly new instances can be placed into FIPS-compliant mode. An instance that has an existing Looker database will fail to start when the `--fips` startup option is specified.\n\nFIPS and SSL\n------------\n\nLooker provides FIPS-compliant SSL for outgoing connections (for example, databases, query result delivery endpoints, OAuth, and others). However, the customer must provide an external SSL termination endpoint for incoming `https` requests.\n\nWe recommend using NGINX with a FIPS 140-2 compliant build of OpenSSL, as described in the [NGINX documentation](https://docs.nginx.com/nginx/fips-compliance-nginx-plus/).\n\nFollow NGINX instructions to [configure SSL termination](https://docs.nginx.com/nginx/admin-guide/security-controls/terminating-ssl-http/).\n\nFIPS and database dialects\n--------------------------\n\nAny database that was used by a Looker instance that is in FIPS-compliant mode won't work with a Looker instance that is not in FIPS-compliant mode.\n\nSeveral database [dialects](/looker/docs/dialects) that are otherwise supported by Looker are not supported in FIPS-compliant mode. The following dialects are not supported in FIPS-compliant mode:\n\n- Actian Avalanche\n- Denodo 7\n- Denodo 8\n- Dremio\n- Dremio 11+\n- Druid\n- Exasol\n- IBM Netezza\n- Microsoft SQL Server (MSSQL)\n- PrestoDB\n- PrestoSQL\n- Teradata\n- Trino\n- Vector"]]
