A Risk Register is Not the First Step in Your Archer Journey

By Eric Noonan • January 26, 2016

Due to the way the RSA Archer product is sold, customers often find themselves the proud owners of the Risk Management module.  Side-by-side with the Enterprise, Policy, and Compliance modules, Risk Management is marketed as a necessary and important module to tackle in the initial phase of the Archer journey.  As professional services providers, clients often ask CyberSheath to assist them with the creation of a risk register as their first step with Archer because it is something they have heard they need to do.

A Risk Register as a First Step is Not the Answer

The problem is that the majority of new Archer customers that we have partnered with are in the information security field, where actual threats and incidents consume every working hour.  The daily realities of malware, vulnerabilities, exception requests, business needs, and compliance requirements take up more than enough of a security team’s time each month for them to be prioritizing a risk register as their first GRC capability.

In today’s fast-paced and dynamic cybersecurity world, a risk register managed by the security team seems almost a quaint and antiquated concept.  I cringe at the memories of my life in a large corporation before CyberSheath, where someone from corporate would take weeks and months to hold working groups, developing a risk register and asking us all about our thoughts on the likelihood and impact of a tsunami hitting our Austin, Texas data center.  At the time, my thoughts and efforts were instead concentrated on actual cyber events happening right then and how we were responding to them both tactically and strategically.

What NIST Recommends Your First Steps Should Be

NIST 800-37 Guide for Applying the Risk Management Framework to Federal Information Systems does not mention the term “Risk Register,” not even once.  In fact, the steps in the RMF Process are now clearly focused on control definition and assessment:

  • RMF Step 1: Categorize Information System
  • RMF Step 2: Select Security Controls
  • RMF Step 3: Implement Security Controls
  • RMF Step 4: Assess Security Controls
  • RMF Step 5: Authorize Information System
  • RMF Step 6: Monitor Security Controls

The RSA Archer Risk Management Module does have a place and is valuable for mature organizations. However, it is best managed at a corporate, non-security level, assessing business risk, and only after significant Archer groundwork has been completed to map out governance.

For commercial information security organizations, the prioritized modules that provide the most value to the security team, in order are:

  • Enterprise Management
  • Policy Management
  • Compliance Management
  • Threat (Vulnerability) Management
  • Vendor Security Management

How Can CyberSheath Help Your Organization?

These modules provide structure, process, metrics, visibility, and accountability that can be used to gain a true picture of the effectiveness and maturity of the security organization.  At CyberSheath, we know cybersecurity processes first, and we use that knowledge and experience to help our partners get real value from Archer.

Cybersheath Blog

3 Reasons Why You Need a Privileged Access Risk Assessment

A privileged account is one used by administrators to log in to servers, networks, firewalls, databases, applications, cloud services and other systems used by your organization. These accounts give enhanced permissions that allow the privileged user to access sensitive data or modify key system functions, among other things. You can…

Incident Response – Learning the Lesson of Lessons Learned

“Those who do not learn from history are condemned to repeat it.” Over the years, variations of this famous quote have been spoken by everyone from philosophers to world leaders. The message — that we must learn from our mistakes or continue to repeat them — is also highly relevant…

What is DFARS 252.204-7012 and NIST SP 800-171?

With the Department of Defense (DoD) promising the release of an update to NIST Special Publication 800-171, it is imperative defense contractors understand what DFARS 252.204-7012 and NIST SP 800-171 Clause is and how noncompliance with the Clause will impact their business.  Compliance is mandatory for contractors doing business with…

Our Trusted Partners

Cyberark McAfee Thycotic RSA Tenable Alien Vault Alert Logic Trace Security