for less than 3.4. We're gonna talk about providing some security to the developers to help them again. Give them some knowledge, get them toe about how to write secure code. But also tell them about this is what we're gonna be performing these the tools we're gonna use to give them a chance to fix bugs before they even get to the security testing portion.
The lesson objectives. We're gonna list some of the i D plug ins to help improve secure coding,
describe the need for coding standards, take a look at some certifications for developers and critique the need for contract enforcement for development projects.
So before coding even begins,
would be interested is to have
I d plug ins that go into in the development environment. So there's ones like spot bugs for Java.
Puma scan for dot net sonar Linz there that there's all these ones so that it's as their developer and writing code riel time. They're getting feedback, saying a. There's a bug here. There's something need to take a look at.
Another component. Might be
that's needed is coding standards. So especially when you want to report ah, vulnerability, you can map it to the standards so that and you can stay abroad, the of the standard we're gonna judge you by so that they know when you report something, you map it that has some teeth to it.
So Carnegie Mellon has this software engineering institute. They have some standards. A wasp has a secure coding practices
and is a nest s STF requirement to the pita. We got seven
to have the code review procedures. So,
for example, ah, process for developers to review the code, some collaboration so that peers can review each other's code to find bugs. You don't have just one person writing the code,
and then the document, the lessons learned so that
the same mistakes don't aren't keep
are being repeated over and over again by the same developer or across the whole development team.
So here's some of the training certifications that may be helpful. There secure secure coding exercises like Range Force Co bashing each other. They provide the scenarios to go through some testing. So you could they concede these vulnerabilities and how to actually fix them into code, or how the bugs get in there and how toe said,
right in a secure fashion,
there's some certifications. Santa's secure coding secure Dev ops. A couple different ones. Carnegie Mellon again, again from the certain has secure coding for Java sea. They have engineering software. Assurance
I C squared has the S R. C s slp different certifications out there that could help,
developers understand how to write or secure code.
And then these things could also be used in contracting. If you say
the developer must have these certifications if they want to work on this project,
I have a question. No one of these. Have you ever had problems explaining security to developers?
I'm not really gonna answer this because it's gets border you think about. But was he was a problem. You were not using same terminology. Maybe, uh, do you not understand each other? Concepts would would have helped if Dev and Ops had some security knowledge.
So kind of these think about maybe these were the problems. And maybe some of these concept that we explain could have helped.
And I mentioned this already, but contract enforcement may be helped the organization
I've seen some of these before. They just say you must write secure code and shouldn't be any bugs.
That doesn't really mean anything. It's no bugs it it just got a fluffy language. So you need to specify requirement to fix. So
ah, sweet, specific timeline for mitigation. Again, If we met back to these coding standards, you could say the no bugs according to this standard
and to find the use of third party libraries. We've talked about that some vulnerability and third party libraries and specify that these are part of Thesiger your coding and that they need to be patched along
with any bugs that are found.
Um, again, you could possibly require some certifications or some
some major or some people within the development team has to have it or certain number of people.
The summary For this We talked about teaching security concepts to developers and giving them the tools they need to write secure code.
And in the next module started. Next lesson, all demo spot bugs, which is this concept of if the plug in in the i D. That gives them real time feedback, so it should be really interesting lesson