--- title: "swg scan block-by-proxy enable" slug: "swg-scan-block-by-proxy-enable" tags: ["Reference", "CMS 11.x", "EX 11.x", "HX 10.x", "FX 11.x", "AX 11.x", "NX 11.x", "IVX 11.x", "Customer", "Network Security"] updated: 2026-08-04T17:22:36Z published: 2026-08-04T17:22:36Z canonical: "docs.trellix.com/swg-scan-block-by-proxy-enable" stale: true --- > ## 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. # swg scan block-by-proxy enable To enable or disable the blocked-by-proxy detection feature on a Network Security appliance, use the `swg scan block‑by‑proxy enable` command or the `no swg scan block‑by‑proxy enable` command in configuration mode. This command requires the **Admin** role. This command enables or disables the blocked-by-proxy detection feature. For information about the blocked-by-proxy detection feature, see the Network Security User Guide. By default, the blocked-by-proxy detection feature is disabled. > [!TIP] > Tip > > We recommend that, after you enable the blocked-by-proxy detection feature, you use the `write memory` command to save the running configuration to the active configuration file. If you do not save the running configuration, the feature will be disabled the next time system restarts. The CLI does not provide a command that displays the status of the blocked-by-proxy detection feature command. ### Syntax `[no] swg scan block-by-proxy enable` ### Parameters `no` Use the `no` form of the command to disable the feature. ### Examples In this example, you enable the block-by-proxy scan: ``` hostname (config) # swg scan block-by-proxy enable ``` In this example, you disable the block-by-proxy scan: ``` hostname (config) # no swg scan block-by-proxy enable ``` ### User role Admin ### Command mode Config ### Supported appliances **Network Security:** Release 7.4.0