Release v1.3.27 - IBM/ServiceNow-Guardium-Vulnerability-Assessment GitHub Wiki

Issues addressed in this release

SGA-3 Missing Last Scan Date in Guardium assessment test after "rescan"
SGA-12 Similar to SGA-22 but test result passes and severity was changed
SGA-14 Change integration run to FAIL if any integration process errors
SGA-19 Managed units not running when CM is first added
SGA-21 Read only role
SGA-22 Orphan test results after changing severity
SGA-23 Rescan error - rescan fails but there is no error
SGA-24 Use "Last Connect" in Discovered Item Last Scan Date
SGA-25 First found on sn_vul_detection
SGA-27 sn_vulc_result is "open" when the Guardium Settings is configured to pass
SGA-34 Last Scan Date is not updated on Guardium data source and Discovered Item
SGA-35 IBM Guardium Server cleanup after running "managed unit" integration
SGA-36 Vulnerability solution summary should show the recommendation
GRD-83489 Guardium SeviceNow Connector Integration skipping Vulnerable Items when updates should be applied

SGA-37 The Risk rating for the new created CC should not be changed after imported to ServiceNow

"Orphan" Vulnerable Item records happen when a Guardium test severity is changed from the default setting to a new value and there exists a Vulnerable Item which references a test with the default severity. When the Guardium assessment is run and test results are imported into ServiceNow, there will be two Vulnerable Item records. One which references a test with default severity and a second which references a test with the new severity.
The process of discovering and closing "orphan" Vulnerable Item records is very time and resource consuming.
To close "orphan" Vulnerable Item and Configuration Compliance Test Result records:
- In ServiceNow, go to "Fix Scripts"
- Search for "IBM"
- Open "IBM Guardium Vulnerability Data"
- Click "Run Fix Script"
The "Fix Script" can be run whenever you feel there are "orphan" VIT or CC Test Result records.