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.
Error Codes
If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in API Gateway Error Codes.
Status Code |
Error Codes |
Error Message |
---|---|---|
400 |
SecMaster.11061001 |
alert process status error. |
400 |
SecMaster.11061002 |
alert rule count out of range. |
400 |
SecMaster.11061003 |
alert rule schedule out of range. |
400 |
SecMaster.11061004 |
alert rule name already exist. |
400 |
SecMaster.20010001 |
Invalid workspace ID. |
400 |
SecMaster.20030001 |
Invalid parameters. |
400 |
SecMaster.20030002 |
Invalid project ID. |
400 |
SecMaster.20030003 |
Invalid name. |
400 |
SecMaster.20030004 |
Failed to create the data object. |
400 |
SecMaster.20030005 |
Failed to obtain the data object. |
400 |
SecMaster.20030009 |
Invalid sorting field. |
400 |
SecMaster.20030010 |
Invalid sorting. |
400 |
SecMaster.20030011 |
Data object update error. |
400 |
SecMaster.20030012 |
Data object deletion error. |
400 |
SecMaster.20030013 |
Data object search error. |
400 |
SecMaster.20030022 |
Failed to find one dataclass. |
400 |
SecMaster.20030025 |
Failed to valid data object. |
400 |
SecMaster.20039999 |
Unknown errors |
400 |
SecMaster.20040000 |
Unknown Error. |
400 |
SecMaster.20040402 |
Failed to query the data class. |
400 |
SecMaster.20040516 |
The number of fields exceeds the maximum. |
400 |
SecMaster.20041001 |
Invalid workspace ID. |
400 |
SecMaster.20041002 |
Invalid parameters. |
400 |
SecMaster.20041003 |
Invalid project ID. |
400 |
SecMaster.20041031 |
Fail to get data object. |
400 |
SecMaster.20041033 |
No associated data object is selected. |
400 |
SecMaster.20041504 |
Failed to create the incident. |
400 |
SecMaster.20041507 |
Failed to update the incident. |
400 |
SecMaster.20041508 |
Failed to delete the incident. |
400 |
SecMaster.20041509 |
The number of incidents created per day exceeds the upper limit. |
400 |
SecMaster.20041804 |
Incorrect content included in the request for converting an alert to an incident. |
400 |
SecMaster.20041805 |
Failed to create the alert. |
400 |
SecMaster.20041808 |
Failed to update alert. |
400 |
SecMaster.20041809 |
Failed to delete the alert. |
400 |
SecMaster.20041810 |
The number of alerts created per day exceeds the upper limit. |
400 |
SecMaster.20041811 |
The number of incidents transferred by alerts per day exceeds the upper limit. |
400 |
SecMaster.20041903 |
Failed to find dataclass. |
400 |
SecMaster.20041904 |
The indicator is not exist. |
400 |
SecMaster.20041905 |
Failed to create indicator. |
400 |
SecMaster.20041906 |
Failed to update indicator. |
400 |
SecMaster.20041907 |
Failed to delete indicator. |
400 |
SecMaster.20042501 |
The number of indicators created per day exceeds the upper limit. |
400 |
SecMaster.20048001 |
The playbook cannot be deleted because it has a running instance or an activated version. |
400 |
SecMaster.20048002 |
The playbook cannot be enabled because it does not have an activated version. |
400 |
SecMaster.20048003 |
The playbook cannot be reviewed because it is in an incorrect state. |
400 |
SecMaster.20048004 |
The resource does not exist. |
400 |
SecMaster.20048005 |
The draft cannot be activated before it passes the review. |
400 |
SecMaster.20048006 |
Incorrect playbook ID. |
400 |
SecMaster.20048007 |
Incorrect playbook version ID. |
400 |
SecMaster.20048008 |
Incorrect playbook action ID. |
400 |
SecMaster.20048009 |
Incorrect playbook rule ID. |
400 |
SecMaster.20048013 |
The playbook is being enabled. You cannot deactivate the version. |
400 |
SecMaster.20048014 |
The playbook has been released and cannot be edited. |
400 |
SecMaster.20048015 |
The playbook name must be unique. |
400 |
SecMaster.20048016 |
Incorrect time range of the scheduled task. |
400 |
SecMaster.20048017 |
Incorrect Corn expression of the scheduled task. |
400 |
SecMaster.20048018 |
The number of versions has reached the upper limit. |
400 |
SecMaster.20048019 |
A new version cannot be created because there is a version being reviewed. |
400 |
SecMaster.20048020 |
Incorrect data object ID. |
400 |
SecMaster.20048021 |
Invalid playbook search text. |
400 |
SecMaster.20048022 |
The end time must be later than the start time. |
400 |
SecMaster.20048023 |
Failed to register schedule job of playbook. |
400 |
SecMaster.20048024 |
Failed to disable schedule job of playbook. |
400 |
SecMaster.20048025 |
End time of the schedule playbook must be larger than start time. |
400 |
SecMaster.20048026 |
End time of the schedule playbook is invalid. |
400 |
SecMaster.20048027 |
The data class id of playbook is empty. |
400 |
SecMaster.20048028 |
The matching process of playbook is not enabled. You cannot submit the version |
400 |
SecMaster.20048029 |
Failed to convert data of playbook |
400 |
SecMaster.20048030 |
The number of playbooks exceeds the limit. |
400 |
SecMaster.20048031 |
The number of matching process exceeds the limit. |
400 |
SecMaster.20048032 |
The scheduled interval of playbook is invalid. |
400 |
SecMaster.20048033 |
The matching process of playbook can not be empty. |
400 |
SecMaster.20048034 |
The dataclass of matching process is inconsistent with the dataclass of playbook. |
400 |
SecMaster.20048035 |
The built-in playbook cannot be modified. |
400 |
SecMaster.20048036 |
The built-in playbook cannot be deleted. |
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