Latest / Talking Security: Insights from Microsoft Security Experts / #35 - DevSecOps Series – How to release Software Securely in a DevSecOps Pipeline?
Transcript
- 0:00Welcome to the Talking Security podcast.
- 0:08We will talk about items related to Microsoft Security.
- 0:21So hi, welcome.
- 0:23There are we again with the Talking Security DevOps podcast.
- 0:28And again, Pujan and Sander are with me.
- 0:32So welcome guys.
- 0:33How are you?
- 0:34What do we have today?
- 0:38After last time we did a recording about the test phase within DevSecOps.
- 0:45What do we have on the menu today?
- 0:47Pujan, it was all yours, I guess.
- 0:52That is true.
- 0:53Yeah, we had some planning in the last episode.
- 0:57So yeah, indeed, from the last episode where we talked about testing and what you can do
- 1:02in your test phase and what the vulnerabilities you are, it's about time to spend some time
- 1:08about release.
- 1:10In my opinion, it's a very important stage in the whole DevSecOps process, because this
- 1:17is the moment that you go from your code towards your running environment.
- 1:24It will be production or acceptance.
- 1:28So it's a pivotal point where you need to think about the process because you don't
- 1:33want to, you want to have that process as fluid as possible, but also in control as
- 1:39possible.
- 1:40But you don't want to stop the developers like Sander too much by creating all kinds
- 1:47of issue or performance for them.
- 1:49So yeah, today we are going to talk about release.
- 1:52Why it is important?
- 1:54Which features in there are important together with you guys?
- 1:58We will also take a look what kind of, what you need to do and what kind of to align this
- 2:07process as well.
- 2:12What is your view on the release?
- 2:15My view on the release?
- 2:16I find, how do you say that?
- 2:22And we're talking about like DevSecOps and release.
- 2:24I think it's a really, really important part.
- 2:25Like Poojan already mentioned it before.
- 2:28When I started learning DevOps and CI, CD a few years ago and stuff, like right after
- 2:33school, it was really cool to me.
- 2:34I could just deploy my applications immediately and release them.
- 2:38But I think with DevSecOps, it's maybe even more important because the entire focus is
- 2:42on the security part.
- 2:43Like in the previous episodes, we talked about security.
- 2:47And now if you have found some security issues and you need to fix them, you need to also
- 2:50be able to release them really, really quickly.
- 2:53And especially like what Poojan then says is right, if we want to release something,
- 2:57we should not have that many barriers in place, but the barriers would still ensure that you
- 3:03are secure.
- 3:04So you need to find a bit of a balance in that.
- 3:06But I think it's a really, it's a fun step of being able to have your software.
- 3:10It's done, it's built, it's secure, it's tested.
- 3:13And now we're actually going to finally release and do something with it.
- 3:15And yeah, it's always a fun thing to do.
- 3:18Yeah, if we want to kick off, what should be the first question you should ask Sander
- 3:26in this area?
- 3:30The first question you should ask?
- 3:32Yeah.
- 3:33What question should we answer to our listeners within this phase?
- 3:40What is the topic that you want to cover within this phase?
- 3:45And probably if you have the question, Poojan can maybe answer that.
- 3:51I think maybe that's a good thing to ask.
- 3:55Maybe it's a bit open.
- 3:56So if we're releasing our code, how do we know that what we are releasing is going to
- 4:01be released to a secure environment?
- 4:04Right?
- 4:05Like we've tested and we've built our code, we did all of our security thingies there,
- 4:10but now we're going to release it.
- 4:11So how can we ensure that what we release will be running securely?
- 4:19So if you look at, if it runs security, it's of course more on the operation side, right?
- 4:26So then we are more going, for example, if you take our code, because this is the pivotal
- 4:33point, right?
- 4:34I think what you're saying is like, release is integrating the code, security and operation
- 4:39together.
- 4:40And for us to see how the code is functioning in operation is building on solutions like
- 4:45Defender for Cloud, right?
- 4:47For example, we are doing container Kubernetes, or we are doing some database changes by monitoring
- 4:55our solutions in operations, but solutions in the Defender for Cloud family gives us
- 5:01a good overview.
- 5:02Definitely when you integrate it with Defender for Devils, but yeah, we have told that a
- 5:06lot of times.
- 5:07That gives a good feel like, okay, what were the changes and how are they functioning in
- 5:12the production side?
- 5:14So that would be a key.
- 5:16And I think of course there's a process on top of that.
- 5:19It's like after your operations center, your security operations center, which is monitoring
- 5:23and responding based on those security alerts or findings or full abilities that are coming
- 5:28from that environment.
- 5:29Yeah.
- 5:30So that would be definitely a way forward, in my opinion.
- 5:35Yeah.
- 5:36That's a good point.
- 5:37If you go back, that's a question to both of you guys.
- 5:43In my opinion, if you take a look at release, it's mainly having defined how we are going
- 5:50to release and what steps are included in there, right?
- 5:55That's part of the DevOps, but it's also part of the DevSecOps because things we discussed
- 6:00last time like code scanning, those are also, in my opinion, part of the release stage,
- 6:06those are things that you define in your workflows often as well.
- 6:13So that brings us to a terminology, of course, that's often used like the CI CD, right?
- 6:18The continuous integration, continuous deployment.
- 6:22And how do you guys see the uses of that in your environments?
- 6:29I'm not really sure if I understand what you mean.
- 6:33The uses of that in my environment?
- 6:35Can you explain that a bit differently?
- 6:37Yeah.
- 6:38Do you have a really, if you build an application, do you have a CI CD in place?
- 6:44Like when the code change hits certain branches that the certain steps happen, or if your
- 6:50main branch is updated, certain workflows get triggered to do certain deployments or
- 6:56packagings or even updating your ETSM or environment?
- 7:01Yeah, definitely.
- 7:03So in my case, normally, when main gets updated, we build our code, you can do your security
- 7:09steps right there that we talked about last episode, which you should definitely listen
- 7:13to.
- 7:14And then there's of course, when that is built, it produces an artifact.
- 7:18At least that's what it's often called in Azure DevOps, which is what I mainly use,
- 7:22which is then released.
- 7:23And then I think it's a really good way, would you say, for example, when we have a new Docker
- 7:27image that we want to, we have scanned, we can upload that to an Azure Container Registry
- 7:33or an AWS registry or whatever kind of registry it is, where also more security steps can
- 7:38take place, which I think is a good thing to do in your release steps.
- 7:43And then of course, we need to publish some more stuff to the cloud or to wherever you're
- 7:48running.
- 7:49Which I think kind of flows into a very nice next step is how do you connect securely in
- 7:55your release step to whatever you're deploying?
- 7:59I hope people are not losing a username and password when they're deploying something
- 8:03to Azure.
- 8:04You should be using the most modern techniques for that.
- 8:08Maybe you can talk a little bit about that, Poojan, because I think you talked about that
- 8:11before.
- 8:12Yeah, definitely.
- 8:13I think the usage of a username or what we see a lot, I think we all, three of us, is
- 8:23the usage of search principle and passwords, for example.
- 8:26Well, there are great tools that can help you.
- 8:30I mean, go for GitHub and security has already code or password detection pre-commit, so
- 8:39it doesn't even get to your commit history.
- 8:43But yeah, we also have like the defender for DevOps, you can integrate that in your workflow
- 8:48that you do a scan to see if there's any code and if there's not, then you will continue
- 8:53with that.
- 8:54So we need and the same is possible with GitHub advanced security, with fair code, for example,
- 9:01what we discussed last time.
- 9:03So the usage of security like passwords is really one of the important things.
- 9:12But one of the things that's also important to check when it comes definitely towards
- 9:19your if you are doing things on cloud like Azure, definitely important to do like, okay,
- 9:26the environment which I'm deploying or maybe I'm creating because that's part of your configuration
- 9:31as well.
- 9:32Are there any full ability there as well?
- 9:34So we see different levels when it comes to security in the release page.
- 9:39But I have like, for example, also customers when it comes to the release is like, okay,
- 9:46we need to have after each deployment to our production, we need to have a change record
- 9:52created for that.
- 9:54So that we are for our compliance purposes.
- 9:58We see that also a lot in this release workflows coming back.
- 10:04I don't know if you guys see that as well.
- 10:06I'm not too familiar with it.
- 10:10And if we look at compliance in policies, we're talking about secure code, scanning codes
- 10:20and so on before releasing it.
- 10:22So we have a secure piece of software that has deploying.
- 10:27But on the other hand, what about policies?
- 10:31If you are, let me give you an example, if you do a pull request and to merge that into
- 10:42a new branch or a new master before deploying.
- 10:48You can't say that anymore.
- 10:50You can't say a monster anymore.
- 10:52I know, but it's an example.
- 10:58How many approvals do you need?
- 11:03What steps do you need to take before something gets a final approval and gets to watch a
- 11:11release?
- 11:12That's a good point.
- 11:13I kind of overlooked that.
- 11:14That's a good point.
- 11:15So yeah, you're talking about, for example, when code is merged, like, you know, who needs
- 11:19to, your code can contain things, but people need to, of course, look at the code as well.
- 11:25But then there's, of course, the really important thing, like, what I usually do is, well, my
- 11:30code gets merged, then it goes to automatically gets deployed to the test environment and
- 11:35then just automatically no one has to look at that.
- 11:38But when we want to deploy the production, someone has to click on the approve button.
- 11:43And in my case, in my teams, my teams are usually pretty small that I work in.
- 11:47So I usually just do any member of the team can do it.
- 11:50So if I want to, I can also just deploy to prod whenever I merged.
- 11:55It's a small team and it doesn't really matter all that much.
- 11:59But for bigger companies and for enterprises, that's probably a good thing to have.
- 12:02Like, hey, maybe multiple members of your team need to look at what you're deploying
- 12:06to production.
- 12:07Maybe if you have multiple really big teams and you are affecting some other team's code,
- 12:13might someone else to also click on the approve button to kind of take a look when stuff is
- 12:18going to be deployed.
- 12:19I think that's a good thing to mention.
- 12:21Yeah.
- 12:22And Poojan, how does that affect the security teams in that?
- 12:25Yeah, that's a good.
- 12:28Yeah, I think it's a great question because but also to add on what Sander mentioned is
- 12:36the number of people that need to approve things.
- 12:38I think it all comes down to the level of workflow that you have created in the sense
- 12:46of how advanced is it like are the code testing, are the functional testing, user testing,
- 12:54all kinds of tests already in your workflow.
- 12:57Like building up your change log, building up your documentation, creating your change
- 13:01requests in your ETSM platforms.
- 13:06So it depends on the security side as well.
- 13:10We also say, OK, for example, if you have your CI part of the deployment, the continuous
- 13:19integration part, pretty well framework and you have your tests, your validations in place,
- 13:25then your deployment checks will decrease, of course, the number of checks because you
- 13:30can rely on your tests more.
- 13:35And the same is for security when it comes if you have done definitely active testing
- 13:42on your code.
- 13:46Let's say, for example, you have multiple solutions and you deploy your code changes
- 13:54to an acceptance environment before you deploy to production.
- 14:00And there you have your code validation part in place and you have that environment also
- 14:05connected to something like Defender for cloud.
- 14:11Then you can both find no vulnerabilities or any misconfiguration or code violations.
- 14:18Then it's much easier to say, OK, the deployment to production needs one approval.
- 14:24That's a good point.
- 14:25So to summarize, I think what you're saying is if you have a lot of active monitoring,
- 14:30for example, in place, the code is running 24-7 somewhere in the cloud.
- 14:34And there's also some monitoring solution that is checking all of that.
- 14:39If there's loads of stuff already before or during the runtime of your application, you
- 14:44don't need to add 20 checks and approvals and ceremonies to the release process.
- 14:52You need to think, especially for your team and for the product you're working on, what
- 14:55part needs to be secured?
- 14:57If I'm deploying some really tricky software that needs to be very well secured during
- 15:02the build process, but doesn't really accept any user inputs or cannot really be talked
- 15:08to, maybe then it's more important to do the build security stuff and let go of the release
- 15:14process, do some basic checks, some basic approvals.
- 15:19And that's it.
- 15:20Yeah.
- 15:21Because you need to ask yourself, I think, the following questions.
- 15:24If you have three people approving your deployment, what are they actually approving?
- 15:34And are they aware of what they are?
- 15:36Yeah.
- 15:37Usually it's nothing.
- 15:38And usually when I work in a team or even when I set up the policies and stuff, I usually
- 15:44always click on the person that created the release is also allowed to merge it.
- 15:51And if you've got to be very puristic about it, you could say, yeah, but if that person
- 15:54has bad intentions, they could release something to production.
- 15:56I never assume people have bad intentions.
- 15:59And I've had multiple occasions where I had to release something in the evening and someone
- 16:03had enabled that I was not allowed to release to production my own code.
- 16:09So I had to call someone to turn on their computer so they could click on a blue button
- 16:12for me.
- 16:13So it's really important.
- 16:14Yeah.
- 16:15Personally, I'm never a big fan of the like, other people have to look at it.
- 16:19I think it's something you talk to with your team.
- 16:21You need to communicate with your team about this kind of stuff.
- 16:24But yeah, it's more of a sidetrack where I'm going right now.
- 16:29Sorry.
- 16:30Well, to point out the first point you made, I never assume anybody.
- 16:34Well, that's not really in line with assume bridge.
- 16:37So you need to always assume someone is trying to because that person doesn't need to be
- 16:42that person.
- 16:43So that's, I think, the whole reason why you have the DevSecond.
- 16:47That's a good point.
- 16:48That's a good point.
- 16:49So on the second part, I think that's one of the biggest challenges for organizations
- 16:54because you don't want to call up your colleague at 7 p.m. in the evening or later even in
- 17:01the hope that they answer to click about that.
- 17:03In my opinion, I think definitely when it comes to security and also developers, developers
- 17:09want always to have speed, right?
- 17:11You want to get things done as soon as possible.
- 17:14And security wants to be in charge and see what has been done and what's going to happen.
- 17:22And that's why the release is so important because if you bring all those requirements
- 17:28into one workflow, like what is security asking us to do and what is developers asking us
- 17:33to do and what's operation asking us to do?
- 17:36If we have that process in one overview and we change that into our CI CD workflows, then
- 17:46in my opinion, you don't need to call someone at 7 p.m.
- 17:49There should be that control should be in place to give you the possibility to do your
- 17:55thing while the monitoring on security is high alert.
- 18:05From the operations side, because we are talking about security and we are also talking about
- 18:10the developers, but I think it has a really huge impact on the operations as well, right?
- 18:14Because they need to be aware what has been changed because at the end, often they will
- 18:20get the calls from the customers or from the employees that something is not working.
- 18:28How do you guys integrate that part as well?
- 18:33That's actually a good point.
- 18:34I haven't really thought about it in that way.
- 18:38Yeah, usually what the team lead or the product owner does is just send an email to the organization.
- 18:44Hey, this is going to be changed.
- 18:46But I guess that works for small companies, for bigger enterprises.
- 18:49I've seen systems where they have like build change logs and then you can just kind of
- 18:54go to an internal page where you can always see what version of a system is running when
- 18:59it was updated and the change logs and stuff you can see right there.
- 19:04That's kind of interesting.
- 19:05On the other hand, I also feel like if you're going to do breaking changes during your release,
- 19:09that should definitely be something that is communicated beforehand or in fact, you should
- 19:13never do breaking changes until everyone is ready for them.
- 19:18But yeah, how do you communicate with it?
- 19:21Is it also kind of an important part, especially if it's going to be something secure that
- 19:26you're going to be deploying or you're going to be deploying changes to your configuration?
- 19:30For example, some biceps, some infrastructure scope, that's going to be deployed with different
- 19:34firewall rules, different security stuff, something that you definitely need to keep
- 19:38in mind when you're going to be deploying that in a big enterprise.
- 19:42Everyone should be aware of that.
- 19:44Yeah.
- 19:45And I think in the end, what you see a lot is that security teams are trying to step
- 19:54in into that developer's ecosystem, right?
- 19:56To get a better understanding and controls in place, and then the same should be there
- 20:01for operations.
- 20:02And I think that's what makes release important is to get a clear overview of all those requirements
- 20:11from those teams as well.
- 20:13But what do you see, for example, as challenges when it comes to, for example, let's say we
- 20:23are having our CI CD in place, we are having our code validation and scanning what we discussed
- 20:30last time and previous, everything in place.
- 20:33And once you do a change and that change got blocked because it contains certain security
- 20:40vulnerabilities.
- 20:41Yeah, that's tough.
- 20:43I mean, I guess it's kind of the boring answer if it depends.
- 20:50I still feel like if there's something happening in the business and something needs to be
- 20:57deployed now, and suddenly I get like a CVE, right?
- 21:01Like a critical vulnerability and the E, I don't know what that stands for anymore.
- 21:07You should, I guess, still be able to deploy it.
- 21:10Before you were deploying something and you didn't know there was a vulnerability, but
- 21:14now you're deploying something and you know that there's a vulnerability.
- 21:17And I think it's just kind of on you, you as the human need to make the decision, am
- 21:21I going to deploy this?
- 21:22Right?
- 21:23So that's kind of where it depends.
- 21:24If the business is losing money at this moment because something needs to be deployed, you
- 21:28can't tell the business, no, we have a security, we have a tiny security issue.
- 21:32You need to still be able to deploy.
- 21:36Perhaps it depends, right?
- 21:37Like if it's for a critical banking system, I don't think you want to do that.
- 21:42I would prefer the bank not to deploy something with a known security availability and I can
- 21:46wait a bit longer if possible.
- 21:48But I feel like if there's a little ceremony, the releases should be able to be done quickly.
- 21:53Like the process of the release itself should be very quick.
- 21:57The release should always either succeed or fail.
- 22:00And you should just be able to do it because you want to release something to production.
- 22:06And maybe you can like set up a workflow, right?
- 22:09Like, yes, I'm deploying something and this artifact that I'm deploying has a vulnerability.
- 22:14So it is automatically cataloged somewhere or someone has mentioned in Slack or like
- 22:19some security officer champion person in the company is notified and says, hey, this needs
- 22:25to be fixed right after this release.
- 22:27So I think some strategies like that, I think could be really helpful.
- 22:32So but that should be already in place, you said, because that's again, something that
- 22:38you see a lot when it comes with when we try to create and put monitoring points into the
- 22:48whole deployment.
- 22:49One of the discussions like often customers say, well, don't do it then or then you need
- 22:54to have a different path to release.
- 22:58And that again, what happens often is that the end it will go through, but it will increase
- 23:04the release time.
- 23:07And that brings us to the second question that I have for you guys is what is unacceptable?
- 23:13Because I get a lot like from our internal team to our customers like this workflow takes
- 23:19too long to validate or to test to deploy because it has certain checks included into
- 23:26it.
- 23:27Yeah, yeah.
- 23:28I like time wise, I mean, how long may an entire pipeline take?
- 23:33In my opinion, not more than 10 minutes.
- 23:35And I've had some I've talked to some of my colleagues, you never like 10 minutes, dude,
- 23:38like my release takes an hour and a half.
- 23:40I'm like, I don't have the patience.
- 23:42I do not have the patient.
- 23:43And that's kind of point in time, I would just go crazy.
- 23:47It really depends on the product.
- 23:48Again, like if you're building some small web applications, if they take longer than
- 23:52five minutes, I'm like, what are you doing in there if it takes that long?
- 23:55Like if you're doing a lot of security checks, that's fine.
- 23:58You know, I mean, if that is needed, that is a good point.
- 24:01And if no one really cares that it takes longer, fine.
- 24:04But if it's a critical business process, I feel like you and you know that this might
- 24:10need releasing very, very soon, very quickly.
- 24:13You might want to think about maybe having a process that allows you to skip some checks
- 24:18and just release it quicker.
- 24:19I don't know some critical software that it might be very vulnerable.
- 24:25You might want to be releasing quickly, but some small status page application doesn't
- 24:29really matter all that much.
- 24:31If that goes quick or bad, quick or slow.
- 24:34I think it really depends on how big the data, the code is and you want to deploy.
- 24:40If it's a small app, like a small web app, for example, it can be a few minutes.
- 24:46But if it's a complete application that has multiple things to do, lots of code, and it
- 24:56could be much, much, much longer than a small one.
- 25:00Yeah, it depends.
- 25:03That's the consultancy answer again.
- 25:06It is.
- 25:07I think it also just kind of like I've had projects where there were like 2000, 3000
- 25:12unit tests.
- 25:13So yeah, those are going to take some time to run.
- 25:14And that's not even that's kind of still the build step and the release step.
- 25:18Then it depends on the, well, on what you're deploying.
- 25:22If you're going to be deploying to E to IIS, I guess is what you're producing in English.
- 25:27Just some web server that goes quite fast.
- 25:29But I've had situations where I wanted to deploy something to Kubernetes, to Azure Container
- 25:33Apps.
- 25:34And then it was just quite slow because Kubernetes had to get another VM running and everything.
- 25:40It really depends on what you're deploying.
- 25:42But I think it might be something that you might want to talk about with your team.
- 25:45It's like, hey, this critical business component, I want to talk about this.
- 25:48I don't want to talk about the status page.
- 25:50That's not waste time on this.
- 25:51This critical business component, how long is it going to be?
- 25:54How long do we want it to take to deploy?
- 25:57And if it takes longer than that, maybe we want to look into this at some point.
- 26:01Yeah, and another question that may be related.
- 26:09In the pre-phase of this recording, Poojan, you talk a lot about chaos engineering.
- 26:16Maybe you can elaborate a little bit on that.
- 26:20Why should we have that?
- 26:23Does it relate to what we have here, the release phase?
- 26:30Chaos engineering, yeah, I think that's something we discussed in our last episode as well,
- 26:36right?
- 26:37Very quickly, I think very quickly.
- 26:40Yeah, chaos engineering, I think one of the most famous, and I think there are even the
- 26:46starters of that.
- 26:49That's Netflix.
- 26:53The chaos engineering is important to the release, in my opinion, because chaos engineering
- 27:01means that you just shut down some of your systems without pre-notice, and then you see
- 27:08if your workflows and everything is in place to get that thing running again without any
- 27:13issues, or that it also doesn't interrupt your production, right?
- 27:21So I think, in my opinion, if it would bring chaos engineering to release, it would mean
- 27:27that it shows that, for example, we have a solution and the whole Kubernetes cluster
- 27:33with all nodes and ports and every configuration containers, everything running there, and
- 27:38somebody just destroys everything, that we are able to rebuild that from zero to everything
- 27:48through the configuration application and the whole operation sites and monitoring,
- 27:56getting that in place fully automated.
- 28:01But I think it also, Sander, has different meanings from the developer's perspective.
- 28:05Yeah, I do.
- 28:06Maybe you can elaborate on that.
- 28:08I think maybe we want to talk about it very shortly, because I think this is a perfect
- 28:12topic for the, like, if we're going to talk about from a developer's perspective, maybe
- 28:17from an ops perspective, I think it's a really good thing for, like, the monitoring episode
- 28:21kind of thing.
- 28:22So for my point of view, what it is really useful for is, let's say we have two services,
- 28:28like a user service and, like, an order service.
- 28:31And the fact that the order service is down, just because some system in Azure or Kubernetes
- 28:36or whatever just kills your system, then your system should at least still be able to restart.
- 28:43And I think that's more of like a thing that should regulate itself.
- 28:47So then how does your system react to this?
- 28:50Do people get notified?
- 28:53Is it allowed?
- 28:54Is the service allowed to be down for 10 seconds?
- 28:56And then do people get notified?
- 28:57How long is the service allowed to be down?
- 28:59All of this kind of stuff is what you can use Chaos Engineering for.
- 29:01Just really truly test, like, hey, 20% of my system is down, but I can still process
- 29:06orders because that's what earns the business money.
- 29:08So we can really test, like, how those critical flows work.
- 29:11Yeah.
- 29:13Werner, I think you were talking more about, like, how is the code released and, like,
- 29:18set in place again after that happened?
- 29:20And I'm thinking more about how the system recovers and how you set up a strategy and
- 29:27how you can write your code in a way so you can test, like, hey, my code is down, but
- 29:31I can still process orders or something like that.
- 29:33It just kind of goes to different ways.
- 29:35Yeah.
- 29:36I think, indeed, it has an impact on different stages and with different scenarios, right?
- 29:43Each scenario, somehow it is applicable, Chaos Engineering.
- 29:49But yeah, guys, so I think that was the release stage.
- 29:54I don't know if you guys have anything to add to it because I think to sum it up, it
- 30:00is somewhere a technical solution in the whole process, right?
- 30:04Because you need to define your workflows.
- 30:07But I think in the end, it is the most important to highlight how important it is that when
- 30:14you do that, that you cooperate your security, like code scanning or any other security features
- 30:22that you want to have in place, right?
- 30:25Because defining security is a big as well, right?
- 30:28Code scanning can be one, but having a change record for your compliance purposes in your
- 30:33ATSM too could be also part of your whole security strategy.
- 30:39So to bring that together, and I think at the end, it shows also what we are discussing
- 30:45here how important that is to have that conversation with your operations, with your security,
- 30:50and with your developers.
- 30:52When you are building and writing out your release strategy.
- 30:56Yeah.
- 30:57Because it's DevOps, right?
- 30:59So we're going to involve the developers, the security and operations people.
- 31:04So we want to know that when we're releasing something, everyone should agree.
- 31:08And that can be a manual process by asking some people or letting people click on the
- 31:12approve button, but also automated, which you were talking a little bit about, right?
- 31:16Making sure that there's some steps involved and some final checks that you can build in.
- 31:21Yeah.
- 31:22And it depends on how big the company is.
- 31:25Because if you have a, we talked about in a previous recording, we did already talk
- 31:30to a bit of it on that.
- 31:32If you are on a small company, like you are developing Sander and work with some small
- 31:38teams, who is doing the security staff?
- 31:43Normally you have your own security team, but is that available in your organization?
- 31:49Or should someone from the dev team take care of that role to approve and to see if all
- 31:59the security checks are done?
- 32:01So I think how many people are involved in the test, but also in the release phase are
- 32:08depending on how big the company is and how big the fees are.
- 32:11Yeah, definitely.
- 32:14I think that is for all the phases, right?
- 32:18It sounds maybe crazy, but also don't make it over complicated if you have a small team.
- 32:24Oh, please don't.
- 32:26Yes, absolutely.
- 32:27Don't put four approvers if you are a team of five people.
- 32:30Ten approvers if you are with three people.
- 32:33Yeah, that's good.
- 32:34No, don't make it so complicated.
- 32:36Like it's, yeah, I could rant about this for half an hour.
- 32:39I'm stopping myself right now.
- 32:41Yeah.
- 32:42Yeah, that's it.
- 32:46That was the release phase, as you mentioned, Poojan.
- 32:50If you have questions when you are listening to this recording, please reach out.
- 32:56We can do a listener session later on when we grab all the questions that we got from
- 33:05participants, from listeners, we can do a specific session on that.
- 33:12The next one is about monitoring.
- 33:17You already mentioned it, Sander.
- 33:19I think.
- 33:20Yeah, yeah, yeah.
- 33:21No problem.
- 33:22Yeah, definitely.
- 33:23That's going to be an exciting one because I feel like that's part, at least where I
- 33:26also still have a lot of stuff to learn, but also have had a lot of lessons learned in
- 33:30the last few years.
- 33:31So I think I'm really excited to talk to you guys about it.
- 33:33Let's do that.
- 33:35And if you like our videos and podcasts, subscribe on our YouTube channel, on our different podcast
- 33:43platforms.
- 33:44Please like and give us a review because that helps us to make these recordings better.
- 33:50And yeah, hopefully see you till the next time.
- 33:52Thank you, guys.
- 33:53Thank you.
- 33:54Thank you.