Welcome to AlgoBot

AlgoSecAlgoBot is your personal security policy management assistant. AlgoBot provides quick and easy access to core ASMS functionality from the comfort of your organization's existing chat platforms, including Desktop, Web, or Mobile options. AlgoBot is supported for Slack, Microsoft Teams, and both online and on-premises versions of Skype for Business.

To deploy AlgoBot, first install AlgoBot on your chat platform, and then on your ASMS

Interested in deploying AlgoBot?

Please let us know. Get in touch with us at [email protected].
We will be glad to support your deployment.

AlgoBot prerequisites and deployment configurations

As a Chat Bot, AlgoBot has to be notified of any new messages that the users may send over one of the supported chat platforms. To integrate AlgoBot with your organization's chat platforms, your system must meet the following prerequisites:

Internet access

The ASMS server must be able to access the internet and the chat platform servers. Unauthenticated proxies are supported if needed.

For details, see the diagrams below: AlgoBot with no proxy | AlgoBot with a proxy

Permissions You must have administrator privileges and access to authorize AlgoBot on your chat platform.
DNS The ASMS Central Manager must be configured with DNS.
Supported Deployments For supported deployments see Supported deployments per architecture structure

Back to top

Install AlgoBot

Follow these instructions to install AlgoBot.

Back to top

Chat with AlgoBot

Chat with AlgoBot to run traffic simulations, submit change requests, analyze application impact, and more!

  • Enter @algobot help to view a full list of available commands and requests.
  • Send direct messages to AlgoBot from your chat platform. If there are more than the two of you in the chat, use the @algobot prefix so that AlgoBot knows you're talking to it.
  • Language support: If you’re typing in English, German, French, or Portuguese, AlgoBot will attempt to recognize the language and reply in kind. By default, AlgoBot replies in English. See on this page Change AlgoBot's default language.

  • Invite AlgoBot to any of your Slack channels. Once invited, AlgoBot listens to all commands you send to @algobot.

Note: Make sure that you have run an analysis in AFA before using AlgoBot. AlgoBot needs AFA data to be able to help you!

For example:

Back to top

AlgoBot maintenance and advanced configurations

The following sections describe how to maintain and troubleshoot your AlgoBot installation, as well as additional configurations.

Logs and configuration files

AlgoBot log files are created under ~/algobot, usually defined as /home/afa/algobot.

A set of log and configuration files are saved for each chat platform, with the platform name, such as slack, as part of the filename.

Each set includes the following files:

algobot-<platform>.conf The configuration data generated as part of the installation and configuration process.
algobot-<platform>.log

General logs, commands, and errors. If you need to contact AlgoSec support in reference to AlgoBot, support may request this file.

utilization-<platform>.log A synthesized, clear log of the commands used in AlgoBot for analytics purposes.

Back to top

Upgrade AlgoBot

To update an existing AlgoBot installation, do the following:

  1. Replace the existing AlgoBot run file on the Central Manager with the new one provided by AlgoSec.
  2. Perform steps 1-3 in Install AlgoBot on the ASMS server.

No additional configuration is required.

Back to top

Run multiple AlgoBot instances on a single machine

To support multiple AlgoBot instances running a the same time, supporting multiple chat platforms or multiple teams, run AlgoBot using the following syntax:

./algobot --config-path /some/path.conf

where /some/path.conf is the path and filename of a separate configuration file. When run using this syntax, the CLI prompts you to create the defined configuration instead of the default.

For example:

algobot slack --config-path /path/to/config1 algobot slack --config-path /path/to/config2

Alternately, use the linux alias command to match each AlgoBot instance with a name and easy-to-run command.

For example:

alias algobot-team1=”~/algobot/algobot slack --config-path /path/to/config1” alias algobot-team2=”~/algobot/algobot slack --config-path /path/to/config2”

Then, run algobot-team1 to launch this instance.

Back to top

Change AlgoBot's default language

Note: Even though the default language is set to a specific language, AlgoBot will still understand other languages as well.

Do the following:

  1. Connect to the ASMS Administration interface (algosec_conf). For details, see Connect to and Utilize the Administration Interface.
  2. In the administration interface main menu, run option 14 - Product and cloud configuration.
  3. Run option 4 - AlgoBot configuration.
  4. Choose the chat platform you want to set the language for.
  5. When prompted, enter the default_language (supported options are "en" (english ), "de" (german), "fr" (french) , "pt" (portuguese)).

Back to top