See what to fix first in one of your cloud accounts.
We scan one cloud account once, through read-only cloud roles, and walk you through what we found. There is no charge and no commitment. You keep the findings report.
What the scan covers
- Posture scanning (CSPM) of one cloud account, subscription or project, through read-only cloud roles
- Identity and data views from the same scan: who can reach what, and where sensitive data appears to sit
- Attack paths: the routes an attacker could take to reach what matters
- Mapping of findings to the compliance frameworks you name, from the 78 Onam maps to
What it does not cover
- Agentless workload scanning. It runs inside your account and creates short-lived scan resources there, so it needs more than read access. We add it only if you ask and agree in writing.
- Code repositories, SaaS platforms and any other cloud accounts
- Reading data contents. Data is labelled from metadata only (store names, tags, column names); Onam never opens a file or reads a row.
- A compliance verdict. Framework mapping says which findings map to which controls; it is not a certification.
What you receive
Every risk ranked, with the exact setting and its fix, and a fix order for this week, 30 days and 90 days. You keep the report.
How two or more findings combine into a route, and which single fix breaks it. Routes are worked out from configuration, not tested.
Who can reach what, and where sensitive data appears to sit, from metadata.
For the frameworks you name. Controls with no automated check are marked for manual review.
Plus a 45-minute readout with your team and a short written summary of the top items. Dollar figures in the report are loss estimates per finding, used for ranking. They are not a price for a whole route, and not predictions. Want to see the format first? Ask us for the sample report, built from a test environment, when you send the form.
What access we need
You run a template we give you, in your own account. Posture scanning connects through read-only cloud roles and changes nothing in your cloud. For Kubernetes, we agree access at the scoping call.
| Cloud | What you create | Access level | Why we need it |
|---|---|---|---|
| AWS | An IAM role that Onam assumes with an External ID | AWS-managed SecurityAudit and ReadOnlyAccess policies | To read how services are configured. Onam stores no secret for AWS; it assumes your role. |
| Azure | Role assignments for Onam's service principal | Reader and Storage Blob Data Reader | To read configuration, and to find where sensitive data lives |
| Google Cloud | A service account | Viewer, Cloud Asset Viewer, Security Reviewer | To read configuration and asset lists |
| Oracle Cloud | A dedicated user and group | read policies across the tenancy | To read configuration, identity and key settings |
| Alibaba Cloud | A dedicated RAM user | A dedicated read-only RAM policy | To read configuration |
| IBM Cloud | A service ID | Viewer-level access, scoped to a resource group | To read configuration |
How it works
- 1Send the form
Tell us which cloud and roughly how big the account is. Anup, our founder, replies within one working day.
- 230-minute scoping call
We agree the account, what is in scope, the frameworks to map to and who sees the results. We can sign a mutual NDA first.
- 3You run our template
You deploy a template in your own account. You can read every permission before you deploy it. We confirm the connection works.
- 4The scan runs once
How long it takes depends on how much runs in the account, so we do not promise a time. We tell you when it has finished.
- 545-minute readout
We go through the top items, the attack paths and the framework mapping with your team. The report and a short summary follow.
- 6You decide
Stop, or talk about a 60-day pilot. If you stop, you remove the role and we deactivate the account.
How we handle your data
- What Onam reads: configuration and metadata from the connected account.
- What Onam stores: configuration and metadata, findings, and the asset and attack-path graph.
- Credentials: where a cloud needs a stored credential (for example Oracle Cloud or Alibaba Cloud), it is kept in AWS Secrets Manager and encrypted with AWS KMS. For AWS, no secret is stored.
- Encryption: encrypted at rest; encrypted in transit for all customer-facing and service-to-service traffic, with one internal job being moved to TLS.
- Hosting region: agreed with you at the scoping call.
- Who sees the results: only the named people agreed at scoping.
- Retention: after the readout we deactivate the account. Your data is kept for 30 days after deactivation, then deleted.
- Ending access: remove the role or service account at any time. That stops all access at once.
More detail in the Trust Center.
After the readout
If both sides want to continue, the next step can be a 60-day pilot on the accounts you choose, measured against success criteria you write before it starts. If not, you remove the role and that is the end of it.
We are taking up to 10 design partners: a pilot, a first-year price in return for honest feedback and, if it works, a reference. Ask us.
Prefer a conversation first? Request a demo or see pricing.