IBM Support

IJ20762: ADDING MULTIPLE LOG SOURCE TYPES TO A RULE CAN SOMETIMES CAUSE THE RULE NOT TO FIRE AS EXPECTED

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • It has been identified that when adding multiple Log Source
    Types to a Rule using "and when the event(s) have not been
    detected by one or more of these log source types for this many
    seconds" test, the Rule does not fire as expected.
    For example:
    Rule with single test "and when the event(s) have not been
    detected by one or more of Symantec Endpoint Protection, Linux
    OS, IBM Proventia Network Intrusion Prevention System (IPS),
    Microsoft Windows Security Event Log for 7 seconds" with
    response configured to generate event.
    Messages similar to the following might be visible in
    /var/log/qradar.error when this issue is occurring:
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
    com.q1labs.semsources.cre.tests.LackOfDeviceTypeEvents_Test:
    [ERROR] [NOT:0000003000][127.0.0.1/- -] [-/- -]Exception
    reading in parms
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
    java.lang.NumberFormatException: For input string: " 11"
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at
    java.lang.NumberFormatException.forInputString(NumberFormatExcep
    tion.java:76)
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at java.lang.Integer.parseInt(Integer.java:581)
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at java.lang.Integer.valueOf(Integer.java:778)
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at
    com.q1labs.semsources.cre.tests.LackOfDeviceTypeEvents_Test.getD
    eviceByTypeIDs(LackOfDeviceTypeEvents_Test.java:58)
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at
    com.q1labs.semsources.cre.tests.LackOfDeviceTypeEvents_Test.popu
    lateEventDataMap(LackOfDeviceTypeEvents_Test.java:104)
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at
    com.q1labs.semsources.cre.tests.LackOfDeviceTypeEvents_Test.setP
    arms(LackOfDeviceTypeEvents_Test.java:136)
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at
    com.q1labs.semsources.cre.tests.CREEventTest.init(CREEventTest.j
    ava:123)
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at
    com.q1labs.semsources.cre.CustomRule.<init>(CustomRule.java:217)
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at
    com.q1labs.semsources.cre.CustomRuleReader.preProcessNewRules(Cu
    stomRuleReader.java:785)
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at
    com.q1labs.semsources.cre.CustomRuleReader.readRules(CustomRuleR
    eader.java:339)
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at
    com.q1labs.semsources.cre.CustomRuleReader.objectChanged(CustomR
    uleReader.java:1157)
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at
    com.q1labs.frameworks.events.config.ConfigurationChangeEvent.dis
    patchEvent(ConfigurationChangeEvent.java:125)
    [ecs-ep.ecs-ep]
    [97d6c86b-f52e-4421-8690-c814b3a99ce2/SequentialEventDispatcher]
       at
    com.q1labs.frameworks.events.SequentialEventDispatcher$DispatchT
    hread.run(SequentialEventDispatcher.java:129)
    

Local fix

  • Create one rule for each single log source type.
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 7.4.1.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 7.4.1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ20762

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    732

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-11-06

  • Closed date

    2020-08-06

  • Last modified date

    2020-08-06

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    QRADAR SOFTWARE

  • Fixed component ID

    5725QRDSW

Applicable component levels

[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSBQAC","label":"IBM QRadar SIEM"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"732","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
12 August 2020