Before connecting ABS, API Security Enforcer must be installed. For more information on installing and configuring API Security Enforcer, see the ASE Admin guide.
The following diagram summarizes the process of connecting ABS to API Security Enforcer:
The following is a sample
abs.conf file which is part of the API Security
; API Security Enforcer ABS configuration.
; This file is in the standard .ini format. The comments start with a semicolon (;).
; Following configurations are applicable only if ABS is enabled with true.
; a comma-separated list of abs nodes having hostname:port or ipv4:port as an address.
; access key for abs node
; secret key for abs node
; Setting this value to true will enable encrypted communication with ABS.
; Configure the location of ABS's trusted CA certificates. If empty, ABS's certificate
; will not be verified
secret_key are the keys that were defined
abs_init.js file when configuring MongoDB.
If ABS is running in cluster mode, choose the IP address and port from any ABS node to add to
abs.conf file in API Security Enforcer.
API Security Enforcer connects to the ABS node defined in abs.conf to obtain available ABS IP addresses (step 1). In stand-alone mode, ABS sends the only IP address. In cluster mode, ABS sends the IP addresses of all available ABS nodes to API Security Enforcer.
After API Security Enforcer receives the IP address, it establishes a session with ABS by sending the secret and access keys (step 2). After successful authentication, API Security Enforcer streams the access log files and API JSON files to the ABS node (step 3). After sending the files, it receives the attack lists (only available if blocking is activated for API Security Enforcer) from ABS (step 4). When the transaction is complete, API Security Enforcer logs out from ABS (step 5).
ABS uses machine learning (ML) algorithms to discover attacks, anomalies, and other traffic information. It stores incoming API Security Enforcer logs and then passes these logs to the machine learning engine for analysis. In high load environments, a single ABS node may not be able to process all log files, and multiple ABS nodes should be deployed for log processing.
The following diagrams show the API Security Enforcer – ABS Dataflow.
In stand-alone mode, a single MongoDB node is used for both read and write operations. A stand-alone mode of deployment is only recommended for testing purposes.
In cluster mode, API Security Enforcer nodes synchronize the
abs.conf file as
well as the state of each ABS node. The ABS cluster nodes do not communicate among themselves.
Each node records its status in MongoDB and reads about the state of other nodes from the