Security Policies and Regulations
The course is part of this learning path
This course is one of four courses covering Domain 1 of the CSSLP. This course explores the topic of security policies and regulations.
- Obtain a general understanding of security policies, regulations, and compliance
- Understand the legal and privacy issues that these regulations aim to address
- Learn about a variety of security frameworks and standards
- Learn about trusted computed principles and how they underpin security frameworks
- Understand the security implications of acquiring software
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 email@example.com.
So let's take a look at some other legal issues that have regulations around them, and that are talking about information that needs to be protected of various types. Now, these other types of laws enter the picture depending upon the industry that the entity is in. And these deal to a large extent with various forms of intellectual property. Intellectual property in this context includes things such as patents, which grant exclusive rights to their inventor. Copyrights, which grant similar rights to the creators, those that have authored books, written papers, published music. Trademarks, which are exclusive rights given for unique identifiers, such as the logo for almost any product that you care to name. And the trade secrets. These are exclusive rights to cover processes, formulas and other creations by entities and individuals that give them the right and provide commercial advantage in their usage.
Now software is excluded from most of these due to its nature. It is of course a written work and copyrights can and usually are applied. But as a functioning work, no protection may be possible. And the reason for this is really quite straightforward. Developers know that there is always more than one way to construct a program to do a particular job. Witness the idea of database. We have more than a dozen programs out on the market that do this sort of thing, but they each do it in their own unique way.
Now, the idea of a database or a graphics program, or take your pick of various types, they each illustrate that there is more than one way to do something. In the case of a database, a database is a program that captures and holds data for usage. But each one is designed in its own unique way. And what this enables is a copyright for each particular product, trademark for its branding and possible trade secrets for various functions that are included within it that are unique to itself and not something it shares with any other competing product. Copyrights, as I say, can be applied, but in the way that it works, there may be no way to secure, exclusive rights to it. And that makes software, at least in one more way, unique from other types of intellectual property that are subject to different forms and increased protections.
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.