Secure Software Design Study Guide - C706

Confidentiality - Information is not made available or disclosed to unauthorized individuals, entities, or processes. Ensures unauthorized persons are not able to read private and sensitive data. It is achieved through cryptography. Integrity - Ensures unauthorized persons or channels are not able to modify the data. It is accomplished through the use of a message digest or digital signatures. Availability - The computing systems used to store and process information, the security controls used to protect information, and the communication channels used to access information must be functioning correctly. Ensures system remains operational even in the event of a failure or an attack. It is achieved by providing redundancy or fault tolerance for a failure of a system and its components. Ensure Confidentiality - Public Key Infrastructure (PKI) and Cryptography/Encryption Ensure Availability - Offsite back-up and Redundancy Ensure Integrity - Hashing, Message Digest (MD5), non repudiation and digital signatures Software Architect - Moves analysis to implementation and analyzes the requirements and use cases as activities to perform as part of the development process; can also develop class diagrams. Security Practitioner Roles - Release Manager, Architect, Developer, Business Analyst/Project Manager Release Manager - Deployment Architect - Design Developer - Coding Business Analyst/Project Manager - Requirements Gathering Red Team - Teams of people familiar with the infrastructure of the company and the languages of the software being developed. Their mission is to kill the system as the developers build it. Static Analysis - A method of computer program debugging that is done by examining the code without executing the program. The process provides an understanding of the code structure, and can help to ensure that the code adheres to industry standards. It's also referred as code review.