Read-only access, secrets in Azure Key Vault, no agents, and strict isolation between customers.
Read-only access
KloudRecon needs only the built-in Reader role. Reader cannot create, change or delete resources, and cannot read secrets, keys, app settings or data inside your services. If we detect write permissions on the app you connect, we tell you and explain why you should remove them.
Secrets stay in Key Vault
The client secret you provide is stored only in Azure Key Vault and accessed with a managed identity. Our database keeps the secret name, never the value. After saving, the secret is write-only: it is never shown again and never written to logs.
Metadata, not your data
We collect resource metadata and configuration, metrics, and cost data. We never read data-plane content such as files, blobs, database rows, messages or secrets.
Tenant isolation
Every query is scoped to your organization, and PostgreSQL row-level security enforces the same boundary a second time in the database. Automated tests check this boundary before every release.
Encryption and transport
All traffic uses HTTPS with HSTS. Data is stored on encrypted Azure managed disks and in Azure Storage with encryption at rest. The database accepts only local connections from the application host.
Passwordless sign-in
You sign in with a one-time code sent to your email, or with your Microsoft or Google account. Codes expire quickly and are rate limited. Every new organization is reviewed by our team before it can connect Azure.
Audit trail
Sensitive actions — connections, secrets, roles, invitations, approvals and exports — are written to an audit log that your administrators can review.
Deletion on request
Deleting a connection deletes its secret and its data. Deleting your organization purges all of its data within 30 days.
Partner sign-in, read only
CSP and MSP partners sign in with their Partner Center account and multi-factor sign-in. KloudRecon asks Microsoft only for read access, keeps the sign-in in Azure Key Vault, and never buys, cancels or changes a subscription or licence. Customers never see their partner’s cost or margin.
Sealed server output
The optional Windows and Linux health scripts are read-only and can be read line by line. Their result is encrypted on the server for KloudRecon only, and each script belongs to one server and expires after 90 days.
AI that can only read
AI features are optional. The assistant uses read-only tools, names and IP addresses can be masked, every number in an answer is checked against your data, and AI text is always labelled as such.
Secure engineering
Before a release, dependencies are checked for known vulnerabilities and the automated test suite runs. Every deployment is health-checked and rolled back automatically if the check fails.
Source code
Read the code that reads your Azure
KloudRecon’s source code is published on GitHub. Your security team can see how it is built before you connect anything, and you can run it yourself for noncommercial use.
Free for personal use, study, research and hobby projects
Free for charities, schools, public research and government bodies
Business use needs a KloudRecon plan or a commercial licence from KloudSchool
Compliance
Compliance mapping
Every check belongs to the KloudRecon Azure Baseline, our own controls built on Microsoft’s public guidance: the Microsoft cloud security benchmark, the Azure Well-Architected Framework and the Azure service security baselines. Each check cites the Microsoft Learn page it is based on and is tested with passing and failing examples. The same checks are mapped to control IDs of MCSB, ISO/IEC 27001, NIST SP 800-53, PCI DSS, SOC 2 and HIPAA to help you prepare for audits, with the share of each framework that needs manual evidence shown next to the result.
Mapping is not certification. KloudRecon does not certify your environment or issue an audit opinion. KloudRecon is an independent product of KloudSchool. It is not affiliated with, sponsored, endorsed or certified by Microsoft or by any standards body.