Cloud cost audit access: least privilege and data boundaries
Published and reviewed: 1 October 2026
Get a quote for my projectA cost audit needs to read billing data and, for some findings, utilization metrics. It never needs to change anything. This guide lists the read-only building blocks on each cloud, the order in which to grant them, and what to settle with your security and data protection leads before the provider receives a single credential.

On this page
If your internal brief is in French, the audit FinOps preparation guide (FR) connects the data request with the agreed diagnosis and handover. Approve access against those deliverables.
Read-only building blocks on each cloud
| Cloud | What to grant | Setup points from the documentation |
|---|---|---|
| AWS | Fine-grained billing, Cost Explorer and Budgets actions; managed policies such as AWSBudgetsReadOnlyAccess and CostOptimizationHubReadOnlyAccess | The legacy aws-portal actions reached end of standard support in July 2023; accounts and organizations created on or after 6 March 2023 already use the fine-grained actions. For a third party, use an IAM role with an external ID condition. |
| Azure | Cost Management Reader at management group, subscription or resource group scope | Enterprise Agreement: the account owner and department admin view-charges settings must be on, set by an enterprise administrator. Microsoft Customer Agreement: the Azure charges policy of the billing profile must be Yes, set by a billing profile owner. Billing account access can take up to 30 minutes. Cross-tenant access has limited support and can return Access denied. |
| Google Cloud | Billing Account Viewer for cost and pricing information; Billing Account Costs Manager only if the provider must manage budgets or the export | Costs Manager does not cover pricing data export. Access to a BigQuery export dataset is granted on the dataset, separately from the billing role. |
Ask the provider for the exact role names or action list it needs, then compare with the table. Anything beyond read access to cost data needs a written reason.
External IDs for third-party roles on AWS
When a provider assumes a role in your account, AWS recommends an external ID in the trust policy to prevent the confused deputy problem, where another customer of the same provider could trick it into acting on your account. The value is generated by the provider, is unique per customer and is not chosen by you. You add it as an sts:ExternalId condition on the role's trust policy. If a provider asks for a role ARN only, ask why there is no external ID.

Billing read access does not include usage findings
Rightsizing and idle-resource findings rely on utilization data that billing roles do not expose: CloudWatch metrics behind AWS Compute Optimizer, Azure Advisor recommendations, Cloud Monitoring and Recommender on Google Cloud. Treat these as a second grant, limited to the accounts or projects where a finding is planned. On AWS, organization-wide Compute Optimizer results require the management account to opt in, which is a decision for your cloud platform team rather than something to hand to the provider.
Prefer a data copy to live access
Four tiers, from least to most exposure:
- Scheduled export copy: cost and usage exports delivered to a storage bucket or BigQuery dataset that the provider reads. No access to your resource APIs.
- Billing console read: cost analysis and commitment views, for the billing scopes in the engagement.
- Metrics and inventory read: on named accounts or projects, for a fixed period.
- Anything that writes, or owner-level roles: not part of an audit. Changes are made by your team under your change process.
Start at tier 1 and move up only for an identified finding.
Personal data and the contract
Billing exports hold account identifiers, resource names and tags. Some organizations put customer names or staff emails in those fields. Whether yours do is a fact to check, because if personal data is present, the provider processes it on your behalf and the GDPR requires a written contract under Article 28 covering documented instructions, confidentiality, security measures, sub-processors and deletion or return at the end. The EDPB guidelines on controllers and processors explain the roles. If the export holds no personal data, a confidentiality clause still applies to commercial information such as rates and volumes.
Also ask where copies are stored, and in which country the provider's staff will read them.
Need an access plan written for your own clouds? Request a quote for this review.
Lifecycle checklist
- Name a business owner and a security approver for the access.
- List each role or policy, its scope and the reason it is needed.
- Write an end date in the access ticket before granting anything.
- Collect the provider's principal, account or service identity, and the external ID on AWS, through a channel that is not the quote form.
- Review the cloud audit log for actions by the provider's identity at mid-point and at the end.
- At the end: remove the role or trust, revoke dataset and bucket shares, and obtain written confirmation that local copies are deleted or returned.
What to refuse
- Passwords, access keys or tokens sent by email or in a web form.
- Root, Owner or global administrator accounts shared for convenience.
- Open-ended access with no end date.
- Write permissions justified as a time saver.
Official sources
Official documentation used for this page.
- docs.aws.amazon.com/cost-management/latest/userguide/billing-permissions-ref.html
- docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html
- docs.aws.amazon.com/compute-optimizer/latest/ug/what-is-compute-optimizer.html
- learn.microsoft.com/en-us/azure/cost-management-billing/costs/assign-access-acm-data
- docs.cloud.google.com/billing/docs/how-to/billing-access
- www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-072020-concepts-controller-and-processor-gdpr_en
Access and data handling questions
Does read only mean the data is public?
No. Billing detail exposes commercial information and identifiers. Scope data handling, recipients and retention as well as permissions.
Can we put credentials in the quote form?
No. Describe the need without access material. Agree a scoped authorization mechanism after you have selected and contracted a provider.
Who creates the external ID on AWS?
The provider. AWS documents it as a value unique to each customer and controlled by the provider. You add it to the role's trust policy as an sts:ExternalId condition.
Continue your review
- FinOps consulting: cloud cost review and implementation scope
- Request a scoped FinOps quote
- How your request is handled: from enquiry to proposal
- AI cloud cost optimization consulting: audit tokens and GPUs
- FinOps KPIs: prove realized savings and business value
- Rightsizing and idle resources: plan a controlled cost review
Request a quote for my project
Describe your project in a few lines and receive a quote from a specialist.
Request my quote