#108 Buzz Word Buster Cybersecurity

Buildings of Tomorrow ·

Show notes

You're wondering what "hardening" or "zero trust" mean exactly? Don't look for the answer on the internet or in a dictionary, where would be the fun? Jon Lester and Alina Matyukhina recorded another buzz word buster episode which will tell you a lot about the vocabulary used when talking about cybersecurity.

Transcript

Hello and welcome to Buildings of Tomorrow, your Smart Buildings podcast. My name is Jon Lester, and in today's episode, we are doing a buzzword buster about cybersecurity. Now, a buzzword buster in this episode, we spend a little bit of time talking about those industry terms, uh, some of the, the words or the acronyms that you hear in the industry about these specific topics to try and make it a little bit easier for you to understand what's going on and what are people talking about in these topics. And as I mentioned, today is all about cybersecurity. And I'm joined by Alina Matthewhina. She is the cybersecurity manager of building automation at Siemens, uh, building products. Uh, Alina, thank you very much for joining us. Hi, John. Hi everyone. Thank you so much for inviting. I'm very happy to be in this podcast and speak more about my favorite topic, cybersecurity. And we're very, very happy to have you. We've, we've had several conversations in the past, uh, on different cybersecurity topics, a lot about Bnet Secure Connect. So thank you again for, for giving us your time and expertise to do this buzzword buster. And if there is ever a topic that is just loaded with buzzwords, it's cybersecurity, right? There are so many different things. You know, from different types of, of cybersecurity attacks right through to more industry-specific topics that it's almost impossible to keep, keep ahead of. So, thank you so much for joining us. We're going to focus a little bit more, let's say, in our, our building industry, let's call it, um, initially, uh, but I could also imagine this is not the last time we talk about buzzwords when it comes to cybersecurity. Now, Alina, are you ready? Because we have a list of, of buzzwords that we put together, um, and there's a lot there, and we're going to, we're going to keep your brain, your brain running, keep your, the ideas flowing for this one. So it's going to be quickfire, and we'll keep you busy. Um, let's dive straight in. The, the first buzzword or, or first buzz phrase that we have for cybersecurity is defense in depth. What does defense in depth mean? So this is, uh, I would say a very um common uh cybersecurity concept uh and you will see, I would say it's a best practice for the industry. So the goal is uh to build the multiple layers of cybersecurity. And in case of, let's say cyberattack, if there is one mechanism which doesn't work or fail or interrupted, there is always in place other, other cybersecurity layers, cybersecurity mechanisms which can provide adequate level of cybersecurity. For example, in our building automation, we are saying that um we need to protect everything from operational level to field level, from physical access control to network protection, and defense in depth only will work if this protection will work simultaneously. OK, perfect. So it's It's having multiple different systems, multiple approaches to give you the best chance to, to remain secure, and if someone bypasses or is able to get past the first level, the second level is there to help protect you and so on. Exactly. OK, perfect. I like it. It's, it's almost like, uh, you know, the castles in the Middle eagle. If you got through the first wall of defense, the second wall is there to back up. So I think this makes sense to me. I like it. Uh, the next one is separation of duties. Mhm. So separation of duties, uh, I would say you will see this buzzwords in the access management access controls, um, it means, uh, that, um. We need to don't have, don't put a lot of power to one individual. For example, software developers, they don't need to have access to, let's say, production data and systems. Another example would be access rights of system management and system administrator have to be separated from, for example, access rights of database administrator. Because in case of cyberattack, if a user or account is compromised, there is no, there is no impact to another account or service. OK, so it's not putting all the eggs in one basket, ensuring that, you know, if, if we do have a compromise situation with one particular user or one particular account, it doesn't open the door to absolutely everything. Yeah, that's true. Perfect, I like it. Uh I think we're going a little bit in the same direction when we talk about least privileged principle. What's the least privileged principle? Uh, so yeah, least privilege, uh, I would say it's also, um, you will see in access management, but it's a little bit different from separated of duties principle, uh, because, um, uh, for example, if you have a service or account or user, uh, they need a bare minimum of privileges to. To make done a certain task. So for example, if there is a service running on the system and it has a user root privileges, it means that it can actually, you can access everything on the device and you can manipulate everything on the device. And in case of cyberattack, if there are a lot of processes they're running with. router privilege, cyber like hacker can take down the whole system. So that's why we are saying in billing automation that all systems, they all services, all applications you have on the device, they should really run with the least privileges. OK, so making sure that again rather than a user, if a device or something like this is, is then breached. You you still have only a certain amount of access, a certain ability to make, make changes within the system, perfect, um, I think some of these things go together, but the next buzzword we have is hardening, or cybersecurity hardening. Mhm. Uh, hardinin, uh, so you will see this term, I would say, um, in documentation, for example, uh, manufacturers, uh, they, um. Publishing cybersecurity or hardening guidelines. So these guidelines, they provide configuration information of the products, for example, how they should be installed in the In the project, uh, what kind of services have to be disabled or enabled? what kind of, uh, for example, firewall rules that you need to also configure in your project and so on. So this is the kind of standard information which you need to provide secure commissioning and also secure operation of the product and system. Thank you. So guidance for anyone who's actually put deploying a system, guidance who's taking a product and putting it into situ, uh, of what they should do or the, the, the minimum or the level of expectation of some of the actions they should take to give you the best chance to be successful, to, to, to make it as secure as, or part of a, a, a secure approach. Um, I almost said the next buzzword just then in the last sentence, um. Uh, this cybersecurity approach, we talk about a holistic approach. What is a holistic cybersecurity approach? So a lot of companies, they are applying this holistic approach to security, which means they are concentrated on 4 basic factors. To improve security in the organization. So these four factors there, it's the people, communication processes, and technologies. So people, they have to be educated on cybersecurity. They should have a broad awareness about possible cyber threats, for example, what is it, phishing emails, how to recognize malicious links in the mail, and so on. Uh, that's why, yeah, I would say that you cannot provide a secure solution if your employees, they're not trained on cybersecurity. And then communication, of course, uh, when it's clear and concise, uh, it actually helps your organization to build a culture of cybersecurity. Processes, which are actively applied, they are becoming as important as technologies. in protecting organization and of course technology has to be tested, also improved to fight with this sophisticated increasing number of cyberattacks. OK. So, the holistic approach, and you'll probably have to remind me of the 4 again, but there's people, communications processes and technology. OK, so all of these combined give you the best chance to have something that not only works today but will continue to work and be maintained and give you this, this, this cybersecurity delivery as expected. Exactly for your organization, these four key factors, yeah, perfect, and I guess this links a little bit back to one of the The first buzzword that we talked about was defense in depth, you know, this is training your people, physical access control, all of these different things combined, um, you need to work together, because training your people, but then not communicating some of the things that you find is a breakdown in that process, which, which means that you have a failure at some point. Perfect, thank you. Uh, now the next two, Uh, are relatively similar, but I guess it's important that we differentiate between the two, there's cybersecurity by design, and there's cybersecurity by default, let's start with cybersecurity by design. OK, so this is a very common term in product security. Uh, it means that, uh, for example, manufacturers, they include in cybersecurity in the initial design of the products. A cybersecurity by default, another term which you mentioned, it's actually when for example you already developed a product and then you want to release it for customers to use. Yes, so cybersecurity by default, it means that you actually Remove all insecure features in your product, so you make like a product secure by default. For example, let's say Port 80 have to be closed because it's insecure. So if Port 80 is closed on the product, it means that it's secure by by default, and yeah. There are a lot of other examples can be provided. So, so secure or cybersecure by design is, as you mentioned, during the, the design process, the research and development process, you've always got cybersecurity as part of the workflow to make sure the decisions you make along that development process, um, will deliver a product that, that has the right capabilities at the end. Um, and then cybersecurity by default is if you take that product and plug it in. Yes. The standard settings, the, the, you know, the, the default settings within the system, are the most secure that that product is capable of doing, and, and I like the example you use, you, you plug it in, uh, you know, port 80 is, is disabled, you could as a, as an engineer, make changes to those if you wanted to, but the the standard default system settings would, Give you the most secure system settings that that are possible as an example. Yes, yes, perfect, I like that, I think, and they're also very different, so but they stand, they sound or look a little bit similar, so I think they're a good one to, to, to differentiate from. Uh, the next 10 trust. What is zero trust? Well, zero trust is a very new term in our industry in operational technology, but it's already exists in IT, I would say, and zero trust, it's when there is a belief that organization, they shouldn't trust anything inside or outside of its perimeter. They like organizations should verify everything we try to access. Uh, and, um, of course, uh, I would say it's very different from traditional approach which we all used to nowadays. Uh, so in traditional approach, uh, if there is something in corporate network inside of corporate network, it's already by default, it's trusted. Uh, but zero trust, it's like really you don't trust anything and you verify everything before. Before release access. OK, so you, you authenticate every device, every user, every communication, every piece of information that's passed, all needs to be authenticated, whether it comes from. The device next door which sits in your system, which is in your building or it comes from outside. OK, yeah, I mean why we are changing this from traditional approach to zero trust is because for example, in corporate network you can find right now a lot of IUT devices like Also cloud connection and this is somehow breaks the paradigm, you know, as it was before corporate network was separated from, for example, operational technology and so on, but right now we really need to improve security. That's why we are saying that zero trust it will be our future technology. OK, so. So the advent of some of these new technologies you mentioned IoT there, cloud connectivity, device connectivity, all of these things enable some great features and functionalities, but they are all connections outside that corporate network, which means that they're, You know, we either start to look at every single one of those connections and ensure that they're secure, or we take a zero trust approach, which means no one is trusted, everyone needs to be authenticated, and everyone needs to be tested before communication can, can ensue. Exactly, yes. Beautiful. I like it, thank you. Um, the next one is threat and risk assessment. What do we mean when we talk about threat and risk assessment? Uh, so strate risk assessment, um, it's a very good term and it's applied every time when, uh, you are dealing with the products. Uh, during the whole, uh, product life cycle, you need to manufacturers they are doing this product. threat and risk assessment to verify if there is, uh, for example, potential risks inside of the product or develop like features, uh, functionality of this product, and also to fix these potential risks. Uh, so I would say that uh this threat and risk assessment, it started really from initial design of the product and also uh repeats uh from like during the whole life cycle. Uh, for example, if you have a significant change of your product, uh, then you need to do a strategy assessment again. Thank you. So start of the part of the standard operating procedure, do, do an assessment, go through the process to understand where the risks live, and then whenever there's serious updates or significant updates to the product or portfolio or software or whatever it might be, go through that process again. OK. Perfect, thank you. Um, the next is pen testing. Now, I'd be interested in, you know, pen testing is a shortened phrase. What does pen testing stand for, and then, and then what do we talk about that? So pen testing, it's a penetration testing, and it's done usually by third party organizations who are very professional in this pen testing for what they are doing. So it's actually the idea is to break a system to make it more secure. Yeah, and if it's, for example, threat and risk assessment is done by manufacturer for pen testing, it's better to involve a really third party organization who is specialized in this and can find those risks which is not, for example, couldn't find companies. OK, OK, so it's, it's, it's a process of getting a product or a solution or a system or whatever it might be and trying to break in, trying to break it. Trying to, to circumvent the security features, and by doing that identifying potential weaknesses so they can be fixed and and updated or whatever it might be, yeah, very true. Perfect, I like it. Uh, the next one is security patch. I guess if you did a pen test, after you've done a threat and risk assessment and then you've gone through the pen testing process, maybe you find an issue, uh, and you get to a security patch. What do we mean when we talk about security patch? So it's a security fix. Um, and, uh, you're right, after, for example, we are done with the pen testing, uh, uh, or some organizations uh reaching us, uh, regarding vulnerability, uh, then, uh, uh, next step is to release a patch. Uh, to remove this vulnerability in the product, so you can remove like known and new vulnerabilities to be able to improve the whole protection level of the product. OK, so when we find a problem, a way to fix it. So whether it's software or firmware or whatever it might be to, to, to close that door to, to bridge the gap. Yes, perfect. Um, I like all of these have been in a little bit of an order, which is nice. The next one is incident handling process. How does this fit together with some of the previous buzzwords? OK, in incident handling, you actually have a notification of the incident. For example, customers, they can reach to manufacturers and say that the OK, we think that there is a vulnerability, you know, or incident in the product, or, for example, security research researchers, they can find something sensitive, and then, uh, uh, after manufacturers they receive this notification, they of course analyze it with security experts involved and, uh, then, uh, um, they are, uh. Again, they are producing these fixes security patches, so it's called mitigation, mitigation, and of course you need to have a disclosure, so you need to manufacturers they are oblique obliged to notify us. Customers of the potential incident vulnerability and also provide a fix which is patch this fits nicely into that communication box from the holistic approach when there's an issue, you react to that issue, you fix it with the patch, but you also have to tell all the people. There that may use a product or work with the product that there is a patch that they should do, how urgent it is, what the risks it would bring with it, etc. etc. Yes, so you see, like there is a really high dependence on people, technology, communication processes to keep it all secure. It's all tying together nicely. It works well. Perfect. Now the next 3, you know, we dive into a little bit of industry standards and things like this, so. Let's start with the first one, IEC 62443. What is IEC 62443? Yeah, this is a very important buzzword. You will maybe hear it everywhere from every corner. So this is a series of the standard which is specifically for industrial control systems, uh, for our building automation controls. And there are kind of different sections of the standard. So for example, Section 2, sorry, 42, it provides the requirements for security of the product. So manufacturers, they are using it in the daily like deployment, developing of the product. Uh, based on these requirements. Uh, also, for example, section 33 speaking about uh how to secure actually the whole system, what kind of requirements you need to fulfill. Uh, and, uh, based on the standards there is a different, uh, certification available, so manufacturers, they are actually uh certify their products based on the standard because, uh, how you can, uh, show, uh, security, of course, uh, by using certification of security, um. Yeah, so this one, it's, I would say. Um, It's uh this standard is used mainly in the Union and also Asia, but for example, for US there is another standard which is the UL 2900, and it's more popular in the US. And, and is it a safe, or maybe the question is, are there really significant differences between between the US and the IEC standard, or are they built on some similar base? Yes, yes, yeah, exactly. They are built on a similar concept, maybe a bit different is based on the market, of course, yes, but the concept of cybersecurity of product system is similar. Yeah, I think that that's a really important one, as you mentioned, because, uh, as you say, how do you measure cybersecurity? You need something to measure against. So you need, you need a standard and you need the certification to approve compared to how you do that. So that's an important one, especially for those out there listening that may. You know, we may be comparing a product or may be looking or they want to have a better understanding about the approach that's been taken. Those standards are a good thing to compare consistently across different systems and whatever it might be. Yeah, and for, for example, people like customers who really wants to know is like this product secure, they really need to look on the security level. In the certification because there is for example security level 1 which actually protection against like unintended misuse or just errors and it doesn't have a very high level of security. …

Full transcript (WebVTT)