Latest / Talking Security: Insights from Microsoft Security Experts / #32- DevSecOps series - Code security from a developer perspective
Transcript
- 0:00Welcome to the Talking Security podcast. We will talk about items related to Microsoft
- 0:11security.
- 0:14Hello, welcome again at a new Talking Security podcast.
- 0:25DevSecOps series.
- 0:26Within the DevSecOps series. This is the second recording. First time we talked about the
- 0:32developer security workplace, the developer workplace and what we should do from a security
- 0:39perspective. Today we're talking about complete and other aspect of DevSecOps. So within DevSecOps
- 0:47there are different aspects that we want to address in the next few recordings. So probably
- 0:55seven or eight or the next recording we will touch that. Today we are touching the code
- 1:01base but also security from a developer's perspective. The developer in-house standard.
- 1:08So what's your view on security within the developer's area?
- 1:19I think that when you're talking about developers, what we're really good at is writing code
- 1:24and that's kind of what we're paid to do. And I often see that security from a developer's
- 1:29standpoint is just not, there's not enough knowledge in a developer to actually do this
- 1:35sufficiently. I know how to write secure code, validate incoming data, stuff like that. It's
- 1:42just basic stuff. But when we're actually talking about deploying your applications
- 1:46to the cloud or scanning for vulnerabilities, all of scanning for vulnerabilities, stuff
- 1:51like this is something that developers often don't really know. And this is what you need
- 1:56specialists for, like you guys. And I think that is definitely something that scales nowadays
- 2:02when you're deploying your code, maybe multiple times per day. When are you actually checking
- 2:07if your application is secure? You can't just ask some security specialist to check that
- 2:11once a week. That's maybe not even enough. That's a difficult thing.
- 2:15And talking from a developer perspective, but DevSecOps, the world changes because you're
- 2:23developing applications and stuff. But we are doing with Infra, Infra-ASCO, we are also
- 2:30doing stuff with code.
- 2:32Yeah, definitely. Yeah. So that's also a big change, I think in the whole developers and
- 2:37the whole DevSecOps these days is the change that's not only about application, but it's
- 2:43also our infrastructure, how it will be deployed and created on a later moment in Azure or
- 2:50any other cloud provider, which is a big part of the whole DevSecOps. And also what you
- 2:58mentioned, I think, if you look at it, I think from an outside to the developer's perspective
- 3:04and see how many stages there are involved within developing a code or application or
- 3:11infrastructure part, that security cannot be just an additional stage that is added
- 3:20to that whole process.
- 3:21It's not like...
- 3:22It can't be an afterthought.
- 3:23No, right? And I think that's the whole idea behind DevSecOps, why they didn't add an additional
- 3:30pilot to it, but they said, no, security should be part of every stage in the whole process.
- 3:36Because I think the end goal is that, and we will touch that today a little, is to find
- 3:44that vulnerability as soon as possible. And I think that's what we are going to talk about
- 3:51in this series, more the shift left approach, which you are seeing, it's coming from developers,
- 3:58of course, but it's also now security is adopting that framework.
- 4:02Yeah. So it's like, you know, you need to... Like you already said, it's not like security
- 4:07is not an extra step in the chain. We're not adding a little, oh, we need to do security
- 4:11at some point. Now, every stage of developing an application, there are lots of stages that
- 4:15should all be done securely and all of them need different steps. So you're kind of, you
- 4:19know, shifting the approach of security more to the left, so more to the developer perspective
- 4:23and more to the planning perspective. When you're planning to build your application,
- 4:27when you're designing it, what do we need? We need to build an application that talks
- 4:32to the cloud. Okay. How does security play a role here? How are we going to talk about
- 4:36security? Not something that you do in the end. You really take it with you in all stages
- 4:40of developing it.
- 4:41It needs to be integrated in every step and every single piece that you're thinking of,
- 4:48security needs to be part of it.
- 4:50Yeah, because we're not nowadays writing like applications anymore and then deploying the
- 4:53files on an FTP server or something like that by hand. We're doing so much more. We're deploying,
- 4:59we're hosting our code somewhere like in GitHub, Azure DevOps, GitLab, stuff like this. And
- 5:03then we're using like CI-CD, like build pipelines, release pipelines. We're doing tests. We're
- 5:08doing monitoring. There's so many things that this works really well, but there's also so
- 5:13many things that can go wrong. And if you just ask a developer to fix all of this, you
- 5:17can't do it. You need security analysts, but this all needs to be done in a continuous
- 5:22way.
- 5:23Yeah, I think that that approach is adopted by developers for a really long time, right?
- 5:28Building, testing, unit testing, all the types of testing of your code. But I think less
- 5:35from the security mind, like, okay, are there vulnerabilities in my code or could there
- 5:41be any vulnerabilities? I think that's the big change, right? Because developers are
- 5:46doing code testing for a really long time, but not always from a security perspective.
- 5:51It is really difficult for a developer to do all of that. Like one important thing is
- 5:58that you need to update your packages, update your dependencies and stuff like that. And
- 6:02not a lot of developers like doing that. It's boring work. It's just takes very time consuming.
- 6:08And often you don't really have any time to do it. You know, the focus is on building
- 6:11those new features. It's not on like updating everything that you've already built.
- 6:16And if you have an application that you built on your own and it's completely your own code,
- 6:22you could scan your code and you're completely aware of what's in it. If you're using libraries
- 6:29or stuff like, for example, look for J, the issue that we have seen, if you're using some
- 6:37other components like look for J, yeah, then you are relying on other stuff. And then it's
- 6:44more harder to check if you are having have any vulnerability or not.
- 6:51Exactly. Nowadays, I don't think any developer is building an application without any dependencies.
- 6:58It is probably possible if you're just writing HTML, CSS, maybe some JavaScript yourself.
- 7:03It is possible, but I would say that 80, 90, even more percent of applications nowadays
- 7:09are built using a framework in a front end like React Angular view or you're building
- 7:13a server application in Java or.NET. Doesn't really matter. Anything is using libraries.
- 7:17And keeping up to date is one thing. But also what dependencies you're using in one package
- 7:23and that package in the front end land, in JavaScript land, has like a thousand dependencies
- 7:29which have dependencies. If one of them in the chain gets a vulnerability somewhere,
- 7:35all the packages above are also vulnerable. And it's, you know, I need to build this feature,
- 7:40you know, I need to build this new checkout page, but I also need to ensure that dependency
- 7:456000 is still valid. It's impossible for me to do that alone. I cannot do that in the
- 7:51time that I have.
- 7:52Puyon, if we look at application development, dependencies are playing a big role. What
- 7:59about infrastructure code? If we are deploying infrastructure on the Azure platform or on
- 8:05AWS or whatever, do we have that sort of dependencies also?
- 8:11Well, not so the dependencies to libraries. When it comes to infrastructure code, it's
- 8:18mainly where we focus is to find the misconfigurations, right? Something we can do on multiple levels,
- 8:25right? We can do that when deploying the resources to our Azure cloud, for example. We can do
- 8:31that with Azure policies these days where we can say, okay, we are allowing users to
- 8:37create a virtual machine in Western Europe. They need to have certain disk encryption
- 8:41models configured and they are not allowed to have a public IP address. So that's something
- 8:48we can do, but that's on the Azure side. And when we start doing infrastructure code, so
- 8:53the developer has done all the configuration, build the templates, commit that code, that
- 9:00code is merged and deployed and at the deployment, you find out that there's some restrictions.
- 9:09And I think that's something that's also a little too late because you want to find that
- 9:15misconfiguration much earlier, like developers. From my understanding is that developers want
- 9:21to find preferably the bug or the misconfiguration in the code on their EDA, not even in the
- 9:29build and validation phase. That would, I guess, be the best thing. You definitely have
- 9:34code analyzers that check, hey, you're writing code here that might be insecure or you're
- 9:38missing validation. And then something in your IDE would be very great. But the thing is,
- 9:44if you only do it in the IDE and you just kind of don't make all of this validation
- 9:50of your dependencies, vulnerability scanning, if you don't make that a part of your pipeline
- 9:54and you only do it in the IDE, then a developer on your team that doesn't use that IDE or
- 9:58doesn't have it configured is still going to let vulnerable packages in.
- 10:01You should be on two faces, right?
- 10:04I guess. I see it most of the times. I see it just happen in the pipelines itself. And
- 10:09for me, that works enough. You do nowadays have it integrated in Visual Studio. You get
- 10:13a warning when it says, hey, when.NET package manager knew that, when it finds out that
- 10:19there's a vulnerable package, you actually get a notification nowadays. It's really,
- 10:22really useful. I never really thought about it. Last week, I started my Visual Studio
- 10:27instance and I saw that Nougat told me, hey, you have vulnerable packages. That's extremely
- 10:32useful as a developer to know. And then you can just make work of it or you can tell your
- 10:36team, hey, next week or next sprint, we really need to start focusing on these packages and
- 10:41we need to update them.
- 10:42Yeah, because Frans, for example, you mentioned Log4G. If you look at Log4G, and I think you
- 10:47had a similar experience, when the customers called us or when we were proactively searching
- 10:55customer environments, if you look, we were looking more on the infrastructure side, right,
- 11:01to find that. Defender, firewalls, Sentinel.
- 11:08It was on the infra side, but the infra side was detecting the applications that are using
- 11:15that Log4G. So the detection was realized on the infra components, but the vulnerability
- 11:23was in the applications. So it's somewhat hard to search all the applications to see
- 11:30the vulnerabilities. And then you need a vulnerability scanner on a network or on an application
- 11:38server, whatever, to find if a certain library is installed and be used in that area. But
- 11:47that's the side from a customer perspective that we have. On the side of a developer,
- 11:52a developer needs to know where his dependencies are. So if Log4G, if we take that example,
- 11:59if Log4G is coming up and there is a vulnerability in a specific package, then Sander, as a developer,
- 12:06he needs to check and he needs to know which applications do I have with that dependency,
- 12:13so I need to update that one.
- 12:14Yeah, exactly. One thing that's really funny when we're talking about package vulnerabilities
- 12:19is when I talk to developers or managers and stuff like that about we need to improve our
- 12:23security because it's insecure and they're like, yeah, but we're just a small company.
- 12:27No one is going to hack us. They don't have anything to gain here. And that is maybe true
- 12:31in the olden days where hackers could just target companies and stuff like this. But
- 12:36nowadays, when we're saying Log4J or when we're saying a package that has a dependency
- 12:41on a package, and I keep going like that, and somewhere in that chain is a vulnerability.
- 12:46You are hacked. You are suddenly vulnerable. And they did not target you. They just targeted
- 12:50one little package and suddenly millions of companies could be vulnerable.
- 12:55I think from a hacker perspective, it doesn't matter what you're doing. If you have a small
- 13:03piece of software that is used by lots of other vendors, application developers and
- 13:10so on, then there's a potential bigger impact in the world and you have access to more machines
- 13:22if you can realize that that way.
- 13:26It makes sense for a hacker perspective as well. Why would you target one little company
- 13:30if you could potentially know how this company, this website is built in React or something
- 13:34like that, or they're hosting their server with.NET. So we're just going to grab some
- 13:40popular.NET packages and we're going to try finding vulnerabilities in those and get some
- 13:44bad stuff going on in there. And I know that the company will install my package. It's
- 13:48so much easier.
- 13:49If we're talking about risks, what are, from your opinion, what are the common security
- 13:56risks and challenges that developers have?
- 14:01Developers I think number one would be from the code perspective, how you're managing
- 14:05your secrets. So you're writing code to connect to services in Azure or just to connect to
- 14:12services from an external service like an invoice service or payment service, which
- 14:16you see often nowadays. How do you make sure that those credentials are kept safe? Lots
- 14:20of developers just, they don't really think about it much and it can be a difficult topic.
- 14:26I see it often just, you see often that they're still being leaked. In 2019 I read that there
- 14:30was like a hundred thousand secrets or something were like leaked from GitHub, like a hundred
- 14:36thousand and that's just not going to stop. That it's just going to keep going.
- 14:39We know a scenario in the Netherlands a couple of, yeah, well it's a year ago almost, of
- 14:44an IT admin which, from my understanding, he wanted to do something good and he wanted
- 14:52to share what he built on a code base and he published it on GitHub so that others can
- 14:58use it and it contained username and password. An admin, highly privileged admin account.
- 15:03Oh, and I have a great story to tell on this. So it was a few years ago, there was in the
- 15:10Dutch tax services, so like part of the Dutch government, there was an employee there had
- 15:16a GitHub account and some Dutch citizen found that GitHub account and was just looking around
- 15:22at it and in there he found some credentials to that employee's private GitLab account.
- 15:27He was like, okay, I'm just going to have a little look and take a look at that GitLab
- 15:31account and what he found was like a plain text file with like all the usernames and
- 15:36passwords of the Dutch tax services like Azure admin account.
- 15:40So what he did, he went in there, he went to the Azure portal, he logged in with username
- 15:44and password and it was correct but luckily of course there was two factor authentication
- 15:48installed so he was like, you know, out of luck. Of course he didn't want to log in,
- 15:52he was a nice guy and a few seconds later he was logged in. So some employee at the
- 15:57Dutch tax company actually like clicked on yes, it is me trying to log in and this guy
- 16:02was logged in as the global admin in Azure and it's just, you can just see like even
- 16:06with these big governments, it is so easy to just leak a secret. It is very easy to
- 16:11do and developers definitely need help. We need to integrate this security perspective
- 16:16all the way into the development of the code and everything else.
- 16:19Yeah and this guy was a white hacker so he informed the tax services that he was able
- 16:25to log in. But one thing I want to highlight on the story that you are describing is there
- 16:33was MFA.
- 16:34Yeah, there was MFA.
- 16:35And someone, because someone gets a notification on his phone and he put down a proof and the
- 16:44hacker is in. So MFA fatigue that we are facing in this area. So I get a, there was one notification
- 16:52probably but how many times are admins are facing with a notification or an approval
- 16:59prompt that comes in multiple times and then in the end I'm fucked up.
- 17:06I'm approved.
- 17:07Yes, exactly. And then you have a potential big impact on, it was a test environment so
- 17:15it was not that big.
- 17:17It was a test, I'm pretty sure it was prod.
- 17:20I thought it was prod.
- 17:21Let's just say it was test to save the grace.
- 17:24Let's hope it was.
- 17:25There was an environment.
- 17:28Exactly.
- 17:29Of a big environment, of a big company, a public company. And that was, it's potential,
- 17:39yeah, crucial that you have secured that sort of user credentials.
- 17:46So this brings us to, I think, a really nice summary of what is happening, right? Because
- 17:52we started with some code, some username password in a code which is published on a repository
- 17:59and all through the whole process that on the upside somebody used that account to log
- 18:05in, right? And that's, I think, the whole gap that is there. So on the left side we
- 18:11had that code which contained the password and on the, all on the right side we had the
- 18:17Active Directory, MFA, whatever in place to try to stop it or try to detect it with things
- 18:24like SIEM Sentinel or Defender for Identity, Impossible, that kind of stuff. We have that
- 18:30in place.
- 18:31Yeah.
- 18:32But we shouldn't, and I think that's when it comes, if you see at the market, everybody
- 18:38is so focused on that side. Everybody's trying to say, okay, how do I find anomalies in user
- 18:45logins?
- 18:46Yeah.
- 18:47Or how do I monitor my firewall? How do I monitor all kinds of operations? And we should
- 18:54also ask ourselves, that's good that we do that, but it's a complete blind spot for us
- 19:00or for companies often that they don't see where the vulnerability started.
- 19:06Yeah. That's a good point.
- 19:07And that's, I think, what brings us to the whole DevSecOps and let's touch on that for
- 19:14today and that's going to be a topic that returns, I think, every session we have. That's
- 19:23the whole shift left model from security because on the right side, we should have everything
- 19:30in place to detect that, but we should also have our processes and our tooling and our
- 19:35things in place to detect that more on the left side.
- 19:38Yeah. Prevention is better than healing, right? You want to prevent all of these things from
- 19:41happening.
- 19:42Yeah. But we know we cannot prevent everything.
- 19:44And that's why it's important.
- 19:46For LACP4G, so we need to have that detection as well on our operations side.
- 19:51Yeah, but also processes in that area that if something happens, what is the next step
- 19:57that we are going to do? So there is something that we do not have detected upfront. So there
- 20:05is an issue later on. So what are the steps to take? I want to get back at the security
- 20:12risk. The first thing that you mentioned was managing secrets. And then we had all discussion.
- 20:18Are there any other topics from a security risk perspective?
- 20:24I think definitely, we already touched upon that. I think that's definitely the dependencies.
- 20:29Dependencies are a big thing. Another one that is still sadly still very common are
- 20:34things like OWASP. Does anyone know here what it stands for on top of their head?
- 20:39No.
- 20:40I don't remember on top of my head, but it's owasp.org. I think it's the list of all the
- 20:44top 10 vulnerabilities that are still found. And number one that is still found, I think
- 20:50every year, is SQL injections and stuff like that. That is really we're talking about code
- 20:55here and how hackers can just get it.
- 20:58Cross-sight injections, that kind of stuff.
- 21:01Stuff like that as well. That's also on the list.
- 21:02Bing is helping me on that. It's the open web application security project.
- 21:08Exactly. I'm not going to remember that, but exactly that. Yeah. So stuff like these, these
- 21:13are definitely things that are happening more often than things like the OWASP vulnerabilities.
- 21:22Like you already mentioned, your programming environment, they're still getting better
- 21:26and better in helping you detect these issues. But when we're looking at number one and two,
- 21:32vulnerabilities and leaking secrets, that is something that is currently not normal
- 21:42for developers yet to think about. Like OWASP stuff is stuff that you learn. It is stuff
- 21:47that you, you know, kind of developers quickly learn when they're becoming a programmer because
- 21:51it's very important. But all of these other things that we just mentioned are newer. You
- 21:55know, they're modern problems for these things that we're building nowadays. And you need
- 22:00to use some products and stuff like that. You need to use tools to improve upon these
- 22:05processes.
- 22:06Do we have any examples how we can address these kind of risks that we have?
- 22:14Well, tools, yeah. So for example, you have things like the dependable is very often used
- 22:27is what I'm trying to say. Sorry. On GitHub. So that's a tool that you can use to automatically
- 22:33get like package updates. And first of all, it's great because it makes your thing more
- 22:37secure. And second of all, it's going to save you so much time. So developers and security
- 22:41people should just absolutely love using tools like this. So that every day you get like
- 22:44a pull request or it's even automatically merged into your code, like, hey, these packages
- 22:48should be updated, or hey, these packages contain vulnerabilities, you should update
- 22:52them or you should even migrate to a new package, stuff like this.
- 22:55Yeah, so maybe to explain a little for the listeners, I think dependable, what it does
- 23:00is it looks, you can define which libraries you're using your code.
- 23:03I think it finds it does automatically.
- 23:05Does it even automatically? Oh, perfect. And based on that, it looks if there are any new
- 23:10versions available. Exactly. And if so, it will need, as you said, automatically integrate
- 23:15or create a pull request for you so that you know, okay, I need to change that to go to
- 23:19so that that's a really, really, really useful only feature, I believe, right?
- 23:25Not dependent bot only runs on GitHub. Yes, but there's a thing called renovate bot, I
- 23:31learned about it like only like two or three weeks ago, and I still need to I need to start
- 23:34implementing that in the code base where I work. The renovate bot is the same idea. So
- 23:40you can self host that and you can use that I think even if you wanted to and like Git
- 23:43lab or Azure DevOps and stuff like that. So that's the same idea you could get the vulnerability
- 23:50updates, package updates, all that kind of stuff.
- 23:53So we're talking about tools that can be helpful to address certain certain vulnerabilities,
- 23:59certain things and misconfigurations. But that are tools. What can we do regarding awareness
- 24:10on the developer side itself on the on the people? What can we do to improve the awareness
- 24:18and expertise on that side?
- 24:20I guess people should listen to this podcast. Definitely. That's a difficult one. That's
- 24:26like I feel like, like a lot of these awareness things, it's a time driven thing. It takes
- 24:32time for people to learn more about this.
- 24:35Do we need do we need to educate them? Because we have security awareness on the end user
- 24:40side, giving people training materials. And so we have that also, from from from a management
- 24:48perspective. So consultants and people who are managing IT systems have also training
- 24:56training stuff for that. But especially for developers, I don't have I don't think it's
- 25:01that that much.
- 25:03So we had a great talk on this with David, of course, the for regarding the fan of cloud
- 25:10focus on DevOps.
- 25:13And I think David Righano. Yeah. And I think the key is based is parsing training in these
- 25:20are people but I think it's mainly to bring those people together. Exactly. And I think
- 25:26that's that's that would be the best approach. Like if you look on like technologies like
- 25:33the Fender for DevOps, right? Part of the defender for cloud stack. Depends on what
- 25:40kind of code scanning you have enabled. But regarding of that is you have features like
- 25:46pull request annotations. So what it does is it automatically scans your code based
- 25:53on passwords or anything else. And that shows an alarm. It goes to defend for cloud. And
- 26:02that syncs back to your DevOps pull request. And it points out like on line three, you
- 26:08have used certain parameter or you use the password or we found that and that and that.
- 26:14But more information click here read more on that. And what it does is it creates a
- 26:20platform where security can take a look in the developers ecosystem finds vulnerabilities
- 26:29that could be there and and give them feedback on their platform. Instead of saying no you
- 26:36developer you need to go to a security portal to see the information now bring that information
- 26:42back to where the developer works. It's like you're getting a taught automatically right?
- 26:47Like definitely learning about this is important. But like you know getting taught about it
- 26:53is important is even even like easier for everyone. The developer gets a notification
- 26:57like hey you did it wrong. I just want to touch upon that product like you said the
- 27:01vendor for DevOps is what you said it. Yeah sorry yeah. Is it still the vendor for DevOps?
- 27:08Yeah it's part of the defender for cloud. Security I think it was something with security
- 27:13now in the name right? Like they're renaming it every month. Yeah so it's still something
- 27:17that says there was something at Ignite. Yeah there was something. What's that? So what
- 27:22I saw is like there's also you know like an let's talk about talking to an external service
- 27:28like SendGrid or something to send emails. So you use an API key send it that way. What
- 27:32I learned some time ago is that that SendGrid's API key is a very specific API key. It's like
- 27:38starts with SG and then something else. So when GitHub detects when GitHub detects a push
- 27:44to your repo and it contains a SendGrid API key it will automatically go and do a call
- 27:49to SendGrid to invalidate that API key. I find that a very very interesting approach.
- 27:54Even if you leak a secret like it is automatically invalidated. So it cannot be used by hackers
- 27:59anymore. I believe GitHub has that also for yourself so you can publish your keys in a
- 28:05certain list and it will automatically scan all the other repositories. If it finds the
- 28:10key outside of your repository it will give you a signature as well. That is interesting.
- 28:15Because that shows if your key is leaked or not. Exactly that's really good. Like but
- 28:19it being invalidated is the next step compared to getting a notification. Getting a notification
- 28:26and you're on holiday for three weeks. Then you might have got hacked three weeks ago
- 28:31when you come back. It getting invalidated immediately and stuff like that. That's the
- 28:36next big thing. The next question that I have was regarding collaboration and communication
- 28:43between developers and security analysts. You already touched a little bit on that.
- 28:48If we are touching a bit more on that perspective. Sending the stock analyst to the developer
- 28:58portal so they can communicate with each other and get feedback, give feedback on the code.
- 29:05Is that the only thing that they can do? Or are there multiple information barriers that
- 29:11needs to be hacked between both of these groups? Because a security analyst is mostly involved
- 29:21if something happens or afterwards. A developer is at the very beginning. There is a lot of
- 29:30things in between. How can we bring them more and more together?
- 29:36That's the entire DevSecOps thing. That's really important. I feel like the tools are
- 29:46definitely important but that's of course not the human. You want more human communication
- 29:50about this as well. You need to know there is also a security person working behind the
- 29:54scenes and stuff. You need to know them. What do they find important? What do I find important?
- 29:59What we are doing right now? What kind of problems do I see? What kind of things do
- 30:04you guys know? What kind of things do you guys recommend to solve this issue? I've seen
- 30:09some places where they actually really make a security person part of the team. Part of
- 30:14the Scrum team. It's not like they are actually analyzing the product every hour of the day.
- 30:23They do actually participate in what the team is doing. When there is a question, they can
- 30:29always go to that security analyst and they can have a look around.
- 30:33Is that a security analyst or is that more engineer? Security engineer? I don't know
- 30:38the types. If it's part of the team, it's often an engineer.
- 30:42Is that a SOC? An operating center analyst or engineer? Or is that more or less a security
- 30:49consultant that is involved into projects to bring the security analyst and the developers
- 31:00together? I think the security analyst is the person
- 31:06that reacts when there is an incident. A security engineer consultant is the one that guides
- 31:14the project and takes constantly with the security. It's more a different role in my
- 31:20opinion. Let's for example, if you look at DevOps,
- 31:27DevOps starts with planning. The first stage is before you do any code, you have done anything.
- 31:34You start with planning and create a design diagram. That's your proposal. Without talking
- 31:43about any code. This is the application. To give you an example, I did a project with
- 31:50a really big financial in the Netherlands. Before we even started doing any resource
- 31:58in Azure or any line of code, we needed to get an approval for our design, like the technical
- 32:06design, the functional design, from the cloud competence team, from the security team, and
- 32:16I believe from the operations team. The cloud competence was looking at are we using the
- 32:22right resources, are we deploying it the right way? Security was challenging us, what kind
- 32:28of data are you processing? Based on that, you have this classification, so you need
- 32:32to do that kind of encryption at a minimum. Operation was like, okay, have you your backup
- 32:38in place? I think that's the first stage where it starts. Communication and talking to each
- 32:45other like reviewing that design, okay, this is the solution that we are going to work
- 32:49on. From that three different perspectives. I definitely agree. The one thing is that
- 33:02I do, as a developer, I do see a bit of an issue there where I'm designing an application,
- 33:07right? I'm going to build a web shop API or something like that. It's important that we
- 33:12store our data securely because it's real customer data. We're handling credit card
- 33:15info, stuff like this. It's really important to know. I like learning about security, so
- 33:20I'll notice all this kind of stuff, and I like focusing on how do we store GDPR data.
- 33:26A lot of developers don't, not because they don't know, they just don't really have the
- 33:31knowledge. Talking to those people is very important. I do think that when we're building
- 33:36this application over time, it's going to get new features, right? And we're going to
- 33:39have new requirements. And then I definitely see people slipping and still at that point
- 33:45implementing something insecurely because they didn't involve all of these teams again.
- 33:49It was something that you did at the beginning, but doing that every time costs too much time
- 33:53or there is no time and stuff like that. So for that, I guess I'm a programmer and I love
- 33:59automating so much things. So I really feel like using tools at least for the future here
- 34:06is going to help us the most using all of these tools like GitHub Advanced Security,
- 34:10Microsoft, the vendor for cloud security DevOps. I don't know the name anymore.
- 34:15Let's go with the defender for cloud. Defender for cloud. We're going to call it defender
- 34:18for cloud. That's what we agree with David, right?
- 34:21Yeah, yeah, yeah. Definitely. Great. I think using all of these tools to make, to set up
- 34:26a design with actual with those teams, they really know what fits the company the best.
- 34:31And you need to use this product because that is what we use everywhere. So that's a good
- 34:34fit, stuff like that. And then we're going to start using these tools during development
- 34:39to get odd, to get like a signal like, hey, you're doing this wrong. Hey, this is insecure.
- 34:42Your code has vulnerabilities. You committed a secret. You shouldn't have this package
- 34:46with vulnerabilities. Here's a PR to automate them. I think that is something that you can
- 34:50do to for developer to really keep your code secure over the time that you're working on
- 34:56it. Yeah. To finish this recording up, because we have touched a few different parts, to
- 35:04finish up, we talk, still talking about co-pilots within the Microsoft area. Co-pilot, security
- 35:12co-pilots, what's helping us within defender for cloud, defender for, for, and defender,
- 35:19what is it? Defender XDR within, yeah, all the, all that names about. Just say it by
- 35:26date, right? Today it's defender XDR. Today. Yeah. And the recording is in the beginning
- 35:30of December. So, um, but we have also co-pilot for windows, co-pilot for productivity and
- 35:37so on. So there are different co-pilots. Do you think that co-pilot or AI will, will,
- 35:45will play a role within the stuff while we're talking about having co-pilot? Yeah, I'm already
- 35:52using it like every, every day. Yeah. Yeah. But that's get up co-pilots. But also when
- 35:58talking about, um, defining, uh, finding vulnerabilities and stuff. So we are using, uh, software,
- 36:06uh, or solutions that scans, uh, code and, and, and much more. But does AI also play
- 36:15a role in that area to detect, um, in other ways for developer? I mean, I know that there's
- 36:22now this security co-pilot. I don't really know yet what it is. Um, maybe that's a topic
- 36:27for later. Cause we, you know, maybe it's a topic for a new episode. Cause it, I think
- 36:30it definitely can play a big role, but I think for developers perspective, when we're using
- 36:34co-pilot, maybe it could learn, you know, from your code base, from your company's security
- 36:38policies. And then when you ask it to generate code or when, when it's running in your program,
- 36:42it's like, Hey, you're writing code here that violates company policies or discovery stuff
- 36:46like this. So during development, you get the notification. This is what we already said
- 36:49in the beginning instead of later on in the pipeline, right? When you're writing the code,
- 36:53a new developer day one immediately gets to know, Oh, I'm doing something here. That's
- 36:57insecure. And I think definitely there's a future in that. I think it's going to happen
- 37:01pretty soon. I believe. And I think you can already in your EDA, for example, in VS code
- 37:07already when you have co-pilot and then get a co-pilot, then you can already, when you
- 37:11have a code, you can already ask it, analyze this code to see if there are any vulnerabilities
- 37:16in there. That kind of features already there. So it's not maybe fully automated. That's
- 37:20I think the answer to the question. But if the future is there, I think, yeah, it will
- 37:26play a bigger and bigger and bigger role in my opinion. So it will help. It doesn't replace
- 37:31anything because we still need to realize stuff and create stuff. AI can help. It doesn't
- 37:41take over in my opinion. Hopefully not. Otherwise we have, we are still starting a podcast.
- 37:49So probably we can extend that one. Maybe the next episode will be AI generated. I heard
- 37:55Bing already a couple of times today. So exactly. That's Bing enterprise and Bing helps also
- 38:00in generating questions and doing stuff with it. So having a smooth conversation with that.
- 38:09Did we touch every single piece that we want to touch? I think we talked about some tools
- 38:16and I think I just want to call out a couple more tools for developers at least to start
- 38:20using. Like you from the, I think that's more from the operations perspective. If you might
- 38:24a defender for cloud, right? I think that's a bit more for the operation side on the right
- 38:28side. So it gives the right side to the operation side, visibility into the left side, right?
- 38:39Because you can suddenly see the codes, scan the code, see what's for the village. It's
- 38:44all there. You can do it on multiple layers. So that's I think something we didn't touch
- 38:51because when we are talking about repositories, right? Where you store your code, it's a vulnerability
- 38:56that can come, you can experience there, but you can also have like misconfiguration on
- 39:03your repository side like that you can do push to the main brain, for example. That's
- 39:09something we do. So the fan of a cloud and in combination definitely with GitHub and
- 39:14security, of course, as multiple layer, it's partially the infrastructure side, your configuration.
- 39:19Like, do you have your project PRs? Do you have like code validation, that kind of sub
- 39:24configured and partially it's like your code, scanning your code and bringing the output
- 39:31to the fan for cloud where a security analyst is, you can look at these results. Yeah, exactly.
- 39:39So, so your security and your operation is completely on the right is seeing, okay, this
- 39:45is coming towards the production, right? You are aware of what's coming. And so then you
- 39:52can choose to interact with things like pull request integrations and then send, okay,
- 40:00on line three, we see this and that and that. And that way create that, bring those two
- 40:08worlds together. Yeah, so like stuff like, you know, like you already said, so GitHub
- 40:13security or the greatly named GitHub, GitHub security, GitHub advanced security for Azure
- 40:20DevOps, dependable is what we talked about renovate, all of these tools will help you
- 40:25like finding your vulnerabilities, it will help you like, it will stop you from pushing
- 40:30code that contains leaked secret and stuff like that. And something that's really interesting,
- 40:34like you said, it's like it would also like send signals to these defender, like applications
- 40:40and really, you know, what we kind of started talking about to wrap, I guess, kind of things
- 40:44up. It really brings these things to together, right? The developers are, you know, we're
- 40:49automatically now stopping vulnerabilities, but we're still analyzing them, we're still
- 40:53integrating the monitoring side with it. And you know, at least what is coming from the
- 41:00security side and the operations side, right? And those days a lot, what you see is that
- 41:06security and operation is surprised because there was a coaching, there was something,
- 41:10there was a vulnerability in the code, which where they weren't aware of. Yeah, no, that's
- 41:17true. Now you can still go with that vulnerability to production. It can be an accepted risk
- 41:22for example. Yeah, exactly. But at least you know what's happening. You know what is happening.
- 41:27So, France. That was all. Yeah, I think that's all. Nice. I want to mention one thing, not
- 41:37from this recording, but from the previous recording to finish up. We mentioned Defender
- 41:43for WSL last time. What happens with that? Because there was no support, whatever, and
- 41:54probably there was a preview. That was the thing that I mentioned. But what happens after
- 41:58our recording? Yeah, so last time, of course, we talked about containers and WSL and that
- 42:05it creates a black hole. WSL, yeah. WSL, sorry. And yeah, I think the same day, the same evening,
- 42:13they announced that it's going to public. I think it's not GA. I think it's public preview.
- 42:19Yeah. So what it does is it creates Defender for Endpoint. So if you have Defender for
- 42:26Endpoint on your machine, your server or your server, it also now scans your WSL environment
- 42:34to see what you are doing there. So if you are doing some scary stuff and you think that's
- 42:40isolated, there's now visibility in that space as well. So I think it's a huge step for Microsoft.
- 42:48So if I'm activating WSL on my Windows machine, Defender can take care of that WSL. Exactly.
- 42:55It can see what you're doing in there and use all of these Defender features. Yeah,
- 43:01but we have Defender for Linux, but also the integration on Windows subsystem for Linux.
- 43:10So that's great. Great. So to make that in order that we talked about the last time.
- 43:16Maybe the next time there are more changes that we are discussing. Does anyone want to
- 43:20do any predictions and then next episode will be out? What we already said in the beginning
- 43:27of this recording, we tried to touch some pieces of the DevSafcops framework. So today
- 43:35we talked more or less about code and code scanning, but also a security perspective
- 43:40from a developer. What pieces do we have in the DevSafcops framework, Poojan? Yeah, so
- 43:51we started a little bit on the left side, right? We started with the endpoint of the
- 43:55developer. We started with the code repository. And I think we are going to partially build
- 43:59that up towards the operations side. So I heard you telling identity and authorization
- 44:07is going to be an awesome topic to discuss. How do you authenticate and how do your applications
- 44:14authenticate your micro services? And co-pilot can be different recording in my opinion.
- 44:23Something like that. And also we're going to talk more about this. We're planning an
- 44:28application or I have a laptop here. How do we get the stuff that I built in it to prod?
- 44:33So the stages that you mentioned, like building, testing, releasing, monitoring, there's like
- 44:39loads of stages there and operations. All of these things I can think deserve their
- 44:44own topic, deserve their own episodes. So lots of topics to cover in the next few months,
- 44:50because we want to try every month to do a recording. So keep posted and see if you can
- 44:57realize that. And if not, you can challenge us. So reach out to us at the different social
- 45:03media channels. We're on LinkedIn, on X, is it today? But also on Reddit and all the social
- 45:12media platforms. So reach out if you have questions or want to be part of this. If you
- 45:19like this recording, subscribe or do some-
- 45:25Don't tell them to ring the bell. No, no, no, not ring the bell. But if you are giving
- 45:30feedback on a comment on the different platforms that helps to spread this podcast in the world.
- 45:37So that really helps us. And for now, thanks for listening and hopefully until another
- 45:45time and that was probably next year. So what is it? 2024? See you next year. Thank you.
- 45:53Thank you.