- 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
Creating a Workspace
Scenario
Workspaces are the root of SecMaster resources. A single workspace can be bound to general projects, regions, and enterprise projects for different application scenarios.
Before using baseline inspection, alert management, security analysis, and security orchestration in SecMaster, you need to create at least one workspace first. You can use workspaces to group your resources by application scenario. This will make security operations more efficient.
This section describes how to create a workspace.
Limitations and Constraints
- Paid SecMaster: A maximum of five workspaces can be created for an account in a region.
- Free SecMaster: Only one workspace can be created for an account in a region.
Creating a Workspace
- Log in to the management console.
- Click
in the upper left corner of the management console and select a region or project.
- Click
in the upper left corner of the page and choose Security & Compliance > SecMaster.
- In the navigation pane on the left, choose Workspaces > Management.
Figure 1 Workspaces > Management
- On the Management page, click Create. The Create Workspace slide-out panel is displayed.
- Configure workspace parameters by referring to the following table.
Table 1 Parameters for creating a workspace Parameter
Description
Region
Select the region where the workspace to be added is located.
Workspace Name
Create a name for your workspace. The name must meet the following requirements:
- Only letters (A to Z and a to z), numbers (0 to 9), and the following special characters are allowed: -_()
- A maximum of 64 characters are allowed.
Tag
(Optional) Tag of the workspace, which is used to identify the workspace and help you classify and track your workspaces.
Description
(Optional) User remarks
- Click OK.
Operations You Can Do with a Workspace
You can perform security operations after adding a workspace. Functions you can use vary depending on the SecMaster edition in use. For details, see Functions.
- Checking the Situation Overview, Checking Security Situation through Large Screens, Security Reports, and Task Center: Check the security situation in a workspace, create security reports, handle to-do tasks, and check security situation on large screens.
- Resource Manager: Manage assets centrally.
- Risk Prevention: Prevent risks through baseline inspections, vulnerability management, emergency vulnerability notifications, and security policy management.
- Threat Operations: Manage threats, including incidents, alerts, and indicators, use intelligent modeling, and perform security analysis.
- Security Orchestration: Implement security orchestration. Security orchestration combines security functions of different systems or components in a system involved in security operations in your organizations based on certain logical relationships to complete a specific security operations process and procedure. It aims to help security teams of enterprises and organizations quickly and efficiently respond to network threats and implement efficient and automatic response and handling of security incidents. You can manage operations objects, playbooks, page layouts, and plug-ins.
- Settings: Configure log collection and access to aggregate logs into SecMaster.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.