ISO 27001 Explained_ 12.2 Protection from Malware

EDUCATION - NATURE - SOCIETY
6 followers
2 Video Views·May 11, 2025
Comments are disabled for this video.
Welcome back everybody.
My name is Christian Hyatt.
I'm the Managing Director here at RISC-360 and I oversee our ISO 27001 practice.
This is our ISO 27001 Explained series where we help cover every control and control objective
in ISO 27001 to help you implement the program and hopefully achieve certification.
Today we're covering off on Control Objective 12.2 Protection from Malware.
Now in this control objective, there's only one control and that's Controls Against Malware.
However, there is a whole lot to think about when you're thinking about malware protection
for your organization.
And the reason is because there's a lot of techniques, a lot of nuances, and different
types of environments to consider when you're thinking about malware in general.
So one way that I like to think about this control is to break it down by environment.
When you're thinking about malware, one environment that you might think about is your endpoint
device, so laptops, desktops, things like that.
And you might have something like a common antivirus tool set or some type of advanced
antivirus malware protection installed on those devices.
That's what most people think of when they think of malware or antivirus.
The other place that you might want to think about it is on your infrastructure.
So I want to talk about each of those and some of the techniques that if you're considering
implementing a program or if you're auditing a program, you can consider too.
It's also important to note that this control talks about protection against malware.
It doesn't necessarily mean that you have to have antivirus installed as the only control.
It doesn't mean that having something like antivirus installed is enough either.
So let's think about some of the ways.
And I want to point out here on the standard.
So on the left hand side of my screen I have the ISO 27001 framework up and on the right
hand side of my screen I actually have the implementation guidance.
So as you can see, while there's only one control in 27001, there's several pages or
two full pages of options when it comes to implementation guidance that literally go
from A to I and with additional information here.
So some of the things that ISO points out that you should consider is, for example,
on your endpoint device, on your infrastructure, having malware tool sets installed but also
things like vulnerability scans.
Also things like application whitelisting or application blacklisting.
Different kind of monitoring controls so you can see if a different software or malware
is installed.
You could also have things like regular reviews or approved software lists, that's the whitelisting
and blacklisting element.
Also thinking about email scans.
So if you have emails that are scanning for malware, ransomware is huge right now so can
you detect a malicious piece of software from email.
So lots to consider when it comes to the malware environment.
Something else I want to point out is on the infrastructure side, especially in the modern
technology stack, it might not make sense to have something like antivirus or malware
installed.
Especially if you're doing something like source code or infrastructure as code in like
a DevSecOps environment or a DevOps environment.
So a couple of things, resources that I'd love to point you guys to is additional reading
outside of this video.
One, SANS has a great course on DevSecOps that I recommend that I've heard great things
about.
Take that course.
I think that if you're thinking about how to automate and integrate security into your
modern cloud stack infrastructure, especially infrastructure as code, that's a great class
to take.
They have also a great white paper available that kind of walks through the whole continuous
integration and continuous development environment in a DevSecOps perspective and they actually
list out different tools and methods that you can consider to integrate security into
that and prevent malware ultimately.
My favorite white paper, of course, is authored by our team here at RISC-360 that does the
same thing.
It covers an end-to-end DevOps lifecycle and where you can integrate security in an automated
basis into that lifecycle to help prevent malware.
And we also list a bunch of tools that you can consider, both open source and paid-for
tools that are very popular in the marketplace that might help you consider some of this.
So those are some of the considerations.
As we mentioned, consider your endpoint devices, consider email scanning, consider infrastructure
and all of the different potential techniques to prevent malware and you have this control
covered.
You can see why there's a lot to unpack, although it's only one control.
So I hope you found this video helpful.
As we continue our journey through Control Objective-12 on operations security, continue
watching.
We're going to break up these videos separately because there's a lot to talk about, even
though some of them only have one control.
So I hope you found this helpful.
If you have any questions, feel free to reach out to me, Christian Hyatt.
Thanks.
Bye-bye.
