A (0:02)

You're listening to the Cyberwire Network powered by N2K.

B (0:12)

What's your 2am security worry? Is it do I have the right controls in place? Maybe are my vendors secure? Or the one that really keeps you up at night? How do I get out from under these old tools and manual processes? That's where Vanta comes in. Vanta automates the manual work so you can stop sweating over spreadsheets, chasing audit evidence and filling out endless questionnaires. Their trust management platform continuously monitors your systems, centralizes your data and simplifies your security at scale. And it fits right into your workflows. Using AI to streamline evidence collection, flag risks and keep your program audit ready all the time. With Vanta, you get everything you need to move faster, scale confidently and finally get back to sleep. Get started@vanta.com cyber that's V A N T A dot com cyber.

A (1:16)

My name is Chetan Konicki. I am the CTO and founder at Shift Left. You know, there are many things that I wanted to be, but given that I'm an immigrant, I grew up in India. It's very natural for majority of the parents in India to charter the course of their children to either become a engineer or a doctor. You know, it was a binary zero one choice. I drifted towards engineering because I always like to hack, build things, reverse engineer things. So it came very natural. I chose math, I chose physics as my core subjects and at some point I got introduced to computer science in my early days at school. And then I coursed my dad to buy a computer for me and my brother. Although we spent most of our time playing games, we also began to understand how games worked, which means we started looking at code. One thing led to the other and I chose computer science as my Bachelor's of engineering discipline. In the early days I enjoyed every aspect of that discipline because you know, it was very close to what I like to do because both liking and doing has to matter and be in conjunction with each other from there on. I came to the United States to pursue my master's and sought a job as a computer engineer and grew up my ranks. When I landed in the United States, the way of life is very different. The degree of curiosity in solving problems is very different. You're not told what to do. You have to actually figure out what to do. So there are many journey points that help you figure out how to position yourself, how to create a brand, equity or reputation so that you become recognized. How do you associate yourself with many communities so that you figure Out a way to initiate dialogue, get answers to certain burning questions that you have in mind. And as a consequence, you find someone to follow. Because in every journey you get inspired. But that inspiration does not lead to anything if you don't have a leader that you want to follow and learn from. So if I charter my journey back, I had the good fortune of meeting certain leaders and then making myself available and proving to them that I'm worthy to join their team, their effort and their initiative. And then observing these leaders of how they behave, how they actually charter their course towards company creation, ensuring that they build teams, making companies successful, and essentially asking questions with without feeling like you make a fool out of yourself. And I continue to learn today also as well, because you know, I'm still not done. I started my career as a generic computer science engineer because computer science is a very generic field. It teaches you how operating systems work, how computers are networked together, and then further on how to write applications to serve needs. Now when you start generic, it is necessary for you to start sharpening your skills in specific fields. Every system, albeit finance, e commerce, networking, all have specializations, but they're using core principles of computer science. I was fortunate enough in my early days to work at startups that were incubated by ex PayPal folks who are looking at reinventing financial instruments. At that point, I cut my teeth in understanding how to take principles of computer science and apply it to a certain domain and optimize it within the domain. Majority of disciplines that we speak of have to be securitized in a certain way because as we deal with financial data, as we deal with customer profile data, we have to adhere to compliances. We have to make sure that we treat that data in a sensitive way. As I grew up the ranks, I began to manage teams. And when you manage teams, you always land up failing audits because there's certain set of people who don't follow principles and rules. And naturally, as a consequence, you begin to subscribe or buy software instruments to observe and see if anyone's violating compliances. And with that observation, you figure out ways to automate it to ensure that this doesn't repeat itself. Now, I did that many a times and I realized that many tools didn't serve my needs. So I started inventing tools with the help of my team to serve our specific needs. Over time, a lot of patterns emerged and with the emergence of patterns, I realized that maybe there is an opportunity to take these patterns and build a company so that we solve for others like me. Within the organization, the entrepreneurial mindset is a sum total of many sufferings that lead to success. I've used that term because as you go through the journey of being an entrepreneur, success doesn't come easy. You falter many a times, you learn as you falter and you optimize your own journey to take you to that path through success. I use the term sum total of many failures because entrepreneurship is a risk. You take a risk, but it's very satisfying when you actually see something that you've built either in the open source or in the consumer space, utilized and purposefully being used in domains. And it's an enjoyable journey, but you got to make sure that you have a mindset tuned for it. From an adversity standpoint, when you have a certain event that plays out in your life, it is important to introspect that event. Because we are the makers of our destiny. When we introspect it, you stop blaming others. This is one of the reasons why I've stayed away from large corporate structures and enterprise. Because when you are in a startup, you have no one to blame except yourself. So once we introspect, we essentially observe and triage that incident, just like we do in DevOps. As you post mortem and incident an issue without blaming others, you figure out what led to it. Then as a consequence, you say, what can I do to make sure it does not repeat again? You take that emotion out, you process something, you say what can I do with it? And then you pick up the pieces and you move on. It is important to actually create narratives and scripts of your journey so that people remember you. I'd like to do that, which is get into a discipline of essentially creating notes. Because over time we as humans essentially have similar patterns. And if someone is going through somewhat of the same journey, they can pick up pieces and breadcrumbs and apply it to their journey to optimize their own. Something that I encourage for all listeners to do is take some time out write. Because as you write in open space, in public forums, you tend to reflect. And as you reflect, you tend to understand how you charter that course and how did you optimize that process and can someone learn from it?