November 16, 2026
Key takeaways
  • 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.

ISO 27001 is the most trusted cybersecurity standard worldwide. It specifies best practices for an information security management system (ISMS) that can effectively mitigate an organization’s unique cyber risk.

A major advantage of ISO 27001 is that certification requires an audit by an independent, accredited third-party. This is the “gold standard” for proving you can safeguard sensitive data.

ISO 27001 is both comprehensive and flexible to support businesses of all sizes and industries. As such, experience with the standard can be very helpful for defining and implementing the most efficient and effective ISO 27001 compliant ISMS.

This article alerts teams pursuing ISO 27001 certification to 7 of the top mistakes they’re likely to make.

3 Questions to Consider before Pursuing ISO 27001 Certification

Should your organization pursue ISO 27001 certification?

Here are the 3 most important questions to consider before you commit to the journey.

What benefits does ISO 27001 offer your business?

If clients and/or regulators are specifically asking for ISO 27001 compliance, then you need to achieve it. But if you have a choice, why go for ISO 27001? What business value will it deliver?

In this era of continuously escalating cyber-attacks and new cyber threats, the ability to prove you have effective information security can be an excellent investment regardless of company size or industry. Some of the top business benefits of ISO 27001 certification include:

  • Increased customer wins, revenue, and market share
  • Trustworthy assurance to customers, owners/investors/stockholders, board, partners, and the public that you can protect sensitive data assets like intellectual property, financial and personal information, and third-party data
  • Enhanced ability to compete and demonstrate strong security internationally
  • Reduced risk of incurring the financial, legal, and reputational costs associated with a data breach
  • Reduced impacts when cyber incidents do occur (and they will)
  • Greater ability to achieve, maintain, and demonstrate regulatory compliance
  • Improved risk management, resilience, and operational excellence

Do you have top management buy-in?

Once you decide to work towards ISO 27001 certification, what is your plan to convince top management? Because you can’t get to ISO 27001 without leadership buy-in.

The ISO 27001 standard mandates and ensures C-suite support and guidance. Management must commit to planning, implementing, validating, operating, monitoring, reviewing, maintaining, and continuously improving your ISO 27001-compliant information security management system (ISMS).

You need management to commit to make sure adequate resources are available, and to provide training and incentives that build a culture of security consciousness. Management also has a big role to play in:

  • Defining and establishing cybersecurity policy
  • Developing and reviewing the cybersecurity plan and roadmap
  • Creating and communicating about ISMS roles and responsibilities
  • Determining acceptable cybersecurity risk

Can you get there from here?

The resources required to attain ISO 27001 certification vary with organizational size and complexity, ISMS scope, current IT/network infrastructure, staffing/expertise, and other factors.

How far is your current security posture from ISO 27001 compliance? Do you have the budget, time, expertise, and organizational drive to realistically get there?

Once you’ve scoped your ISMS, you’re ready for a “gap analysis” to accurately determine where you are and where you need to go. That analysis will demand a thorough understanding of your true cybersecurity picture and current cyber risks, along with all the ISO 27001 requirements as they relate to your business.

From there, you’ll need to chart a roadmap to successful certification, including a prioritized list of risks and how you plan to treat them.

Once you finally have those key facts and figures, you can decide on issues like:

  • Can you find the necessary implementation staffing, including third-party resources?
  • Do you have adequate budget for new security technology and other IT expenses?
  • Can you mount sufficient effort to achieve compliance in the planned timeframe?
  • Are top management and technical leaders firmly committed to putting the business 100% behind the ISO 27001 certification project?

One: Starting with a gap assessment

In our ISO 27001-as-a-Service practice, the single most common mistake we see with organizations prepping for ISO 27001 certification is starting off with a gap assessment.

At face value, starting with a gap assessment would seem to make sense. It tells you where you are versus where you want to be. Which tells you a lot about timelines, costs, and so on. So why not start there? What’s the problem?

John Verry, Lead Managing Director at CBIZ Cybersecurity, explains that the nature of the ISO 27001 standard is the reason why a gap assessment needs to come later in the process: “ISO 27001 is not prescriptive, so it doesn’t tell you the specifics about the implementation of a control. Each control is implemented in accordance with your risk appetite and appropriate to your context or scope.”

“That’s why ISO 27001 starts with context and with understanding risk,” John continues. “Because that’s the clauses say. So that first clause, Clause 4, is context or scope. That’s about what we’re protecting, why are we protecting it, and what are we protecting it against?”

An ISO 27001 information security management system (ISMS) is built on understanding scope/context and cyber risk. You need this understanding before you can assess your level of ISO 27001 compliance or what controls you need.

Questions to help you gauge ISO 27001 scope and risk include:

  • What information are we trying to protect?
  • For what stakeholders are we protecting this information?
  • What cyber threats are most likely to manifest in our environment and what would be the ramifications?
  • What other laws and regulations impact how we handle and secure certain data (e.g., payment card data, healthcare data)?
  • What do our contracts require us to do for information security and privacy?
  • Where exactly is our sensitive data stored?
  • Who has access to sensitive data, including employees, vendors, etc.?

“All of that is what we need to understand to properly understand risk,” explains John. “And understanding risk also allows us to optimally define the set of controls that would be necessary to mitigate that risk. Then once we know what those controls should look like, then we can do a gap assessment.”

Two: Defining the wrong ISO 27001 scope

Incorrectly defining your ISO 27001 scope is like putting the ladder against the wrong wall. Nothing you do after that will be correct.

Many organizations have the mistaken view that ISO 27001 allows them to define what their ISO 27001 ISMS will protect and what it will not protect.

For example, you might want to protect just your email system and SharePoint environment. But that is only acceptable if those are the only two places where sensitive data resides.

If not, you need to expand your ISO 27001 scope to provide meaningful assurance to stakeholders that you can protect their data, even when it’s on laptops or in the cloud.

A good way to view this challenge is to let your information define your ISO 27001 scope.

Three: Viewing ISO 27001 as an “IT project”

A very common misperception about the ISO 27001 certification journey is that it can just be an “IT project” that the IT team can largely handle. But because ISO 27001 requires you to build and certify a holistic management system, you need to involve the people, processes, and systems that handle data across its lifecycle.

“You really need to understand that ISO 27001 is about the full lifecycle of information,” John advises. “Remember: people, process, systems, right? So as an example, human resource management is important. Are the people that you’re hiring properly vetted and background screened? Are the people that you’re hiring appropriately qualified? Are the people that you’re hiring appropriately trained with regards to good security practices? Are they trained on your specific requirements for information security? Do you have good physical security? Because if you don’t have good physical security and [hackers] can walk into your office, it doesn’t matter if you’ve got good digital security.”

For example, your HR team may need to be involved so they can facilitate training on cybersecurity and privacy responsibilities for each role. Legal and compliance teams are needed to confirm that contractually mandated security controls are in place, and to manage compliance processes. The physical security team also has a key role to play in protecting data.

Don’t forget legal and compliance

Another key area of ISO 27001 involvement for most companies is legal and compliance. Does your organization understand and address the laws, regulations, client contractual obligations, etc. that it’s subject to?

“We did some work recently for a law firm, and we asked to see some contracts,” recalls John. “[Some of them] specifically cited that if you’re going to work with us, all of our work needs to be done on an isolated network, on dedicated systems. So, we asked, ‘Hey, are you guys doing this?’ And the answer was, ‘No, we didn’t realize that.’”

“That’s why you can’t just have IT and IS handle [ISO 27001 certification prep], right?” says John. “You should involve a good cross-section of the organization. A lot of people need to be involved.”

The role of “top management” in your ISO 27001 ISMS

Perhaps most importantly, senior management involvement and commitment is central to ISO 27001 certification and ongoing governance. Cybersecurity is a business issue at the C-suite and boardroom levels, and ISO 27001 requires confirmation that leadership is championing the certification effort.

ISO 27001 certification is a big change for most businesses; one that impacts not just IT but many departments from legal to HR to the C-suite. Because what you’re actually certifying under ISO 27001 is your information security management system (ISMS) and not your controls, governance, and therefore senior management, is meant to play a pivotal role in achieving and maintaining an ISO 27001 certificate.

The ISO 27001 standard emphasizes that senior management involvement and direction is critical to the effectiveness of any ISMS.

John explains: “Senior management tends to think, ‘Hey, [ISO 27001] is IT/InfoSec and we really don’t need to be involved.’ But ISO 27001 makes it very, very clear that an ISMS, the information security management system that you’re certifying, needs to be governed. And it needs to be governed by ‘top management.’”

Cybersecurity is a business issue

Another big reason why the C-suite needs to be steering the ISO 27001 ISMS is that cybersecurity is a board-level business issue, now more than ever.

As John puts it, “Information security risk is no longer just InfoSec risk, it’s a business risk. And you need to be assured, as management, that that risk is understood, that that risk is being effectively managed on an ongoing basis and that you’re validating that.”

“And that’s what ISO 27001 says,” John emphasizes. “If [your business is] seeking ISO 27001 certification and you are ‘top management,’ you will be playing a role in ISO 27001.”

Four: Rushing your ISO 27001 certification

Most organizations pursue ISO 27001 certification because they are under pressure from clients, regulators and/or investors to prove they can protect sensitive data. Often, there’s time pressure as well. Deals may be on the line. So let’s get that ISO 27001 certification in hand ASAP and we’ll iron out the details later, right?

Wrong. Trying to rush your ISO 27001 certification process can negatively impact your security posture and increase the risk of failing your certification audit.

How long does ISO 27001 certification usually take?

It’s no surprise that one of the universal questions we get in our ISO 27001-as-a-service practice is, “How long is this going to take?”

As John relates, “‘We really need to do it as soon as we can, because we have a contract we’re about to lose. Or ‘We have a contract we can’t win.’ Or ‘We can’t bid on this particular project unless we’re ISO 27001 certified.’”

But ISO 27001 certification isn’t a turnkey effort.

“Probably you could get ISO 27001 certified in three or four months,” says John. “But I wouldn’t advise you to do that, because it’s not going to be a good implementation. It might get certified, but it’s not going to maintain certification. And believe it or not, it may actually negatively impact your overall security posture. And it’s going to cost you a lot of money to fix it after the fact.”

“Getting ISO 27001 certified in most organizations should take… Six months is a pretty quick timeframe,” continues John. “10 or 11 months is typical, and anything longer than that is a little on the slower side. But if you’ve got an organization where there’s a lot of people involved, a large organization with some complexity, it’s not unusual for the project to take a year or so.”

Interdependencies must be addressed sequentially

As the ISO 27001 standard dictates, what you’re certifying is not your controls but your information security management system (ISMS). Like most systems, your ISMS processes interconnect and interoperate.

“The reason I say moving too fast is actually counterproductive is that there are elements of an ISO 27001 management system that are hierarchical and interdependent,” John shares. “As an example, take data classification. We can’t classify data until we understand what data there is. And data classification takes place by asset owners. So, until you have the concept of asset ownership, asset custodians, you can’t actually have data classification. And until you have asset management, you don’t have the idea of asset custodians.

“Those are three distinct controls that we’re configuring and setting up,” John points out. “If we do them in parallel, as you might imagine, you’re going to have things not work quite properly.”

Five: Using information security policy templates

Clients often ask us whether they can make their lives easier by using information security policy templates to document compliance with the ISO 27001 standard for certification purposes. Our answer is uniformly “No.” Here’s why.

The ISO 27001 standard has over 50 requirements in clauses 4 through 10, and 93 controls in Annex A. None of those requirements mandates or even recommends the use of templates for security policies and procedures. So why do organizations seeking certification often want to use templates to document compliance with ISO 27001? Usually it’s because they’re either not sure what they need to document, and/or they believe that templates will save them time in documentation.

But if you don’t have the expertise to document your own existing security policies and procedures for compliance purposes, you probably also don’t have the expertise to comply with or modify the policies and procedures documented in your chosen template.

Likewise, templates don’t save time because the disparity between your chosen template and your real-world policies and procedures is too great. The time you might save compared with documenting your procedures from scratch ends up being outweighed by the time you spend either changing your real-life procedures to comply with what’s described in the template, or changing what’s described in the template to reflect what your organization is actually doing.

If templates aren’t useful, why are there so many of them out there? Consultants and others who help organizations achieve ISO 27001 certification create templates for one reason: because their clients ask for them. Templates describe “best practices,” so clients often assume that a template will include whatever the auditor is looking for. But that might not be what’s appropriate for your organization, and it’s also probably not what your organization is currently doing.

ISO 27001 certification is like an open-book test, and using templates to document information security policies and procedures is like studying the wrong book. For example, say you download a Backup Policy template that’s outdated and talks about best practices for offsite rotation of tapes and periodically performing restores to test backup tapes. But these days your organization doesn’t even use tapes for backups anymore. Instead, you rely on disk-to-disk backups to NAS devices plus SAN replication to a colocation facility for business continuity and disaster recovery. Now you’ve got a nonconformity to correct before you can be granted ISO 27001 certification because your modern IT organization doesn’t comply with that outdated backup policy template.

Another good example relates to password policies. You can download a password policy template that addresses all the best practices for password management. But it’s unlikely you can enforce those best practices in the legacy applications your business may rely on to generate most of its revenue or provide critical services. Now you’ve got a nonconformity for failure to comply with your password policy. The time spent on documenting a corrective action plan for that nonconformity would’ve been better spent identifying the risks of weak passwords in legacy applications and making a risk treatment decision driven by a business justification, instead of a change driven by the need to match your business process to a template.

Keep in mind also that the purpose of documenting your policies and procedures is to clarify and optimize the rules for running your business, not to pass an audit. All the best practices that templates provide are already provided in the standard’s implementation guidance. That’s the only “template” you really need.

Here’s the quickest, cleanest and most useful way to document your security policies for ISO 27001 compliance purposes: Compare the best practices the standard describes to what you do now, and document the ones that you currently use, plan to implement or would like to eventually implement.

Can you achieve ISO 27001 certification using templates? Sure. But most likely you can do it better and faster without them.

Six: Failing to leverage ISO 27001 for other compliance needs

The challenge of achieving ISO 27001 certification can monopolize organizational focus. But it is also important to take a step back and think about longer-term cybersecurity goals you can advance at the same time.

“Folks get very focused on getting to ISO 27001,” observes John. “I always like to take a step back and say, okay, let’s talk about what you’re trying to achieve today. And let’s try to think about where you might be going in the future.”

“The reason that’s important is that if you are choosing to get ISO 27001 certified, usually that means you’re processing someone else’s data, and you’re being asked for a strong form of attestation,” John continues. “And it’s highly likely that you’re going to be asked for one or more other forms of attestation. So as an example, if you are processing medical claims, then HIPAA comes into play and maybe you’re signing business associate agreements.”

“And as we’re proceeding towards ISO 27001, by overlaying HIPAA on top of that, and then either through the internal audit process or through the certification audit process, actually auditing and validating the HIPAA controls and being able to provide an additional layer of attestation there, we’re able to provide double duty, right? We’re killing two birds with one stone. You’re saving a little a bit of money,” John advises.

In these situations, it can be helpful to plan to implement, audit, and validate additional compliance requirements alongside ISO 27001. Planning upfront to build and manage controls to do “double duty” can save time and money while simplifying compliance governance.

What about privacy attestations?

An increasingly critical area where more and more companies face compliance challenges is privacy. This makes working toward ISO 27701 in parallel with ISO 27001 certification an attractive option for many SMBs.

As John explains, “It’s important that we make good decisions now in order to capitalize on [the ISO 27001] effort and not lose any ground in the future. So, as an example, if you’re dealing with personal information and CCPA and APAC and GDPR apply, you might want to look at ISO 27701.”

Choosing your external audit partner

A final reason to broaden your focus as you’re pursuing ISO 27001 is that your future needs might impact your choice of an ISO 27001 registrar, the organization that’s going to perform your external audit and stand behind your certificate.

“If you are somebody who might need CMMC certification, or you might have to proceed towards FedRAMP, or you might want to go towards SOC 2 in the future, you’re going to want to make sure that you pick an ISO 27001 registrar that is able to do whichever of those you’re going to require,” says John. “So the registrar, if you want to go to SOC 2, needs to also be a CPA firm. If you want to go towards a CMMC, you want a registrar that’s also a C3PAO. If you need to go towards FedRAMP, you’re going to need a registrar that’s also a 3PAO. In the payment card industry data security standards, maybe you need a QSA registrar.”

Using the same partner for multiple audits can save time and money while improving the value of audits for feedback and continuous improvement.

“So, it’s important to understand where you’re going, and what does one year, two years, three years look like for you?” emphasizes John. “That way, as you’re building your information security management system, and you’re creating your partnerships with the people that you’re going to need to achieve them and certify them, make sure that you’re accounting for the future.”

Seven: Failing to stay focused after achieving your initial certification

After gaining their coveted ISO 27001 certificate, it is common for teams to put ISO 27001 processes on the back burner and get back to business as usual. However, an ISO 27001 ISMS is an ongoing effort that requires monitoring and maintenance in between annual audits.

ISO 27001 compliance also requires certified organizations to show continuous improvement in their security posture. Newly certified teams need to stay focused and operationalize cybersecurity activities so they become part of the business culture.

Getting off to a strong start with cybersecurity awareness training not only helps operationalize an ISO 27001 ISMS, but also helps neutralize threats and reduce cyber risk.

Why You Should Tell Your ISO 27001 or SOC 2 Auditor That You Want as Many Nonconformities as Possible

In the initial meeting of an audit, we always say the same thing: “Give me any nonconformities (NCs) and Opportunities For Improvement (OFIs) you can find.”

We understand why the average CISO/CIO/Security Director doesn’t want findings in their audit:

  • Audit findings are an indication that things aren’t working right/can be improved, and hence are often perceived as a negative reflection on the auditee. No one wants management to think that they are not doing a good job.
  • Audit findings often require some short-term and longer-term work to develop a Corrective Action Plan and likely solve a slightly challenging issue (or you would have solved it yourself already). Everyone is busy and more work is not what you are looking for.

But here’s why we take the opposite approach and embrace and even encourage audit findings:

  • Telling an auditor that you “want” findings gives them the latitude to tell you that your baby is ugly. You pay auditors a lot of money and the unfortunate reality is that if they give you a lot of findings you will be unhappy, and unhappy clients often become former clients. So auditors are “incented” to only give you findings when they “have to.” That dynamic is dysfunctional and “lose-lose.” Giving me every finding you can is “win-win.” It tells your auditor you want the best ISMS/Information Security Program you can have, and ensures you are going to get the best work the auditor can give you.
  • Your ISMS actually improves. Your year-over-year risk goes down and the likelihood that your organization has a significant security incident plummets.
  • Audit findings get CxO/Board level visibility, which is often what is necessary to get you the funding and/or staffing you need to address the issues you have tried to address on a shoestring budget or with too few people/resources.

If you are a CISO/CIO/Security Director who wants to employ the “give me all the NCs and OFIs you can” approach, start by setting an expectation with management that this is what you are doing and explain the rationale. Management’s first reaction to a list of audit findings is trying to figure out who is to blame for each one of them. Getting ahead of that and explaining to them the value proposition of embracing audit findings is critical to your long-term success.

If you are a COO/CFO/Board Member that wants to employ the “give me all the NCs and OFIs you can approach,” start by setting an expectation with the CISO/CIO/Security Director that you understand that there is no such thing as being 100% secure. Which directly translates to there being no such thing as a perfect Information Security Program. Hence, it would be foolish to think that an auditor worth the investment would not be able to find ways to improve our security program. Giving your CISO the ability to embrace “failure” gives you the assurance that you are going to get an accurate picture of your security/compliance. Plus, then your CISO is incented to share the truth instead of hiding it.

Shift your security culture to one that embraces “ugly babies,” and you (and your ugly baby) will sleep better at night knowing you know everything you need to and that you are continually improving your security posture.

Next steps

ISO 27001 certification requires significant organizational dedication, expertise, planning, and resources. For many SMBs, just getting started can be a challenge. Evaluating and auditing current controls and interpreting the ISO 27001 standard are other common hurdles.

Businesses looking to avoid missteps on the path to ISO 27001 certification should prioritize planning, stakeholder collaboration, and risk assessment. A trusted partner can support a wide range of essential tasks in the certification process, from policy and documentation updates to ISMS scoping to risk assessment to developing efficient controls.

CBIZ Pivot Point Security is a leading consulting firm for ISO 27001 certification and has a 100% success rate in bringing over 100 organizations of all sizes to certification. Contact us to talk about how we can optimize your ISO 27001 efforts, costs, and ROI.

Back to Blog