So we have reached the end of Domain 1: Secure Software Concepts. Now in these four modules, what we've covered is some basics. We have achieved an understanding of what underlies secure software. Through this discussion, I hope that you've become familiar with the practice of risk management and how it integrates with software development.

We should be able to apply the security concepts throughout the development life cycle, regardless of which management method we're going to use. We've talked about the various security models and how they may apply, what concepts they may lend to the project. Being familiar with the legal and regulatory factors and their effects on software development. Applying design methods to address these issues of performance and resilience, and understanding how security and assurance integrate into the acquisition process.

In the end, what we're trying to achieve ultimately, is a balance between the design and build, the security and the operations, throughout the life cycle in all phases, and all ways that are appropriate and reasonable to ensure that we produce the best product that conforms to the secure by design, secure by default, holy grail features that I mentioned at the beginning.