Diagnostic access is limited to sample or read-only data.
Where possible the diagnostic uses sample, anonymized or read-only sources. Approving the diagnostic does not approve write access to production. Those are two separate decisions.
InfoSec appendix
Security and data-handling posture for the review path.
A review-ready appendix for IT, InfoSec, procurement and operations, to read before approving a diagnostic or any later technical validation.
For operations teams
Wherever possible, we begin with sample or read-only data. Your team decides what is shared, where it is processed and who can access it, and no live system action is approved as part of the review.
Customer systems remain under customer control.
Customer teams approve the systems in scope, the credentials, the retention, the deletion date, and whether the analysis must stay inside their environment.
Evidence requirements at every phase.
Recommendations, approvals, actions and recovery records should all be captured before you move from understanding the work (Observe), to suggesting without acting (Shadow), to a person approving each action (HITL), or to proven routine actions running within agreed limits (Autopilot).
Data handling by phase
| Area | Diagnostic default | Before production validation |
|---|---|---|
| Data scope | Limited samples, time-boxed extracts, or anonymized records where the pattern remains valid. | Named systems, fields, residency needs, masking rules, and retention period approved by customer IT. |
| Access | Read-only access or customer-provided files for the diagnostic question. | Least-privilege service identities, customer-managed secrets, owner, expiry, and revocation path. |
| Auditability | Workshop artifacts, assumptions, and recommendation packet. | Required input, rules evaluated, operating-limit result, approval, final action, and documented recovery or escalation evidence. |
| Regulated workflows | DPDP-aware and customer-policy led review language. | Keep sensitive execution inside the customer environment unless IT approves another path. |
Phased trust
Four-stage progression of system responsibility.
- ObserveUnderstand the workInspect samples, logs and process records without changing a single customer system.
- ShadowRecommendations without executionMeasure suggestions against the team's real decisions and see exactly where the two disagree.
- Human approvalSupervisor approval of each actionSupervisors approve, edit or reject each prepared action before it runs.
- Controlled automationAutomation of proven categoriesOnly customer-approved action categories may run automatically after the operating limits, monitoring and response procedures are agreed and tested.
Review agenda
Questions for IT review
- Which systems and datasets are in scope for the first diagnostic?
- Can sample or anonymized data answer the operating question?
- Where should credentials and secrets be managed?
- What audit destination, retention period, and deletion confirmation are required?
- Which performance measure, threshold, recovery owner, escalation owner, and monitoring owner are required before controlled automation?