Cloud and Kubernetes integrations
Secorvia connects to four cloud providers and to Kubernetes, always with a credential that can look but not change. Each page below says what Secorvia reads from that integration, what connecting takes, and what it does not do.
Cloud providers and Kubernetes
AWS: connect with an IAM role, which is the recommended route, or an IAM access key. EC2, S3, IAM, RDS, Lambda, EKS and CloudTrail are the services listed on the homepage.
Azure: connect a subscription with a service principal. Azure support is in beta, and the page says what to check on your first scan.
Google Cloud: connect a project with a service account key. GKE, BigQuery, Cloud IAM, Cloud Storage and Cloud Run are the services listed on the homepage.
DigitalOcean: connect with a read-scope API token, with optional keys for Spaces. Droplets, Spaces, Managed Databases and Kubernetes are the services listed.
Kubernetes: register a cluster through an in-cluster collector that reports outbound, or directly with credentials you supply.
What every integration has in common
Cloud posture scanning is agentless, so nothing is installed in your cloud accounts. You create the credential yourself, which means you decide how narrow it is and you can rotate or remove it at any time. Secrets are encrypted before they are stored and are not shown again after you save. Connecting an account starts its first scan, and a finished scan is the milestone to wait for before you read the results.
All of it lands on one security graph, so an attack path can cross providers. The graph and attack paths start on the Starter plan, and the number of accounts you can connect per provider grows with the plan. The pricing page has the numbers, and the security page covers what the connection can and cannot see.
What cannot be connected
Oracle Cloud and Alibaba Cloud accounts cannot be connected. Secorvia does not list them, and this site does not claim coverage it does not have. If your estate includes a provider that is not on this page, the connection guide lists exactly what the product connects to today, and Enterprise plans can ask about custom connectors.
Beyond the clouds
Findings and events also go outward. Notifications reach email, Slack, Microsoft Teams and Discord. Webhooks send selected events to an HTTPS endpoint you run, signed with a secret. API keys let your own tooling read and write through a service identity, and full API access is part of the Growth plan. Infrastructure as code scanning parses Terraform, CloudFormation, ARM, Bicep, Helm and Kustomize, and it is included on every plan.