Cybersecurity Challenges in Multicloud Environments – Rajesh Deenadayalan, Hitachi Vantara
Rajesh Deenadayalan, director of cloud security services for Hitachi Vantara, explains why cybersecurity is becoming so much more challenging as more workloads are deployed across multicloud environments.
Transcript
This is Textron TV. Hey guys. Thanks for the throw.
We're here with rejection and dialing who is director of cloud Security Services for Hitachi Ventura. And we're gonna be talking about devsecops and Cloud Security in general and the state there are just welcome the show. Thanks, Mike.
Thanks for having me. I feel like we've been talking about this topic for a very long time but it's not clear to me that progress is being made and maybe it's just Harder Than People realize but we're talking about shifting things left towards developers. But sometimes we don't give them the tools and when they do put stuff up in the cloud, there's a lot of misconfigurations because people don't exactly know what they're doing with all those apis.
So what is your sense? I mean, am I being too pessimistic is progress being made or do we just have a long way to go still? Yeah, I think I think the progress is being made.
So Dev psychopsis still evolving within the industry and there are there are different ways in which people pursue their psychops, right? So are through hark Cloud Security Services. We take a holistic approach towards the devsecops using our modern security framework.
So our deaf secops framework is built using a security by Design and security by default approach. So what we mean by that is, you know, taking a shift left and a shift right strategy within the desktop spring work. So how does that work?
Exactly? Is it a cloud service or a framework with some built-in tools that is tied into my devops workflow or how exactly does one take advantage of this? Yes, so just to give a background.
So how does Hitachi application reliability Center so which is a Confluence of finest engineering Talent tools processes framework. Everything coming together to operate cloud workloads in a much more secure and modern day. So it's a combination of multiple things, you know, and and the primary focus is how how modern workloads can be effectively operated in the cloud from resiliency from a security and cost standpoint.
So is that essentially a managed service that you guys are managing on behalf of the customer who's then building the applications per se but you're taking care of all the infrastructure management and the workflows around that. Absolutely. Yeah, it is.
It is a mandate services that we manage end to end event operations for customers. Do you think more people are starting to consume devops as a managed service because it's getting a little more complex out there with all the security concerns historically a lot of people have built this stuff themselves. So what's your sense of how many organizations are going to shift to a managed service?
Absolutely, I think as we talk to customers what we hear from them as they look at Cloud security as one of the major concerns as they move their workloads into the cloud this is because they think cloud security is complex because of the because of the agile nature of the cloud that brings a lot of cloud misconfigurations and especially as they adopt more modern services like microservices containers kubernetes, especially across a multi Cloud environment. So this The the notion of security and compliance, you know becomes much more complex for cloud. So for customers so customers look forward to manage services providers certainly, you know, you know who bring in that engineering talent and skill set to effectively manage security on the cloud.
You think that that conversation is gonna be forced more because people are aware of the misconfigurations in the cloud and the vulnerabilities is a lot more talk about software Supply chains. So has this conversation been kicked up a few levels in organizations. So it's not just the development team, but it's the security people and the sea level suite are all part of a bigger conversation.
Absolutely. I think it is. It is definitely you know, multiple teams coming together and and talking about this approach because their Secaucus by itself is how different teams come together and collaborate, you know in a collaborative manner right to to bring that security joint ownership across the development team the IT team as well as the security team.
So so what we what we are seeing is devsecopsis is is evolving in the industry and on the security team requires, you know to work much closely with the development team to to bring that collaborative approach. What is it that you see organizations doing that makes you shake your head and go. Geez.
I just wish we would all kind of understand one or two basic concepts and maybe we'd be a lot further down the path. So talking about you know, so our throughout our devil say cost methodology. So we take a multi-level difference approach.
So what we mean by that is you know, how security can be imposed across the entire digital infrastructure right or the entire digital estate and we call it as the Pisces security model. So which is security across Cloud containers clusters, you know customer data as well as as well as code. So when we say cloud how do we ensure security across the infrastructure and the platform and customers have challenges and understanding the chat responsibility model when it comes to security between the csps and what customers have to do?
So yeah. Do you think we're gonna see a lot more regulations coming down the pike because we are seeing a lot more interest for securing software Supply chains. And is that going to have some sort of impact on how we think about devsecops?
Absolutely, I think especially with the evolving threat landscape and which so much of threat and new attack vectors that are happening in the industry. The regulatories are also continuously changing their compliance requirements. They are strengthening their compliance requirements, you know, frequently.
This also becomes another major challenge for customers in keeping up with their you know compliance changes in the cloud. Of course, we hear about the skills shortage all the time when it comes to anything to do with security. Do you think that that's also pushing people more towards a managed Services mindset?
I think absolutely so one of the key challenges which the industry as a whole has is the shortage of the Cyber skill set. and and you know that becomes a major challenge for customers because the one primary reason why customers look at Cloud security as complex is because they don't have the right engineering skill set to handle it. So with with the right Talent Cloud Security, in fact becomes much more much more effective in terms of imposing a security because of its, you know software defined nature.
So I think that's that's one of the reason why customers are really looking forward to manage services to get that engineering Talent who can effectively manage security for them. Of course, we hear a lot about AI these days will AI save us from ourselves what she which is since it wants the state of the art with AI and security these days. I think Ai and another major role in security space because security of course is all about huge amount of data and and security is also continuously evolving.
So Mission learning and a technique plays a key role in terms of identifying animals Behavior new patterns that are happening in the security in order to be much more proactive and efficient in terms of you know, mitigating our protecting against these data breaches. So looking into your crystal ball for 2023. What do you think?
We're going to see? What do you expect to happen? And what should people be prepared for?
I think of I think the good part is that now customers are realizing that security is extremely important, especially in their in their devops. And that is why devsecops is gaining more and more attention. And and in fact when we were talking to one of the customers the customer business team engaged as for doing a Dev psychops implementation and as we speak to them, we understand that what happens is, you know, they they develop their software and then when it goes to the release their security team comes in which is a thing small team, they find out all vulnerabilities and then send the developers back, you know to fix it.
So they were losing so much of time. So they wanted to take a deep psychops uproach to ensure that security is, you know adapted much earlier in the much earlier in the life cycle. So I think I think customers are really understanding and understanding the importance of security and especially Dev psychops and the shift left approach that they should take do you ever think that we will no longer need the term devsecops because Security will just be part and parcel of the whole thing and then from the beginning and maybe we don't need a cumber with some kind of terminology or do you think it's devsecops to stay?
Maybe I think eventually this might change because one reason why it moved from devops to Dev psychopsis because you know, we wanted to emphasize the importance of security across the devops pipeline. So I would say this is still in an evolving phase. But once a security becomes an integral part of the process, whether it is, you know, setting up of an infrastructure or application development security should become part of the design.
So that's why you know in our services we call it as design for security because security should not be an afterthought or a bolt on tool that comes in later in the process. So when that maturity comes in the industry, maybe this term devsecots will change to something else. All right, folks.
I think we all know that there's a little bit of a dirty Secret in this industry about how all these vulnerabilities are out there in production code and they're some that we know about many that we don't but I got a feeling we'll be fixing them all as much as we can real soon. Hey rejection. Thanks for being on the show.
Thanks, Mike. All right back to you guys in the studio.