![]() |
NoteThis documentation is relevant only to Cloud Risk Management standalone customers.
|
User Access
User Role
|
Can Access
|
![]() |
|
![]() |
|
![]() |
|
![]() |
|
![]() |
Content
Cloud Risk Management offers a multi-cloud subscription-based
service to our customers.
AWS
- Select the AWS Accounts tab
- Click on the Cancel button to remove an AWS account.
- Click on the Add an account button to add an AWS account to Cloud Risk Management.
Azure
- Select the Azure Subscriptions tab
- Click on the Cancel button to remove an Azure account.
- Click on the Add a Subscription... button to add an Azure account to Cloud Risk Management.
Google Cloud
- Select the GCP Projects tab.
- Click on the Delete button to remove a GCP account.
- Click on the Add a GCP Project button to add a GCP account to Cloud Risk Management.
View Account Size
Enable Users to Search and View Accounts by Account ID
- From the Subscription page, toggle the On/Off button next to View and Search Cloud Account IDs in account menu is enabled to allow your Organization's users to be able to search a Cloud Account by its ID in the Account menu on the Dashboard.
- Once you've enabled this option, your users will be able to enter an Account ID in the Search Box in the Accounts menu and search for an account.
Account Usage and Billing
Trend Vision One – Cloud Risk Management Pay-As-You-Go billing allows
customers to use Cloud Risk Management on a
consumption basis, growing their usage alongside the growth of their cloud
environment.
Pay-As-You-go is beneficial to customers:
- who want to pay on a month-to-month basis through the AWS Marketplace
- are likely to grow their cloud environment throughout the contract period and want to pay for usage on a pro-rata basis
- are not able to predict their spending for an entire contract period
- who want the flexibility to use any Trend Vision One service and change their usage of each service throughout the contract period
Cloud Risk Management Pay-As-You-Go billing uses per account
pricing, based on the size of the account. It is determined by the number of
resources scanned within an account per hour.
Billing Dimensions
|
Examples
|
Cost (in USD )
|
Small sized cloud account – typically dev or test
|
AWS and Azure: Accounts with less than 1,000 resources
|
$0.07/account
|
Medium sized cloud account – typically staging or production
|
AWS and Azure: Accounts with 1,000 – 5,000 resources
|
$0.29/account
|
Large sized cloud account – typically large production
accounts
|
AWS and Azure: Accounts with 5,000+ protected resources
|
$0.35/account
|
FAQs
Q: How can I see what size my accounts are? A:
- Add your account to Trend Vision One - Cloud Risk Management
- Go to Administration.
- Click on Subscriptions to view all your accounts with their sizes.
Q: How does the system know the number of resources in my accounts?
A: Each time the Compliance scan scans an account, it runs its rules engine against the resources within the account
for misconfigurations. This process produces an updated resource count which determines
the account size.
Q: How frequently is my usage metered?
A: Every hour (24/7) a usage service reports on the number of protected accounts a
customer has, including which size tier the account is based on the resource count
of the last Compliance scan scan.
Q: What’s the definition of a resource?
Any infrastructure component that is used to host, process or store your data or applications
is called a Resource. Cloud Risk Management scans resources when checking for misconfigurations in cloud services. We count all
individual resources as a part of consumption pricing.
Below are some examples of resources;
- ebs-snapshot
- sqs-queue
- ec2-accountattribute
- ec2-instance
- ec2-networkinterface
- iam-credentialreport
- iam-policy
- s3-bucket
- autoscaling-launchconfiguration
- dynamodb-table
Q: Do all resources contribute to the sizing dimension?
A: The resource count excludes resources ingested from native security services such
as AWS Trusted Advisor and Guard Duty so that customers are only billed for resources
that Cloud Risk Management protects. Cloud Risk Management also excludes resources from services with only a small number of best practice rules.