Added Context: topics mentioned but not on the slides
Not from the slides
Everything in the “Added context” column below is general knowledge or comes from your own class notes (
University/Fund. Info security/Chapter 4 (Access Control).md), not from the three decks. Where the slides only name a topic, that is stated. Use this note to know what to ask your lecturer or check in the textbook; do not assume the exam follows it.
Topics the slides name but never explain
| Where named | Topic | Added context (not from slides) |
|---|---|---|
| 03 s.3 (learning objective) | Bloom filters in password management | A Bloom filter is a compact bit array plus several hash functions that tests whether an item is in a set. It can give false positives but never false negatives. In password management it can hold a large dictionary of disallowed passwords so a proactive checker (03 s.20, Concept - Better Passwords) can reject them without storing the whole dictionary. |
| 03 s.2, s.33 | Case study: security problems for ATM systems | No slide covers it. Nothing to add without the textbook; the only ATM mention on the slides is the memory card + PIN example (03 s.22) and the iris application (03 s.32). |
| 04 s.28 (summary) | UNIX traditional and ACL mechanisms, case study | No slides. In UNIX, each file has permissions for owner, group and other (read, write, execute); this matches the owner/group/world classes on 04 s.10. An ACL lists, per object, which subjects have which rights (the column view of the access matrix, Concept - Access Matrix). |
| 05 s.38 (summary) | Statistical database security | No slide. In general it concerns databases that answer only aggregate queries (counts, sums) and the risk of inferring individual values from them; it is a form of the Concept - Inference problem. |
| 03 s.32 | CIN in the iris system | Not expanded on the slide. |
From your class notes (Chapter 4, not on the slides)
| Class note says | Relation to the slides |
|---|---|
| Four access control models: DAC, MAC, RBAC (role-based), RBAC (rule-based, optional) | The slides define only DAC, MAC and role-based (04 s.4-6). Rule-based access control (access decided by rules, e.g. time of day or network location) is the likely meaning of the fourth; confirm with your lecturer. |
| Access rights: read, write, execute, delete, create, search | Matches 04 s.11. |
| Active Directory: a Windows Server software that helps manage access rights | Not on the slides; useful as a real-world example of centralized administration of users, groups and rights. |
| ”To deal with unauthorized access you need access control models related to users and groups; you need a policy” | Matches 04 s.2 and s.4. |
Syntax caveat
- 05 s.24 says the
IDENTIFIED BYclause supplies a password that “must be used to revoke the access rights of this GRANT command”. Treat this as the lecture’s wording (write it that way in an exam); mainstream SQL dialects do not useIDENTIFIED BYthis way inGRANT.
Related: 03 User Authentication - Index, 04 Access Control - Index, 05 Database Security - Index, Past Exam - Question Bank & Style Guide