Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
- What's New
- Function Overview
- Service Overview
-
Billing
- Billing Overview
- Billing Modes
- Billing Items
- Billing Examples
- Changing the Billing Mode
- Renewing Your Subscription
- Bills
- About Arrears
- Billing Termination
- Cost Management
-
Billing FAQs
- How Is SecMaster Billed?
- Can I Use SecMaster for Free?
- How Do I Change or Disable Auto Renewal for SecMaster?
- Will SecMaster Be Billed After It Expires?
- How Do I Renew SecMaster?
- Where Can I Unsubscribe from SecMaster?
- Where Can I View the Remaining Quotas of Security Data Collection and Security Data Packages?
- Can I Change the Billing Mode for SecMaster?
- Getting Started
-
User Guide
- Buying SecMaster
- Authorizing SecMaster
- Checking Security Overview
- Workspaces
- Viewing Purchased Resources
-
Security Governance
- Security Governance Overview
- Security Compliance Pack Description
- Authorizing SecMaster to Access Cloud Service Resources
- Subscribing to or Unsubscribing from a Compliance Pack
- Starting a Self-Assessment
- Viewing Security Compliance Overview
- Viewing Evaluation Results
- Viewing Policy Scanning Results
- Downloading a Compliance Report
- Security Situation
- Resource Manager
- Risk Prevention
- Threats
- Security Orchestration
-
Playbook Overview
- Ransomware Incident Response Solution
- Attack Link Analysis Alert Notification
- HSS Isolation and Killing of Malware
- Automatic Renaming of Alert Names
- Auto High-Risk Vulnerability Notification
- Automatic Notification of High-Risk Alerts
- Auto Blocking for High-risk Alerts
- Real-time Notification of Critical Organization and Management Operations
-
Settings
- Data Integration
-
Log Data Collection
- Data Collection Overview
- Data Collection Process
- Adding a Node
- Configuring a Component
- Adding a Connection
- Creating and Editing a Parser
- Adding and Editing a Collection Channel
- Verifying Log Collection
- Managing Connections
- Managing Parsers
- Managing Collection Channels
- Viewing Collection Nodes
- Managing Nodes and Components
- Partitioning a Disk
- Logstash Configuration Description
- Connector Rules
- Parser Rules
- Upgrading the Component Controller
- Customizing Directories
- Permissions Management
- Key Operations Recorded by CTS
-
Best Practices
-
Log Access and Transfer Operation Guide
- Solution Overview
- Resource Planning
- Process Flow
-
Procedure
- (Optional) Step 1: Buy an ECS
- (Optional) Step 2: Buy a Data Disk
- (Optional) Step 3: Attach a Data Disk
- Step 4: Create a Non-administrator IAM User
- Step 5: Configure Network Connection
- Step 6: Install the Component Controller (isap-agent)
- Step 7: Install the Log Collection Component (Logstash)
- (Optional) Step 8: Creating a Log Storage Pipeline
- Step 9: Configure a Connector
- (Optional) Step 10: Configure a Log Parser
- Step 11: Configure a Log Collection Channel
- Step 12: Verify Log Access and Transfer
- Credential Leakage Response Solution
-
Log Access and Transfer Operation Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Alert Management
- Incident Management
- Indicator Management
- Playbook Management
- Alert Rule Management
- Playbook Version Management
- Playbook Rule Management
- Playbook Instance Management
- Playbook Approval Management
- Playbook Action Management
- Incident Relationship Management
- Data Class Management
- Workflow Management
- Data Space Management
- Pipelines
- Workspace Management
- Metering and Billing
- Metric Query
- Baseline Inspection
- Appendix
- FAQs
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Buying SecMaster
- Authorizing SecMaster
- Viewing Security Overview
- Workspaces
- Viewing Purchased Resources
-
Security Governance
- Security Governance Overview
- Security Compliance Pack Description
- Authorizing SecMaster to Access Cloud Service Resources
- Subscribing to or Unsubscribing from a Compliance Pack
- Starting a Self-Assessment
- Viewing Security Compliance Overview
- Viewing Evaluation Results
- Viewing Policy Scanning Results
- Downloading a Compliance Report
- Security Situation
- Resource Manager
- Risk Prevention
- Threat Operations
- Security Orchestration
-
Settings
- Data Integration
-
Log Data Collection
- Data Collection Overview
- Adding a Node
- Configuring a Component
- Adding a Connection
- Creating and Editing a Parser
- Adding and Editing a Collection Channel
- Managing Connections
- Managing Parsers
- Managing Collection Channels
- Viewing Collection Nodes
- Managing Nodes and Components
- Partitioning a Disk
- Logstash Configuration Description
- Connector Rules
- Parser Rules
- Upgrading the Component Controller
- Customizing Directories
- Permissions Management
- FAQs
- Change History
-
User Guide (Kuala Lumpur Region)
- Service Overview
- Authorizing SecMaster
- Security Overview
- Workspaces
- Viewing Purchased Resources
- Security Situation
- Resource Manager
-
Risk Prevention
-
Baseline Inspection
- Baseline Inspection Overview
- Creating a Custom Check Plan
- Starting an Immediate Baseline Check
- Viewing Check Results
- Handling Check Results
- Viewing Compliance Packs
- Creating a Custom Compliance Pack
- Importing and Exporting a Compliance Pack
- Viewing Check Items
- Creating a Custom Check Item
- Importing and Exporting Check Items
- Vulnerability Management
- Policy Management
-
Baseline Inspection
-
Threat Operations
- Incident Management
- Alert Management
- Indicator Management
- Intelligent Modeling
- Security Analysis
- Data Delivery
-
Security Orchestration
- Security Orchestration Overview
- Built-in Playbooks
- Security Orchestration Process
- (Optional) Configuring and Enabling a Workflow
- Configuring and Enabling a Playbook
- Operation Object Management
- Playbook Orchestration Management
- Layout Management
- Plug-in Management
- Settings
-
FAQs
-
Product Consulting
- Why Is There No Attack Data or Only A Small Amount of Attack Data?
- Where Does SecMaster Obtain Its Data From?
- What Are the Dependencies and Differences Between SecMaster and Other Security Services?
- What Are the Differences Between SecMaster and HSS?
- How Do I Update My Security Score?
- How Do I Handle a Brute-force Attack?
- Issues About Data Synchronization and Data Consistency
- About Data Collection Faults
-
Product Consulting
- Change History
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Show all
Copied.
Billing Items
Billing Description
The billing items of SecMaster consist of the service edition, quota, and value-added package. For details, see Table 1.
Billing Item |
Description |
Billing Mode |
Billing Formula |
|
---|---|---|---|---|
(Mandatory) Edition |
Billing factor: service edition + Quota. Different editions provide different functions. |
Yearly/Monthly and pay-per-use billing |
|
|
(Mandatory) Quota |
||||
Value-added package (optional) |
Large screen |
SecMaster large screen can display security analysis result 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: large screen - security situation metrics. |
Yearly/Monthly and pay-per-use billing |
|
Log audit |
If security data collection and storage are required, you can purchase the data collection volume and data retention volume packages separately. Billing factors: security data collection volume and security data storage volume. |
Yearly/Monthly and pay-per-use billing |
||
Security analysis |
If security data collection, security data retention, security data export, platform security data, and security modeling analysis are required, you can purchase security analysis quotas separately. Billing factor: security analysis data volume. |
Yearly/Monthly and pay-per-use billing |
|
|
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 how many times workflow nodes (including the start and end nodes, but excluding judgement nodes) are executed during playbook execution. |
Yearly/Monthly and pay-per-use billing |
|
Table 2 describes the functions in the value-added package.
Scenario |
Description |
---|---|
Purchase |
|
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 security analysis 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 analysis, and security orchestration, there are some limitations you need to know. The details are as follows:
|
Function |
Standard Edition |
Professional edition |
|
---|---|---|---|
Security analysis |
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 |
|
Platform security data |
40 MB/day/quota |
40 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 |
Package |
Recommended Configuration for Yearly/Monthly Subscription |
Package Specifications |
Applicable Range |
---|---|---|---|
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. |
Billing Examples
- The first billing period is from 15:50:04 on June 30, 2024 to 23:59:59 on July 30, 2024.
- The second billing period is from 23:59:59 on July 30, 2024 to 23:59:59 on Aug. 30, 2024.
Figure 1 shows how the price is calculated.
For pay-per-use billing examples, see Billing Example.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot