Onboarding overview
The onboarding process has 7 steps from scope confirmation to final decision. Most pilots complete steps 1–5 within the first week.
Confirm scope
Define the pilot or deployment boundaries before connecting any cloud environment.
- Cloud providers (AWS, Azure, GCP)
- Accounts, subscriptions, or projects
- Regions to include
- Asset limits and environment tiers
- Business-critical systems and crown-jewel candidates
- Pilot success criteria
- Required stakeholders for the review session
Create read-only access
Cloudryption uses read-only access for discovery and analysis. The customer creates an approved role, service account, or equivalent identity with the permissions required for metadata discovery.
Cloudryption does not require production write access for standard platform operation. Permission templates and minimum-privilege reference policies are provided during onboarding.
Connect environment
The customer connects the selected cloud environment to Cloudryption. Cloudryption validates:
- Authentication and credential validity
- Permission coverage for required metadata
- Account and project visibility
- Region visibility within agreed scope
- Scan readiness confirmation
Run first scan
Cloudryption collects cloud metadata and builds the first decision graph. The first scan identifies:
- Assets, identities, and policies
- Exposures and public access points
- Network relationships and paths
- Storage and data classification signals
- Misconfigurations and security control gaps
- Potential attack paths from exposure to sensitive assets
Review results
Cloudryption reviews the first results with the customer. Focus areas:
- Top exposures and public entry points
- Crown-jewel reachability
- Identity risk and blast radius
- Attack paths to sensitive assets
- Risk drivers and root causes
- False positive review and business context enrichment
Generate reports
Cloudryption produces the full report set for stakeholder review:
- Executive report — board-ready risk summary
- Technical report — evidence-backed findings
- Remediation plan — prioritized actions by risk reduction impact
- Risk reduction narrative — before/after exposure estimate
- Annual deployment recommendation
Decide next action
At the end of the pilot, the customer decides:
- Close the pilot (with full report set retained)
- Extend the pilot (15-day extension available under the conversion offer)
- Convert to an annual package
- Expand scope to additional cloud providers or accounts
- Request enterprise terms for custom deployment
Ready to see which cloud risks matter most?
Start with a controlled pilot and receive a board-ready executive report, a technical evidence report, and a prioritized remediation plan.