Installation Steps

1. Download the content and unzip the package to a directory on qradar console
2. Go to “setup” directory.
3. Simply run “bash install.sh” with root privilege.
4. Make the relevant configuration for your environment. An example configuration will be installed which can be modified later on.
5. Check the status of the lssc service at the end of the installation. PS: ruby and libyaml are dependencies for this application but both package and installer script contains the dependencies and relevant installation commands. Rpm packets are compatible with Qradar 7.3.x,7.4.x (RHEL7), packets must replace with older versions for Qradar 7.2.x

Configuration Arguments / Options

Config file path: /opt/lssc/config.json

Example config

{
  "sender": "qradar@example.com",
  "subject_stopped": "Log source stopped:",
  "subject_running": "Log source running:",
  "control_frequency": 1,

  "groups": {

    "Firewalls": {
      "stop_tolerance": 5,
      "notify_frequency": 10,
      "notify_clean": true,
      "receiver": [
        "youremail1@example.com",
        "youremail2@example.com"
      ]
    },

    "test 2": {
      "stop_tolerance": 2,
      "notify_frequency": 10,
      "receiver": [
        "youremail3@example.com",
        "youremail4@example.com"
      ]
    }
  }
  
}

• “sender”: to define email sender address of the Qradar Server
• “subject_stopped”: to define email subject of the notification
• “subject_running”: to define email subject when stopped log source starts again
• “control_frequency”: to define the frequency of checking to the configurated log sources group’s online/offline states.

Under the “groups” list, N elements of log source group can be defined. To apply Log Source Stop Control Application, simply choose one of the log source group defined in the Qradar and open a list to make it applied. An example configuration is already installed and can be found in the package.

Configuration parameters under the groups:

• “stop_tolerance”: to define log source stop tolerance (minutes of interruption of the log source state)
• “notify_frequency” : to define frequency of the reminder mail notification in minutes
• “notify_clean”: to define having notification when the state of the log source is turned as “running” (true/false)
• “receiver”: to define list of the users to get the log source stop notification emails.

It is recommended to check your config file with an online json validator for complex json files.

After updating the json file, lssc service needs to restart for load new configs.

HA Log Source Stop Control Settings

LSSC Application support HA availability of log sources. It is possible to set HA Log source pairs. Thus, As log as both HA stops sending events, notification will be sent to the receivers. To set HA option, each failover peer should contain “ha:failoverpairname;” in log source description.

In example: logsourcename1 and logsourcename2 are failover log sources. To set HA option for LSSC application:

Simply “ha:logsourcename2;” must contain in logsource1’s description and “ha:logsourcename1;” must contain in logsource2’s description.

Email templates in the views directory can be easily edited. Following images are sample of default templates

Scripts are not official IBM solutions. IBM highlights Modified (YUM) is not supported through all other installations of non-QRadar software modules, RPMs, or Yellowdog Updater. Use at your own risk.