Kunal Anand, Imperva | RSA Conference 2023
Cybersecurity wargaming can help security teams proactively develop and test playbooks before a data breach occurs to sharpen overall incident response and communications programs. Learn more about the benefits of wargaming and how to build effective incident response playbooks.
Transcript
This is texturung TV. Welcome everybody. Welcome back.
We are here at rsac 2023 in San Francisco joined by a very special guest. I've done some podcasts and zoom conversations, and we finally get to meet in person. And you know, there's something just really special that it's nice to connect with you.
Come on. Welcome man. Hey, it's so good to see you in person good to see you as well.
So since I talked to you last you're now siso and CTO with him. That's right. So on one side, but the CTO role I get to build in the build is products technology strategy, and then I also get to protect.
And I get to protect our customers impervians our partners all of that. So it's a dual role and you know, it's fascinating is one feeds the other. Mm-hmm.
Well kind of the learning back and forth from both. So it's hopefully the this the stove pipes of the blood the walls that are always built up that we talk about. Hopefully they're going down anyway, but it's much easier to get communication flowing and what do we do for improvements?
What do we do to make the product easier better secure and you know, I I use all the products. So the nice thing about it is I get to kind of be that you know, that first user that Alpha user that beta user that can provide feedback because if it doesn't work for me, how's it going to work for somebody else? And then at the same time, you know, this has been a truly special show for me because all previous rsas.
I would always attend as a CTO. Mmm. So your vendor you're talking to people as a CTO and you have very different conversations because it's all about products technology.
But then coming in as a SEO now I'm having these totally different discussions because they're my peers. Yeah exactly. You're at a peer level as well as in some case or many cases customers.
Yeah, but tell me about that conversation. How is that different? Yeah, so what's really refreshing is we kind of just cut through the noise of you know, we're not talking about specific vendors.
You know a lot of what I had to do when I came in was reestablish our risk register. And you know, there's been a lot of change in the Cisco Community where there's newer csos. Now that have taken on great positions at some great companies and getting to talk to them about how they've built their risk register.
They've designed it how they've constructed it and then what's on their roadmap what's on their agenda? How do they organize their teams? How do they project manage various initiatives?
How do they communicate with their boards? How do they interact with their peers? And when I took the role on I was really serious about about it and I just started having conversations with great seesaws who I know.
Ask them, you know. Tell me what you know, what what's amazing about what you do? How do you how do you kind of go into it?
What are some of your mental models things that work really well for you? And I I soaked all that stuff up like a sponge. I'm such a such a nerd for for like productivity and you know mental models and all that.
It's been great. I think we talked before about you're interested in security going way back into movies when you're a kid and yeah with those interests too. I'm curious.
How does your your role as a CTO? How does that how does that help you be a better see so Yeah, well, it pushes me and a totally different way. So when I was talking to cisos and you know, I've gotten to work with plenty of cisos over the last 20 years many of them basically are very set in their ways.
I would say she says for a very long time. I've just been you know, it's got to fit into these nice packaged Frameworks, whether they're Frameworks provided by the government or regulatory Frameworks or Frameworks that peer groups have sort of designed. I would say that that rigidity.
You know gets challenged. By ctOS mmm because on the CTO side, you're always looking at Innovation. You're always looking at what's new and we were talking a little bit about this before we started rolling AI right AI is such an interesting thing where every single week there's some disruption on the previous week's models So, you know, we can generate photos.
We can generate video we can now generate audio saw this wild demo this week of being able to generate audio just by uploading 30 seconds of you talking and you know, it's it's wild to see these new Innovations, but it means that csos have to be adaptive as well. And I think cto's are really great at that almost to a fault right of you know, always thinking about what's next. What's next?
What's next? Then I think on The Cisco side, it's always about constraining things to the present. I think there's a healthy tension between the two and so I'm I'm reconciling those things as well.
But there's a lot of things that by combining both. You both can apply and learn it also share with your customers because you know my time in security you kind of learned that it's best way to secure something is don't put it on the network or don't change thing. It's kind of maintaining, you know as much control around as you can so that you minimize your tax surface and the other hand you're trying to innovate you're trying to introduce new technologies.
You're trying to respond to Customer Events. And I think a lot of cisos have had to make that transition to think more broadly about the business and yes, there's Frameworks and there's lots of good things for us to use. It's a moving Target though.
It's not a static thing. You're still spotting. So I was just I just came from a meeting at RSA and I was talking to another sea so of one of the biggest, you know oil and gas companies in the world and we were having a conversation as peers to see so yeah and yeah, you know, he was asking me what was your digital transformation like this, you know, we made a move to the cloud as well.
We're in the same boat as everybody else. I mean, I think that's the one thing. That a lot of people sort of forget when they think about security or technology companies is they're literally going through the same things that you know, you are in your existing business and I look at it like this over the last three years.
We've all transformed right? No one debates going to the cloud anymore. So funny years ago, you know, I would talk to those same, you know oil and gas companies and it was like the cloud no, no, we can't do security and You know what's crazy is I literally saw people take seven year roadmaps to go to the cloud and do them in six months.
So we know it's possible but we're on the other side of that now which is the sort of post-transform, you know postmodern world, whatever you want to call it. And you know, we're having these healthy conversations with each other. What are you doing?
Are you thinking about this? Do you have any recommendations for me? And so we were talking about things like acceptable use policies and things around like AI like do we want our teams to use this stuff?
And it's so interesting because you can meet certain peers who are like no, we won't allow our company to use this because we don't understand it yet. And that's totally fair to take that approach and you have another type of company. That's like, oh no if we we want to do this because we want to continue innovating because if we don't our competitors as well, and so it's just this crazy thing and of course that has ramifications for seaso and so we get into this Interesting set where you can have these great discussions with people and it's like, okay.
Let's philosophically talk about this instead of you know, diving into feeds and speeds because we can do that all day regulatory Frameworks and all kinds of exciting weeks mature necessary the very necessary, but at the same time, you know, there's a place for that and I think as we're just getting to meet each other in person now, right and the fact that we can have this type of conversation in person. Do you really want to use this opportunity where we're just meeting each other for the first time to talk feeds and speeds or you want to use this opportunity to build a relationship and I think people are really going for the latter instead of the form, which is frankly, it's great to see. Well, it's one of the things we do a show called she's so talk and you know, it's only at the top and a lot of roles right where there's a c CEO or see so and I think see so is especially even more so that I think CTO is more naturally networks.
So it's come from more protective more conservative. Maybe you could some people might say paranoid. But it's just the security mindset.
So you're less likely to share at least that's been sort of the Persona is yeah don't disclose a product reviews. Don't talk about what we do but I think so many csos are looking for people to communicate to share with to say, what are you doing? This is what I'm doing.
I need some you know, I got check here. Give me your feedback. Or maybe maybe I'm not working on the right problem, you know, those kind of conversations that you're not going to have over Zoom.
Probably you're gonna have over yeah dinner or set a drinks or you know, good conversation with coffee is that's what this is about. Yeah precisely and I will also say I I've kind of come into the role approaching it and this is where you know, the CTO side's been helpful. You know for a long time.
In technology, we've had open source, and you know, our company has been very transparent about open source, and we put things out throw things up on GitHub GitHub, you know and stuff like that. And that transparency is actually been really great for technology and technologists being able to build on top of other people's learnings. Right?
We didn't have open source. We wouldn't have all these wonderful applications. You wouldn't have that lovely laptop.
I mean that's a running this wonderful operating system that is you know, build on top of years or Decades of Open Source. So I've actually kind of come into this a little bit differently, which is I actually am being very transparent. From the CSO perspective as to what's going on.
I mean if someone were to ask me. Oh, how many applications do you have? How many data stores do you have?
What type of Technologies do you use? I'll tell them. And and the reason for it is if there's a way for me to get better or away for me to improve.
I will absolutely You know incorporate all of that into the way I think but also into the program that we're building and I think the more closed we are about that stuff. We don't really make that incremental progress. Yes.
I'm never I'm not going to tell you where I you know manage encryption Keys, you know, but I will tell you that. I've got certain things that are important to me in Myra's register. I'll tell you the number of applications and data stores.
I have I'll tell you the types of controls that I put in place and what keeps me up and I'm happy to talk about that stuff. And I think it's very different from the sort of existing or the previous generation of cisos that were a little bit more closed and I think we're finding more of this because the folks that are taking on these seesaw rolls now are people who have that technology background and people who can also reconcile software security, you know, I think for a long time a lot of people who came into the role of Cisco and rightly so came in with, you know, more of a network security background because that's where it all started right all the stuff you could go back to three decades this whole network security and you know, we still need network security. But we also need to reconcile the fact that there's network security and point application data, then, you know, you sort of think about it from multiple dimensions and different environments different GEOS out in the regulatory mindset.
And so it's just a skill or it's just a point of awareness that you need to know about. But what I'm really, see now are these sort of broader? Thinking see so is coming into the role and it's changing and I think it's changing for the good that's good.
You know, it's I keep asking myself. Is it me or is this the first RSA where we've really talked about appsac and we've really talked about softer supply chain more than just we can add a few example companies it or attacks, right or just or like exciting and saying like oh that's struts to everybody but we're out of Applause for stretch too or like here's log for Shell, you know, I mean, like I'm just saying, you know, you know, what are yeah, whatever. The latest is your is.
Yeah, exactly about tell me your perspective on that. I mean absolutely come from the technical background software as well as security and network. How is that conversation going internally with software teams and Security Professionals.
And then also how do you see your customers making that transition if they're coming up from a little bit broader technology base and experience? So I think the stack is just changed. I mean you had mentioned to me right before we started about kubecon, right and The thing that I hear in a lot of application security discussions today is all about, you know containers and I hear a lot about kubernetes.
I hear a lot about service meshes. Okay, so if we kind of you I like first principles thinking like what are those things? Right?
Well, it's a new type of substrate for compute networking. That's ultimately what we see it is. Yeah, but it's a software oriented approach.
And when you talk about supply chain, we have to examine all parts of that. And I think what companies are really struggling with is several facets one. How do they kind of take their large monolithic architecture decent decomposed deconstruct, whatever you want to say and you know build it into this or tessellated service.
Mesh. How are they going to do that? And so there's there's questions there that I think technologists are going through.
As they do that they're having in pondering, you know more about API security microservice security this these are the things that they're really worried about and then at the individual workload, they're really worrying about open source. And what's interesting to see is, you know, I get to travel the world and get to see a lot of other people think and get to also see what governments are doing. And so like the Singaporean government years ago put out a whole framework around the supply chain the software supply chain.
They seriously like put together a framework with guidelines and everything that you have to adhere to and I thought that was awesome to see and to the point where they outline, you know, critical cyber functions and roles that every company needs to have and then when you kind of unpack that and I did a search I was like looking through all of it. How many times is the phrase supply chain show up because I was really curious like did they do they actually, you know walk the walk and yeah, they actually do and it's so different because when you come to, you know, the United States, you know, I think it took several big breaches for us to sort of activate and think about this but if you think about it, the supply chain issues are and I've been around for quite some time and that's been notable and I think people are now starting to understand that 95. I think it was GitHub or yeah, I was GitHub in Microsoft put out some stat that it's like 90 to 95 percent of their applications are all built on open source, which basically means 5% proprietary, but the way I kind of look at it is that that 90 to 95 percent you didn't write and so all these companies now are kind of circling back and going okay, we didn't write this stuff.
But we need to harden it in some way shape or form or we need to build better acceptable use policies or we need secure repositories for where we store known good versions of these things and reconcile it with CVS that come out. So I think everyone's just kind of In limbo right now while they try and figure this out figure that out. I think this one of the one of the pluses of cloud native kind of architectures is that if you kind of go back to First principles draw this as a network diagram to a network engineer think of it as that way a service mesh all these API calls, they aren't simply, you know Ingress and egress on the exterior of this model of the applications about how the whole thing talks just like we would see elements in your network would be talking and scaredy and the proxine or firewalls for that API firewalls things like that where she will do to a lot of that in that in your space too.
It's it's now you can have the conversation with security and software professionals and have some common ideas about how things work and I'll be transparent. So when I took the Cesar roll on. We had we you know from the CTO side for several years.
We we were rebuilding our core platform. And we took a monolith based architecture and we deconstructed it into lots of microservices. We use kubernetes.
We use containers all over the place internally. We also expose some of those things to you know, customers Partners in the form of apis. So we've got you know, north-south.
Api's north south applications East West applications east west apis. So I take the roll on. The first thing you think guys do we have an asset inventory of all these applications and the answers.
Yes, we do. Great. Do we have an asset inventory of all of the apis?
Sort of and it's like well, this is an opportunity where I could dog food our own product and actually enable Discovery so, you know, I'm now one month into the role. And we kick off this discovery process for all of our apis. And you know got about 1100 public facing applications and apis today.
I still found 2000 apis. Wow. and what's crazy to me is and and I hope you and folks appreciate the transparency here.
But you know when I go and I talk to really large companies. I mentioned that oil and gas company that I just came from. They were telling me that you know through their process of running a discovery for apis, you know, they found tens of thousands of things.
Yeah, and you know, when you talk to Financial Services, it's in the tens of thousands and it's not like apis are new. Go back to soap, you know, and like they're not all grpc and they're not all like the latest and greatest protocols, you know, there's rest there's soap and then there's previous ones as well. And you know, there's Decades of this stuff people don't have schemas people don't really know where they are.
It's just this changing inventory. And so I think you're absolutely spot on. People are now waking up, but they're also now realizing that in the changing architectures that they have.
To get their arms around this very much appreciate the transparency. Because it's very real and I'm thinking about your timing and moving into the Dual role with Cisco seems like that's about when you're Discovery API Discovery product came out was a pretty close to that. So your dog food god dog food eating your own product pretty early and it's you know introduction.
Yeah, you're you have an awesome memory. Yes, that's exactly what it was. So we we basically took it for a spin internally and this is where we were able to provide feedback to the product teams and say listen, I would actually like to see reports that look like this so I can consume this differently or you know, wouldn't it be great.
If you could give us an assessment because you know the stat that I read recently that blew my mind was 44% of API Developers. Like this only started writing apis in the last two years. Okay, so recent art.
Yeah, and so you get into this point, which is it's recent. There's a lot of them, you know, when covid started apis were 20% of all internet traffic apis are now 84% of internet traffic exactly. What is that jump so you're talking about the fact that most of the traffic we see today are apis.
Or API based then you take into consideration the fact that most people are not sophisticated enough to write secure apis, or you know, they're just figuring it out, right? And then you think about the fact and this is the one that blew my mind and we have the stats. Now, you know, 45% of all API.
Traffic is shadow apis. Crazy, that's crazy. So and because they're being developed everywhere all across the organization not just within it, you know, third parties being tired by the marketing organization to build some app and proof.
Now, you've got 500 morning apis or whatever. It might be so go back to those percentages if let's say 80% of all internet traffic is API based. And if we said 50% of that is Shadow apis or basically saying is 40% of all internet traffic.
to these organizations a shadow how crazy is that? That's got to be scary to US security version. But it could be.
and what motivated and what should motivate people isn't the fact that they have these apis but it's the fact that this stuff is structured. And why do apis exist? To get data in or out of a database or a data store.
So I think what should inspire people is? Okay, we have these things do we know the data that's going back and forth. Let's get our arms around that they also have longevity too.
I mean, you know, you may change of all these guys over time but you also want you know some longevity because you're otherwise you're changing code every day and every time and they persist and and they have versions. So, you know, it's very common for big technology companies to have you know, if they've been in business for 10 years for them to be on V4 or V5 of an API, which means they still have to keep the old ones around. Because core Technologies are already leveraging it.
Mmm. What's the what's the what's the conversation? We should be having next if we were talking about these things as both security and software professionals.
Where do you think the conversation moves now? Is it about Ai and the role that app plays in our inner because our Technologies suppliers are going to be bringing it to us too. Right?
So it isn't like we can say no. Yeah, I mean virtually every vendor is going to providing you some form of AI in their products as well as what you might do with it. I think we definitely saw some vendors talk about it this year at RSA.
I think what we need to start to see though are. Real use cases where AI makes a difference. Hmm doors real value is not just a that's just I candy, right.
So if you're gonna use AI, you're either, you know speeding up a process which means that you're getting to a decision faster. And I can see applications of it. You know and things like threat hunting.
I can also see applications of it in terms of helping build better mouse traps or security whether it's for blocking an attack or detecting an attack. but if we want to embrace those things we have to also understand what the trade-off is. Mmm or what the trade-offs are because AI is fundamentally Based on data that we provided.
And so, you know, there's a huge thing right now. I think that we have to kind of get our arms around which is acceptable use policies around AI I think every company is having these discussions. Had several this week and I've asked everybody.
Hey, do you have an AUP around Ai No, but that's a good idea. And so now when I can borrow to start from right? Well, I want to I wanted to actually do this in an open manner.
Mmm this you know again talking about reconciling these things. I would love to put something on our GitHub just a repository that is here is our acceptable use codified, you know, written out and mark down or PDF doesn't matter and feel free to hack on it. Feel free to you know, pull it into your world and make changes.
And also if you have ideas, you know do a pull request send them in because we got to get our arms around and the fact that data is the most valuable thing as we kind of move into that that world You know and we see an acceleration of those types of products and capabilities. We just have to make sure that we're doing the right thing and we're not, you know giving away State secrets. Well good all it's been fantastic talking with you and seeing you in person, especially yeah.
This has been a fantastic. It's been amazing. Yeah.
Look forward to our next conversation. Yeah. This is gonna be awesome.
Thank you cool. Be sure and check out imperva the technology that we're talking about today and the thinking that goes into it and you're getting some special inside kind of look and understanding of what you know, a great company like imperva thinks about in terms of security and technology and Innovation and moving those things forward. So come back with another great guest so hang tight and we'll be right here.





