
Canadian businesses are investing more in cybersecurity, but those investments aren’t necessarily translating into fewer breaches. For managed service providers, that raises an important question: how can they help customers get better results from the money they’re already spending?
Recent research from the Canadian Internet Registration Authority (CIRA) found that 78 per cent of surveyed Canadian organizations increased their IT and cybersecurity spending, while 42 per cent reported experiencing a data breach, compared with 29 per cent in 2022.
For Adam Bowles, CEO of Barrie, Ontario-based MSP ACT360, the disconnect highlights a challenge he regularly encounters with customers: businesses may be willing to purchase security technology, but getting employees and management to engage with the processes required to make that technology effective is another matter.
In this episode of In The Channel, Bowles discusses how ACT360 approaches cybersecurity across a customer base ranging from small businesses to large enterprises, and why he believes people and organizational culture play such an important role in security outcomes.
He shares examples of businesses investing in security awareness training without establishing responsibility for employee participation, and explains why MSPs need to understand a customer’s internal structure and decision-making processes before implementing new security initiatives.
The conversation also explores practical security priorities for smaller businesses with limited budgets, the risks of accumulating overlapping security tools, and how MSPs can demonstrate the value of their cybersecurity services.
Ultimately, Bowles argues that effective cybersecurity should support the business rather than stand in its way. For MSPs, that means combining technical expertise with an understanding of the people and processes their customers rely on every day.
Podcast: Play in new window | Download
Subscribe: Apple Podcasts | Spotify | Amazon Music | Android | iHeartRadio | Youtube Music | RSS
Read Full Transcript
Robert Dutt: Welcome to In The Channel from ChannelBuzz.ca, bringing news and information to the Canadian IT channel for the last 16 years. I’m Robert Dutt, editor of ChannelBuzz.ca, and your host for the show.
Canadian businesses are spending more on cybersecurity, but are they getting the results they’re looking for?
That’s the question at the heart of today’s conversation.
Recent research from the Canadian Internet Registration Authority, or CIRA, found that 78% of Canadian organizations surveyed had increased their spending on IT and cybersecurity. At the same time, the proportion reporting data breaches climbed to 42%, up from 29% just a few years earlier.
Those numbers caught the attention of the team at ACT360, a Barrie, Ontario-based managed service provider, and prompted them to reach out to us.
And they raise some interesting questions. If organizations are investing more heavily in cybersecurity, why aren’t they seeing a corresponding improvement in the number of breaches? Are businesses investing in the wrong technologies? Are threats simply evolving faster than our ability to defend against them? Or are there other factors that determine whether those investments actually deliver?
My guest today is Adam Bowles, CEO of ACT360, an MSP serving customers ranging from small businesses to large enterprises.
Adam has a pretty clear perspective on what’s happening. From his experience, businesses are often willing to spend money on cybersecurity tools, but making the organizational commitment to use those tools effectively can be considerably more difficult.
And that opens up a much broader discussion about the role of employees, management, organizational culture, and the MSP itself in delivering better security outcomes.
We talk about why security awareness training sometimes fails despite businesses paying for it, the importance of establishing internal ownership of security initiatives, and how MSPs can help customers make better use of their existing investments.
We also get into practical priorities for businesses with limited cybersecurity budgets, the danger of accumulating overlapping security products, and why Adam believes effective cybersecurity ultimately comes down to helping people do their jobs safely.
It’s a useful conversation about the business of delivering cybersecurity, and one that I think will resonate with MSPs working to balance customer expectations, budgets, and real-world risks.
Let’s get right into it in my chat with Adam Bowles.
Robert Dutt: Adam, thanks for taking the time. I appreciate it.
Adam Bowles: Thanks for having me.
Robert Dutt: Before we get into the cybersecurity discussion, let’s kind of set the table a little bit. Give me the elevator pitch, or the Coles Notes version, of ACT360. Who you are, what kind of customers you work with, and what are the big priorities for your business these days?
Adam Bowles: Yeah, so we’re a managed IT provider. I’ve been doing this now since 2008, and we typically serve small businesses anywhere from 20 to 50 users. But then we also get into some corporate clients with multiple locations, and some of our clients go into the enterprise area of 5,000 or 6,000-plus users.
So quite a range of portfolio, and we’ve been dealing with this ever-changing world for quite a while now.
Robert Dutt: And quite a range of different requirements, needs, appetites, and budgets amongst that customer base.
Adam Bowles: And ways of managing people. It’s all different across the board. It’s all the people, yeah.
Robert Dutt: Oh, good fun.
You’ve been working with businesses of all sizes, by the sounds of it, for quite a while now. How has the conversation around cybersecurity changed over the years? Is it something that customers are coming to you to ask about at this point, or is it still a situation where you’re having to initiate the conversations, educate, and help customers along the trail?
Adam Bowles: Yeah, so because we have such a range of clients, we’ve found that when you get to the larger corporate clients, they’re typically proactive in asking about security, and that’s baked in.
It’s in their RFPs, it’s in their question decks, it’s something that the VPs will ask right off the bat. Depending on the company, that will affect how deeply they go and how they actually manage it quite heavily.
But when you get into the smaller businesses, it’s usually something that we have to bring up.
It’s seen as a cost. In a lot of cases, they haven‘t experienced being on the other end of a security event, so there’s a little bit of the “it won’t happen to me” mentality that we see.
And so it’s trying to figure out, for those businesses, which is probably most of the audience, how do you turn cybersecurity into a bit of a business benefit for them? How do you show them the cost-benefit? And how do you keep the costs reasonable and supportable for them?
Because they’ve never gone through it before. They don’t know how big of a problem and how terrifying it is yet. And that can be quite a position to pitch.
Robert Dutt: I can only imagine.
The reason we’re talking today is your team reached out with some interesting CIRA research. The headline numbers are pretty striking. More than two-thirds of Canadian organizations surveyed are increasing their IT and cybersecurity spending, but the proportion reporting data breaches has climbed from 29% a few years ago to almost half in 2025.
What jumped out at you about those numbers, and how closely do they reflect what you’re seeing with customers, especially with those smaller customers who either haven’t been breached yet or maybe don’t think they’ve been breached yet?
Adam Bowles: Yeah, I think what’s happening is it’s relatively easy for clients to spend money on cybersecurity tools.
As much as nobody wants to do it, and it’s painful to get them to do it, that’s not terribly difficult to get them to do, which is where we see the statistics that the budget is increasing.
But what they’re not doing with it is the corresponding training, oversight, and ongoing maintenance—the people side of the equation.
It can be a lot harder for a small business to pull their staff aside, give them training, and show them how to do things, how to use the tools, and how to actually perform in these situations.
And I think that’s where we’re seeing the budget going up from a dollar perspective, but we’re not seeing the corresponding people management go up.
And I think that’s the big gap on the SMB side. It’s not really the budget that’s the problem. It’s the tool management and monitoring and staff support that needs to come along with it.
Robert Dutt: So, to use perhaps a bit of a ham-fisted analogy, lots of people are willing to buy the gym membership on January 1, but not so many are willing to actually go to the gym and put in the hours to get the desired result.
Adam Bowles: Yeah, that’s a very good analogy. Trying to get them to spend the time is a lot harder than getting them to spend the money.
Robert Dutt: Well, and ultimately, especially with smaller customers who are looking at you probably as, if not their entire IT team, then certainly an extension of their internal IT and security team, how does that reflect on you?
And how do you manage how that reflects on you when they’re saying—I don’t imagine, maybe some are self-reflective enough to say, “You know what, we really should make that investment.”
But I’m sure the more frequent or feared response is when the customer looks at you and says, “Well, we bought all this stuff. Why aren’t we getting the results we want?”
Adam Bowles: Yeah, that’s a really good question.
A really good example of where we see this being an issue is that a lot of places, and a lot of insurance policies, require training to be provided to their employees. Some sort of security awareness training, or SAT, which is the term for giving employees the training and helping them to actually dig in and understand what they’re doing.
And the way a lot of those trainings work is they’ll send you out emails and do phishing training. They’ll give you little videos and other things to go along with it.
So it’s all fine and good that the company pays for the software. But if nobody’s telling the staff that they have to do the training, they have to interact with it, they have to log on to the portal, they have to pull team members aside and tell them, “If you don’t do this, there are consequences to it.”
If the company’s not doing that and isn’t willing to back up their provider in getting that stuff done, then there’s nothing an outside agency can do to force their staff to interact with all of these tools.
We make the tools as fun as possible. We make the tools suck as little as we can, and we try to change providers.
But at the end of the day, if the company is not going to do that, we see it time and time again where we’ll put that software in place and try to have the company start to teach their employees how to do this, but they don’t have an HR department.
There’s nobody there to help tell the employees to spend their time on it, so they just don’t.
And then, lo and behold, they get a phishing email and they don’t notice it because they’ve never been trained on it. And they ask, “I thought we had training on this.”
You have software. Nobody’s using it. That’s not really training.
Robert Dutt: How do you get around it, or what have you found works to get around that?
It sounds like what you’re describing isn’t necessarily even a problem with just getting the upper echelons, the leadership, to buy into the vision and the approach as much as it is getting someone who’s in the trenches and making the tactical steps happen.
Adam Bowles: Yeah, I think what we’ve really found is these are conversations that have to happen before you even purchase the software.
We have to tell them what it’s going to look like, how it’s going to work, and make sure that the business knows, “Okay, this is what the software is going to do. It’s going to send out emails to your team, and it’s going to have them interact with it. They’re going to get pass/fails if they click on phishing things and give them experience for what it does.”
We then have to discuss, “Okay, who on the team owns that? What happens when people are failing badly? What happens when they’re failing constantly? How do we give them feedback? How do we support the staff in a constructive way so they actually learn and engage from this?”
And that’s where we’ve found that if you do that at the start and you put that in place as a part of it, then there’s a much better chance of the business being able to run with it.
Some businesses will admit, as soon as you start talking about that, they don’t have any way to do it. They don’t have any way to support that. They don’t have anyone who can engage with their team.
And so then, in some cases, the software will get dropped.
Which is where, for some MSPs, of course, they’ll go, “Well, I don’t want to bother doing that then,” because now they’re not getting paid for the software, because now they’ve decided they’re going to drop it.
But that’s realistically the only way to help, making sure that you have put those plans in place right at the beginning.
Because once it’s already out there, they’ve already spent the money, good luck getting them to do it after the fact.
Robert Dutt: When you’re talking to those customers, does that become something that you build on more yourself?
It sounds like it really is key to have that internal ownership or that internal go-to. It’s not something that necessarily you can do as a third party very easily.
Adam Bowles: Yeah, I think that’s the big gap that businesses can miss with working with a security partner, or even with internal staff, is there’s only so much that those people can do on their own in a vacuum.
The company has to have that as a part of their culture, and it affects every single person.
I don’t know the statistic, but I would imagine almost the vast majority of cybersecurity events are around social engineering and finding vulnerabilities with the people.
Very few of them are where someone just sits there and spams your firewall until they find a way in.
It’s far easier to find a weak link, make them pick up a flash drive, plug it in, make them access a website, do something with phishing. It’s way, way easier to do that stuff than reaching security vulnerabilities directly.
Robert Dutt: And at the same time, you mentioned that a lot of smaller customers especially still have the “Oh, it can’t happen to me” kind of mindset.
But I’ve seen some numbers that indicate that’s not necessarily the case increasingly, especially as common tools proliferate and as things like AI drive down the cost of going big with an attack.
Increasingly, it’s attractive to go after small businesses because you can kind of scattershot and get at them that way.
Adam Bowles: Yeah, it’s absolutely changing really quickly.
I think the scariest example that I’ve seen recently that we got called into is someone had their email inbox hacked.
And as soon as they received an invoice, it was deleting the invoice. AI would edit the invoice, change the directions on where to send the payment, and put it back in their inbox with a different from address.
The person then would have potentially already seen the invoice, but then when they go back to open it to pay it, they just pay the details that are on this new invoice.
And AI has now enabled that entire process to take about two minutes, from delete to reposting it.
And it took them several occurrences of sending money to the wrong spot to realize that it was on their end, not on the other end.
Because they, of course, just think, “Oh, it’s on the other person’s side. It’s not my side.”
And that type of stuff that you can now do with AI, where you can just sit in someone’s inbox and manipulate their emails, is terrifying.
Robert Dutt: When you look at the customers you’re working with, where do you see the biggest disconnect in terms of the spend, in terms of what they’re willing to invest in?
Where do you see the biggest disconnects between what businesses think they’re getting from their cybersecurity investments and what they actually end up getting?
Adam Bowles: I think the biggest disconnect is really on the staff training side and knowing how to interact with the software and the tools that they’re purchasing.
It’s the setup and the usage of the tools.
And that’s where I see a lot of businesses. Places are quite happy to pay for the things, but then they forget to set up and use them.
They’ll forget to monitor the backups. They forget to watch the error logs for the breaches and the alerts.
They put antivirus on the computers, but the antivirus reports to the employees, who don’t tell bosses that things need to happen, instead of going centrally.
So I find in a lot of cases it’s the setup and the monitoring and the management, and making sure that the people who are interacting with all of these things are equipped and empowered to actually use it, and everybody is being supported and trained on how to use the things.
Robert Dutt: That management, though, and that ongoing keeping an eye on the indicators as they come in and those sorts of things, that comes back up to you, though, right?
Adam Bowles: That comes back up to us in the case if they’re using an MSP.
A lot of providers, of course, have in-house staff. And when they have in-house staff, it’s very easy for them to be very busy on lots of things, and so those types of alerts get pushed aside because they don’t scream at you like your boss does.
So it all depends on the type of business and where you’re going as to who should be responsible for that.
That’s where, in some cases, when you get to larger companies, they have people just dedicated to security, which works great because then they don’t get the same distractions and they can watch these alerts.
That causes its own problems, because then you get security for security’s sake, and you don’t let people do anything.
So then they can swing too far the other way, because they don’t have enough work to do, so then they just start making up policies.
But we’ve really seen where, especially when you’ve got internal people, you’ve just really got to make sure that they’re reporting on it and they’re managing it, and that the bosses know what needs to be done.
Which is the hard part of having internal staff. Who manages them? Who helps to hold them accountable when their boss isn’t an IT person as well?
And the person managing their time isn’t the person who knows where their time needs to go.
And the technicians, in a lot of cases, aren’t the best at explaining themselves in these things.
And this is where, again, it comes back to the people and what kind of culture you’ve made. How do you, as a manager who may not necessarily understand this, make sure that these things are getting done?
Robert Dutt: I understand why organizations, especially when they’re larger, have internal security staff and that sort of thing.
I’m curious if you have a strong feel or preference for working with an internal security staff versus the ability to have that carte blanche that, mostly with smaller customers, I would imagine, where you come in, set the agenda, and hopefully drive more of that as opposed to co-piloting.
Adam Bowles: Yeah, I think it really depends on the size of the business.
When it’s the smaller businesses, it’s much easier as an agency for us to have the carte blanche where we can go in, set up the policies, and support it.
And then we just have to make sure that we’re running through with management what they need.
In some cases, we’ll be checking in with their insurance company to make sure that we’re compliant with their insurance company needs, and that we are doing any of the extra little things that will get us discounted rates with them.
So that can be a really good piece of accountability for us as an external agency. How do we stay compliant with your insurance provider so that, if something happens, everybody’s protected and the insurance company has what they needed from the get-go?
But that can really help because there’s not as many hands in the pie necessarily.
And at a small company size, they’re not getting some of those overzealous security rules, because they don’t necessarily need all of it.
And the nice thing is we see it across a lot of clients, so it’s not our first time experiencing things.
Whereas when you’re an internal IT person, if you’ve been there for three, five years, a lot of things are your first time because hopefully you’re not having a lot of security events.
So it’s different problems.
Robert Dutt: Well, let’s talk about customer conversations.
When you’re sitting down with an SMB owner or an IT decision-maker to discuss security, what are they typically most concerned with?
Are they worried about breaches? Are they worried about ransomware, business interruption, compliance, insurance, or is it simply the cost of protecting themselves?
Adam Bowles: Yeah, I think it’s a really good mix.
I know there’s a good number of clients that are worried about downtime, and business interruption is usually something that’s very top of mind for them, and we hear quite a bit.
There’s some companies where they have some IP, and so making sure that’s kept safe and secure is a really big thing for them.
Whereas there’s a lot of other companies where they go, “If somebody hacks me, there’s nothing in here. I don’t really care.”
They don’t have anything that’s IP-related, and so they think that it doesn’t matter.
I would say it still does because you still have your customers and you still need to protect that, but that’s the mindset that we hear quite a bit.
And then I think from there, clients tend to get into the social engineering side of making sure they don’t send wire transfers and the phishing emails.
They just want to keep that noise out of their inbox because it’s a distraction, and it takes a lot of energy to try and check an email and figure out, “Is it legit?”
And they want us to try and figure out how to block as much of that and save some of that mental load as possible.
Robert Dutt: Acknowledging that there’s going to be a range of answers here, when customers decide to increase cybersecurity spending, how are they looking at that spend?
Is it strategic investment? Are they simply looking at the latest headlines and chasing the latest threat or incident, the latest product that you or your peers are presenting to them?
Basically, how are they thinking about it and approaching it?
Adam Bowles: I think in a lot of cases, depending on the size of business and what their experience is, smaller businesses start off seeing it as just a cost of doing business, a necessary evil.
As the business grows, I think it then starts to become where they realize it as a strategic investment, because they realize the value of the IP and the relationships that they have, and what they can protect by not having their name in the headlines for having an incident.
So the mindset starts to shift.
And I think as well, when cybersecurity is done well, a lot of the policies and things that are in place, when it’s done with an even hand, make it easier for people to work.
Having unique passwords, having MFA, having a password manager, that actually makes it easier for people to get in and access things.
Being able to have your own account and tell who did what, that can be really useful for telling what happened and what’s going on.
And those aren’t cybersecurity. Those are things that are needed for cybersecurity, but they also just help the business to run as a whole.
So this is where, as the business starts to grow, they start to realize that when done properly, cybersecurity is also a bit of a growth investment because it helps the company to grow.
It’s an organization tool that gets put in place.
Robert Dutt: Do you find that’s something that most customers have to learn through getting there, or is that something that you can proactively promote, teach, show the way to?
Adam Bowles: Depends on the relationship.
If it’s a cold new client, it definitely starts off as they have to get there themselves.
Whereas if you’ve got a relationship, you can get them a little bit of the way there and help them to realize it.
But I think until they hit a certain size and there’s a certain amount of complexity with the business, until it gets to that point, it just doesn’t register for them.
They don’t realize that being organized does actually save you money.
And that’s where a lot of cybersecurity stuff is helping people to be organized, have some of these policies, and have procedures in place that people know how to use.
But that reaches beyond cybersecurity, because once you start to do that, it then touches other policies in the company, and it just makes for a mature business.
Robert Dutt: Let’s turn this around a bit and talk about what works.
When you look at customers who you think are getting genuinely good results from their cybersecurity investments and their security stance, what are they doing differently, or how are they thinking about it differently than the masses?
Adam Bowles: Yeah, I think the biggest thing is the way that they’re pushing out a lot of the initiatives and how they approach getting approval and putting new initiatives out.
Is the team and the company at large getting engaged in this? Do they have the ability to make adjustments and get feedback on things?
Or are the security policies just being pushed on them, and they have to follow them blindly, and they’re not really getting communicated out to the staff?
So I think it really comes down to the culture.
Is the culture in the business one of collaboration, where the employees actually have a voice?
They know what’s going on. They know why they have to do the phishing emails. They’re being coached on it. Their reviews include stuff on the phishing emails and all these other training pieces on how to do things.
Or is the culture more combative, where the employees just have to do their jobs, and it’s very much head down, working in a silo, and they don’t really have that voice?
They’re not a part of the big picture, which would make it a lot harder for security people to push things out and to realize, “Hey, this policy that I pushed out, it made this person’s job ten times harder because now they can’t do the things.”
There’s probably five other ways to do it, but I didn’t know that my policy was causing those impacts because nobody’s allowed to speak to me.
And I see companies at both ends of the spectrum in how they treat their employees and just how the owner runs it.
Do they run it with an iron fist, or do they encourage that feedback and collaborative approach?
Robert Dutt: Man, I have to imagine as an MSP, managing the technology state can be easy compared to managing the internal politics and culture of an organization.
Adam Bowles: It can be.
And this is one of the interesting parts when you’re going in to work with a client. We can change the technology, but we can’t change the culture in the company.
And in some cases, I feel like as an MSP, we’ll actually internally talk about the culture at the different clients.
What is this client going to want? What are they going to support? How do we put these different things through? Who do we need to work with to get different things done?
And it’s talking about the politics and acknowledging that the politics are a very real part of cybersecurity.
And it’s probably one of the hardest parts as an MSP, supporting the client through their internal politics because we are a little bit on the outside.
How do we make sure we’re on the inside and able to support them properly?
Robert Dutt: One of the challenges, I think, for a lot of MSPs, and it sounds like this might fall for you as well, as you’ve described a broad array of different types of customers at different sizes, different cultures, different internal resource levels, different risk tolerances.
If you’re working with a smaller business that simply can’t afford the full stack, to go all in, how do you prioritize?
What are the fundamentals that you absolutely want to get right before you start spending on anything else?
Adam Bowles: Yeah, that’s a very good question.
I would say the biggest thing that we typically do is the emails, and around the emails are a huge spot to start from security, making sure that that is as locked down as the provider allows, whether it’s Google or Microsoft, having 2FA.
And then typically the next piece that we’re doing on top of that is adding in the monitoring of the email accounts to make sure things like impossible travel—are you going to have logs being monitored? Are you watching for suspicious sign-ins? All of that around the email accounts.
And then from there, starting to connect so that as many platforms as possible use the email account for sign-in.
Because now we’ve locked that platform down as much as we can, which makes it a lot easier for us to have control over their sign-in experience to all their other platforms.
Typically, a part of that, though, of course, is looking at where their data is.
If different things get breached, having the conversations with the client: if this gets breached or this gets lost, what are the implications to the business? How long can you be down for? What does it do to your reputation?
And prioritizing things that way.
It’s the same with disaster recovery. That’s how I would approach that conversation.
If this happens and you’re down for three days, what’s the implication to the business?
And then deciding how big of a disaster recovery solution needs to be in place and what that might cost, and trying to balance the two out.
Can we afford every three years that there’s a two-day event? No? Okay, we need to get that down to a one-day event. That’s what this costs.
And then finding the balance, because there’s always tons of options. It’s just finding the balance and what the business can afford.
Insurance-wise, that’s what the disaster recovery is versus the cost.
Robert Dutt: At the other end of the spectrum, when a customer is bigger, has a more substantial cybersecurity budget, how do you make sure that any extra budget they’re getting translates to better protection rather than just having more tools, more complexity, or what you described earlier with security employees adding layers of unnecessary security because it’s, you know, justifying your own existence?
Adam Bowles: Yeah, I think this is where it gets really important, and this is where things like AI help us a bit.
As you’re doing this, it’s documenting the things that exist and what’s been made from a cybersecurity standpoint, and what the purpose of these are.
And that way you can easily go back through, be doing audits of the different processes that are in place, checking the reports, and making sure that you have an idea of what are they picking up and what are these tools actually doing.
And then, in the case of a larger company, it’s really going through, again, where is the data and what are we trying to protect against?
Are we watching for data exfiltration from employees leaving? Are we trying to watch for people getting in and getting access to things that we aren’t supposed to? Are we dealing with PHIPA and trying to protect medical data, and where that data lives?
So it’s really all about where the data lives, and then making sure that you have clear documentation and clear oversight of what all the tools are supposed to accomplish.
And that’s an area that I think falls down quite a lot.
Tools get put in place, a person leaves, the next person doesn’t know they exist, and they put their three favourite tools on, and then they leave.
And all of a sudden, we have tool soup, and nobody knows what exists.
And I think with AI, this really should be something that there’s no excuse for anymore.
You document it, you go into Claude, you ask it to look through the documentation and help you to understand what is where and what it’s doing.
And that way you can start and trim things down and really manage it. You don’t have to try to process 200 documents in your head anymore.
Robert Dutt: That is a blessing, I have to imagine.
You mentioned audits and that sort of thing. What do you find works to demonstrate the value of cybersecurity spend to customers?
It’s difficult to prove the value of something that didn’t happen.
What are the metrics or outcomes that you use to show customers that their investments are making a difference, are in line with where they want to go and where they want to be?
Adam Bowles: Yeah, I think it’s a combination of two things.
Because I think cybersecurity does cover things like disaster recovery and some of those pieces, I think it’s just showing them a picture, giving them a very clear picture of, in the event of some of these emergencies, what will happen and what are you prepared for, and what’s it costing you to actually be in that state?
And that way the client has a very clear understanding of, if my server blew up tomorrow, it’s going to take me three days to get back up and running.
To be in that state, because of the complexity of my network, it’s costing me $20,000 a year because I have Azure servers on standby.
That gives them a very clear picture of the cost, the benefit, and what that’s outcome is.
From a cybersecurity tool, I would say it’s similar, again, to some of the documentation, but I’d probably be doing something a little bit more visual, giving them an idea of what are the different tools and what are the assets and the entry points that they’re protecting, and what are they actually doing?
And giving them a little bit of statistics into what’s getting picked up, because most of these tools try to justify their worth.
Pulling out some of those reports from those tools and giving them a little bit of statistics as to what those tools are actually doing, and making sure that there’s no overlap between the tools for them.
Robert Dutt: Okay, last one for me.
For an MSP who’s listening to this conversation and thinking about how they and their organization approach cybersecurity with their own customers, what’s the single most important thing you’d encourage them to reconsider about how they’re advising customers or allocating budgets, or just managing multiple customer security states?
Adam Bowles: As much as some might not like this, I would say it’s very much people first.
Because I think the people are where the biggest vulnerabilities happen, but the people also have to get their jobs done.
The reason that cybersecurity exists is to protect their work.
If we make it so tight that they can’t work, we’ve defeated our entire role.
So I think we have to remember, as cybersecurity experts, our job is to let people do their jobs, first and foremost, in a secure way.
And I think having that mindset is something that sometimes gets lost in translation, and people just try to lock everything down.
But then it can make it so people can’t work, they can’t innovate, they can’t experiment.
And this is what can bog a lot of these larger corporations down, because they just get things tightened so much that they can’t try new things.
Or they haven’t been able to introduce AI to their company three years in since it came out, because they had to wait. They weren’t allowed to do it yet.
And I think that’s where we have to find that balance as security experts between keeping our companies secure and letting them do their jobs and get work done.
Robert Dutt: I know I said last one, but I want to follow up on that.
I assume that you’re, as your own organization, observing some of that people-centric security model that you described there.
I’m curious how that has informed or shaped how you hire, how you train, how you structure, how you work with customers.
Adam Bowles: It really does, because it means that as we’re hiring, I’m having to look for people culture-wise.
Because there’s a lot that you can do. You can train skills, but you can’t train culture.
How do people question and interact with each other when you have a person on the team who pays heavy attention to security?
How do they push that stuff out to the team members, and how do they collaborate to find the best ways to do things?
I find a lot of security people that we’ve had through, they put out their policies and they expect them to be followed and to just do the thing exactly.
And they don’t listen to how people do their jobs and the impacts of what they’re doing.
And so that’s really changed how we hire and how we interview.
It’s looking for those collaborative skills. Can they look at the big picture, or are they just focused on security to the point of not letting work get done?
Robert Dutt: All right, you’ve given me a lot to think about here. You’ve been generous with your time.
Thanks for taking the time to talk about how you guys see security with customers.
Adam Bowles: Thank you for having me.
Robert Dutt: My thanks to Adam Bowles, CEO of ACT360, for joining me today, and thank you for listening.
There are a few things from this conversation that I think are particularly worth taking away.
The first is that buying cybersecurity tools and actually implementing an effective cybersecurity program are two very different things.
Adam’s example of businesses paying for security awareness training software without having anyone responsible for ensuring employees complete the training really brings that one home.
And it highlights something important for MSPs: before recommending a product or service, it’s worth establishing who within the customer’s organization will be responsible for making sure it gets used properly.
Because even the best technology has limited value if the processes and people needed to support it aren’t in place.
The second is the importance of organizational culture.
Adam made the point that MSPs can change a customer’s technology, but changing how that customer manages people and approaches security is a much bigger challenge.
That means successful cybersecurity engagements require more than just technical expertise.
They also require an understanding of how the customer’s business operates, who makes the decisions, and how employees are involved in implementing change.
Finally, I really liked Adam’s closing observation about the purpose of cybersecurity itself.
The objective isn’t simply to lock everything down as tightly as possible. It’s to protect the business while allowing people to work, collaborate, innovate, and get things done.
That’s a useful perspective for MSPs advising customers on where to invest their security dollars, particularly when those dollars are limited.
If you enjoyed this conversation, please subscribe to the podcast wherever you get your podcasts. We’re on Apple Podcasts, YouTube, Spotify, all the usual suspects.
And if you have a moment, a rating, a review, or a recommendation to a colleague is always appreciated.
Until next time, I’m Robert Dutt for ChannelBuzz.ca, and I’ll see you in the channel.

Be the first to comment