Juniper Security Binary Log Collector log source parameters for Juniper Networks Security Binary Log Collector

If QRadar® does not automatically detect the log source, add a Juniper Security Binary Log Collector log source on the QRadar Console by using the Juniper Security Binary Log Collector protocol.

When using the Juniper Security Binary Log Collector protocol, there are specific parameters that you must use.

The following table describes the parameters that require specific values to collect Juniper Security Binary Log Collector events from Juniper Security Binary Log Collector:

Table 1. Juniper Security Binary Log Collector log source parameters for the Juniper Security Binary Log Collector DSM
Parameter	Value
Log Source Name	Type a name for your log source.
Log Source Description	Type a description for the log source.
Log Source Type	Juniper Security Binary Log Collector
Protocol Configuration	Juniper Security Binary Log Collector
Log Source Identifier	Type an IP address or host name to identify the log source. The identifier address is the Juniper SRX or J Series appliance that generates the binary event stream.
Binary Collector Port	Specify the port number that is used by the Juniper Networks SRX or J Series appliance to forward incoming binary data to QRadar. The UDP port number for binary data is the same port that is configured in Configuring the Juniper Networks Binary Log Format, Configuring the Juniper Networks Binary Log Format. If you edit the outgoing port number for the binary event stream from your Juniper Networks SRX or J Series appliance, you must also edit your Juniper log source and update the Binary Collector Port parameter in QRadar. To edit the port: In the Binary Collector Port field, type the new port number for receiving binary event data. Click Save. The port update is complete and event collection starts on the new port number.

For a complete list of Juniper Networks Security Binary Log Collector parameters and their values, see c_logsource_JuniperSBLCprotocol.html.