liveBook · Manning

Mandatory access control

As explained in Grokking Relational Database Design

Mandatory access control is an access-control model in which a central authority assigns fixed classification-based permissions that users cannot override.

Mandatory access control (MAC) protects confidential database information by enforcing fixed, classification-based permissions. A central authority assigns classifications to data and clearance levels to users; mismatches deny access with no exceptions. section 7.4

High school records database

Label tables as sensitive or confidential, then configure which clearance levels may access each label. A user without the matching clearance cannot view, modify, or delete that data. The sensitivity classifications must be configured manually. section 7.4

Keep these practical rules in mind:

  • Treat MAC as strict central enforcement rather than user-controlled permission management. section 7.4
  • Distinguish MAC from role-based access control, which assigns permissions to roles and users to those roles. section 7.4

How Grokking Relational Database Design covers it

How deep it goes
Defines classification-based enforcement and illustrates it with student records, but stops short of implementation commands.
Examples
Uses a high school student-records database with sensitive and confidential table classifications.
What it assumes
Assumes basic awareness of databases and confidentiality while defining access control and classifications in plain language.
What you can do after
Evaluate database access scenarios by matching user clearance levels against data classifications.
How it connects
Connects confidentiality, access control, encryption, databases, and role-based access control.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Relational Database Design. The section links point to the parts of the book it draws on.