ISO 27001 Explained_ A.10 Cryptography

EDUCATION - NATURE - SOCIETY
6 followers
1 Video View·May 15, 2025
Comments are disabled for this video.
Hi, my name is Christian Hyde, I'm the Managing Director of X360, and I oversee our ISO 27001 practice.
And this is our ISO 27001 Explained series, where we cover all 114 controls of the ISO 27001 standard,
and try to provide an explanation to help you have some guidance if you're new to the framework.
Today, we're going to cover NX10, or Control Objective 10, around cryptography.
Cryptography only has two controls, as you can see here on the standard,
but these controls are somewhat nuanced, so I'm going to walk through some of the things that you need to think through as you navigate these controls.
So, 10.1.1 is around policy and use of cryptographic controls.
So, what this looks like is that you need to have a policy in place, defining what is a cryptographic key,
how do you control it, what kind of encryption do you require, that type of thing.
I'm going to show you a policy here in just a second, I'm going to walk through what that would look like.
And then, the second control, 10.1.2, is around cryptographic key management.
So, if you have encryption keys, how are you storing them, how are you rotating them, how are you ensuring they're secure, that type of thing.
So, to get into detail on these, I'm going to go into our example policy over here.
So, if you're a RISC 360 client, you'll have access to all of our policy templates,
and what we'll do is we'll help walk through the strategy when it comes to cryptography,
and walk through every layer to come up with a customized approach, but we'll start with this baseline.
So, in our policy here, 10.1.1, establishing the policy, some of the things that we're trying to think through is,
what is the applicability of encryption?
So, some of those decision points we're thinking about, how are we going to do laptop and in-point device encryption,
how do we encrypt applications, file servers, databases.
So, going through your inventory of assets and thinking about where data lives and how you want to encrypt that data,
and if it's appropriate to encrypt it.
The other thing you want to think about is encryption in transit.
So, that means thinking about email or web browser traffic as things travel from one place to another,
and how you want to control that.
Things like VPN tunnels, remote access, email, remote desktop, web browsers, as I mentioned,
and just defining those.
So, what is the applicability of encryption?
Then you want to make sure that you define in policy that you have to use a strong encryption standard.
These standards are rotating all the time, so I recommend reading something like NIST
and figuring out what an appropriate encryption standard is based on your list level and technology that you're using.
And then you want to talk about key management.
So, some of the decision points around cryptographic key management for control 10.1.2 is around, for example,
when you encrypt something, how do you store a secure key to decrypt it?
So, a decision point should be your laptops, if you enable BitLock on a Windows device, for example.
Where do you store the encryption key in the event you need to decrypt that hard drive?
If your engineers use SSH keys to access a production environment, how do you store those keys?
If you use any kind of cloud infrastructure or even leverage technology like AWS's KMS or Azure or GCP's equivalent.
So, working through your different assets, deciding a few things.
How do I encrypt data at rest? How do I encrypt data in transit?
And then how do I rotate and protect encryption keys across all of my technologies?
Again, there's only two controls in A10 cryptography,
but as you can see, there's a lot of decision points that need to be made to think about how you're going to manage this.
So, I know that's a lot, but I hope this was helpful.
If you want more information, you can continue watching our ISO 27001 Explained series
or check us out on list360.com and we'd be happy to help.
Thanks.
