You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/wwl/design-responsible-ai-security-governance-risk-management-compliance/includes/8-design-access-controls-ground-data-model-tune.md
+31-59Lines changed: 31 additions & 59 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,116 +10,88 @@ Grounding data is the authoritative information used to produce reliable model r
10
10
11
11
### Key Design Principles
12
12
13
-
**Least privilege by default** - Allow the minimum necessary access for each role, agent, model, or service.
13
+
-**Least privilege by default:** Allow the minimum necessary access for each role, agent, model, or service.
14
14
15
-
**Rolealigned data partitions** - Separate grounding data by function (e.g., customer support, finance, engineering).
15
+
-**Rolealigned data partitions:** Separate grounding data by function (e.g., customer support, finance, engineering).
16
16
17
-
**Clear ownership and stewardship** - Assign accountable stakeholders who govern quality and security of each data domain.
17
+
-**Clear ownership and stewardship:** Assign accountable stakeholders who govern quality and security of each data domain.
18
18
19
-
**Auditability** - All access events and data retrieval operations must be logged and reviewable.
19
+
-**Auditability:** All access events and data retrieval operations must be logged and reviewable.
AI systems retrieve grounding data during search, retrievalaugmented generation (RAG), or context assembly. Each retrieval mechanism must enforce:
44
28
45
-
**Connectorlevel authorization** restricting which data types the model can query
46
-
47
-
**Structured query filtering** preventing models from accessing disallowed fields
29
+
-**Connectorlevel authorization:** restricting which data types the model can query
48
30
49
-
**DLP and sensitivity labeling**applied across all data stores
31
+
-**Structured query filtering:**preventing models from accessing disallowed fields
50
32
51
-
**Regionaligned access rules**ensuring data residency adherence
33
+
-**DLP and sensitivity labeling:**applied across all data stores
52
34
53
-
**Professional Visual: Retrieval Access Flow**
35
+
-**Regionaligned access rules:** ensuring data residency adherence
54
36
55
-
Prompt → Policy Check → Search Index → Sanitization Layer → Model Context Injection
37
+
-**Retrieval Access Flow:**Prompt → Policy Check → Search Index → Sanitization Layer → Model Context Injection
56
38
57
39
## 3. Access Controls for Model Tuning
58
40
59
41
Modeltuning operations—evaluation, supervised finetuning, or reinforcement learning—require elevated permissions. These processes must be insulated from production operations.
60
42
61
43
### Model Tuning Access Requirements
62
44
63
-
Segregated environments for **development, evaluation, and production**
64
-
65
-
Approval workflows for introducing new training datasets
66
-
67
-
Verified data lineage and documentation of tuning datasets
68
-
69
-
Security scanning of all tuning inputs
70
-
71
-
Restricted ability to promote new tuned models into production
72
-
73
-
### Model Tuning Role Matrix (TextBased)
45
+
- Segregated environments for **development, evaluation, and production**
74
46
75
-
Role | Permissions
47
+
- Approval workflows for introducing new training datasets
0 commit comments