Top GRC Questions & Issues

The San Jose GRC Fundamentals, Strategy, & Technology bootcamp is underway with terrific interaction. The bootcamp is comprised of implementers of large down to medium sized organizations, professional service firms, and a few technology providers.

The top questions/issues that the attendees are trying to resolve over the course of three days are (coming directly from them):
  • New SEC Disclosure requirements (coming to bear in February 2010) that require statements of board responsibility for risk oversight
  • GRC is complicated – how do you make sense of all of it.
  • What have others implemented, and what are the tasks and steps to start a GRC strategy
  • How do align and optimize GRC to business processes and performance
  • How do you make GRC relevant to the line of business
  • Overview of the broad GRC environment within large corporations and how different roles work together
  • Bringing OCEG content and training to Europe
  • Global issues impacting GRC in large distributed organizations
  • How large organizations strategize to approach GRC from the board down
  • How do GRC solutions deliver value and how do you approach and define the GRC technology market
  • Seeing more adoption of GRC and ERM – what are the differences
  • What are the board responsibilities and communications related to GRC
  • There is a disconnect within a specific organization on what to achieve – how do you overcome different factions and control issues within GRC strategies
  • How do you know if your GRC strategy is effective and providing value to the organization
  • A new organization implementing GRC wants to understand how do they accelerate maturity so that GRC success and value does not take years to realize
Great interaction and discussion so far. Sorry that most of you have to miss it – though please comment on your thoughts to the top GRC Questions & Issues.
 
The Atlanta and Chicago Bootcamps are coming up soon (Atlanta registration closes in a few days). We will be doing one in Europe this summer as well as more across the US.
 
Events Hosted By Corporate Integrity, LLC

GRC BOOTCAMP Atlanta: GRC Fundamentals, Strategy, & Technology

Wednesday, February 17, 2010 at 8:00 AM Friday, February 19, 2010 at 5:00 PM (ET)

Atlanta, GA | TWELVE Atlantic Station

WORKSHOP: Effective Policy Management & Communication

Wednesday, February 24, 2010 from 8:00 AM – 5:00 AM (CT)

Delafield, WI | The Delafield Hotel

WORKSHOP: Developing a Risk Assessment & Management Process

Wednesday, March 31, 2010 from 8:00 AM – 5:00 AM (CT)

Delafield, WI | The Delafield Hotel

GRC BOOTCAMP Chicago: GRC Fundamentals, Strategy, & Technology

Wednesday, April 21, 2010 at 8:00 AM Friday, April 23, 2010 at 5:00 AM (CT)

Chicago, IL | The Ambassador East Hotel

 

BPS & Resolver – Synergetic Merger

2010 is proving to be an interesting year for the reorganization of the GRC space. It kicked off with the public announcement of the EMC/RSA acquisition of Archer Technologies. Shortly thereafter you had the announcement of the merger of BPS and Resolver.

 
The merger of BPS and Resolver is intriguing. Unlike the acquisition of Archer in which you had a good size organization acquiring a smaller one, with the merger of BPS and Resolver it is two smaller organizations recognizing their symbiotic strengths to produce a stronger and compelling offering.
 
A GRC merger of this nature makes a lot of sense. Together they have hundreds of clients ranging from the mid-market up into the global enterprise. They now have a combination that delivers both traditional software as well as cloud/SaaS solution. The risk scoring technologies of Resolver expand the risk management capabilities of BPS. The audit management capabilities of BPS expand capabilities for Resolver. They bring together an offering that spans organizations size, industry, and needs. With both of their headquarters in Toronto provides further synergies and less upheaval for this integration. Though there are still areas that the combined organization does not deliver – such as policy management.
 
Expect 2010 to bring many more acquisitions similar to BPS and Resolver as well as those like EMC/RSA and Archer. There are a lot of closed door discussions happening right now as well as some firms looking at significant roll-up and integration strategies with a variety of players.

CCEP – Certified Compliance & Ethics Professional

I just passed the Certified Compliance & Ethics Professional (CCEP) exam from the Society of Corporate Compliance & Ethics (SCCE). While I meant to do this years a go – I never got around to it.

 
The certification requires so many years of professional experience and training. While many assume that you have to go to the official CCEP class . . . this is not true.
 
The exam (I cannot talk about the content because of the fine print) actually was much easier than I anticipated: which is a disappointment. I spent one hour preparing for the test. That is right, one hour. I reviewed the Compliance 101 book from SCCE ($60 for a 100 page paperback book) and the large binder The Complete Compliance and Ethics Manual ($315). I whipped through both skimming sections in one hour. For the price tag – very disappointed. The Compliance 101 book is enough. It takes the meat out of The Complete Compliance and Ethics Manual and reprints it in a small paperback. Most of the large binder is printouts of various regulations and guidance that is freely available.
 
With one hour of quick study I took the exam. I got 93 questions correct out of 100.
 
Of course much of this could be because of my experience in the compliance world for many years as well as a law degree – but I thought it would be more challenging than it was. The added process of professional experience and documented learning help provide more credibility to the certification.
 
No matter what – it is a good exam to test basic compliance knowledge and understanding from a United States perspective. It currently has limited value from an International perspective. So if you think you know compliance – I suggest taking it and testing your experience and knowledge. If you have a few years dealing with corporate compliance issues it should not be a problem.

Corporate Policies in Disarray and Chaos

 

Policies are a critical component of a GRC strategy – but often the most overlooked or neglected component. It amazes me the number of companies I go into that have complete disarray and chaos in their approach to managing corporate policies and procedures.

Simply put – organizations cannot ignore policy management. Consider that:

  • Policies establish the culture, value, ethics, and tone of the organization.
  • Policies establish boundaries for risk taking.
  • Policies define how the organization complies with regulations and requirements.

Mismanagement of policies and procedures can introduce liability to the organization as a policy or procedure can establish a duty of care. Improper policy management can be used by regulators, prosecuting/plaintiff attorneys, and others to place culpability on an organization.

The typical organization suffers with ineffective policies, management, and communication. The typical organization has:

  • Policies scattered across dozens of places. The typical organization has numerous portals and binders in which policies are published. There is no single authoritative source where all policies and procedures are consolidated, maintained, and managed. There is no place where an individual can see all the policies that apply to their specific role in the organization.
  • Policies bound by paper. The typical organization still suffers with having numerous printed policy manuals and has not fully embraced online publishing and access to policies and procedures.
  • Policies grossly out of date. The typical organization has policies that are published at some point and time and not reviewed on a regular basis. In fact, I regularly encounter organizations that have policies that have not been reviewed in years for applicability, appropriateness, and effectiveness.
  • Policies that lack an owner. The typical organization has numerous policies and procedures that lack an owner that is responsible for managing them and keeping them current.
  • Policies that lack any lifecycle management. The typical organization has an ad hoc approach to writing, approving, and maintaining policies with no defined system for managing the workflow, tasks, versions, and approval process.
  • Policies that do not map to exceptions or incidents. The typical organization finds that it has no established system to document and manage exceptions to policies. Further, there is a lack of a system to map incidents, issues, and investigations to policies – this helps to understand where policies are breaking down and need to be addressed.
  • Policies lack adherence to a consistent style guide. The typical organization has policies scattered across the organization with no through to the consistency, style, and template as to how they are written. The language and format of policies vary significantly within organization policies and procedures.

These issues are further compounded when organizations approach technology for policy management in an ad hoc manner and begin publishing policies through various content management systems (e.g., SharePoint sites) with no process to manage consolidate, manage, and keep policies consistent.

In summary, organizations are in a complete disarray in managing corporate policies and procedures – policies are out-dated, scattered across parts of the business, and not managed consistently. The recent trend in legislation and regulatory guidance is to demonstrate training and not just attestation. Policies establish the culture, values, ethics, and duties of the corporation and its agents. Organizations that take an ad hoc approach to managing and communicating policies face significant risk to their business.

When the organization is under the microscope – having a detailed trail of what policy was in effect, how it was communicated, who read it, who was trained on it, who attested to it, what exceptions were granted, what other incidents violated the policies all can provide grounds for defending the organizations. An ad hoc ‘dust in the wind’ approach to policy management may very well expose the organization to significant liability.

To consistently manage and communicate policies organizations are turning toward defined processes, workflow, and technologies to manage the lifecycle of policies. The policy management lifecycle involves several stages from definition, approval, communication, awareness, training, attestation, maintenance, and archiving. This is supported by a technology infrastructure to manage the content and process of policy management.

In the generation of Web 2.0 and YouTube it is no longer enough to simply make policies available, organizations need to deliver training and establish that individuals understand policies and procedures. Delivering interactive policy training modules has become just as important as presenting a written policy and tracking attestations.

Over the next several weeks we will look at Effective Policy Management and Communication. We will specifically explore:

  • Defining a process lifecycle for managing policies
  • Establishing policy ownership and accountability
  • Providing consistency in policies through consistent style and language
  • Communicating policies across extended business relationships
  • Tracking policies attestation and delivering effective training
  • Monitoring metrics to establish effectiveness and/or issues with policies
  • Relating policy management to risk, issue/case, and other GRC areas
  • Using technology to manage and communicate policies

In addition to this series on policy management, Corporate Integrity is also offering a full-day workshop on the topic of Effective Policy Management and Communication.

I would love to hear your thoughts, experiences, and approaches to effective policy management.

GRC Reference Architecture: Industry, Geographic, & Technology Views

 

Over the past few months we have explored together the various components of my GRC Reference Architecture. This embodies the technology end of my broader GRC EcoSystem – which to date has over 1300 technology providers, professional service firms, and content providers of GRC cataloged into the GRC market.

The components of the GRC Reference Architecture that we have looked at to date include:

  1. GRC Enterprise Data Architecture and Framework,
  2. GRC Enterprise Architecture Application Core, and
  3. GRC Business Process/Role Specific Applications.

Today we conclude the GRC Reference Architecture series with a quick overview of the industry, geographic, and technology views of applications aimed to help manage risk and compliance and broader GRC.

There are a variety of contexts for GRC initiatives within organizations. Some are focused on putting out specific fires, dealing with particular issues, meeting a requirement, or managing a solitary risk area. Others are focused broadly on driving agility, consistency, efficiency, transparency, and accountability across a range of GRC processes. This generates the demand for both enterprise GRC applications as well as business process/role specific GRC applications. This get’s further dissected into applications that aim to help organizations achieve compliance or manage risk in other areas such as:

  • Industry specific issues. There are a range of solutions on the market that help specific industry verticals with the GRC related issues they face. In my analysis of the market and catalog of vendors you have dozens of technologies aimed at managing GxP compliance in life sciences, many focused on the complexity of managing credit/market/operational risk in financial services, there are a few focused on things such as Medicare/Medicaid RAC audits, even to the point of one vendor that manages compliance for car dealerships to state car sales laws. The point is that not every risk or compliance application is focused to solve every GRC issue for every industry. There are a variety of very specific GRC solutions aimed to help solve industry specific GRC issues. Even broad cross-industry GRC technology providers may have all the bells and whistles to help with industry specific issues – but they need to know what they are up against and how to solve client issues.
  • Geographic specific issues. Another way to approach the GRC market is to understand the geographic reach of a vendor. There are vendors that have a very broad GRC solution that spans industries – but they only have language support or operations in specific localities. Further, there are GRC vendors that market and sell a solution for a specific geography to deal with laws and regulations, or to manage risk, within that jurisdiction.

Putting it together . . . with the GRC Reference Architecture you are able to map a vendor to what it provides for functionality – enterprise and/or business role specific as well as industry and geographic specific solutions. These work in harmony together to define what a vendor is about. One technology solution might offer enterprise GRC capabilities in risk, policy, and audit management but really is successful at selling into the IT role. Another vendor might have a very focused solution for dealing with Medicare/Medicaid RAC audits in health care within the United states.

The final way of looking at the GRC technology landscape through the reference architecture is to understand a solution’s technical capabilities. This involves understanding the technology building blocks that makes the solution work. Specific technology capabilities include the solution’s features for:

  • Content management
  • Process management
  • Workflow management
  • Survey & assessment management
  • Collaboration management
  • Project & resource management
  • Business intelligence
  • Dash boarding & reporting
  • Business rule engine
  • Enterprise application support
  • Enterprise integration capabilities
  • Learning & training management
  • Security architecture
  • Identity, role, and access management
  • Storage & retention architecture
  • Enterprise asset management
  • XML & data feed integration
  • Configuration & change management
  • System log management
  • Records management & Retention

This concludes our high-level look at the GRC Reference Architecture. I would encourage you to review the several related newsletters and blog posts and provide feedback as I put this into a written document to be published in the next month. You may comment on my blog or send me an e-mail.

The next step, besides publishing under the Corporate Integrity name, is to integrate this into the OCEG GRC Technology Blueprint which is in revision to be finalized with these changes in the next few weeks. This is meant to be a resource in framing the variety of GRC solutions on the market today and be a guide to vendors looking for solutions to their governance, risk, and compliance problems.

Beginning next week I turn the newsletter to a new topic of looking at the disarray of policies within organizations and ways to improve policy life cycle management and management.

2010 GRC Research Agenda & Education

 

Happy New Year! I trust that 2010 will bring you success and direction in your personal and professional life.

First I need to state a deep thank you to all of my subscribers that have reached out to me over the past several weeks with your sympathy and prayers for my family as my father passed away. I am amazed and overwhelmed with emotion at the number of personal comforts and encouragements you have given when most of us only connect on a professional level. My father’s struggle with cancer came on suddenly at the end of May and already in June the Doctor’s only gave him two weeks to live. Two weeks turned into six months – from which we are grateful. I spent more quality time with my dad (traveling to Seattle) than I ever have – cherished memories. My clients have been great – I had to reschedule the San Jose GRC Bootcamp (I was in San Jose for it when I learned of his passing) and everyone attendee was encouraging and open to rescheduling. I have some of the greatest clients in the world!

My purpose of this newsletter is to communicate my upcoming research agenda and direction in 2010.

The GRC market in 2010 is already proving to be interesting – particularly with the EMC/RSA acquisition of Archer. I am already seeing a lot of interaction from large Fortune 1000 companies down into small to medium sized organizations to define a GRC strategy and resolve cumbersome risk and compliance processes. There will be a lot of consolidation of the market in 2010.

The greatest shift is that I am doing more training and education worskhops/bootcamps. Since first creating the GRC market (eight years back) I have been continually frustrated in the lack of good GRC training and understanding on what it is. I continue to partner with OCEG to provide the best risk, compliance, and broad GRC training available. This is being offered in three day bootcamps, as well as very topic specific workshops (e.g., policy management, risk management).

I am kicking off the New Year with my Online Workshop: 2010 GRC Drivers, Trends, & Market Directions. In this workshop I am communicating the shape, size, and direction of the GRC market as well as best practices, approaches, and trends in a two-hour online format.

As for my upcoming research agenda:

  • GRC Reference Architecture. Representing the Technology end of my GRC EcoSystem, the GRC Reference Architecture will be wrapped up in blog/newsletter format this week with another newsletter coming into your inbox on the business/role specific GRC applications. I will tie all of this together in a Corporate Integrity research piece on the GRC Reference Architecture by the end of January and will incorporate this into the revised OCEG GRC IT Blueprint as well for review and approval by the OCEG Technology Council.
  • Investigations Management. I have been working for the past three months on research covering investigations management platforms – the market, players, feature/functionality, and best practices in investigations management. I originally planned to publish this by the end of December but my family circumstances put this into January. This will be published in the next month as well.
  • Policy Management. After I wrap up the GRC Reference Architecture newsletter this week I will begin a newsletter series on effective management and communication of policies across the organization. This ties into the full-day workshop training I am doing on this subject at the end of February. I am also working on a book on policy management in 2010.
  • 3rd Party/Supply-Chain/Vendor Risk Management. In a few months I am going to take up the topic of managin risk and compliance across extended business relationships. This area has been keeping me very busy for the past two years and want to do more writing on this topic.
  • Risk Management and ISO 31000. With the release of ISO 31000 I plan on doing more writing, expository, and training on risk management to align with this important standard in 2010.
  • Economic Value Proposition of GRC. 2010 will also bring more focus of my research on the economic justification and reasoning for GRC processes and solutions. I am frustrated with the amount of money companies waste on manual, paper-based efforts for GRC or ones that are encumbered by email instead of workflow and spreadsheets for assessments that have no integrity, audit trail, or scalability. GRC processes and solutions make sense because they improve business agility, consistency, efficiency, transparency, and accountability.

My upcoming 2010 events (those that are planned out to date for the next few months) are as follows:

ONLINE WORKSHOP: 2010 GRC Drivers, Trends, & Market Directions

Thursday, January 14, 2010 from 11:00 AM – 1:00 PM (CT)

 

OCEG BOOTCAMP San Jose: GRC Fundamentals, Strategy, & Technology

Wednesday, January 27, 2010 at 8:00 AM – Friday, January 29, 2010 at 5:00 PM (ET) San Jose, CA | Hotel Valencia Santana Row

 

OCEG BOOTCAMP Atlanta: GRC Fundamentals, Strategy, & Technology

Wednesday, February 17, 2010 at 8:00 AM – Friday, February 19, 2010 at 5:00 PM (ET) Atlanta, GA | TWELVE Atlantic Station

 

WORKSHOP: Effective Policy Management & Communication

Wednesday, February 24, 2010 from 8:00 AM – 5:00 AM (CT) Delafield, WI | The Delafield Ho
tel

WORKSHOP: Developing a Risk Assessment & Management Process

Wednesday, March 31, 2010 from 8:00 AM – 5:00 AM (CT) Delafield, WI | The Delafield Hotel

 

OCEG BOOTCAMP Chicago: GRC Fundamentals, Strategy, & Technology

Wednesday, April 21, 2010 at 8:00 AM – Friday, April 23, 2010 at 5:00 AM (CT) Chicago, IL | The Ambassador East Hotel

Additionally, my social networking has continued to increase. This newsletter goes out to over 6,000 subscribers. My Corporate Integrity LinkedIN Group now has nearly 1900 members. And I have over 650 followers on Twitter. And my blog continues to get significant traction and reference.

That concludes my 2010 update – now back to serious GRC strategic planning and work

EMC/RSA Acquisition of Archer: 1 + 1 = 3

For the past two years Archer Technologies has been a disruptive force in the GRC market. They have been going strong in the IT/information security segment of GRC for several years – but the past two years has shown them to be a formidable competitor in what is referred to as the enterprise GRC (eGRC) market.

 
I have noticed as GRC buyers have repeatedly been impressed in the RFP process by Archer as well as much of the inquiry and questions from competitors who did not see Archer coming.
 
Archer has done particularly well in reaching large Fortune 1000 companies that need a platform that can be adapted and configured to different GRC related processes. When it comes to flexibility of the platform – Archer wins almost every deal. On the downside, Archer hasloses some deals by not having deeper risk analytics and modeling. There strength is in customization, workflow, and modularity of their platform.
 
Archer has also done very well with their GRC Exchange (similar to Salesforce.com AppExchange) direction – taking the cloud computing content to GRC. With that they have also tied content and services into the exchange in addition to application modules. They also are excellent at partnering with their clients and making the client feel ownership in Archer.
 
Enter EMC/RSA . . . this is a deal that makes complete sense. RSA needs the IT GRC capabilities that Archer delivers, and Archer can use the breadth of products and resources that the RSA (security division) of EMC brings. This further strengthens EMC with an eGRC strategy – to date it has been largely centered on a build it yourself approach with Documentum. With Archer, EMC can deliver an enterprise/eGRC solution for its clients that is established and can integrate into the Documentum environment. The synergies in this acquisition are truly remarkable.
 
However, the downside happens if EMC does not allow Archer the freedom and flexibility to be an eGRC platform. Archer is part of the RSA Security Division of EMC which may mean it gets locked into a perception of remaining an IT GRC player with limited eGRC capabilities. EMC should address this by making sure that Archer is perceived as being part of EMC itself and not just an extension of RSA’s security products.
 
This is the first acquisition of 2010 in the GRC space with a lot more to come. There is a lot of interest and activity in this space, we can fully expect a lot of consolidation and realignment of the GRC space over the next year.

Enhancing Business Performance through Risk Management

 

The following is an abstract from my latest research piece “Enhancing Business Performance through Risk Management

While the market seems eager to grasp onto the phrase “risk intelligence,” it means nothing if corporations cannot take action on the intelligence it provides. Being intelligent is not the same as being wise – most organizations lack both risk intelligence and wisdom. There are organizations that acquire a lot of information, but without transforming this information into knowledge by understanding the context of their business risks, they fail to make better business decisions. Risk is often completely disconnected from business strategy, objective, and performance management.

 

Risk management requires the proper context across the entire culture of an organization. The only way an organization can manage risk appropriately is if acceptable and unacceptable risk tolerances and appetites are defined and managed. The culture of risk tolerance at all levels helps formulate these tolerances: This is where risk management relies on governance. The board and management must clearly define and communicate the organization’s culture of confronting risk. If the governance function does not do this, risk strategy is left up to individuals and the integrity of the organization is in jeopardy.

A mature risk-management program does not operate in isolation from the business. A mature risk-management program is integrated with corporate performance, strategy, and objective management. This requires that the organization relate performance to risk, allows for multiple inputs impacting the risk environment from both internal and external contexts, and has a variety of ways to look at risk information to analyze, model, and relate risk back to performance and strategy.

Effective and mature risk management delivers:

  • Alignment of risk in the context of business strategy. Risk strategy is fully integrated with business strategy where business management realizes risk management is an integral part of business responsibilities.
  • Risk intelligent business decision-making. Risk-management culture and policies are effectively applied across the organization, supported by management. The business has what they need to make risk-intelligent business decisions.
  • Risk-based business planning. Risk is a key component in business planning. Risk assessments and reports are structured to complement the lifecycle of the business to help executives and the board make effective decisions.
  • Establishment of risk culture and policy. Risk policy is clearly communicated across the business and is effective at establishing a culture of risk management. Risk policies are current, reviewed and audited on a regular basis.
  • A risk appetite harmonized with business strategy. Risk appetite and tolerance levels are established and reviewed. They are mapped over to business performance and objectives.
  • Integration of risk and performance monitoring and metrics. Defined KRIs are in place and appropriate mapped to business KPIs. Risk indicators have established limits/thresholds, and are defined at all levels of the business, its operations, and relationships.
  • Communication of business relevant risk information. Risk reporting and indicators are relevant to the business and effectively communicated. Risk information adheres to information quality, integrity, relevance, and timeliness to the business.
  • Ownership of risk within the business. Every risk, both at the enterprise as well as business process level, has clearly established risk owners. These owners represent roles that can take action on the risk.
  • Holistic awareness of the range of risks the organization faces. The organization has defined risk taxonomy at the enterprise level which drills down into specific risk areas. A regular process is in place for risk identification to keep the taxonomy current. Various risk frameworks used across the enterprise are harmonized into an enterprise risk framework.
  • Multi-perspective risk analysis. The organization uses a range of risk correlation, stress testing, and scenario analysis. Various qualitative and quantitative risk analysis techniques are in place and the organization has an understanding of its historical loss to feed into analysis.
  • Effective risk treatment in context of business objectives and strategy. Risk treatment plans – whether acceptance, avoidance, mitigation, or transfer – are in place and monitored for progress. Audit functions conduct regular reviews. The solution reviews risk-treatment plans.
  • Governance of risk from the board down into the business. The organization has a role and system in place to aggregate risk information across the business and effectively communicate, monitor, and manage risk. There is effective communication and accountability for risk oversight at the board of director’s level.
  • Visibility of risk as it relates to performance and strategy across the business. An enterprise view of risk is in place and maps over to corporate performance and strategy. Risk is effectively communicated to stakeholders and the organizations track record shows successful taking and management of risk.
    Consistent ranking and measurement of risk. Risk is categorized and structured according to its impact on business strategy, performance, and optimization.

Successful organizations face the challenge to move from immature to mature approaches to risk management. Immature risk-management programs operate in silos and are disconnected from each other: no consistency or efficiency is gained. Many ERM programs are not much better than this, as they are nothing more than an enhanced SOX strategy, focusing on a slightly expanded view of financial and other internal controls. A mature risk-management program is a seamless part of business performance, strategy, and objective management. Risk must be managed within the context of business. This requires the organization to take a top-down view of risk led by the executives and board, and make it part of the fabric of business, not an unattached layer of oversight.

 

GRC Reference Architecture: Role/Process Specific Applications

 

Over the past few weeks we have looked at both theinformation model and the enterprise application core of Corporate Integrity’s GRC Reference Architecture. The GRC Reference Architecture provides the framework to approach technology, classify software offerings, and is part of my broader GRC EcoSystem (which includes over 1300 technology, professional service, and information providers). The GRC Reference Architecture represents the core to the revisions to the OCEG GRC IT Blueprint to be released by the end of this year. Your feedback is appreciated.

 

We now turn to the next component of the GRC Reference Architecture – the business role/function specific applications. These are the applications that are predominantly focused to meet the needs of a specific business function, process, or role in the enterprise. Applications in this area may very well have significant risk and compliance relevance as well as impact on the enterprise – but they are 80% or more used to a specific subset of GRC user roles. The enterprise application core that we previously discussed represents applications that span GRC business users/roles across the business.

 

The various business roles and functions that have specific uses of GRC technologies and applications are scattered across the enterprise. In one sense, every part of the business touches on GRC as it relates to different aspects of performance, risk, compliance, values, and control.

 

The primary, but not all inclusive, business function/role application categories include:

 

  • Audit. While audit is a broader part of the enterprise application core of GRC, audit also maintains its own category of role specific applications dealing with assurance, audit management (e.g., calendaring, resource scheduling, work paper management), as well as audit analytics and automation.
  • Brand & Reputation Management. This category offers targeted solutions for management the corporation’s brand and reputation – in both the physical world as well as online. This includes brand surveillance management.
  • Business Continuity. From disaster recovery, business continuity, as well as crisis management – all are very relevant to GRC and are solutions that enterprises need to manage and maintain continuity of operations across the business.
  • Business Operations (line of business). The line of business is the front line of GRC. From management of global trade compliance, procurement management, to customer relationship management . . . many aspects of business transactions, interactions, and relationships have relevance to GRC.
  • Corporate Compliance & Ethics. Within corporate compliance and ethics there are solutions aimed at communicating code of conduct, delivering compliance training, as well as whistleblower reporting through hotline/helpline systems.
  • Corporate Secretary. Board and entity management software is the primary vehicle for the corporate secretary role to carry out the function of managing board papers, communications, calendars, and corporate reporting.
  • Corporate Social Responsibility/Sustainability. CSR is a burgeoning and growing field becoming increasingly relevant to organizations around the world. Solutions in this category aim to help monitor emissions and carbon tracking, as well as offering broader GRI (Global Reporting Index) reporting.
  • Environmental, Health, & Safety. EH&S software helps the organization manage and maintain environmental controls as well as the health and safety of individual employees, partners, and clients. Solutions in this space have many offerings from areas like environmental monitoring and reporting to MSDS management.
  • Finance & Accounting. The finance and accounting function focuses on using software to manage risk and compliance within business financial transactions, validates that the organization is managing finance and budgets within boundaries, and monitors finance and treasury risk management. This entire area is often referred to as Finance-GRC.
  • Fraud. The area of fraud management utilizes software for fraud investigations, fraud prevention/management, as well as specific areas such as anti-money laundering.
  • Human Resources. HR issues from hiring practices, discrimination, harassment, wage & hour, compensation, employee privacy, and other areas often carry some of the most significant risk and compliance risks the organization face. While broad HRMS systems have much relevance to GRC, there are specific areas of software that HR leverages to help communicate and prevent issues of risk and compliance such as employee evaluations and surveys, as well as learning/training management solutions.
  • Information Security, Risk, & Compliance. What is often referred to as IT-GRC represents the most expansive domain of software solutions aimed at managing technology and information risk and compliance. This includes areas of threat and vulnerability management, configuration management, identity and access management, encryption, and many other components.
  • Insurance. The role focused on managing insurance and claims management has software specifically aimed to support its function in GRC.
  • Investigations. Part of the broader enterprise GRC application core as well, investigations management software enables the organization to consistently and efficiently intake issues, manage investigations, and record and manage loss across the organization.
  • Legal. The legal department has a variety of technology solutions aimed at supporting the legal role in areas such as matter management, contract management, discovery management, and the management and protection of intellectual property. The terms Legal-GRC and legal process management are starting to be used to identify solutions that bring these components together.
  • Physical Security. Physical security is dependant on many areas of technology for surveillance and physical access systems to protect the organization, and in some areas to comply with laws and regulations.
  • Privacy. A variety of solutions have come to the market specifically aimed at managing privacy programs. These include software focused on information protection, privacy policy communication and training, to incident response and managing disclosure requirements.
  • Quality Management. Quality management systems provide a backbone of managing quality within the line of business – while monitoring and resolving quality and control issues.
  • Risk Management. Risk is a fundamental core to GRC but also has a variety of business roles across the organization. From enterprise risk management software, down into the bowels of many components of operational, geo-political, and financial and treasury risk management software – there are solutions aimed at meet
    ing a variety of specific risk needs.
  • Third-Party/Supply-Chain Management. Risk and compliance issues do not start at the traditional corporate boundaries but carry on to a complex web of business partner and supply chain relationships. Solutions in 3rd party management aim to communicate code of conduct and policies while managing and monitoring risks, compliance, and controls across extended business relationships.

These roles represent a significant but not exhaustive look at the categories of risk and compliance software solutions targeted at specific areas of the business. These applications need to be able to report and feed information into broader GRC reporting systems and dashboards to maintain a 360 degree view of GRC throughout the business. All are very relevant and part of a broad GRC strategy.

 

Further, the discussion and breadth of GRC business/function roles and supporting technologies underline the fact that GRC is a federated effort. There is not one group of the organization that does GRC. While there may be a role leading the collaboration, it really extends throughout the business.

 

Over the next few weeks we will wrap up the initial discussions on the GRC Reference Architecture. The next posting will provide commentary on the geographic and industry specific views of GRC technology, and the final one will look at the technology components/capabilities that GRC solutions are comprised of.

 

Detailed training on the GRC Reference Architecture can be found in Corporate Integrity & OCEG’s GRC Strategy & Technology Bootcamps.

Good Risk Management Guidance – Here At Last in ISO 31000

We interrupt this broadcast . . . yes, I know many of you have been waiting in eager participation for my next installment of the GRC Reference Architecture which is to focus on the application taxonomy of specific business roles/functions that are part of GRC (in previous weeks we looked at the core enterprise GRC data framework and applications). This installment will be out next week. This week something particularly relevant has come up: ISO 31000:2000(E).

The world has an overwhelming menu of standards of all formats and varieties for business to use – navigating them can be difficult. In fact, many standards are inferior and not worth their weight in paper (or bytes if you are like me and keep them on your Amazon Kindle). Then there are exceptions – and ISO 31000 is one of those standards I have been waiting to be finalized for quite some time.

ISO 31000 is the new international standard on Risk Management. As we learn – a good house is build on a solid foundation, ISO 31000’s foundation was largely on the AS/NZS 4360:2004 risk management standard. It has been years as an ISO standard and has now arrived.

Its beauty is its simplicity and adaptability. ISO 31000 provides a risk management approach that can be used across the silos/domains of risk scattered across the organization. It is just as relevant to areas such as legal risk management as it is to information security, quality, or environmental, health & safety.

It is also very concise – just 34 pages! It amazes me that we push children to write papers of a certain length in which they learn bad writing in long sentences and filler language and then turn and tell them to be successful in the real world they need to write concisely (yes this is a long boring sentence). As many of you know – I am NOT an advocate of COSO ERM Integrated Framework. ISO 31000 communicates more practically and adaptability to the organization what it takes the COSO ERM Framework to do in 125 pages of poorly written confusion. I read COSO ERM and am left with no guidance and practical approach to risk management. While inspiring and thought provoking in parts, it lacks the pragmatic simplicity and agility that ISO 31000 delivers.

A few things I particularly like about ISO 31000:

  • Correct definition of risk. ISO 31000 defines risk as the “effect of uncertainty on objectives.” Simple and right to the point. It also allows for different views of risk whether you focus on just avoiding loss to the organization or if you take risk to seek return to the organization.
  • Starts with establishing the context. I see too many risk management programs that are nothing more than SOX on steroids. These programs are encumbered by a myopic view of internal control and context. While the internal context is important, many organizations fail to comprehend the external context business operates in – which introduces significant risk. The context guidance in ISO 31000 provides a holistic approach to make sure the full view of context is set.
  • Monitoring and review is more than a life-cycle. While ISO 31000 loops through monitor and review at the beginning and end of the risk management process it is also part of every stage of the risk management process.
  • Communication and consultation are integrated throughout the process. The risk management function does not own risk, the business owns risk. It is necessary that every stage of the risk management process involve the risk owners.

Of course I have already referenced the simplicity and adaptability of the standard as well.

ISO 31000 is a great source of guidance for anyone developing a risk management program – which is part of an organization’s GRC initiative. From the broader GRC perspective, my favorite guidance is OCEG’s Red Book 2/GRC Capability Model. ISO 31000 (in draft at the time) as well as the AS/NZS 4360:2004 were source documents in developing Red Book. Red Book provides the GRC ‘Rosetta Stone’ which links the various groups of governance, risk, and compliance across the organization into a common collaboration and architecture.

Don’t worry – next week we will get back to the GRC Reference Architecture. In the mean time, for those in the United States, go out and buy yourself a copy of ISO 31000 to read as you digest your Thanksgiving turkey dinner!

Detailed training on the risk management, Red Book, and the GRC Reference Architecture can be found in Corporate Integrity & OCEG’s GRC Strategy & Technology Bootcamps.