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

Normalize lab docs and keep reusable TNS alias
Some checks failed
Repo Quality / structure (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Rodrigo
2026-05-18 11:30:35 -03:00
parent b8d6de0fb5
commit 2188ea8e58
17 changed files with 67 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
scenarios/01-ai-prompt-injection/README.md
View File

@@ -23,7 +23,7 @@ After Oracle Deep Data Security is enabled, the database enforces data grants on
Run shell commands from the repository root:
```bash
cd ~/DEEP-DATA-SECURITY/oracle-deep-data-security-lab
cd <repo-root>
```
Connect with SQLcl:
@@ -171,3 +171,6 @@ Oracle Deep Data Security reduces the risk of AI prompt injection and overprivil
See [RUNBOOK.md](RUNBOOK.md) for deeper technical notes, expected evidence, and official Oracle documentation references.
For a LiveLabs-style guided workshop, use [WORKSHOP.md](WORKSHOP.md).
Connection alias note: ddslab_tunnel is the TNS alias configured in the wallet `tnsnames.ora` for this lab. If your wallet uses another alias, replace ddslab_tunnel with your own service alias.