- Cybersecurity is now a business enabler that builds trust, wins customers, and reduces innovation risk.
- CISO/vCISO role is shifting from technical operations to board-level strategy, business continuity, and risk management.
- A strategic CISO/vCISO must communicate cybersecurity priorities in business terms to gain C-suite support.
- vCISO services suit SMBs with limited budgets, early programs, or urgent needs and offer scalable access to virtual security teams.
- Choose a vCISO matching your strategic versus tactical needs, industry experience, communication skills, and cultural fit.
This post explains in straightforward terms the process we follow to build an International Organization for Standardization (ISO) 27001 certifiable Information Security Management System (ISMS).
Step 1: Understand Your Scope
The first step towards an ISO 27001 certifiable ISMS is to understand your organizational context and scope. To develop any kind of information security plan, it’s critical to understand the organization itself, including its business goals and information security expectations.
An easy way to think about this activity is to ask: What information do we need to protect and what are the processes that act on that information?
Understanding the relevant processes will require you to identify and document the people, systems and hard assets (e.g., employees, contractors, vendors, hardware, software, physical offices, data centers, networks, etc., etc.) that support those processes.
The easiest way to gather this information is through a series of interviews with an organizational cross-section of “the right people” who know how things work.
Simply put, scoping is about understanding all of the many factors that influence your company’s information related risk and associated risk management decisions.
Step 2: Understand Your Information Security (InfoSec) Controls
A major factor in any information security plan is (no surprise) the strength and maturity of your current information security posture/program. There is quite a bit of overlap between documenting your current “security status” and understanding your organizational scope, as discussed in Step 1. You can gather this information during the scoping process as a “controls understanding/enumeration.”
As you perform this fact-finding activity, the focus is not yet on “assessment” (passing judgement) about how effective an information security control is or isn’t. Instead, it’s about learning what controls are currently in place, and the extent to which they are implemented and operating. As you learn more about your risks starting with Step 3, you’ll be in a better position to assess your controls in the context of your environment.
The easiest way to gather a “controls understanding” is via artifact review (policies, standards, procedures, audit/assessment findings, penetration test results, incident reports, and so on) combined with discussions with your IT and information security staff.
Step 3: Identify and Analyze Information Related Risk
A key element in any information security plan is the risk associated with your information assets, and whether that risk is reduced to a level you are comfortable with. This process is often referred to as risk assessment. It has two components: risk identification and risk analysis.
By the time you go through Steps 1 and 2 to get to this point, you will have already identified a number of risks, even though this wasn’t your explicit intent. In this Step 3, your initial focus should be on identifying all the additional risks to your organization’s information assets. This is the risk identification part of the activity.
Once you have a firm understanding of all the risks, you can then assess and document which risks are currently being managed effectively by information security controls that are already in place, and which are not yet effectively managed. This is the risk analysis part of the activity.
To do a risk assessment, you need to consider the likelihood of a risk being realized, taking into account the information security controls now in place, along with the impact that risk realization would have on your organization. For example, some risks might be unlikely but potentially catastrophic (e.g., exfiltration of your customer database by a competitor). Others might be both likely and damaging (e.g., a ransomware attack if proper controls aren’t in place). Others might be likely but not particularly dangerous (e.g., a reconnaissance/probing attack that your firewall repels).
In a nutshell, risk assessment is the process of identifying the universe of risks to your information assets, and then determining if/which of those risks necessitate improvements to your information security program.
Step 4: Build a Risk Treatment Plan
Once you understand which risks you need to address, it’s time to develop a plan to improve your security controls to reduce those risks to a level that the business is comfortable with. The group of risk treatments, ideally approved by senior management, that results from this analysis and fact-finding is your risk treatment plan.
In essence, a risk treatment plan functions as a simplified, near-term, tactically focused Information Security Plan. For many small to medium businesses, this is the only document you’ll need until you’ve effectively managed all your noteworthy risks. (More about that in the next step.)
Longer-term, there may be some value in translating the risk treatment plan into a more formal, “strategic” Information Security Plan. This document would define a longer-term vision for your information security program with a prioritized view of ongoing improvements to more effectively manage risk in alignment with management’s directive.
Step 5: Execute the Risk Treatment Plan
A good risk treatment plan prioritizes the necessary risk treatments based on these interrelated factors:
- Risk
- Level of effort
- Logical relationships between different treatments
This may seem obvious, but do not skip this step. In many cases your risk treatment plan will say you need to take action on more things than the bandwidth of your organization can handle. Prioritization is key, as well as realizing that security is a journey, not a destination.
Successful execution and ongoing operationalization of your plan (“making it real”) positions you to verify the effectiveness of your existing and updated controls. We’ll cover how that happens in Step 6.
Step 6: Conduct an Internal Audit
A hallmark of ISO 27001 is the requirement that management ensures “the suitability, adequacy, and effectiveness” of the ISMS. The key to doing this is a well-designed ISMS Internal Audit program.
The two-part goal of your Internal Audit program is:
- To identify what is working well; and
- To document what isn’t working and how it will be corrected.
The documentation on how you will correct issues is called the Corrective Action Plans (CAPs). Once complete, you can begin working with management to review the results and formally approve the CAPs.
Step 7: Certify Your ISMS
To achieve your initial ISO 27001 certification, the operation of your ISMS is formally evaluated and certified by an ISO 27001 Registrar in an independent “Certification Audit.”
Stage 1 of the audit is different from what you might expect, in that it focuses on the design and operation of ISMS clauses 4 through 10 in the ISO 27001 standard. For that reason, making sure you are optimally prepared and/or supported by an experienced ISO 27001 implementer can go a long way towards a successful Stage 1 outcome.
After successful completion of Stage 1, the auditor will return several weeks later to conduct Stage 2 of your certification audit. This stage concentrates on the design and operation of controls as outlined in ISO 27001’s Annex A. Understanding the external audit program, its relationship to your risk assessment, and the auditor’s background are all keys to a smooth Stage 2 audit and subsequent certification of your ISMS.
ISO 27001 Certification Audits: What are Stage 1 and Stage 2 All About?
If yours is among the fast-growing number of organizations pursuing ISO 27001 certification, you know there’s a certification audit in your future.
What will your ISO 27001 certification audit look like and what will it focus on? What are you getting into and what do you need to be prepared for?
A big area for questions about the ISO 27001 audit process are the Stage 1 and Stage 2 phases. What goes on in each and how do they relate?
Stage 1
One way to look at it is that Stage 1 is largely a “tabletop audit” or documentation review, whereas Stage 2 is a full-on system audit with a lot of control testing.
But that doesn’t mean Stage 1 is a cakewalk. As John Verry, Lead Managing Director at CBIZ Cybersecurity, notes, “The meaningful part of ISO 27001 is, what, 10 or 11 pages? You’re literally going clause by clause, and we might be sitting there for 12 hours, right? And you’re asking questions like, ‘Demonstrate that the information security management system considers confidentiality, integrity and availability as impact criteria. Go.’”
Stage 2
The more detailed Stage 2 part of the audit may seem more familiar because the format is more like other audits companies may experience. But Stage 1 is vitally important because it reveals whether you have a robust ISMS. And a properly functioning ISMS will serve to ensure that you have viable security controls.
“What makes me a fan of ISO 27001 is the fact that it has the management system, and it’s the process by which you rationalize the actual implementation of the controls,” John Verry clarifies. “So, as an auditor, you can look at that and say, ‘If I can trust the management system [Stage 1], I should, in theory, be able to trust the controls, so let me sample them appropriately to make sure.’ [Stage 2]”
That’s why an ISO 27001 certification audit has two parts, and why they are focused differently.
Step 8: Maintenance, Continuous Improvement and Recertification
It’s possible to get an imperfect ISMS certified, but it’s impossible to keep it certified. Your initial ISO 27001 certificate is valid for a period of three years. It’s understood that this initial audit will be somewhat limited because your ISMS has probably not been operational for long at that point.
To retain your ISO 27001 certification, you’ll need to undergo a recertification audit in three years’ time. You’ll also experience at least two (or possibly four) “surveillance visits” during that period, where the independent auditor checks how things are going, reviews progress towards closing any nonconformities and validates that your ISMS remains operational on an everyday level.
Of course, the point of maintaining and improving your ISMS is to make your company more secure and more desirable to do business with, not because you need to pass an audit. A well operationalized ISMS will make it much easier to adjust to ongoing changes in your business environment, like new threats, new technology, new regulations and new client expectations.
Have questions about ISO 27001 certification or the best way to achieve your information security goals? Contact CBIZ Pivot Point Security: we specialize in advising organizations on how to manage information security risk.
Back to Blog