Security
How TruCost.Cloud protects customer data, what we access in your cloud accounts, and how to report a vulnerability
1. Certifications
CLOUD TRUCOST (OPC) PRIVATE LIMITED is certified to two standards. Both certificates cover the FinOps platform and FinOps consulting services.
- ISO/IEC 27001:2022 (information security management system). Certificate IN/85728342/4968.
- ISO 9001:2015 (quality management system). Certificate IN/45128341/9684.
Both were issued by ICV Assessments Pvt. Ltd. on 17 October 2026 and are valid until 16 October 2029, subject to annual surveillance audits. They can be verified with the certification body at icvassessments.com.
On request we share the certificates, provide a Data Processing Addendum and complete customer security questionnaires. Write to security@trucost.cloud.
2. What We Access in Your Cloud
We read billing and usage data (the AWS Cost and Usage Report and the equivalent Azure and Google Cloud billing exports) and resource metadata such as instance types, sizes, tags and utilisation metrics.
For AWS, access is through a cross-account IAM role that you create in your own account from our CloudFormation template. The role is protected by an external ID that is unique to each customer. We do not store AWS access keys or passwords for your accounts.
- The role cannot create, change or delete your workloads. Its only write permission is to set up and maintain the billing data export the service reads.
- You choose the level of read access when you create the role: the AWS-managed
ReadOnlyAccesspolicy, or a scoped policy limited to billing, commitments, optimisation recommendations and resource descriptions. - The template is plain text. You can review every permission before you deploy it.
- You can end our access at any time by deleting the role or the stack.
We use this access for cost analysis only. We do not read the contents of your applications, databases or storage.
3. Hosting and Data Location
The service runs on Amazon Web Services in the Mumbai region (ap-south-1). Customer data is stored in that region.
Databases are not reachable from the public internet.
4. Customer Isolation
Each customer workspace has its own database schema and its own query workspace. Application access is scoped to the workspace of the signed-in user.
5. Encryption
Data at rest is encrypted. Databases and object storage use AWS-managed encryption keys through AWS KMS and S3 server-side encryption.
Traffic between browsers or API clients and the service uses TLS 1.2 or higher.
6. Access Control
- Single sign-on (SAML) is available.
- Role-based access control, with custom roles.
- API keys are scoped and can be revoked.
- Outgoing webhooks are signed.
- Sign-in is rate limited.
7. Audit Trail and Logging
Administrative and security-relevant actions in the application are recorded in an audit log.
Administrative activity in our own AWS account is recorded by AWS CloudTrail, with log file integrity validation.
8. Backups
Databases are backed up daily with 7 days of point-in-time recovery, and deletion protection is enabled.
9. Secure Development
Automated tests run on every change. Third-party dependencies are checked for known vulnerabilities, and the source code is scanned for leaked credentials.
10. Data Handling and Sub-processors
We process billing and usage data and user account details (name and work e-mail). We do not need the content of customer workloads to deliver the service.
Amazon Web Services is our infrastructure provider. The current list of sub-processors is shared with customers on request.
Data is deleted after the contract ends, in line with the customer agreement. The privacy policy has the details. For data requests, write to privacy@trucost.cloud.
11. Security Incidents
If we confirm a security incident affecting customer data, we notify affected customers without undue delay, as set out in the customer agreement.
12. Reporting a Vulnerability
If you believe you have found a security vulnerability in the TruCost.Cloud website or platform, write to security@trucost.cloud. We acknowledge reports within 2 business days and aim to give a first assessment within 5 business days.
What to include
- A description of the issue and its impact.
- The exact URL or API endpoint affected.
- Steps to reproduce it, with a proof of concept where possible.
Please do not include customer data or screenshots of real accounts.
Scope
In scope: trucost.cloud and its subdomains, the TruCost.Cloud application and its API.
Out of scope:
- Denial-of-service attacks, spam and automated high-volume scanning.
- Social engineering or phishing of our staff or customers.
- Physical attacks.
- Services run by third parties that we do not control.
- Reports with no security impact, such as missing headers with no working exploit or software version banners.
Good-faith research
- Test only with accounts you own or have permission to use.
- Do not view, change or delete data that is not yours. If you reach such data, stop and tell us.
- Give us reasonable time to fix the issue before you disclose it publicly.
We will not take legal action against good-faith research that follows these rules. We will tell you when the issue is fixed.
We do not run a paid bounty programme.
13. Contact
Security contact: security@trucost.cloud