Improve shared app account scenario
Some checks failed
Repo Quality / structure (push) Has been cancelled
Some checks failed
Repo Quality / structure (push) Has been cancelled
This commit is contained in:
@@ -18,13 +18,27 @@ Show that a shared technical application account should not be the real data aut
|
||||
|
||||
## Before - Vulnerable Environment
|
||||
|
||||
1. Reset the scenario:
|
||||
1. From the repository root, connect as `ADMIN`:
|
||||
|
||||
```bash
|
||||
cd ~/DEEP-DATA-SECURITY/oracle-deep-data-security-lab
|
||||
export TNS_ADMIN=~/DEEP-DATA-SECURITY/wallet-ddslab
|
||||
sql admin@ddslab_tunnel
|
||||
```
|
||||
|
||||
Presenter note: `ADMIN` prepares the lab objects. The risk will be shown later using the shared application account.
|
||||
|
||||
SQLcl note: after running a script with `@file.sql`, do not type `/`. The slash reruns the last command in the SQLcl buffer and can make a successful command look like an error.
|
||||
|
||||
2. Reset the scenario:
|
||||
|
||||
```sql
|
||||
@scenarios/02-shared-app-account/sql/99_reset.sql
|
||||
```
|
||||
|
||||
2. Create the table, data, and technical account:
|
||||
Presenter note: this makes the demo repeatable and removes previous Data Grants or roles.
|
||||
|
||||
3. Create the table, data, and identities:
|
||||
|
||||
```sql
|
||||
@scenarios/02-shared-app-account/sql/00_schema.sql
|
||||
@@ -32,12 +46,38 @@ Show that a shared technical application account should not be the real data aut
|
||||
@scenarios/02-shared-app-account/sql/02_identities.sql
|
||||
```
|
||||
|
||||
3. Simulate an application or API using the `DDS_APP` account to query all orders:
|
||||
Presenter note: `DDS_APP` represents the application connection pool; `alice` and `bruno` represent real business users.
|
||||
|
||||
4. Show all rows and columns as `ADMIN`:
|
||||
|
||||
```sql
|
||||
SELECT order_id, customer_name, region, seller, amount, margin
|
||||
FROM dds_orders
|
||||
ORDER BY order_id;
|
||||
```
|
||||
|
||||
Presenter note: `MARGIN` is commercially sensitive and should not be visible to every seller.
|
||||
|
||||
5. Exit and connect as the shared technical application account:
|
||||
|
||||
```sql
|
||||
exit
|
||||
```
|
||||
|
||||
```bash
|
||||
sql 'dds_app/AppPool#2026Lab!@ddslab_tunnel'
|
||||
```
|
||||
|
||||
Presenter note: this simulates a web app, API, BI tool, or AI service where many users arrive through the same database account.
|
||||
|
||||
6. Simulate an application or API using `DDS_APP` to query all orders:
|
||||
|
||||
```sql
|
||||
@scenarios/02-shared-app-account/sql/04_test_queries.sql
|
||||
```
|
||||
|
||||
Presenter note: before DDS, the database sees `DDS_APP` and the broad SQL returns too much data.
|
||||
|
||||
## Expected Result Before
|
||||
|
||||
- The shared account can see orders from every seller and region.
|
||||
@@ -46,18 +86,74 @@ Show that a shared technical application account should not be the real data aut
|
||||
|
||||
## After - Applying Deep Data Security
|
||||
|
||||
1. Apply data grants by business role:
|
||||
1. Exit and reconnect as `ADMIN`:
|
||||
|
||||
```sql
|
||||
exit
|
||||
```
|
||||
|
||||
```bash
|
||||
sql admin@ddslab_tunnel
|
||||
```
|
||||
|
||||
2. Apply data grants by business role:
|
||||
|
||||
```sql
|
||||
@scenarios/02-shared-app-account/sql/03_data_grants.sql
|
||||
```
|
||||
|
||||
2. Run the same query in the context of `alice` and `bruno`:
|
||||
Presenter note: `seller_role` is limited to the seller's own rows and excludes `MARGIN`; `latam_manager_role` can see LATAM orders with full manager fields.
|
||||
|
||||
3. Test Alice, the sales representative, with a normal business query:
|
||||
|
||||
```sql
|
||||
@scenarios/02-shared-app-account/sql/04_test_queries.sql
|
||||
exit
|
||||
```
|
||||
|
||||
```bash
|
||||
sql 'alice/Welcome1_DDS!@ddslab_tunnel'
|
||||
```
|
||||
|
||||
```sql
|
||||
ALTER SESSION SET CURRENT_SCHEMA = ADMIN;
|
||||
|
||||
SELECT order_id, customer_name, region, seller, amount
|
||||
FROM dds_orders
|
||||
ORDER BY order_id;
|
||||
```
|
||||
|
||||
Presenter note: this is Alice's legitimate workflow. She needs customer, region, seller, and amount to manage her pipeline, but she does not need commercial margin.
|
||||
|
||||
4. Try to force Alice to see `MARGIN`:
|
||||
|
||||
```sql
|
||||
SELECT order_id, customer_name, region, seller, amount, margin
|
||||
FROM dds_orders
|
||||
ORDER BY order_id;
|
||||
```
|
||||
|
||||
Presenter note: this simulates an application bug, abused API endpoint, prompt injection, or AI-generated SQL asking for a sensitive column outside Alice's business role.
|
||||
|
||||
5. Test Bruno, the LATAM manager:
|
||||
|
||||
```sql
|
||||
exit
|
||||
```
|
||||
|
||||
```bash
|
||||
sql 'bruno/Welcome1_DDS!@ddslab_tunnel'
|
||||
```
|
||||
|
||||
```sql
|
||||
ALTER SESSION SET CURRENT_SCHEMA = ADMIN;
|
||||
|
||||
SELECT order_id, customer_name, region, seller, amount, margin
|
||||
FROM dds_orders
|
||||
ORDER BY order_id;
|
||||
```
|
||||
|
||||
Presenter note: Bruno has manager visibility, so he can see LATAM orders and the margin needed for his role.
|
||||
|
||||
## Expected Result After
|
||||
|
||||
- `alice` sees only her orders and does not see `margin`.
|
||||
@@ -76,4 +172,3 @@ Show that a shared technical application account should not be the real data aut
|
||||
- Fine-Grained Data Authorization: https://docs.oracle.com/en/database/oracle/oracle-database/26/ddscg/fine-grained-data-authorization.html
|
||||
- Create Data Grants: https://docs.oracle.com/en/database/oracle/oracle-database/26/ddscg/create-data-grants.html
|
||||
- End-User Security Contexts: https://docs.oracle.com/en/database/oracle/oracle-database/26/refrn/DBA_END_USER_SECURITY_CONTEXTS.html
|
||||
|
||||
|
||||
Reference in New Issue
Block a user