In this final section of Module 08, we examine relational databases. As touched on in the previous section, this database model is based on tables which are comprised of rows and columns. In turn, tables in the relational model are related to one another via columns that they have in common. This allows for pulling information from many combined tables. We discuss tables and liken them to a storage shelf where like items are grouped. An example is a customer table that holds information associated with customer accounts. The principle of normalization is then discussed. This process assures that there are no duplicates in the table. We also introduce the primary key which uniquely identifies every record in a table. It's noted that good database design utilizes the principle of normalization along with entity integrity which dictates that the primary can never be null (empty). We conclude with a discussion of how a key from one table is linked to one in another table. This is the feature that puts the "relational" in the relational model. The principles of a one-to-many relationship, cardinality, degree, tuples, and database schema and design conclude the video.
They are responsible for knowing where a network's possible vulnerabilities are and providing mitigation strategies to combat them. An effective Cyber Security Operations Manager will have experience in a technical security role including ...