SecMaster
SecMaster
- 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
On this page
Workspace Overview
Updated on 2025-01-20 GMT+08:00
This topic describes the following details about workspaces:
Actions you can do:
- Creating a Workspace: Workspaces are top-level operation platform in SecMaster. A workspace can be associated with general projects, regions, and enterprise projects to meet different security operations needs. 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.
- Viewing a Workspace: You can view the details about a workspace, including its name, type, and creation time.
- Editing a Workspace: You can modify the workspace basic settings, including its name and description.
- Deleting a Workspace: If you no longer need a workspace, you can delete it. After a workspace is deleted, SecMaster may be unable to detect security risks of assets managed in the workspace. So the risk of those assets may fail to be prevented. Deleted workspaces cannot be restored. Exercise caution when performing this operation.
- Managing Workspace Tags: After creating a workspace, you can add, edit, and delete tags configured for the workspace. A tag consists of a key-value pair. Tags are used to identify, and classify workspaces. Workspace tags are used for workspace management only.
- Creating a Workspace Agency: You can create a workspace agency to perform cross-account secure operations. In this way, you can centrally view asset risks, alerts, and incidents in workspaces of other users. You can create agencies to authorize other users to manage your workspaces in a project. In this way, asset risks, alerts, and incidents across workspaces can be centrally managed for security operations.
- Managing Agencies: On the Agencies page, you can manage agency views, workspaces you are managing for others, and agencies managing your workspaces.
- Agency Views: On this tab, you can view all agency views you create and their details. You can view, edit, modify, and delete an agency view, as well as delete agency views in batches.
- Workspaces Managed by Me: On this tab, you can view workspaces managed in the agency view you create. You can check tasks managed by you and task parameters, and manage (accept, reject, release, and delete) tasks managed by you.
- My Workspaces Managed by Others: On this tab, you can view which agency views are managing workspaces you create. You can view parameters related to the agency views, modify accepted agency tasks, withdraw accepted agency tasks, request for agencies again, release an agency, and delete agency tasks.
General Rules for Workspaces
- 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.
- Permanent deletion of workspaces: Workspaces are deleted immediately and cannot be restored.
- Workspace agencies:
- A maximum of one workspace agency view can be created for an account in a region.
- A maximum of 150 workspaces from different regions and accounts can be managed by a workspace agency view.
- A maximum of 10 agencies can be created for an account.
- Currently, performing operations across different workspaces in multiple browser windows at the same time is not supported.
Parent topic: Workspaces
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.