- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Buying SecMaster
- Authorizing SecMaster
- Viewing Security Overview
- Workspaces
- Viewing Purchased Resources
- Security Situation
- Resource Manager
- Risk Prevention
- Threat Operations
- 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
- 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
- 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
Overview
When to Renew Subscriptions
After your yearly/monthly SecMaster expires, it cannot be used anymore. If you want to continue using SecMaster, you need to renew it within the specified period.
Only yearly/monthly SecMaster subscriptions can be renewed. If you use pay-per-use SecMaster, just ensure that your account has a valid payment method configured or a top-up account with a sufficient balance.
If you renew your SecMaster before it expires, resources will be retained and you can continue using it. For details, see Impacts of Expiration.
How to Renew Subscriptions
Table 1 describes renewal methods for yearly/monthly SecMaster subscriptions.
|
Function |
Description |
|---|---|
|
For yearly/monthly SecMaster, you can renew it on the SecMaster console at any time as long as it has not been deleted automatically. |
|
|
After auto-renewal is enabled, SecMaster automatically renews your subscription before the subscription expires. This prevents resources from being automatically deleted if you forget to manually renew the subscription. |
In different phases of the lifecycle of a yearly/monthly SecMaster instance, you can choose a renewal mode best fits your needs. For details, see Figure 1.
- SecMaster works properly and its functions are available from the time it is purchased to the time it expires.
- If the resource fails to be renewed before expiration, SecMaster enters the grace period first. If the resource still fails to be renewed after the grace period expires, the resource is frozen.
- If it still failed to be renewed when the grace period expires, the instance enters the retention period. If you do not renew it within the retention period, the resource will be deleted automatically.
Auto-renewal can be enabled before your SecMaster instance expires. The system will automatically renew the instance at 3:00 a.m. on the seventh day before it expires. If the auto-renewal fails, the system will try again at 3:00 a.m. every day until your SecMaster resource expires or the renewal is successful. Renewing resources 7 days before expiration is a default value. You can change it if needed.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
