SECURITY PROPYCHECK PORT ADD
    Usage: SECURITY PROPYCHECK PORT ADD [SCAN-ALL]

    You can add a port to be scanned, by using the "ADD" method.

    Normally, when adding a port, no scan protocols are defined, and no scans are performed on that port, pending further configuration. However, if you wish to specify that the proxy scanning engine should scan for all known protocols, without having to issue separate commands, you could use the "scan-all" keyword.

    Example:
    /as security proxycheck port 80 add scan-all
    /as security proxycheck port 1080 add

    SECURITY PROPYCHECK PORT DEL
    Usage: SECURITY PROPYCHECK PORT DEL

    You can remove a port from the list of ports to be scanned, by using the DEL method.

    Example:
    /as security proxycheck port 1080 del

    SECURITY PROXYCHECK PORT LIST
    Usage: SECURITY PROXYCHECK PORT LIST

    You can use this command to see the configuration for a specific port object.

    Example:
    /as security proxycheck port 8080 list

    SECURITY PROXYCHECK PORT SCAN
    Usage: SECURITY PROXYCHECK PORT SCAN [protocol] {enable|disable}

    You can select from a wide variety of known proxy server protocols to scan for, and individually select or deselect among them for each port you scan. You can do so, using the "SCAN" options.

    The following protocols are defined:

    SOCKS4: This is the revision 4 of the popular SOCKS protocol. Most proxy servers have support for this protocol. It provided for no built-in authentication, and as such, is very insecure.

    SOCKS5: This is the revision 5 of the popular SOCKS protocol. Most proxy servers have support for this protocol. It provides for built-in authentication, although many server administrators do not enable it, allowing their system to be used as proxy servers.

    HTTP: This category implements scanning for proxy servers using the HTTP protocol used by web servers. It encompasses HTTP-GET, HTTP-POST and HTTP-CONNECT. Many cache servers, used to speed-up content access are not properly secured, and allow connection proxying via HTTP. Note, that this scan mode results in three separate connections, one for each scan mode (GET, POST and CONNECT) as described below:

    HTTP-GET: This scan protocol is actually as subset of the HTTP scan mode. It specifically scans for servers that allow proxying through the use of the HTTP GET command.

    HTTP-POST: This scan protocol is actually as subset of the HTTP scan mode. It specifically scans for servers that allow proxying through the use of the HTTP POST command.

    HTTP-CONNECT: This scan protocol is actually as subset of the HTTP scan mode. It specifically scans for servers that allow proxying through the use of the HTTP CONNECT command.

    ALL: This is not really a protocol at all, but a shortcut, allowing you to enable or disable scanning for all known protocols with a single command. Currently the "ALL" keyword will perform scans for servers which allow for proxying through SOCKS4, SOCKS5, HTTP via GET, HTTP via POST or HTTP via CONNECT.

    Example:
    /as security proxycheck port 8080 list