1. Home
  2. Training Library
  3. Security
  4. Security Courses
  5. CSSLP Domain 7:1 - Secure Software Installation and Deployment

CSSLP Domain 7:1 - Secure Software Installation and Deployment

Deployment, Operations, and Maintenance - Introduction
Overview
Difficulty
Beginner
Duration
30m
Students
18
Description

This course covers the security aspects that a CSSLP needs to keep in mind when dealing with the final stages of the software development life cycle including deployment, operations, maintenance, and the disposal of the software.

Learning Objectives

  • Learn the essentials of how to develop, deploy, and maintain software

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.

Transcript

Now, once software has been formally accepted by the customer or client, it is ready to be installed or released. But the installation and deployment process itself needs to proceed and be performed with security firmly in mind. It does not necessarily mean that it will be deployed with security controls in place. Now, all of the software assurance efforts in designing and building the software can be rendered futile if the deployment process does not take into account security. In fact, it has been observed that software faces hiccups when it is installed. A decision such as following the software to run with elevated privileges or turning off the monitoring and auditing functionality, oftentimes, adversely affects the overall performance and security of the software.

Once the software is deployed, it needs to be monitored to guarantee that the software will continue to function in a reliable, resilient, and, importantly, recoverable manner. Ongoing operations and maintenance, including addressing of the incidents impacting the software and patching the software to mitigate its chances of being exploited by hackers and malware threats. Finally, there is a need to identify the software and conditions under which the software needs to be disposed of or replaced because insecure and improper disposal procedures can and often have had serious security implications.

We're gonna cover the security aspects that a CSSLP needs to bear in mind when dealing with the final stages of the software development life cycle, comprising deployment, operations, maintenance, and, ultimately, the disposal of the software. Understanding the importance of this process, being familiar with secure startup or bootstrapping concepts, knowing how to harden the software and the hardware to assure trusted computing as the result, being familiar with the configuration management concepts and how they impact the security of the software, understanding the importance of continuous monitoring, understanding the need to determine the root cause of problems that arise in software as part of problem management, and knowing how patching can affect the state of software security.

About the Author
Avatar
Ross Leo
Instructor
Students
5501
Courses
75
Learning Paths
17

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