DBST 668 is a three-credit graduate course at the University of Maryland Global Campus, with DBST 651 as the prerequisite.
UMGC describes an overview of both the theory and applications of providing effective security in database management systems, with assignments that focus on database security concepts and require a remote access laboratory.
The course sits between database and security study. Students often find it demanding because it asks for precise definitions of access control models and for careful reasoning about how information can leak even when direct access is blocked.
Course at a Glance
| Item | Details |
|---|---|
| University | University of Maryland Global Campus (UMGC) |
| Code and title | DBST 668 Database Security |
| Credits | 3 |
| Prerequisite | DBST 651 |
| Lab | Assignments require use of a remote access laboratory |
| Subject area | Database and information security |
What DBST 668 Covers
| Topic (from UMGC) | In plain language |
|---|---|
| Discretionary access control | Owners grant and revoke privileges to users |
| Mandatory access control | The system enforces rules based on security labels |
| Data integrity, availability and performance | Keeping data correct, accessible and usable under protection |
| Secure database design | Building security into the schema from the start |
| Data aggregation and inference | Preventing sensitive facts being deduced from permitted data |
| Secure concurrency control and transactions | Avoiding leaks through timing and locking behavior |
| Multilevel secure databases | Models for relational and object-relational systems |
Key Concepts Explained
Discretionary Versus Mandatory Control
In discretionary control, a data owner decides who gets which privilege, often with GRANT and REVOKE. In mandatory control, labels such as Unclassified and Secret are attached to users and data, and the system enforces rules the owner cannot override.
Illustrative example: With a "no read up, no write down" style rule, a user cleared to Confidential can read Unclassified and Confidential data, but cannot read Secret rows. Writing down is limited so a user cannot copy Secret content into a lower level.
Inference and Aggregation
Someone may infer a hidden value from permitted queries. If individual salaries are hidden but averages for small groups are allowed, comparing two averages can reveal one person's salary. Controls include minimum group sizes and query restrictions.
Polyinstantiation
In multilevel databases, the same key can have different values at different levels to avoid revealing that a hidden row exists. Know why it helps and what consistency problems it creates.
Typical Assignments and How to Approach Them
| Assignment type | What it tests | How to approach it |
|---|---|---|
| Access control lab | Applying privileges and roles | Plan who needs what, then script grants and test as each user |
| Security custom analysis | Understanding formal models | Define the rules and trace example requests |
| Inference case | Spotting leakage paths | List permitted queries and combine them to see what can be learned |
| Design report | Secure design reasoning | Tie each control to a specific threat |
Where Students Get Stuck
- Mixing models. Keep discretionary and mandatory rules clearly apart.
- Testing only as admin. Always test with the least-privileged user.
- Missing inference paths. Think about combinations of allowed queries, not single queries.
- Vague threats. Name the threat before choosing the control.
Planning Your Work
| Stage | Do this | Output |
|---|---|---|
| Start | Confirm lab access and create test users | Users and roles list |
| Design | Make a privilege matrix | Table of users, objects, rights |
| Test | Try allowed and forbidden actions | Evidence of both outcomes |
| Report | Explain each control | Threat to control mapping |
A privilege matrix is the quickest way to show correct thinking: users or roles down the side, objects across the top, and the allowed operations in each cell.
A Worked Inference Example
Illustrative example: Users may not see individual salaries but may run queries returning the average salary of a department. If a department has one employee, the average is that person's salary. If a department has five and the user can query the average with and without one named employee, the difference reveals that salary. Controls include a minimum group size, limiting overlapping queries, and adding noise.
Use this pattern whenever you are asked to analyze inference: list the permitted queries, combine them, and ask what can now be known that was meant to be hidden. Then propose a control and say what it costs in usefulness.
Also practice a small privilege matrix. Rows are roles such as clerk, manager and auditor; columns are tables; cells list allowed operations. Then write the GRANT statements that implement it and the tests that prove the forbidden cells are really forbidden.
Study Tips for DBST 668
- Learn the formal rules of each model by working small examples.
- Keep a threat list and map every control to a threat.
- Show evidence that denied actions are actually denied.
- Revisit concurrency control from DBST 651 for the secure transaction topics.
How We Help with DBST 668
Send the assignment, lab instructions, rubric and feedback. We can explain concepts, prepare custom worked solutions, or review your own scripts and reports for errors and clarity. We do not log in to lab environments for you.
GradeEssays is independent of UMGC. Our work is a study and reference aid; you complete and submit your own work under UMGC's academic integrity policy. Orders are written from scratch, include free revisions within the scope of your original request, and are refunded in full if late.
Make Sense of Your DBST 668 Work
Share the assignment and your attempt. A database writer prepares a worked model to study and compare with.
Start My DBST 668 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
DBST 651.
Three credits.
Yes, assignments focus on database security concepts and require a remote access laboratory.
DAC lets owners grant privileges; MAC enforces label-based rules set by the system.
Deducing sensitive information from data you are allowed to see.
UMGC says multilevel secure models for both relational and object-relational databases are analyzed.