rodrigo.pace/oracle-deep-data-security-lab
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify view bypass lab access paths
Some checks failed
Repo Quality / structure (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Rodrigo
2026-05-18 12:29:10 -03:00
parent 1d11986e94
commit 033d5e9456
5 changed files with 42 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
scenarios/04-view-bypass-mac/evidence/expected-results.md
View File

@@ -1,6 +1,13 @@
# Expected Results
## Before Oracle Deep Data Security
- Direct table access can return accounts owned by other users.
- The legacy view returns only the current user's account because it contains the intended owner filter.
- The control depends on users and tools using the correct access path.
## After Oracle Deep Data Security
- The base table returns only the account owned by the current end user.
- The view returns the same restricted rows.
- The broad view data grant does not bypass the base table policy when MAC is enabled.
- Direct table access no longer bypasses the base table policy when MAC is enabled.