To fill the gap in assessing and auditing compliance, should we seek technical people or people who understand and work in technology? The answer is detail-oriented professionals who communicate well and value standards, guidelines, and baselines.
I’m describing cybersecurity and privacy governance, risk, and compliance practitioners. Or am I?
Governance, Risk, and Compliance (GRC) work is expanding in importance, scope, and purpose. Regulations are changing, and new technologies loom. Where are we going to find the necessary workers who can assess, audit, document, communicate, and (where appropriate) guide?
I propose that the answer is Technical Business Analysts.
Information
Technical Business Analysts transform data into information and knowledge. They excel at blending technology, technical concepts, and problem-solving, using their skills to fully identify a problem and formulate a proposed solution. Often, business analysts work in requirements gathering for software and process projects, and this exercise is similar to eliciting information about an organization’s policies, procedures, and other types of practices as they relate to a compliance project. As such, the work is similar; both operational paths are half people, half technology. Each requires expertise in data and understanding how it’s used…and the people who use it.
Communication
Whenever people and technology meet, there’s an extra chance for misunderstanding and miscommunication. Communication between at least two people is already fraught with assumptions and lack of confirmation. Add technical terms, unwanted additional work, and fear into the mix with an audit or assessment.
Technical business analysts navigate this situation well as change management agents. Often workers neither want nor understand the changes the organization’s seeking to make. There’s also cross-functional work required to move projects forward, and the people involved on these teams vary in their knowledge and application of technology. The description of these components and situations should seem familiar when discussion governance, risk, and compliance work as well.
Standards and Frameworks
There’s structure to successful business analysis. Stated assumptions that are then tested. Documentation. Knowledge of when to move to the next section…or not. Whether frameworks are formalized and distributed or internal, there are frameworks involved.
Frameworks are the center of GRC discussion, whether they are guidelines or strict in compliance basis. Technical business analysts can both understand and appreciate cybersecurity frameworks with training.
Show Me the Gaps
Gap analysis is the core of business analysis. I’m in place A – Chattanooga. I need to be in place B – Atlanta. How do I get there? What are those gaps?
At the core of change management is a deep look into existing versus desired state. The technical business analyst reviews the factors that block the transformation as well as those that are known but difficult.
With those known factors of as-is and desired state, professional business analysts do their work to define the detailed path.
The gaps are simpler and better defined for as-is and to-be in cybersecurity when using standards and frameworks. Once the analyst is trained on the framework and assessment/audit procedures, the rest of the work has a familiar cadence and knowledge of success.
Document, Iterate, Document
Do business analysts understand the need for the skill to produce clear, concise documentation? Why, yes, they do! That need’s present in all forms of business practices, but never is it more necessary than in efforts to change.
Governance, risk, and compliance is all about managing the risk of change (or staying stagnant…while everything else changes around you, so…change). How does an organisation manage change? It manages the reasons and desired outcomes and documents the journey, both the stops and the map of the path. Who does the work? People with technical business analysis skills.
The documentation needs in governance, risk, and compliance rival those (and likely surpass) of functional and technical specifications and lessons learned documentation. The structure of the documentation will be familiar as well. It’s purpose-driven communication. Future work will rely on this documentation.
Analysis, Risk, and a Path
Requirements gathering and GRC assessment and auditing work both involve structured, stakeholder-driven processes so that the person or doing the work understands needs, identifies and documents gaps, and also documents actionable outcomes. While requirements gathering focuses on building systems to meet business needs, GRC assessments ensure organizations operate securely and compliantly. The underlying methodologies and mindsets are closely aligned, and salary data I analyzed looks to be comparable.
So, what’s the issue? Will organisations be willing to provide a bit of training on frameworks and cybersecurity in general in order to broaden their qualified application pool? Will technical business analysts seize this opportunity and seek that training on their own to solidify their careers?
I hope the answer to both is “yes,” as the work is both growing and waiting in the governance, risk, and compliance field.
