Archer 6.2 is RSA’s latest Archer Platform version. The move from 5.X to this version brings some pretty big (and mostly desirable) changes. RSA advertises the best of these: new modules such as Operational Risk Management, new functionality such as CSA/rCSA/pRCSA, and new features such as Advanced Workflow, which is baked into new versions of applications including some foundational ones like those in the Issue Management solution (Findings, Remediation Plans, and Exception Requests).
If you are standing up a new Archer environment on 6.2 there’s some good news. Depending on your license, you’ll get all the 6.X components and features right out of the box. If you’re upgrading a 5.5 database, however, it’s a different story.
We at GRCential have learned first hand through multiple 5.5 to 6.X upgrades, that if a 5.5 database is involved in the upgrade to 6.X, even if your license includes them you WILL NOT receive new 6.X modules like Operational Risk Management, and your applications WILL NOT receive updated features like advanced workflow. I know what you’re thinking, “Huh? Why would that be?”. The answer is simple: because in order to receive features like Advanced Workflow, you need to receive the new versions of your applications. If that were to happen on upgrade, all your 5.X customizations would be lost. Similarly, new modules like Operational Risk Management have new versions of some of those old applications. Rather than overwrite them, RSA decided to just disable it from showing up at all after a 5.5 upgrade.
What does this mean to you? Upgrading Archer from 5.5 to 6.X is a multi-step process that requires careful planning. There is a balance
between retaining all 5.5 customizations and obtaining new 6.X features and functionality that must be carefully planned and executed, and unfortunately that means there’s a lot of work involved.