Security
Security principles for evidence-first RCA.
This page stays deliberately practical: scoped access, data boundaries, evidence handling, secrets, audit trail, least privilege, and deployment-specific isolation.
No unsupported compliance or infrastructure promises are added here.
Principles ledger
Boundary first, claim second.
01
Scoped access
What it means
Agents should reach only the evidence path needed for a specific service, provider, cluster, or incident question.
What is not claimed
This is not framed as broad unsupervised access to every customer system.
02
Data boundaries
What it means
Useful RCA data is incident-focused: alerts, telemetry, deploys, provider state, affected scope, hypotheses, validation checks, and action notes.
What is not claimed
This does not define a full data-retention or archival policy.
03
Logs and evidence
What it means
Signals that support a cause should sit beside signals that still need validation so responders can inspect the RCA.
What is not claimed
This does not claim that every log source is automatically connected.
04
Secrets
What it means
Credential and secret paths are deployment-specific and should be scoped to the systems needed for RCA.
What is not claimed
This does not declare a universal secret-storage model.
05
Audit trail
What it means
The RCA flow should preserve ownership, validation steps, rollback candidates, mitigation notes, and handoff-ready summaries.
What is not claimed
This is not a replacement for a customer audit platform.
06
Least privilege
What it means
Agents query the MCP Servers and provider APIs needed for a specific incident path, then return consolidated evidence.
What is not claimed
This does not claim unrestricted provider or cluster permissions.
07
Deployment-specific isolation
What it means
OpsDiag is positioned as deployed close to the customer environment, with isolation details defined per deployment.
What is not claimed
This does not claim a fixed private-cloud or compliance model.
Explicitly not claimed
Security copy stays tied to the product facts.
No certification status is claimed.
No universal retention policy is claimed.
No fixed private-cloud model is claimed.
No universal encryption architecture is claimed.
No unrestricted provider or cluster access is claimed.
Scope
Incident-scoped access
Access should be described in relation to the systems required for a specific incident path.
Evidence
Reviewable analysis
RCA output should keep supporting signals and missing validation visible instead of hiding uncertainty.
Deployment
Defined per environment
Exact controls for secrets, retention, isolation, and audit details should be defined per customer deployment.