This course looks at the second section of Domain 6 of the CSSLP certification and covers pre-release activities which include implementing the actual testing process, the actual conductive test, and the variations of the test that will be employed at this stage.
- Understand the pre-release activities to carry out before launching software
- Understand the pre-release testing process
This course is intended for anyone looking to develop secure software as well as those studying for the CSSLP certification.
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.
We're going to discuss pre-release activities which include implementing the actual testing process, the actual conductive test, and the variations of the test that will be employed at this stage. Now, this part of the process consists of all actions taken throughout the design, development, and testing process to determine if the product is actually ready for release and thus deployment.
The testing process began with the concept definition and design phases. It ran then in parallel with the development stages with increasing depth and sophistication. The object has been to assure that the conceived product has proceeded in alignment with the planned design or plan design as modified by changes found along the way, yet still performs as intended throughout each stage and through each progressing stage. The process also continues to be employed over all changes that follow production release to ensure that the performance and consistency are also maintained.
Now in the pre-release activities, we have to consider that part of the overall master testing plan and the tests that make it up should include selections made by and agreed to by both customer and by the builder to ensure that the technical construction aspects of the builder and the functional desired effects of the customer are given proper waiting and consideration.
Now the combination assures that real-world and test bench cases are examined in proportion and with validation of both. The procedures, the definitions, and the criteria for interpretation would also be decided early on, and then reviewed and adapted as warranted by the project or product evolution, including all the changes that take place along its timeline. Overall, the objective is to ensure that the final product appropriately meets the requirements of the product's intended use in the target environment and not only the more sanitary cases found in the testing environment itself.
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.