What is cybersecurity as a service (CSaaS)? Why should I care?

Security & GRCVendor/Product Assessment
1.8k viewscircle icon3 Comments
Sort by:
CEO and Co-Founder in Software4 years ago

It's a forcing function. What I'm hearing from customers is that they don't have the people and even if they get the people, they can't retain them. They're not excited doing the same thing everyday and they're being pushed every second. So it’s a way to solve the people and skills gap.

Lightbulb on2
Director of Technology Strategy in Services (non-Government)4 years ago

If you're going to outsource your security, you can outsource responsibility for keeping your company secure but you still need to have someone in the company who's accountable for that security, for that outsourcing and for overseeing who's doing it for you and who understands it. That's probably the biggest gap that most organizations are dealing with. I can't speak for those outside New Zealand but it probably isn't much different in many other countries as well.

Most companies assume they're paying these vendors to make sure that the company's safe and secure but are they actually keeping on top of it enough to understand what that means? And do they have someone there as a proxy security manager who actually makes the decisions and calls the shots, so that when the reports come through and the vendor turns around and says, “This is what this means for you,” someone is actually making an informed decision on that end? I'm not sure that's happening at the moment.

Lightbulb on2
Board Member, Advisor, Executive Coach in Software4 years ago

There was a poll on the Pulse platform that asked whether you’re embracing cybersecurity and I found the results interesting. 24% of people said yes, they're embracing cybersecurity as a service using a managed security service provider (MSSP). 28% said they’re embracing managed detection and response (MDR) or extended detection and response (XDR). 35% said yes, but they're shaping their internal efforts that way and about 13% said no. 

I'm happy to see that people are embracing cybersecurity as a service (CSaaS), even for an internal approach because it gives you more established service-level agreements (SLAs). It also provides better metrics and reporting, which you can use to demonstrate to management how you're doing and what outcomes they're getting from it.

Lightbulb on2

Content you might like

I wanted a point of view on migration from on-prem AD and SCCM to AAD and Intune. Would be great to have a perspective on, - Is there a real need since SCCM is still undersupport from Microsoft? - I understand that we can get rid of onprim AD Infrastructure and move on SaaS, but any other benefits we get by doing this?

Do you have a lock out policy for system accounts? If so, how many attempts do you have it set too? 

Have you considered not having a lock out policy where accounts are vaulted / rotated & standing access is removed?

I'd like to discuss the privacy and data security implications of compromised accounts where a CoPilot (such as Microsoft's) is profiled on an account. It's clear that this poses a significant security risk, as a CoPilot with access to all our Graph services presents a unique attack vector. Those interested in learning more about what can be accessed and seen should feel free to ask. In cases where an account has been hacked, a thorough data-mining activity is often necessary to assess the extent of the breach. Have you thought about?

I don't have any concern about.16%

I feel there is a gap... but I haven't thought about before75%

I already have something on track to fix it6%

Other1%

View Results

It's been announced that Windows 11 will be serviced on a monthly basis, similar to Windows 10's infamous "Patch Tuesdays". What's the ideal service cadence for this OS?

Updates should be released daily.10%

Updates should be released weekly58%

Updates should stay monthly.22%

Updates should be pushed quarterly.8%

Other (comment below)

View Results

Does someone have advice on how they have balanced the risk/reward as it relates to introducing Open-Source Software to organization? My org is dipping its toe into the OSS world and the architecture and risk governance teams are looking to get ahead of these requests by coming up with policies and standards for OSS technology being brought into our environment. To clarify, this is not for software development and CI/CD pipelines, SDLC etc. This is for installing solutions that already exist out there (Zabbix, GreyLog, Prometheus etc.) into the organization's environment. We are looking to provide a balance on the obvious risk with the ability to move fast (like everyone else now).