This is the fourth course in Domain 3 of the CSSLP certification and covers the essential ideas, concepts, and principles that you need to take into account when building secure software.
Learning Objectives
- Understand the process and controls available to secure your software
- Learn about the main security technologies available
Intended Audience
This course is intended for anyone looking to develop secure software as well as those studying for the CSSLP certification.
Prerequisites
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.
Operating systems of course play a key and indeed critical role in all of this. Now the software products, which is what an operating system is, designed to manage hardware and create environments for software as applications to run, plus all the service code. They're designed to create a well-managed environment on the hardware and enable the applications and data to interact, as well as ensuring that they are isolated from each other in any way that might cause a system failure or a violation of the security policy.
Now some of these will be embedded systems and these are quite common. We see them in the functionality of various devices like video cassette recorders, temperature-controlled devices, and others, where the software is embedded in a chip and functions strictly from there in a very limited way. Now there are other ones which we call IOT or control systems, and they are in various categories. Some are called SCADA, some are called ICS, industrial control systems, are program logic controllers that in their various functions, are representatives of the body of what we refer to as IOT or the internet of things. These connect and control devices that collect data, manage industrial processes such as refineries or emergency response systems, and the electrical grid of the nation. Firmware is code embedded in ROM chips and function as operating system and bios for such systems.
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.