Addressing Your Most Pressing Questions about RSA Archer GRC 6.1
With the excitement that’s been building for RSA Archer GRC 6.1, we’re sure you’ve heard some rumblings about what is changing. We’d like to take this opportunity to address some of the things we’ve heard from Archer users as “Fact” or “Fiction.”
If you have other questions about RSA Archer GRC 6.1, please use the “Add a Comment” button below and we will work to get you the answers.
RSA is changing product packaging for RSA Archer offerings.
FACT: RSA’s primary mission is to make our customers successful and help them achieve their strategic business objectives. The GRC market is changing. More and more companies have mandates to manage risk. And these are companies of all sizes across differing industries across many parts of the global.
The new RSA Archer packaging simplifies and speeds deployment. It makes it much easier to select the tools to address your organization’s specific risk and compliance challenge, while reducing the time and effort associated with standing up a GRC program. It provides integrated use cases focused on key processes that work together to mature your GRC program, allowing your organization’s program to grow incrementally as your needs change.
RSA recognizes that not all organizations have the same GRC needs or maturity levels. It is common for organizations that are just beginning their GRC programs to have more basic needs than organizations with mature GRC programs in place spanning the three lines of defense. The new RSA Archer use case packaging enables us to better support the varying needs of our customers by providing specific GRC use cases that best match our customers’ business and GRC maturity needs, while reducing the historical cost and complexity associated with GRC deployments.
A complete listing of the new RSA Archer use cases can be found on the RSA Link community, along with use case overviews, descriptions, capabilities, benefits, videos, maturity maps and more. Additional information on each solution’s use cases is also available via links from each solution page.
I have heard that I need to upgrade to RSA Archer GRC 6.1 right away.
FICTION: Existing RSA Archer customers can transition to the new use case packaging during your term renewal process. You will continue to use RSA Archer solutions with the current licensing scheme throughout the remainder of your current licensing term.
I also heard that I need a new license key if I want to upgrade to GRC 6.1.
FACT: RSA Archer customers that would like to upgrade to RSA Archer GRC 6.1 will need to transition to the new use case licensing. The RSA Archer sales team will work with you to help you manage the process for moving to the new use case packaging and licensing. You can reach out to your RSA sales representative for more information. Our commitment to you is to ensure that all functionality you have currently licensed transitions to the new model.
Existing RSA Archer customers can also leverage the new use case approach to add to your portfolio of RSA Archer solutions. Consult with your RSA sales representative to learn more.
The Archer “Modules,” like Policy Management, are going away.
FACT and FICTION: Modules (such as Policy Management, Compliance Management, Risk Management, Enterprise Management, Vendor Management, etc.) will continue to be available on RSA Link for GRC 5.x customers and will continue to be supported until GRC Platform 5.x reaches its End of Primary Support (EOPS) date. However, RSA will not create new functionality for these Modules going forward and Cumulative Patch Releases (CPRs) will be provided only as needed.
From a functional perspective, the new use case packaging provides the same functionality and capabilities as our previous “Modules.” The naming and configuration of RSA Archer solutions and use cases themselves is what is changing. The new RSA Archer use cases contain all of the applications, reports, questionnaires, etc., necessary to support each use case. This eliminates the need to license and implement broader products, like the module Enterprise Management.
Since I have GRC 6.0, I don't need a new license key for GRC 6.1.
FICTION: The RSA Archer GRC 6.1 Upgrade Process also applies for those that are using GRC 6.0. GRC 6.0 offerings were still leveraging the "Module" licenses. Those licenses will need to be converted to the new "Use Case" licenses. Please review the Upgrade Process for the full process and then contact your Account Representative if you have any questions.
Speaking of Enterprise Management, I’ve heard that it will no longer be available.
FACT and FICTION: RSA Archer will no longer sell the Enterprise Management “Module.” However, the functionality available in the Enterprise Management module has been integrated into individual use cases; therefore the capabilities for managing your business hierarchy or operational infrastructure are available where applicable for each use case.
RSA Archer Focused Solutions will no longer be supported.
FACT: On January 1, 2016, RSA moved all applications and integrations classified as RSA Archer Focused Solutions to the new RSA Link Community. While RSA is discontinuing sales and development of these products, we will continue to make them available to RSA Archer customers on RSA Link as non-RSA supported products. RSA will follow the standard End of Primary Support (EOPS) policies as outlined on RSA Link.
I heard that I can apply my GRC 6.1 license to my GRC 5.x environment.
FICTION: DO NOT APPLY your license key for GRC 6.1 to your GRC 5.x environment. To do so could result in the loss of data. Your GRC 6.1 license key will be created based on the new use case packaging.
We also strongly recommend backing up your existing GRC 5.x environment before beginning the GRC 6.1 upgrade process.
RSA Archer GRC Platform 5.3 SP1 is the minimum required version of the Platform that will allow me to upgrade to GRC 6.1.
FACT: RSA Archer GRC Platform 5.3 SP1 is the minimum required version to upgrade to GRC 6.1. If you are using an earlier version of the Platform, you will need to upgrade first to RSA Archer GRC Platform 5.3 SP1 or higher before initiating the upgrade process to RSA Archer GRC Platform 6.1.
I heard that GRC 6.1 changes the Platform’s Task Management capabilities?
FACT: The RSA Archer GRC Platform 6.1 Installer updates existing Task Management fields in order to support the new Task-Driven Landing Screen. Some fields that were previously optional are now required fields. Minor remediation may be required. Please refer to the RSA Archer GRC Platform release 6.0 and release 6.1 Release Notes for more information.
When I upgrade to GRC 6.1, I will need to immediately update all of my applications to work with the Advanced Workflow capabilities.
FICTION: While it is true that RSA Archer GRC Platform 6.x introduces new Advanced Workflow capabilities, the existing Platform 5.x basic Workflow and Data Driven Event (DDE) logic will continue to work as is with GRC 6.1. There is no need to immediately convert your existing applications to use the Advanced Workflow capability.
If your organization is interested in applying one of the new use case packages that is making use of Advanced Workflow (Operational Risk Management, Issues Management, and/or Business Impact Analysis) over an existing use case/module enabled with the basic 5.x Workflow engine, additional work will be required. Further information about how to configure advanced workflow is included in the 6.1 release materials and online help.
My existing APIs will work with GRC 6.1.
FACT: Custom public API integrations will continue to work when you upgrade to RSA Archer GRC Platform 6.1. Custom coded objects are not a part of the release certification process; therefore, we cannot guarantee they will work upon upgrading, as they may require some adjustments.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.