One-time Setup for Azul Vulnerability Detection Within Your Organization
Table of Contents
Azul Vulnerability Detection is a webservice provided by Azul. Once an account has been created for your organization, you will need to perform some on-time actions to configure the tool for your needs. Part of this initial setup also includes the installation of minimal one Forwarder within your application environment.
The Forwarder is the communication broker, providing a single point of communication between many JVMs and the Azul Vulnerability Detection service. Your organization must have at least one Forwarder.
About the Forwarder
The Forwarder is a central point of communication for an organization’s JVMs to reach Azul Vulnerability Detection. By moving requests through a Forwarder, organizations can maintain fewer firewall rules for outbound communication, improve the speed of JVMs through local communication and caching, and maintain application control.
Your organization must configure one or more of these Forwarders to receive data in Azul Vulnerability Detection, based on a mix of network and organizational structure requirements. The primary role of a Forwarder is to act as an intelligent proxy so that many JVMs can connect to Azul Vulnerability Detection without any JVM being directly connected to the internet.
Communication Patterns
Each JRE on a network communicates to the Forwarder, which communicates to Azul Vulnerability Detection. The Forwarder cannot initiate communication with a JRE and can only respond.
Failure Resiliency
Communication between a JVM and the Forwarder is fault-tolerant. A JVM will always continue to operate its workload regardless of its ability to communicate with the Forwarder.
If the network is unreliable, or connection difficulties occur between a JVM and the Forwarder, the JVM will attempt to reconnect. If reconnection succeeds, data loss between the time of disconnection and time of reconnection may occur.