--- title: "Enabling FIPS 140-3 and CC-NDcPP compliance using the Web UI" slug: "enabling-fips-140-3-and-cc-ndcpp-compliance-using-the-web-ui" updated: 2026-08-25T13:50:04Z published: 2026-08-25T13:50:04Z canonical: "docs.trellix.com/enabling-fips-140-3-and-cc-ndcpp-compliance-using-the-web-ui" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Enabling FIPS 140-3 and CC-NDcPP compliance using the Web UI ### Prerequisites - If your appliance is managed by a Central Management System disconnect your appliance from the Central Management System before enabling compliance. - (Optional) If you have a trusted platform module, it is beneficial to enable it as an additional entropy source. This step is optional as our kernel LRNG module is certified for hardware and virtual appliances. The new X600 hardware appliances do not have a TPM. - Enable compliance on managed appliances before enabling compliance on the Central Management System that manages them. For CC-NDcPP certification, the managed appliances must run release 10.0.0. For FIPS 140-3 certification, the managed appliances must run release 9.0.3 or later except for Endpoint Security (HX), which is release 5.0.3. - Administrator access - Make the Settings: Compliance page visible by running the `compliance options webui enable` command in configuration mode. To enable both FIPS 140-3 and CC-NDcPP compliance using the Web UI: 1. On the Web UI, select the **Settings** tab. 2. Select **Compliance** on the sidebar. 3. Click **Enable FIPS + CC Compliance**. 4. Click **Reboot Now** to continue. 5. Check that there are ![All_Enabled_icon.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-2bf6666a-119d-e0d1-b4a6-c1f20c9a2ed2.png?sv=2026-02-06&spr=https&st=2026-11-19T21%3A46%3A31Z&se=2026-11-19T22%3A46%3A31Z&sr=c&sp=r&sig=eCVb%2F8%2FcdvEQlIQsObCsdWhJDIAv1r%2BJq2pmQQEoyKQ%3D) icons in the FIPS column and CC-NDcPP columns on the Settings: Compliance page. ### Note After compliance has been enabled on an appliance, you must use SSH from a server or desktop with supported ciphers. If your SSH client does not support compliant ciphers in its default configuration, you need to specify one or more ciphers on the command line. For example: `aes128-gcm@openssh.com` Otherwise, the connection might fail because the ciphers are incompatible. For example, if by default your client only supports `aes128-cbc`, you could see an error message like the following: `no matching cipher found: aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr` :