หน้านี้ยังไม่พร้อมใช้งานในภาษาท้องถิ่นของคุณ เรากำลังพยายามอย่างหนักเพื่อเพิ่มเวอร์ชันภาษาอื่น ๆ เพิ่มเติม ขอบคุณสำหรับการสนับสนุนเสมอมา
- 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
Copied.
Overall Situation Screen
Scenarios
There are always such scenarios as presentation, reporting, or real-time monitoring where you need to present the analysis results of SecMaster on big screens to achieve better demonstration effect. It is not ideal to just zoom in the console. Now, SecMaster Large Screen is a good choice for you to display the service console on bigger screens for a better visual effect.
By default, SecMaster provides a large screen for comprehensive situation awareness by displaying the attack history, attack status, and attack trend. This allows you to manage security incidents before, when, and after they happen.
Procedure
- Log in to the management console.
- Click
in the upper part of the page and choose Security > SecMaster.
- In the navigation pane on the left, choose Workspaces > Management. In the workspace list, click the name of the target workspace.
- In the navigation pane on the left, choose Security Situation > Large Screen.
- Click Play in the lower right corner of the comprehensive situation awareness image to access the screen.
This screen includes many graphs. More details are provided below.
Security Score
The security score of the current assets is displayed.
Parameter |
Reference Period |
Update Frequency |
Description |
---|---|---|---|
Security Score |
Real-time |
|
The score is calculated based on what security services are enabled, and the levels and numbers of unhandled configuration issues, vulnerabilities, and threats. Each calculation item is assigned a weight.
|
Alert Statistics
The alert statistics of interconnected services are displayed.
To view details about the alert statistics, choose Threat Operations > Alerts in the current workspace.
Parameter |
Reference Period |
Update Frequency |
Description |
---|---|---|---|
New Alerts |
Today |
5 minutes |
Number of new alerts generated on the current day. |
Threat Alerts |
Last 7 days |
5 minutes |
Number of new alerts generated in the last seven days. |
Unhandled Alerts |
Last 7 days |
5 minutes |
Number of alerts that have not been cleared in the last seven days. |
Handled Alerts |
Last 7 days |
5 minutes |
Number of alerts that have been cleared in the last seven days. |
Asset Protection
The protection status of servers and websites is displayed, including the proportion of protected and unprotected assets. You can hover the cursor over a module to view the number of protected/unprotected assets.
Parameter |
Reference Period |
Update Frequency |
Description |
---|---|---|---|
Asset Protection (%) |
Last 7 days |
5 minutes |
The protection status of servers and websites is displayed, including the proportion of protected and unprotected assets.
|
Baseline Inspection
The fixing status of the baseline configuration and vulnerabilities of your assets, distribution of risky resources, and vulnerability fixing trend within seven days are displayed.
- To view details about the baseline data, choose Risk Prevention > Baseline Inspection in the current workspace.
- To view details about the vulnerability data, choose Risk Prevention > Vulnerabilities in the current workspace.
Parameter |
Reference Period |
Update Frequency |
Description |
---|---|---|---|
Baseline Settings |
Real-time |
5 minutes |
Numbers of baseline settings that passed and failed the last baseline inspection. |
Vulnerabilities |
Last 7 days |
5 minutes |
Numbers of fixed and unfixed vulnerabilities in the last seven days. |
Resources by Severity |
Real-time |
5 minutes |
Numbers of unsafe resources at different severities in the last baseline inspection. Severity: Critical, High, Medium, Low, and Info. |
Vulnerabilities |
Last 7 days |
5 minutes |
New vulnerabilities by the day for the last seven days and vulnerability distribution. |
Recent Threats
The numbers of threatened assets and security logs reported every day in the last seven days are displayed.
The x-axis indicates time, the y-axis on the left indicates the number of threatened assets, and the y-axis on the right indicates the number of logs. Hover the cursor over a date to view the number of threatened assets of that day.
Parameter |
Reference Period |
Update Frequency |
Description |
---|---|---|---|
Attacks |
Last 7 days |
5 minutes |
Number of alerts reported every day in the last seven days. To view details about the alert statistics, choose Threat Operations > Alerts in the current workspace. |
Logs |
Last 7 days |
5 minutes |
Number of security logs reported every day in the last seven days. |
To-Dos
The to-do items in the current workspace are displayed.
Parameter |
Reference Period |
Update Frequency |
Description |
---|---|---|---|
To-Dos |
Real-time |
5 minutes |
To-do items on the Security Situation > Task Center in the current workspace. |
Resolved Issues
The alert handling status, SLA and MTTR fulfillment rate in the last seven days, and automatic incident handling statistics in the last seven days are displayed.
To view details about the alert statistics, choose Threat Operations > Alerts in the current workspace.
Parameter |
Reference Period |
Update Frequency |
Description |
|
---|---|---|---|---|
Alerts |
Alerts |
Last 7 days |
5 minutes |
Number of new alerts generated in the last seven days. |
Handled |
Number of alerts that have been cleared in the last seven days. |
|||
Manual |
Number of alerts that were handled within the SLA time in the last seven days. Alerts handled as planned and earlier than planned are counted. |
|||
Auto |
Number of alerts that were automatically handled by SecMaster playbooks over the past seven days. To determine how an alert was handled, check whether the value of close_comment is ClosedByCSB or ClosedBySecMaster in the alert details. If it is, the alert was automatically handled. If it is not, the alert was manually handled. |
|||
SLA and MTTR [Last 7 Days] |
SLA Statistics |
Last 7 days |
5 minutes |
Alert handling timeliness in the last seven days. The formula is as follows: For an alert with Service-Level Agreement (SLA) specified, if Alert closure time - Alert generation time ≤ SLA, it indicates the alert was handled in a timely manner. Otherwise, the alert fails to meet SLA requirements.
|
MTTR |
Average alert closure time in the last seven days. The formula is as follows: Mean Time To Repair (MTTR) = Total processing time of each alert/Total number of alerts. Processing time of each alert = Closure time – Creation time. |
|||
Handled Alerts [Last 7 Days] |
Last 7 days |
5 minutes |
Total number of alerts handled in the last seven days.
To determine how an alert was handled, check whether the value of close_comment is ClosedByCSB or ClosedBySecMaster in the alert details. If it is, the alert was automatically handled. If it is not, the alert was manually handled. |
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