Skip to content

Commit 75d7aff

Browse files
authored
Unit 9 Module 11
1 parent 903c142 commit 75d7aff

1 file changed

Lines changed: 66 additions & 90 deletions

File tree

Lines changed: 66 additions & 90 deletions
Original file line numberDiff line numberDiff line change
@@ -1,180 +1,156 @@
1+
## Overview
2+
13
Audit trails are essential for maintaining trust, compliance, and operational integrity across AIdriven systems. Solution architects must design mechanisms that provide full visibility into _who_ made changes, _what_ changes occurred, and _when_ modifications happened across models, data sources, prompts, configuration objects, and agent workflows.
24

35
This unit provides patterns for building robust auditing capabilities across Azure AI Foundry, model lifecycles, and data governance processes.
46

57
## 1. Purpose of audit trails in AI systems
68

7-
Audit trails help organizations:
9+
### Audit trails help organizations:
810

9-
Track changes to model versions, parameters, training datasets, and evaluation results.
11+
- Track changes to model versions, parameters, training datasets, and evaluation results.
1012

11-
Diagnose issues, anomalies, and regressions.
13+
- Diagnose issues, anomalies, and regressions.
1214

13-
Meet regulatory expectations around transparency and accountability.
15+
- Meet regulatory expectations around transparency and accountability.
1416

15-
Support investigations during incidents and security reviews.
17+
- Support investigations during incidents and security reviews.
1618

17-
Strengthen operational governance by enabling approvals, rollbacks, and lifecycle controls.
19+
- Strengthen operational governance by enabling approvals, rollbacks, and lifecycle controls.
1820

19-
A welldesigned audit system is continuous, immutable, and integrated into the AI platform's control plane.
21+
- A welldesigned audit system is continuous, immutable, and integrated into the AI platform's control plane.
2022

2123
## 2. Audit trail requirements for model changes
2224

2325
### Model lifecycle events that must be audited
2426

25-
Registration of new model versions
27+
- Registration of new model versions
2628

27-
Tuning operations such as finetuning, parameter updates, or evaluation runs
29+
- Tuning operations such as finetuning, parameter updates, or evaluation runs
2830

29-
Promotion of models between dev/test/prod environments
31+
- Promotion of models between dev/test/prod environments
3032

31-
Rollbacks to previous versions
33+
- Rollbacks to previous versions
3234

33-
Deployment actions, endpoint configuration, scaling changes
35+
- Deployment actions, endpoint configuration, scaling changes
3436

35-
Access attempts to model assets, including unauthorized requests
37+
- Access attempts to model assets, including unauthorized requests
3638

3739
### Recommended architectural attributes
3840

39-
Immutable logs
41+
- Immutable logs
4042

41-
Timestamped change records
43+
- Timestamped change records
4244

43-
Rolebased attribution (linked to identity provider)
45+
- Rolebased attribution (linked to identity provider)
4446

45-
JSONstructured logs for machine parsing
47+
- JSONstructured logs for machine parsing
4648

47-
Separation of duties and approval logging
49+
- Separation of duties and approval logging
4850

4951
## 3. Audit trail requirements for data changes
5052

51-
Grounding data, training data, memory stores, semantic indexes, and application logs are core inputs into generative systems. You must audit:
53+
Grounding data, training data, memory stores, semantic indexes, and application logs are core inputs into generative systems.
54+
55+
### You must audit:
5256

53-
Data ingestion events
57+
- Data ingestion events
5458

55-
Schema changes
59+
- Schema changes
5660

57-
Data refresh cycles
61+
- Data refresh cycles
5862

59-
Sensitivity label changes
63+
- Sensitivity label changes
6064

61-
Sanitization or filtering applied
65+
- Sanitization or filtering applied
6266

63-
Data movement across regions
67+
- Data movement across regions
6468

65-
Access attempts and approvals
69+
- Access attempts and approvals
6670

67-
Architects must ensure logs capture _metadata_, not _content_, to avoid unnecessary exposure of sensitive information.
71+
- Architects must ensure logs capture _metadata_, not _content_, to avoid unnecessary exposure of sensitive information.
6872

6973
## 4. Azure AI Foundry controlplane auditing
7074

71-
Azure AI Foundry provides a centralized control plane for model registration, environment configuration, agent deployment, and diagnostic logging.<br>Key audit features include:
75+
Azure AI Foundry provides a centralized control plane for model registration, environment configuration, agent deployment, and diagnostic logging.
76+
77+
### Key audit features include:
7278

73-
### Foundry Activity Logs
79+
#### Foundry Activity Logs
7480

7581
Track administrative actions across workspaces, registries, and deployments. Logs support export to:
7682

77-
Azure Monitor
83+
- Azure Monitor
7884

79-
Log Analytics
85+
- Log Analytics
8086

81-
SIEM tools (such as Sentinel)
87+
- SIEM tools (such as Sentinel)
8288

83-
### Foundry Diagnostics and Tracing
89+
#### Foundry Diagnostics and Tracing
8490

8591
Diagnostics provide traceability of execution across:
8692

87-
Model calls
88-
89-
Pipeline activities
90-
91-
Tool interactions
92-
93-
Failures, latency spikes, or unexpected behavior
94-
95-
### Professional Visual (Textbased Diagram)
96-
97-
+-----------------------------+
98-
99-
| Foundry Control Plane |
100-
101-
+-----------------------------+
102-
103-
| Activity Logs
104-
105-
| Diagnostics
106-
107-
v
108-
109-
+-----------------------------+
110-
111-
| Azure Monitor / Sentinel |
112-
113-
+-----------------------------+
114-
115-
| Insights | Alerts
116-
117-
v
93+
- Model calls
11894

119-
+-----------------------------+
95+
- Pipeline activities
12096

121-
| Audit Dashboards & Review |
97+
- Tool interactions
12298

123-
+-----------------------------+
99+
- Failures, latency spikes, or unexpected behavior
124100

125101
## 5. Designing audit pipelines with tracing
126102

127103
Tracing allows architects to follow execution paths and debug generative AI behaviors. When integrated into audit trails, tracing provides:
128104

129-
Endtoend visibility of model inference
105+
- Endtoend visibility of model inference
130106

131-
Identification of performance bottlenecks
107+
- Identification of performance bottlenecks
132108

133-
Attribution of requests to model versions
109+
- Attribution of requests to model versions
134110

135-
Correlation of user actions to model activity
111+
- Correlation of user actions to model activity
136112

137-
Detection of unusual patterns (loops, excessive token spikes, cascading failures)
113+
- Detection of unusual patterns (loops, excessive token spikes, cascading failures)
138114

139115
### Recommended tracing fields
140116

141-
Correlation ID
117+
- Correlation ID
142118

143-
Model version
119+
- Model version
144120

145-
Input metadata (nonsensitive)
121+
- Input metadata (nonsensitive)
146122

147-
Prompt category or classification
123+
- Prompt category or classification
148124

149-
Response latency
125+
- Response latency
150126

151-
Downstream tool usage logs
127+
- Downstream tool usage logs
152128

153-
Safety evaluation outcomes
129+
- Safety evaluation outcomes
154130

155131
## 6. Designing auditready processes
156132

157133
### Governance workflows to include
158134

159-
**Approval workflows** for promoting new model versions
135+
- **Approval workflows** for promoting new model versions
160136

161-
**Mandatory logging** for all model tuning operations
137+
- **Mandatory logging** for all model tuning operations
162138

163-
**Periodic audit reviews** for drift detection
139+
- **Periodic audit reviews** for drift detection
164140

165-
**Automated evidence collection** for compliance reporting
141+
- **Automated evidence collection** for compliance reporting
166142

167-
**Immutable storage** of audit logs
143+
- **Immutable storage** of audit logs
168144

169145
### Retention policies
170146

171147
Define retention requirements with Legal, Compliance, and Information Security teams.<br>Common patterns:
172148

173-
90 days for lowrisk workloads
149+
- 90 days for lowrisk workloads
174150

175-
12-24 months for regulated workloads
151+
- 12-24 months for regulated workloads
176152

177-
Indefinite retention for incidentrelated archives
153+
- Indefinite retention for incidentrelated archives
178154

179155
## 7. Professional Visual — Audit Trail Architecture
180156

@@ -252,8 +228,8 @@ Indefinite retention for incidentrelated archives
252228

253229
## References
254230

255-
[https://learn.microsoft.com/en-us/azure/ai-foundry/control-plane/overview?view=foundry](/azure/ai-foundry/control-plane/overview)
231+
- [https://learn.microsoft.com/en-us/azure/ai-foundry/control-plane/overview?view=foundry](/azure/ai-foundry/control-plane/overview)
256232

257-
[https://learn.microsoft.com/en-us/training/modules/tracing-generative-ai-app/](/training/modules/tracing-generative-ai-app/)
233+
- [https://learn.microsoft.com/en-us/training/modules/tracing-generative-ai-app/](/training/modules/tracing-generative-ai-app/)
258234

259-
[https://learn.microsoft.com/en-us/training/modules/azure-ai-foundry-secure-environment/enable-foundry-diagnostics](/training/modules/azure-ai-foundry-secure-environment/enable-foundry-diagnostics)
235+
- [https://learn.microsoft.com/en-us/training/modules/azure-ai-foundry-secure-environment/enable-foundry-diagnostics](/training/modules/azure-ai-foundry-secure-environment/enable-foundry-diagnostics)

0 commit comments

Comments
 (0)