Billing Items

(Mandatory) Edition

Billing factors: the service edition and quota. Different editions provide different functions.

Yearly/Monthly and pay-per-use billing

• Yearly/Monthly billing: (Service edition + Quota) x Required duration
• Pay-per-use billing: (Service edition + Quota unit price) x Billing duration

Quota (mandatory)

Value-added package (optional)

Large screen

SecMaster large screen can display security analysis results on a large screen, making it easier for you to obtain better demonstration effects for some scenarios such as onsite presentation, reporting, and real-time monitoring.

Billing factors: security situation metrics on large screens.

Yearly/Monthly and pay-per-use billing

• Yearly/Monthly billing: Unit price of large screen security situation metrics x Required duration
• Pay-per-use billing: Unit price of large screen security situation metrics x Billing duration

Log audit

If you need to use security data collection, security data retention, and security modeling analysis, you can buy them separately.

Billing factors: security data collection volume, security data retention volume, and security modeling analysis volume.

Yearly/Monthly and pay-per-use billing

• Yearly/Monthly billing:

  Unit price of the security data collection package x Required duration

  Unit price of the security data retention package x Required duration

  Unit price of the security modeling analysis package x Required duration

• Pay-per-use billing:

  You are billed for the actual log data volume collected for you.

  You are billed for the actual log data volume stored for you.

  You will be billed for the actual log volume for security modeling analysis.

Security orchestration

Security orchestration can help you handle and investigate incidents automatically. You can buy security orchestration separately.

Billing factor: You will be billed for the total number of times workflow nodes are executed during playbook execution. Note that this includes each execution of the start and end nodes, but excludes judgement nodes.

Yearly/Monthly and pay-per-use billing

• Yearly/Monthly billing: Security orchestration analysis times/day x Required duration
• Pay-per-use billing: You will be billed for the total number of times workflow nodes are executed during playbook execution. Note that this includes each execution of the start and end nodes, but excludes judgement nodes.

Purchase

• The standard and professional editions provide a value-added package (including large screen, log audit, and security orchestration) at extra cost. To buy and use these functions, buy the standard or professional edition first.

Billing

Value-added packages are billed separately. There is no impact on the service edition and quota you have purchased.

Free quotas

A certain free quota is offered for log audit and security orchestration in the value-added package. Table 3 shows details about free quotas.

If the free quotas cannot meet your business needs, you can enable corresponding functions in the value-added packages separately.

Use

If you purchase yearly/monthly security data collection, security data retention, security modeling analysis, and security orchestration packages, there are some limitations you need to know. The details are as follows:

• Security data collection, security data retention, and security modeling analysis resource packages:
  • The quotas of security data retention, security modeling analysis, and security data collection packages can be counted together. However, these packages cannot cover what you used before the purchase. Subscriptions to these packages cannot be cancelled.
  • For yearly/monthly security data collection, security modeling analysis, and retention packages, data volume in excess of the package quotas will be billed on a pay-per-use basis.
  • Pay-per-use resources will not be disabled automatically even if yearly/monthly security data retention, security modeling analysis, and security data collection packages expire. They will always be enabled on a pay-per-use basis.

    For yearly/monthly security data collection package, data volume in excess of the package quota will be billed each day on a pay-per-use basis.

    For example, a user purchases a security data collection package with 5 GB/day/quota for one month. If the user uses 5 GB data collection before 22:00 on the purchase day, and then uses 2 GB data collection between 22:00 00 and 24:00, the extra 2 GB will be billed on a pay-per-use basis. Starting from 00:00 on the next day, a 5 GB/day/quota is available to the user again.

  • You can use the packages immediately upon purchase.
  • The quotas from your security data collection, security modeling analysis, and security data retention resource packages can be pooled. Usage is deducted first from the package that expires the earliest. Note that quotas cannot be shared across regions or applied retroactively to prior usage. Quota deductions may appear up to 4 hours after actual use.

• Log audit and security orchestration:
  • Log audit: You will be billed for data volume you specify. If the quota for log audit (security data collection, security data retention, and security modeling analysis) is used up, these capabilities become unavailable on that day, but they will be automatically available at 00:00 the next day.
  • Security orchestration: You will be billed for times playbooks are executed for you. If the quota for security orchestration is used up, this function becomes unavailable on that day, but it turns to be available at 00:00 the next day.

  For example, if you purchased security modeling analysis of 1 GB/day for one month and used 1 GB before 22:00 on the purchase day, security modeling analysis will become unavailable between 22:00 and 24:00 on that day.

Log audit

Security data collection

120 MB/day/quota

120 MB/day/quota

Security data retention

120 MB/day/quota

120 MB/day/quota

Security data export

120 MB/day/quota

120 MB/day/quota

Security Modeling Analysis

×

120 MB/day/quota

Threat management

Preset threat models

×

Calculation model data: 120 MB/day/quota; preset models: 200

Preset response playbooks

×

Preset playbooks: 30

Security orchestration

Security orchestration

×

Operations: 7,000

Security Data Collection

The volume of data you expect SecMaster to collect each day.

Minimum value: 5 GB. You can estimate the volume by multiplying the number of ECSs you have by 120 MB. Maximum volume for each order: 500 GB.

When you make a purchase, SecMaster auto-fills this parameter based on the new log volume you specify. You do not need to configure this parameter separately.

5 * 1 GB

0 GB to 5 GB (included)

5 * 2 GB

5 GB to 10 GB (included)

5 * 3 GB

10 GB to 15 GB (included)

...

The others follow the same rule. A maximum of 500 GB can be purchased through an order.

...

The others follow the same rule.

Security Data Retention

The volume of data you expect SecMaster to store.

The minimum volume is 100 GB. You can estimate the volume by multiplying new log volume per day by seven. The maximum volume for each order is 3,500 GB.

When you make a purchase, SecMaster auto-fills this parameter based on the new log volume you specify. You do not need to configure this parameter separately.

100 * 1 GB

0 GB to 100 GB (included)

100 * 2 GB

100 GB to 200 GB (included)

100 * 3 GB

200 GB to 300 GB (included)

...

The others follow the same rule. A maximum of 3,500 GB can be purchased through an order.

...

The others follow the same rule.

Security Modeling Analysis

Log volume for analysis.

Minimum value: 5 GB. You can estimate the volume by multiplying the number of ECSs you have by 120 MB. Maximum volume for each order: 500 GB.

When you make a purchase, SecMaster auto-fills this parameter based on the new log volume you specify. You do not need to configure this parameter separately.

5*1 GB

0 GB to 5 GB (included)

5*2 GB

5 GB to 10 GB (included)

5*3 GB

10 GB to 15 GB (included)

...

The others follow the same rule. A maximum of 500 GB can be purchased through an order.

...

The others follow the same rule.