--- title: "Local BA signers whitelist" slug: "local-ba-signers-whitelist" tags: ["Product Usage", "EX 11.x", "FX 11.x", "AX 11.x", "NX 11.x", "Network Security"] updated: 2026-08-21T18:19:39Z published: 2026-09-12T20:42:46Z canonical: "docs.trellix.com/local-ba-signers-whitelist" --- > ## 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. # Local BA signers whitelist The Local Binary Analysis (BA) Signers whitelist feature allows you to enable or disable BA signers in the local whitelist. Enabling or disabling BA signers allows you to customize the whitelist to work specifically with your local endpoint environment. > [!NOTE] > Note > > Only disabled BA signers can be enabled again. The Local BA Signers whitelist is a list of trusted company names. Portable Executable (PE) files from the companies in the list are trusted because they are signed by an Authenticode certificate. When a file is received, it is searched. If the company name found in the file matches a name on the whitelist, the file is approved and excluded from further analysis. This feature also allows you to switch between signer modes. The appliance or sensor has two signer modes, default and insecure. You switch to a mode depending on which whitelist you want to use. If you switch to the default mode, you are choosing to use the standardTrellix BA signers whitelist. If you switch to the insecure mode, you are choosing to use the local BA signers whitelist and the standardTrellix BA signers whitelist. > [!NOTE] > Note > > The default mode for the appliance or sensor is default. The feature allows you to perform the following actions: - Switch signer modes - View the local whitelist - Enable signers in the local whitelist - Disable signers in the local whitelist You manage the whitelist in the CLI using the following commands: - **signer-whitelist mode***mode*—Switches to a specified mode. See [Switching between signer modes using the CLI](/network-and-platform/docs/switching-signer-modes-using-the-cli) for information about how to use this command. - **show signer-whitelist mode**—Displays the current signers mode. See [Identifying signer modes using the CLI](/network-and-platform/docs/viewing-signer-modes-using-the-cli) for information about how to use this command. - **show signer-whitelist**—Displays all enabled signers in the local BA signers whitelist. See [Viewing a local BA signer whitelist using the CLI](/network-and-platform/docs/viewing-the-local-ba-signers-whitelist-using-the-cli) for information about how to use this command. - **signer-whitelist disable***signer*—Deletes a signer from the local BA signers whitelist. See [Deleting a BA signer from the local whitelist using the CLI](/network-and-platform/docs/disabling-a-ba-signer-using-the-cli) for information about how to use this command. - **show signer-whitelist disabled**—Displays all signers that were deleted from local BA signers whitelist. See [Viewing a deleted BA signer using the CLI](/network-and-platform/docs/viewing-disabled-ba-signers-using-the-cli) for information about how to use this command. - **signer-whitelist enable***signer*—Adds a signer to the local BA signers whitelist. See [Adding a BA signer to the local whitelist using the CLI](/network-and-platform/docs/enabling-a-ba-signer-using-the-cli) for information about how to use this command. ### Use case A customer receives a false positive message during the analysis of a PE file. An Authenticode signature is also found in the file. The customer wants to whitelist the file because a trusted signature was found. The customer asksTrellix to whitelist the file. The request is denied because the standardTrellix BA signers whitelist is global and the message indicates questionable content. The customer configures the Local BA Signers whitelist feature on a local appliance or sensor. The customer can now enable the file in the local whitelist. ### Prerequisites To manage your local BA signers whitelist, ensure the following prerequisites are met: - Administrator or Analyst access. - An established connection between your appliance and the Internet.