Version 9.1-GA (9.1.384.4) Release Notes

See the Version 9.1-GA (9.1.384.4) Feature Overview Video article for a video introduction to these features. 

New Features 

Vulnerability and Ticket Archiving 

RiskVision now provides configuration settings to archive vulnerabilities and tickets. When configured, vulnerabilities and/or tickets that have not been updated within a customer-defined time frame, such as the last 90 days, will be archived. The benefit to archiving these objects is that the scalability and performance for non-archived records will improve because there will be fewer records in the tables to query and perform operations against. 

KRI Enhancements 

KRI assessments have received two categories of enhancements. First, they can now be restarted and archived. When restarted, users will not be able to edit prior periods. This will enable KRI assessments to behave more like traditional assessments. Second, KRI assessments now support a comment per KRI period so that specific KRI values can be explained.

SAML LDAP Group Support 

Customers using SAML for authentication will now be able to import LDAP groups associated with user records from their Identity Provider. These LDAP groups can then be used to map user roles in Resolver RiskVision.

Ticket Instances Tab

Tickets now have a Vulnerability Instances tab that shows which vulnerabilities relate to which entities on a ticket. This tab also allows users to mark specific instances as resolved. 

Error Tracking 

A common request we receive from customers is to provide more tools to diagnose performance degradation. To that end, we have provided the following new charts on the Server Administration page: 

  1. Recent Connector Activity: Connectors that have been active in the last thirty minutes
  2. Currently Running Jobs
  3. Slow Running Queries 

You can also view further information about active server jobs by going to Administration>Scheduled Jobs. The Current Status column shows the status of scheduled jobs. When a job is triggered, its status will change to Executing from ‘xx’ seconds. Finished jobs have a status of Not Executing.

Health Reports 

The Health Report now shows the number of attachments, as well as the aggregate storage space consumed by the Attachments folder. 

Also, to provide Resolver with important metrics to use for scalability and performance testing and to aid in prioritization of future scalability and performance optimizations, Health Reports will now be automatically sent to Resolver. You can disable this functionality or adjust how frequently Health Reports are sent. 

RiskVision Permissions

A new permissions check that restricts users access to RiskVision pages based on user permissions has been added and tested against RiskVision default roles. However, while rare, customers with custom roles may run into access issues with specific pages. These are unintended issues and should be reported to Resolver Support as soon as they are encountered.

Bug Fixes 

  • RRV-1326: Files attached to findings carried forward for restarted assessments will now be accessible.
  • RRV-931: Fixed an issue with OpenSSL that caused the Apache Service to log SSL warnings. 
  • RRV-993: JasperReports Server was upgraded to version 6.4.3 to resolve the following TIBCO vulnerabilities : CVE 2018-5429, 2018-5430, and 2018-5431.
  • RRV-1025: The following issues no longer occur: 
    • When evidence and files attached to objects such as entities, findings, and tickets are deleted in the UI, they will be deleted from the data/attachments folder.
    • When assessments are restarted, evidence files are linked and not copied, which will result in less storage space being consumed. 
  • RRV-70: The load time of the Control Results page has been improved.
  • RRV-71: Filtering the Control Results page by Show Applicable now has improved performance. 
  • RRV-72: Assessment workflows no longer transition slowly. 
  • RRV-1757, RRV-1729 and RRV-1892: Documents attached to findings and responses now load correctly.
  • RRV-1768: Fixed an issue where documents attached to entities displayed the incorrect version number. 
  • RRV-935: Users who synchronize findings to the current workflow definitions are no longer added as stakeholders to the related findings.

Known Issues

Tracking ID 



JasperReports Server is unresponsive after saving a scheduled report in Internet Explorer. 

Workaround:This issue can be resolved by refreshing the page. 


Not all Microsoft® Word documents can be imported as RiskVision policy documents.

Workaround: Most issues can be resolved by manually editing the imported document or by copying and pasting one section at a time.


The default choice template (a drop-down list) does not work with table-type questions.

Workaround: Create a new choice template for use with table-type questions. 


An error message is generated when exporting a JasperReports Server repository using the script js-export.bat. This is the result of a JasperReports Server bug that creates an error message when one should not be created. The export is fine, and will be able to be successfully imported into the same or another instance of JasperReports Server. 


An error message is generated when executing the command: js-export --everything --output-zip >>test.log. This is a known issue for Amazon Corretto 8. The export and import of is successful and there are no known issues due to this error. 









Preferred ownership issues:

• Viewing assessment details in a program can reveal all stakeholders in the workflow, rather than only the preferred owners in the current stage.

• Enabling preferred ownership on a workflow that is already in use only applies to subsequent preferred ownership assessments that use the workflow.

• Deleting preferred ownership from controls after the launch of assessments does not change the assignment of controls to stakeholders.

• If content in a program is added at the group level, and if it has preferred ownership added at the control level, duplicate controls will be created when the program is edited, or when assessments within that program are restarted.

Workaround: Assign the preferred ownership at the same level as the content added in a program. For example, if the preferred ownership is assigned to the content at the group level, assign the content to the program at the group level. If the preferred ownership is assigned to the content at the control level, assign the content to the program at the control level.

• Preferred ownership works only in the first stage of assessment workflows with branching. 

• Controls assigned to the assessment stakeholders do not get updated after editing the program to select the following program option: Do not assess controls with preferred ownership configured when the entities being assessed have no owners that correspond to the preferred owners associated with the control.


A custom dashboard or chart that uses the comment column from the agl_ramitigationtable will fail to execute the query.

Workaround: To execute the custom query successfully, rename the comment column to mitigation_comment.


The cache does not update immediately when controls and sub-controls are updated. 

Workaround: Wait a few minutes for the controls and sub-controls to be updated in the relevant assessments.


When propagation is enabled, answering the parent entity assessment will not update the scores of its child entities on the Program Details page>Assessments tab. Scores are updated correctly on the Assessment Details page > Control Results tab of the parent.

Workaround: To update the scores, select the child entity, then select Propagate Control Results from the More Actions drop-down list.


When a user tries to run a Jaspersoft report after logging out of RiskVision, the report appears to run but is not rendered. The reason the report appears to run is that the Jaspersoft user interface is still available.

Workaround: Close the browser where the Jaspersoft application is running.


Creating a Table chart-type of Policies no longer executes the query. This issue persists only with the Oracle database.

Workaround: To build the chart without errors, ensure that the Selected Columns contain any string-type column at the top and the Audience column is moved down the selected list.


Risks added to an assessment cannot be removed, even if the stakeholder changes the answer choice from any assessment workflow stage.

Workaround: Manually delete the risks.


Adding the same input control multiple times when importing a RiskVision chart does not produce the desired results.

Workaround: If you need to have the same input control more than once, create a new input control with a different resource ID.


It may not be possible to create an assessment that contains a dynamic group of more than 17,000 entities.

Workaround: Whenever a dynamic group contains more than 17,000 entities, split the excess entities into a separate dynamic group and then run the assessment.


It is impossible to export JasperReports Server Fusion charts to formats other than PDF and HTML.


The schema name is saved in the database in uppercase, even if the user entered it in lowercase when creating the schema:

1. Whenever hyphens are used in the schema name during import, the schema name is converted to uppercase. Example "schema-name" becomes SCHEMA- NAME.

2. When an export is performed with the original name (schema-name in lower case), a "schema not found" error message is thrown. Export is successful if the schema name is given in uppercase.

Workaround: Avoid using hyphens in schema names. If you must use a hypen, reference the schema name using uppercase.


Risks are not auto-identified and text-type sub controls fail when scoring for text-type questions is enabled in Questionnaire Presentation Options.


The Jasper Reports Server installation fails if the length of the installation path is longer than 260 characters.


The JasperReports Tomcat service fails to start on a computer if the Jasper Reports Server installation path contains special characters, such as $, %, &, and @. The service does not start even when it is attempted manually.


Users with an assigned Vulnerability severity filter receive an error message when accessing the entity. 

Workaround: Use Entity Vulnerability General.Severity for this entity as a condition instead of Vulnerability General.Severity.


It is not possible to advance a workflow stage if it is assigned a team of more than 200 stakeholders.


Control results are not propagated down to related entities if multiple assessments for the related entities are created after the controls results have been propagated by the source entity.

Workaround: Execute Propagate control results from the More Actions drop-down on the Programs > Assessments page.


Entities cannot be copied if they are imported into RiskVision without a primary owner.

Workaround: Assign a primary owner to all imported entities before copying them. 


Users with an Entity filter condition of Classification. Internal or external encounter an exception when running reports.

Workaround: Avoid using the Classification. External or internal attribute within any filter conditions. Use the Entity. Internal or External attribute instead


Entities cannot be retrieved for users with the filter condition EntityCustomAttributes_CustomText_1.

Workaround: Filtering based on CLOB-type columns on the RiskVision server is not supported. Any report attribute to be excluded from filtering must be marked as a non-filterable (‘filterable=”false”) in the ReportAttributes.xml file.


Data in RiskVision doesn't honor the EntityCustomAttributes_CustomEncryptedString_1 filter. 

Workaround: Any report attribute to be excluded from filtering must be marked as non-filterable (‘filterable=”false”) in the ReportAttributes.xml fileACL filters with conditions based on encrypted fields are not supported.


Unable to load data to users with the Incident filter condition of Incident_Incident_Comment ACL. Filtering based on CLOB-type columns is not supported on the RiskVision server.

Workaround: To prevent report attributes based on CLOB or similar columns from being displayed in Filter Manager’s filter condition field list, mark the report attributes as non-filterable (‘filterable=”false”) in ReportAttributes.xml file.


Exceptions requested from Home-Exception Requests are not displayed in the Exceptions tab and Control results drill down.

Workaround: Create the exceptions at the assessment level, not on the Home > Exceptions page.


The filter condition Entity Custom Attributes. Custom Rational Number 3 generates an error.

Workaround: Add the Custom Attributes extensions for Float in the ReportAttributes.xml file: 

<Group name="AssetCustomAttributes">

<Attribute name="Asset.CustomAttributes.CustomAttributes.float1" displayname="Custom Rational Number 3" datatype="float" category="%Asset% Custom Attributes"></Attribute>

Restart Tomcat Services.


After upgrading from version 7.0 to version 8.5HF2, RV user and sysadmin cannot login to Standalone Jasper. 

Workaround: After upgrading RiskVision, perform the following steps to login to Standalone Jasper:

  1. Log in to RiskVision with a user that has admin privileges. 
  2. Click R7 Analytics. The Jasper home page is displayed. 
  3. Navigate to Manage > Users
  4. Click Add User and enter the necessary information.
  5. Go to the %Home%\Reportserver\ReportServer\postgresql\bin folder and open pgAdmin3
  6. Connect to the RiskVision database.
  7. Open the jiuser table. 
  8. Copy the password of the newly created user.
  9. Find the sysadmin or rvjasperuser user and change their password to the copied password. 
  10. Restart Jasper services
  11. Verify that sysadmin or rvjasperuser user can login to Jasper Standalone using the new password.


Horizontal scroll bars are missing in JasperReportsServer dashboards that require horizontal scrolling. This is a bug in JasperReports Server version 6.3.0 and will be fixed in a future JasperReports Server release.

System Requirements

The following hardware requirements represent the minimum system requirements to install Resolver RiskVision™ V. 9.1. These specifications are for planning purposes only. To learn about the recommended hardware and software for your environment, contact Resolver Support.  



Total number of CPU cores



16 GB

Disk Space

At least 100 GB of free disk space 

Supported Versions

This release supports the following versions of third-party software:



Operating System

Microsoft Windows Server® 2008 R2 SPI Standard x64 Edition and Windows Server® 2012 R2 Standard x64, Windows Server® 2016

Amazon Coretto (JDK)


Apache Tomcat


Apache Web Server


Apache OpenOffice


Jasper Reports Server





Web Browser 

Internet Explorer® 11, Edge, Mozilla Firefox®, Google Chrome®

Adobe® Flash browser plug-in

Adobe® Flash Player, version 11 (optional)

JasperReports Server 6.4.3 comes with the following technologies: 





Apache Tomcat


Oracle JDK 8 

1.8.0_151 (8u151)