Capability truth
Trust starts by separating current, limited, planned, and unsupported workflows. Public pages should echo the docs rather than stretch claims for demand generation.
Trustbottom
Last reviewed 2026-06-30
Cloudeval trust, evidence, and product limits
Direct answer
Cloudeval's trust model starts with clear capability boundaries. The product is Azure-first today, documents ARM and Bicep-through-ARM support explicitly, labels AWS CloudFormation template support as beta, links findings back to project/report evidence where available, and tells users not to assume broader AWS, GCP, Terraform, Kubernetes, or compliance-attestation parity.
Evidence truth
Cloudeval should present findings with source, resource, report, timestamp, and project context wherever that evidence exists.
AI truth
AI answers are valuable when grounded in Cloudeval project data. Public pages should avoid implying freeform cloud answers have the same confidence as evidence-backed project answers.
FAQ
Does Cloudeval need broad cloud permissions?
Azure Cloud sync uses service-principal-scoped discovery. Teams should start with the documented Azure permissions path and scope access where appropriate.
Are Cloudeval findings compliance attestations?
No. Security and architecture findings are recommendations and evaluations, not compliance attestations.
