We will continue to build on the essentials of those elements, ideas, concepts, and principles about what issues must be considered when embarking, that is, before embarking on a building program of secure software. We'll discuss the active employment of those essentials and making the optimal use of them through better building. It is less important whether you are working in an Agile Scrum shop, a classic waterfall operation, or a DevsSecOps continuum than it is to ensure that the building of resilient, resistant, recoverable software incorporates structures and features that will make the final product effectively secure.

Every type of practice model can be, and must be able to do this if the final product of secure software will live up to the performance and reliability expectations. What we cover in this module will have a critical impact on the process and the final product produced by your project. In fact, it is more than likely that the impact will be significantly negative if they're not used to inform the functional and detailed design decisions reached in this phase. In this module, we will cover making the best use of these concepts.

So onward. So here we have our domain objectives. We're going to first attempt to understand programming fundamentals, we're going to become familiar with different development methodologies, we're going to know common software attacks and the means of exploitation, we're going to understand defensive coding principles and protection techniques, we're going to, when we're complete, know how to implement safeguards and countermeasures, and then how to conduct code peer reviews.

So here we have section one, common software vulnerabilities and countermeasures. In this, we're going to cover vulnerability information sources, common vulnerabilities in the countermeasures, input validation failures, general programming failures, enumerations, and then other common attack forms.