InsightsPodcast

Episode 01

Are we falling short in our ability to defend against cyberattacks?

With Agni

4 March 2026 · 47 min 35 sec

Listen.

It plays here, and it keeps playing while you read the rest of the site. No account, no advertising.

The Security Question, cover art

A cyber security podcast that goes after the questions the news cycle skips, in interviews with the people who carry the same problems. Hosted by Deepayan Chanda and Neeti Rodrigues.

What was said.

Deep's own summary of the episode.

Today investing in cybersecurity tools is necessary — but investing alone is no longer sufficient because of the deeper challenges that lie in organizational culture, cross-functional collaboration, and how leadership truly perceives security risk and its impact. With candor and clarity, Agni unpacks why organizations continue to struggle — and what meaningful, lasting change actually looks like !!! If you're someone in the industry concerned about cybersecurity, this one was made for you — listen in and join the conversation that's long overdue.

The whole conversation, in writing.

It follows the audio as it plays. Pick any time to hear that moment.

Automatically transcribed. Not yet checked against the audio.

  1. To your question are we falling short yeah we are but there is a slight misconception in the industry that cyber security tools are falling short no they're not at the risk of

  2. sounding artificial I think the problem is with human intelligence and and the problem is that we really don't work very well with each other we have silos we have kingdoms that we create

  3. So, there is an IT team that doesn't, that finds very difficult trying to understand or communicate with business teams. There is a security team that finds it difficult to communicate priorities with

  4. IT team. The organization structure that we have in many companies is also not tuned to focus on how do we succeed, how do we become breach ready. The focus is how do we enable

  5. IT for business benefit. Hello everyone and welcome to our podcast The Security Question along with our co-host Neeti. How are you doing today Neeti? I'm doing very well especially with

  6. this wonderful tea that you've given me. Okay. And very excited for our main guest. Yeah. Some something to refresh, right to start with. So would you agree with me that cybersecurity threats have

  7. been on the rise in the past many years and especially between 2022 and 2024? Absolutely. You know, I also feel that cybersecurity threats continue to evolve with variety of attacks like

  8. ransomware and you know cryptocurrency type that we keep hearing about. There are supply chain attacks that is always dominating the headlines. I think there are numerous supply chain attacks that has happened right starting from SolarWinds to up until now. What I also read and hear from

  9. all the experts across our you know cyber security community that the cybercrime cost is supposed to go up and it is supposed to grow up by 15 percent every year which is

  10. really a concerning number right and especially in the last two years or so this has been on the rise it is also predicted that it will rise up to you

  11. know a staggering figure of 10.5 trillion US dollars which is again very surprising number but yeah let's see how that goes you know I also came across the first ever world cybercrime index list this was released by Oxford

  12. University. You know that list talks about scoring of countries based on the cybercrime hotspot and such stuff like that where obviously you know without any surprise Russia tops the list followed

  13. by Ukraine, China, UK in the eighth position and not surprising enough but India is on the 10th position on that list and you know in 2024 we have also seen the change in strategy by

  14. ransomware operators, some of the ransomware operators. They have some very clever strategies drawn on, especially one that I can quote is about the meridian link ransomware attack that happened,

  15. which was I think with the threat actor BlackCat. They also interestingly claim that they will be reporting it to SEC about the breach because of the regulations that they're supposed to to report about cybercrime and ransomware attacks, right?

  16. Whether or not they reported it, I couldn't verify that but you know, this at least emphasizes the fact that the dynamics are certainly changed. So I'm sure you also have your observations.

  17. So what are some of your recent observations, Neeti? Deep as you know, it's always expensive to make things private. It's free to make them public.

  18. Organizations will always put a lot effort and resources into data protection. However one simple mistake, negligent behavior or lack of attention can mean all of those efforts that we put is in vain. In 2023 itself we saw nearly 43% of the cyber attacks were

  19. directed at small businesses. So it's simple you know I read in a report from Mastercard, trust that took years to build can be shattered in seconds. I mean one of the things that I always you know hear a lot about is supply chain

  20. attacks. They've reached their peak, leading to numerous high-profile incidents. You would have heard recently of the Deloitte incident. You know, the RIBridges is the single-client

  21. system that was being managed by our very well-known Deloitte, and it was impacted by the Brain Cipher data breach. And the governor himself, Dan McKee, quote-unquote, said

  22. that it included social security numbers, date of birth, possibly banking information of anyone who has ever applied or received benefits from the services that are hosted by them.

  23. So you know what we have also seen in the past decade that organizations have made significant effort in ramping up against cyber attacks.

  24. Investments also have increased. I think there are a number of things going on and the technology transformations are happening, upliftments are happening, there are at least last few organizations that I have

  25. worked with or few clients that I worked with, there are tons of investments coming in. There is no doubt about it. There is significant effort going on there. However, these disruptions

  26. and the attacks strongly emphasize that the growing sophistication of cyber attacks And these keep growing up and up, right? They keep changing the dynamics.

  27. They keep upgrading their or changing their tactics and techniques all the time, no matter how much investments we have been doing or how much changes we have been doing at our end.

  28. But we are probably not also having enough success in terms of keeping the organization safe in that sense. Get the drip.

  29. Despite of massive time, money and resource investments, somewhere we have been lacking, right? And this is exactly where probably I will drive towards our question,

  30. today's question, the key focus of this podcast today. Are we really failing short in our ability to defend against cyber attacks?

  31. And this is what we will like to discuss a little bit more further along with our guests today. I think this is the right time to introduce our special guest today, right Neeti?

  32. Absolutely. So, I welcome Agnidipta Sarkar and he likes to address himself as Agni, if I'm not wrong.

  33. So, back to you Agni, why don't you introduce yourself? Hi, yeah, I'm happy to be here. Like Deepayan said, yeah, I like everybody calling me Agni, that's short and it's easier to pronounce and that makes life easy.

  34. In any case, we are in a difficult profession, right? Cyber security. So easier things done, better it is for all of us. To your question, are we falling short?

  35. Yeah, we are. But there is a slight misconception in the industry that cyber security tools are falling short.

  36. No, they're not. Cyber security tools are designed to do a specific task and they do their job. They are good at what they do.

  37. So it doesn't matter what tool you're looking at, whether it is an EDR or a firewall or any other security solution that you're using, a SASE or almost every one of the top few products

  38. that are available in the market do what they claim to do. The problem lies somewhere else. The problem lies actually in about five to six years

  39. known areas which we tend to ignore when it comes to all these issues. If you really evaluate at least the top 10 cyber attacks that have happened, they

  40. have not really happened because there was a problem with cybersecurity. Yeah, of course you keep the issues that have happened where there are vulnerabilities in the tools themselves. I'm counting them out something like an

  41. Okta or similar kind of events that have happened, but most of them have to do with configuration errors, they have to do with change management, they have to do with asset management, supply chain,

  42. how do you manage patches and vulnerabilities, how much control do you have over SaaS applications, the proliferation of shadow IT, and zero day vulnerabilities, and of course the biggest of

  43. all. It's called as human error. So I don't know if I answered your question, but in reality, we are failing and I don't see us succeeding in very near future because businesses will continue

  44. to be agile. They will continue to demand facility to get connected and that will push cybersecurity leaders to compromise and not work in tune with other IT teams and

  45. hence we have these issues. That's my point of view. Yeah I think yeah you you did address the question that I already had in mind right where where are we falling short but that kind of brings me to the second part of the question

  46. actually right why do you think we are falling short in defending against the cyber attacks. Even though we have been making significant investment, significant time, and there are dedicated teams working, you know, in terms of protecting the organizations day in

  47. day out. Okay, in the age of, you know, at the risk of sounding artificial, I think the problem is with human intelligence, and the problem is that we really don't work very well with each

  48. other. We have silos, we have kingdoms that we create. So there is an IT team that finds very difficult trying to understand or communicate with business teams. There is a security team

  49. that finds it difficult to communicate priorities with the IT team. The organization structure that we have in many companies is also not given to focus on how do we succeed, how do we become breach ready.

  50. The focus is how do we enable IT for business benefit. But I think and that's the main reason why we're falling short.

  51. If we take our businesses look, in real life we think differently. If you had to go from point A to point B, you will think, do I have enough fuel in my vehicle to go from point A to point B?

  52. That's normal human attitude. But when it comes to doing business, we just want to go. We don't want to think about the fuel. Do we have enough protection that is my car or vehicle that I'm traveling on?

  53. I hope it doesn't have leaks. We make some minimal checks before we go ahead. But in business, we don't do that. We go ahead and get it done. We want everything now, which is good to plan for everything now, but to have everything now,

  54. we need to take a step back and plan for getting to the point where we say, okay, we have everything now, we're good to go. So ideally, cybersecurity is an investment which has to be seen from the perspective

  55. cyber defense something that will allow an organization to become digitally operationally resilient this if we focus upon then a digital transformation

  56. becomes easy because now you're saying okay let's check box are we are we resilient to cyber attacks do we have have we combined our strategies we combined our tools and our strategies with our methods so that if tomorrow

  57. something were to go wrong, we will find ways to continue doing our business and not be affected by cyber attacks. The fact is we don't control whether the cyber attacks will go up or not. What we do control is can we defend ourselves or

  58. not. So I hear all the time news coming out that says there has been an unprecedented cyber attack. And as part of our normal procedures, we have shut down our business.

  59. That's not doing business. That's not doing business. That's that seems that you are not really, you didn't plan for doing business. Ideally, the message should be there was an unprecedented cyber

  60. attack. As for our normal procedures, we continue to operate while our experts and cyber security practitioners focus on disrupting that attack but that we don't hear. What do we hear? We hear

  61. shutdowns. Shutting down is not business but if you focus on and if you plan for anticipate model your possible attacks in the future then you really can go to that stage where you say

  62. okay there has been a cyber attack we know we must notify authorities people stakeholders That's what we are doing right now, but here's the good news, we are in business, our business is not shut down.

  63. I think very valid point, right? So no, I agree. I agree with everything I've been saying, because security has to be perceived as a business enabler rather than a business inhibitor.

  64. And more importantly, I think you have to be encouraged to share because there is nothing called 100% security. I mean simply when I look at lock 4j you know 40% of lock 4j downloads are still vulnerable.

  65. So attacks are going nowhere and I absolutely agree with what Agni said. I mean inaccurate asset inventory absolutely true. I mean there's a famous joke and I work very closely with asset management tools.

  66. Now when a CISO asks the organization or his team how many windows hosts do we have you'll find different answers in point team says 7 4 3 2 EDR will say 6 9 4 5 another

  67. team CMDB will say 5 8 4 7 and they're all right in their own aspects but there is no symphony between all the teams so a very good point Deep would you like to add something more?

  68. Yeah you know I think one of the point that really resonates with me is the human error And to be very honest, one of the aspect of human errors I consider is related to the configuration errors.

  69. Because yes, this is an error of automation and all that. But ultimately, there are certain aspects where the configurations are still probably the configuration files are built by the humans or at some point, there is a human touch.

  70. We cannot completely take that aspect away. So configuration errors as part of cybersecurity issues, these can lead to range of complexities

  71. like system downtime, performance degradations is what I have seen sometimes and then security vulnerabilities that they expose to. So that doesn't go away at all.

  72. One of the examples that I can talk about is really, it's a little bit old that has happened probably around June, 2023 was with Toyota, where about 260,000 customer records were exposed.

  73. It did not expose massive amount of sensitive data, but what it does signifies is that misconfigurations can really allow access to sensitive information to adversaries.

  74. And one of the key facts about this particular attack was the timeframe, the duration, the organization couldn't even figure it out for eight years, at little over eight years that there was a configuration mistake

  75. which was exposing so much of data. So that kind of, you know, kind of emphasizes the fact that how important to look at the configurations, to look at the way we set up the system, the way we design the system.

  76. I think the whole industry is talking about secure by design, but they often jump to conclusions that yes, I'm doing secure coding and I'm following CI/CD principles.

  77. So I'm following secure by design, but secure by design is more of a overall picture rather than just doing bits and bytes, right? So configuration management is something very important part of it.

  78. And I think in this, I will also like to mention that it's more of a cultural change, the way we release our products, the way we build our products.

  79. So one of the similar example is Trello, where 15 million users details were exposed due to an API misconfiguration.

  80. And this list continues, there is no end of it. Probably we will end up talking next two hours on just configuration errors and API attacks. And our firmness, CrowdStrike.

  81. Yeah. So yes, while we are on that point, why not? So CrowdStrike incident, I don't really consider particularly as human error or something.

  82. It's probably accidental. But that does not deviate from the fact that it caused massive disruptions across the globe. I know some of my friends were stuck in airports and we were chatting and we were laughing

  83. that how our own profession is making us suffer at times. So it was point of joke at that time. But nevertheless, the fact still remains.

  84. Our systems are not fail safe. We, somewhere we fail to build fail safe mechanisms big into the system. So I think probably that's more of a question for you Agni.

  85. I would like to hear your thoughts on this. How can we really minimize impact of these kinds of errors and issues that we continue to see, which has probably never stopped in the last many, many years to my knowledge.

  86. So my view may be quite divergent to what you guys were discussing just now. And my view is that we have to stop looking at it from the perspective of a security activity

  87. versus an IT activity versus a business activity. And we have to review it as one single piece, which is the business.

  88. So what happened, for example, during CrowdStrike human error? Can we stop that?

  89. No, we can't. Human error is inherent. Every human can do an error. Somebody might say, why don't we do this? Why don't we put artificial intelligence instead of a human, and then we won't have an error.

  90. But let's understand that an artificial intelligence is also controlled by a human. So that's one thing. But coming to cyber attacks, if we look at a business from a perspective

  91. that here is a business objective, And as a business leader, I own everything, including the IT, the IT security, cyber security, everything.

  92. The question then I have is I have other people who are actually doing the job for me, but I'm the client, I'm the owner of that business. And hence, I would like to know and question the CIO, the CISO, am I secure enough?

  93. Now trust me, if you put that rigor, suddenly things will change because every CIO and every CISO is focused on doing the best that they can, that they think they are doing without talking to each other.

  94. But if everybody is forced to talk to business in making sure, like you said, Neeti, in the very beginning, cybersecurity is a business enabler.

  95. It doesn't need to be an enabler, it needs to be a service provider. So there's a difference between an enabler and a service provider. An enabler is is like a table that you're keeping your cup of tea on that's a

  96. that's your enabler but if you are inherent part of the business then it is there you you have an expectation in return that I'm going to fund you 100

  97. million dollars you're going to give me this benefit and if that works in tandem then every component of the business is going to get aligned you don't need to force align somebody. Like you said Deepayan, you know people say that I'm doing CICD, so you know

  98. I'm just following whatever I'm being told. Now the moment you start getting into that mode, you've lost the leadership position completely. So everybody who's got a stake in business, and the CSO needs a stake in business, the CIO needs a stake in business, the business owner

  99. should know we can't solve vulnerability management and we can't solve it because of of reason one, two, and three, and every time there's a vulnerability, we will have to take this position. If that is known as a business owner, what I would do is I would work within

  100. those limitations, depending on how much money I'm spending, how much priority I'm giving to the patch management. I mean, I, I'm sure all of you have heard this, that when you go and you want to patch something which is urgent, a rating of nine dot zero, right?

  101. And the business comes back saying, no, no, no, we have an important release now. You can't patch it now. So the question goes back to the business owner. Are you okay to live with the possibility of an attack?

  102. For the time you're not patching it, if the business owner says, okay, then you go ahead, but the business owner wouldn't say okay, if he was part of the system, the business owner would like to now understand, I'm willing to take that risk.

  103. But tell me what happens if we get attacked? Then you have a plan in place for cyber defense, which says, okay, if you are attacked in the event this system goes down, so will system three, four and five go down because they're connected.

  104. They're within the blast radius of this system. And in that case, we need to shut down operations in ABCD plans so that it doesn't spread anymore.

  105. That's the only thing that you need to know about before you go ahead and say, don't catch it. But that doesn't happen because these are not connected. They're all silos.

  106. The CIO will come and say, sorry, the business leader is saying we can't do it. The business leader in his mind says, oh, that's an IT activity.

  107. You know, those guys should tell me whether I should do it or not. No one's going to take initiative. No one's going to get this done. The CISO is going to go back and say, I told you so. But let's change that paradigm.

  108. That's what I've been saying. Put the CISO on the table. Put the CIO on the table. Put the business leader on the same table and say, okay, If something goes wrong, all of us will get fired.

  109. So everybody is a stakeholder. You heard this very commonly, right? That the CISO does not have a stake at the main table on the board. Trust me in my experience.

  110. If the CISO gets on the board, then the CISO is a CXO. And a CXO is accountable for a business failure.

  111. If that doesn't happen, if that culture doesn't exist, then this is gonna go on, we're gonna meet next year and discuss the very same thing over and over and over again.

  112. The only way to fix it is to have everybody in one table, three partners running a business, the business leader, the CIO and the CISO.

  113. And everyone should be tuned to the fact that we have X amount of dollars, we have Y amount of digital systems, we have Z amount of cybersecurity tools.

  114. How do we combine all these into a potent combination so that tomorrow if something goes down, no matter what the cause is, it could be human error, it could be a cyber attack, it could be lack of asset management, like you said, the numbers differ.

  115. The businesses will be able to take the right position. It's all about taking risks. It is not about who takes the risk.

  116. It's about the business leader taking the risk, knowing fully well that I'm taking a risk. If something goes wrong, this is my fallback option. Yeah. I don't have that answer.

  117. You know, you made a very valid point and I have a question on that because this is something which I probably have seen throughout my career, right?

  118. There is a risk race by relevant security teams and all the analysis team. And, you know, these days we have architectural governance.

  119. They raise a bunch of risks when they are looking into a system or a solution being developed. When it goes to the business, the business owner, the first thing they do is to try to negotiate and I face it, let's be honest about it.

  120. And they try to negotiate. Yes, we explain it, they understand it. It's a 50-50 chance. 50% time I have seen that business accepts the risk, even when we have given them the full picture

  121. what could happen and yeah hold on hold on hold on I I don't think there is some there should be something called acceptance I think there has to be there is one very important part of action on a risk that we don't do which is risk

  122. taking the whole idea of doing the business is to take risk there is no business where you don't take risk it is just that when it comes to cyber security we tend to ignore the risk taking and how do you take risk by knowing all facets of the risk and it's you know outcomes and then you take a

  123. risk yes you can call that as a risk acceptance but that's not really acceptance acceptance of risk is when the risk is very low if you think that there are those four quadrants right where risk is high medium impact is high

  124. and like what is is medium and all that so the point that I'm trying to make is when that happens, if something falls in the lowest quadrant, you go and say, OK, let's go ahead, he'll accept the risk.

  125. But the whole idea is we are not focusing on taking the risk. We need to move from organizations who get into risk acceptance to organizations who take risks.

  126. I tend to agree. That's my point. Interesting. Very interesting. I mean, I haven't heard of this risk taking before.

  127. You made me have a paradigm shift, so good. And you know, you also mentioned a couple of words like blast radius, maybe we will talk about it.

  128. But if you'd like to explain for the audience a little bit on that, and then I have a question for you. Okay. Risk-taking is doing business.

  129. Every business you do. In fact, in our life, individually, we are all excellent risk managers, excellent. I used to do a training course for people when I was in HP.

  130. One of the things that I used to train them on was, how do you decide which risk to take? One example that I used to give is, let's say you leave home and you're going here on your way to office,

  131. And, and you realize there is a traffic, you know, catch up and you have really urgent meeting in the morning, you have to reach by certain time, let's say you have to reach by 9am and you're on the road, you left on time, but there's an unknown, unprecedented, unforeseen block on the road, which is going to delay your meeting by 30 minutes, what do you do?

  132. Do you try to treat the risk? Do you try to transfer the risk? Do you try to tolerate the risk?

  133. Or do you try to terminate the risk? There's no easy answer because paradigms, I mean, the situation will keep developing and changing.

  134. It's dynamic just like it is on the business. But if you are in that situation, you'll realize that you have taken the best decision at that point in time.

  135. That decision could be you turn back home and start working from home. That decision could be you find another route to go to office. That decision could be you hand over your intelligence to someone else.

  136. You take the call from the car. It could be any of these things, but what you really do is you decide to take the risk because without you taking the risk, if you remain quiet and do nothing, the thing will break.

  137. Your business objective is lost. So taking the risk is the most important part of business. Now, how do you take risk? You take risk by having knowledge of what could go wrong and what you could do if those things were to go wrong.

  138. In the case of a cyber attack, let's say. So if there's a cyber attack, and coming to the blast radius point of view, if there's a cyber attack, imagine a company who's got a web server which is exposed on the internet, right?

  139. And that web server has a vulnerability which is CVSS 9.0 or 9.7. Now you go and tell the leader that you have a CVSS 9.0 and I hope nobody has a rule in the company that says you need to fix everything which is 9.0.

  140. That doesn't work. So you have a rule, you have a CVSS 9.0, you go to the business leader now and you go to the business leader and you tell the business leader that you have a, you need to, you know, we need to update this.

  141. Now what does the business leader say the business leader can say No, I don't I won't allow you to do it right now because we have an important whatever is going on Right at that point the business leader should

  142. Not be stopping there because today most business leaders stop there because they feel it is IT's job to fix it and IT feels That's the business leader has said I can't do so I'm done It was business's job to fix it, to take the risk.

  143. It's not my job. So when it goes between my job and his job and my job and his job, it doesn't work. Now, when you come to understanding that if that web server had to be fixed, if the IT leader or the security leader had communicated to the business, look, if you don't fix this,

  144. if it gets hacked in the time that you give us, then your only alternative is ABCD. The business leader can now start thinking, Oh God, no, this seems to be more riskier than continuing with it, so go fix it.

  145. Or I understand that there is a risk, the alternate method in my mind, just like you would do in the traffic jam, in my mind is that I will hold on to the update for some time, I'll take the risk.

  146. And he takes the risk, and then you go and fix it. Then everybody is good, it will work. But if the cyber attack happens at that time, in between the time that you want, the business leader is going to say, I didn't do the job.

  147. I didn't really want to say the security guys did not do the job. And it's all a blame game then. It doesn't work because at the end, if the organization has to succeed, business has to succeed.

  148. You have to treat your business like your leader. So that's what I'm saying. I don't know if I explained that. Glass radii means if that system got attacked, how many other systems which are connected to that system would get attacked?

  149. And how many other systems behind that would get attacked? So let's say your web server gets attacked and that CV is misused. If you understand what that CV can do, like you talked about Log4j, if you can understand what that CV can do

  150. and only a technical guy can understand that. So in your words, the enterprise architect would probably be in a position to tell the leadership, if that gets attacked, then your application server, which is behind the firewall, can be compromised.

  151. If that gets compromised, then, and if that also has a set of vulnerabilities, right, could have, you may decide not to fix it. You would know about that at that point in time.

  152. And then if that gets attacked, then we have this database that will get attacked, But this machine, which can get compromised, which means we may not be able to operate for three days, that would lead us to this situation.

  153. If you tell that to a business leader, the business leader will visualize and understand the risk. And like every good risk manager, trust me, everybody's a good risk manager.

  154. Every good risk manager, he will then say, let's take the risk, let's do it. Or he will say, let's not take the risk, and you go fix it.

  155. And let me know, I'm going to delay my business outcome by one day, that's okay, I'm going to take the risk. Now the risk parameter has changed. Instead of taking the risk of getting hacked, he's now taking the risk of delaying his business objectives.

  156. It's a risk either way. But in absence of this knowledge, the risk taking is all moved on to somebody else. He actually learned something new today.

  157. Risk acceptance versus risk taking. Yeah, no, I mean, I like the fact Agni, that you were actually in many ways actually answered a question that I had in mind, which is what is the right balance between spending and descending.

  158. But before I go into that question, I think a few points that you brought about, getting the full picture, bringing everybody on the table, absolutely deep.

  159. These are, you know, very important things. I think Admi is talking about risk taking. So thanks for all those inputs and tell me if there's more that you want to add about

  160. what would be the right balance between spending and defending for security leaders to be adequately able to defend themselves from cyber attacks.

  161. So some of my leaders and some of my colleagues tend to blame me and reward me with the fact that I have never had a situation where my budget was turned down, so the key thing for security

  162. leaders. Yeah, I think we probably have discussed this last few years. Yeah, and one of the reasons

  163. that I mean at some places I did get turned down and I realized and I went back to the drawing board and realized why I was turned down. My analysis of all my security budgets getting

  164. turned down is because the person who's taking the decision to invest or not invest did not understand my articulation of the risk. That's why I failed. That's really the reason. So

  165. that is true with everything we do. So to answer your question, what's the right balance? The right balance doesn't exist.

  166. There is no right balance. The right balance is something that happens in your mind where you intend to do something and then you evaluate how difficult are the circumstances.

  167. Let's say, you know, like you decide to go to Tasmania on a drive, okay? And you realize that you need to reach a particular point at a particular time, otherwise you

  168. You would miss a boat or something, a connecting boat and you would have to spend an extra night somewhere else because you missed that. So the question now is if you reach that moment where you say, if I go, I have to arrive to

  169. go very fast and you get into that urgency mode in your mind or and that becomes dangerous for driving or I can take it slow and I can start tomorrow.

  170. In any case, I'm going to miss that connecting boat. This balance, there is no real answer. I mean, some people would leave and take the risk and drive very fast and reach there on time.

  171. Some people are good at that. Some people are not good at that. They would rather, and it all depends on the propensity to take risk. This differs from human to human.

  172. Because let's understand, every decision maker is a human. Even if you had an artificial intelligence take the decision on risk, that would be a human-based input, right?

  173. It would be a program. So the whole idea of taking risk is about the human deciding on what the propensity is.

  174. Some people have the propensity to be risky. Some people have the propensity to be controlled. But in the end, the organization, I mean, if you were to compare the propensity to take risk versus the propensity to control risks, if you become too controlling, you will not be able to do business.

  175. It will become slot. If you become too risky, you'll become another startup who just failed because you were taking too many risks and it didn't work out. So there is a middle line and that middle line will differ from company to company will differ from individual to individual. So there's no real answer to your

  176. question. The real thing is every time somebody is taking a risk is he or she in a position to evaluate, am I in between the control and intend to take risks? If you are somewhere

  177. in between, that's how we all lead our lives, then you are ok. And I think to your point, because you brought that point up about the road trip, it was

  178. more or less designed that way, that we don't miss things out. Yes, there were some bits and pockets where it was unplanned and we wanted it to be unplanned that way but yeah I think

  179. just to emphasize on your point it was really created in a way that we don't take unnecessary risks so yeah we reached a day early to some places where we wanted to visit and start to think.

  180. Yeah but that's the whole part about that's the whole part about doing that so when you become control oriented that means you're wasting money when you become risk oriented you're not wasting

  181. money but you're not really enjoying either so you can argue both ways yeah very true so you know on a separate note actually I mean we keep hearing things like network diagrams or network maps

  182. threat models threat maps there are so many different versions of these things right so So it will be probably not right if we don't talk about these things in today's discussion

  183. also. So I think based on my conversations with you from past so many years, you have spoken a particular term quite often, right?

  184. Security maps. And I have heard about it many, many times. So I think it will be really nice if you can give a little bit of idea to our listeners

  185. what a security map is and how we can use it and probably also add a little bit of idea about what is the difference between security map and the network diagram or threat map that

  186. we keep talking about. So what does a network diagram do? A network diagram shows the network of how computers are connected.

  187. What does a data flow diagram do? It shows you how data is flowing between the patients. Unfortunately, we don't think of security diagrams like that.

  188. Now we could, because we don't do it as a normal practice, we could use an embellished network diagram with cyber security or we could have a security diagram by itself where each digital asset

  189. and its data flow is connected with how secure or insecure that asset is and that would give

  190. you a very different view of how really to build cyber defense like we discussed the case right, where we talked about a server being on exposed and it has a CVSS 9 vulnerability.

  191. Then suddenly as a visual that if you are able to do this in some way, that should be, it should be able to, for people to see it as your riskiest part.

  192. And in the same view, you should be able to see about the safest part and how can you keep the safest part safe. It's not wrong to be insecure, but it is wrong to recognize

  193. what really is of value to business. See, one of the questions that I've been consistently asking people and some people get upset with that is, tell me what do you do as a business?

  194. How do you make money? So when I go to CISOs and ask them, how do you make money? Trust me, in my experience, only a few can come back with the stick question with that answer Okay.

  195. We sell potatoes and hence we make money. So it's not easy because they don't, they really don't know themselves. How does the company make money? If you know how the company makes money, then your next question is what are those digital

  196. systems that are really fueling your company, make money, and you could have some which are direct. And then you go back in the second question and ask what are those digital systems that are making these digital systems work?

  197. If you follow that as a diagrammatic picture, then you know that this, and you know, I normally think about there's one aspect that, you know, if you see my notes on LinkedIn, etc., I use a term called containment.

  198. So when there's a cyber attack, there are two kinds of containment that needs to happen. One kind of containment is how do you quarantine the attack in the place that it happened?

  199. The second kind of containment is, how do you isolate that digital business that must continue to work? I don't know if this is making sense.

  200. So basically you're going to have three parts of your organization. One part of your organization, which is under attack and it is quarantine, which means it can't spread anymore.

  201. The second part of your organization are those digital assets that you really need to protect and they need to continue to operate. And the third part of your network, which is going to be the largest part of your enterprise is the part that you don't know anything about.

  202. Whether they have already been attacked or whether they can be attacked, but you definitely know the one that you isolated is going to work.

  203. Think about an SAP server, which has got a connection to a web server and you have somehow been able to cut that web server out from the enterprise.

  204. Now, that means that the rest of the enterprise continues to work business as usual. But the outside people who are coming through web server are no longer able to reach the SAP server so that business is under attack, right?

  205. But you still have the rest of the business continuing to work but you still also don't know whether that attack has proliferated because you'd never know for sure how deep the attack

  206. has gone. But if you are able to contain your SAP that means that you know for sure this is not going to get attacked. Not in the time that I'm able to disrupt the ongoing attack. So the middle

  207. part, the unknown part is the one that you have to now discover more and more and make sure you have to make sure that that is not under attack. Because there is something which is called as

  208. aftershocks. Like earthquakes, cyber attacks have aftershocks. Log4j if you remember, there were a lot of aftershocks. Somebody removed Log4j. Bang! In six months it came back. Why did

  209. it come back? It came back because we did not do the diligence that said, okay, this part I know for sure is good. This part I know for sure is bad. This part I don't know. So I'm going to focus

  210. my energy on two parts. I'm going to focus my energy on fixing the bad and on vaccinating the one in between, so that by the time I'm done, I've increased the good to the level I want to go.

  211. I don't know if I answered your question, but that's exactly what a security diagram can be. It does, it really does. I think you also partly answered my next question, which was like, how can they get started?

  212. But I think you already addressed it. And with that, I think this was really a great conversation And I think you will really give us another opportunity to talk to you again with another security question next time.

  213. So really thank you and thanks for being with us today.

The other episodes.

  1. Episode 02,

    Should we knock down and rebuild the Internet Backbone again?

    With Deb Radcliff, cybercrime journalistThe Security Question

    27 min 5 sec

See every episode

Start with a conversation.

If an episode touches a decision in front of you, a short conversation is the quickest way to test it against your own situation.

Book a conversation