Secure Software Requirements - Summary

The course is part of this learning path

Start course

This course is the third installment of three courses covering Domain 2 of the CSSLP, covering the topic of functional and operational security requirements.

Learning Objectives

  • Explore the functional and operational requirements for building secure software

Intended Audience

This course is designed for those looking to take the Certified Secure Software Lifecycle Professional (CSSLP)​ certification, or for anyone interested in the topics it covers.


Any experience relating to information security would be advantageous, but not essential. All topics discussed are thoroughly explained and presented in a way allowing the information to be absorbed by everyone, regardless of experience within the security field.


If you have thoughts or suggestions for this course, please contact Cloud Academy at


So in Domain 2, we have talked at great length about requirements: what they are, where they come from, how we capture them, that some will be operational, some will be functional, some will be non-functional, and some will be derived from other sets of requirements or conditions that we find along the way.

In this, we have presented and amplified the essential qualities for conceiving secure software in the capture, design, and derivation of the various requirements that we need. It shows us how we break down policy into its various parts so that it opens up and informs us about the conceptualization and the design process and how and where to find our requirements. In this, we've introduced the data lifecycle, and we've discussed how the confidentiality and integrity and availability requirements of the CIA triad fit into it.

We have to be sure that we get familiar with, and an attempt has been made in this module, to get you familiar with the data classification cycle and what activities take place at each one. We've gone through and deconstructed the process of identifying, validating, and capturing these requirements. And these will lead eventually to the software product as conceived, or, more often, as it evolves through the cycle. And this will happen in both functional and non-functional aspects.

About the Author
Learning Paths

Mr. Leo has been in Information System for 38 years, and an Information Security professional for over 36 years.  He has worked internationally as a Systems Analyst/Engineer, and as a Security and Privacy Consultant.  His past employers include IBM, St. Luke’s Episcopal Hospital, Computer Sciences Corporation, and Rockwell International.  A NASA contractor for 22 years, from 1998 to 2002 he was Director of Security Engineering and Chief Security Architect for Mission Control at the Johnson Space Center.  From 2002 to 2006 Mr. Leo was the Director of Information Systems, and Chief Information Security Officer for the Managed Care Division of the University of Texas Medical Branch in Galveston, Texas.


Upon attaining his CISSP license in 1997, Mr. Leo joined ISC2 (a professional role) as Chairman of the Curriculum Development Committee, and served in this role until 2004.   During this time, he formulated and directed the effort that produced what became and remains the standard curriculum used to train CISSP candidates worldwide.  He has maintained his professional standards as a professional educator and has since trained and certified nearly 8500 CISSP candidates since 1998, and nearly 2500 in HIPAA compliance certification since 2004.  Mr. leo is an ISC2 Certified Instructor.

Covered Topics