Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
- 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
Show all
How Long Are Logs Stored in SecMaster?
SecMaster can aggregate logs from many cloud products, such as WAF, HSS, and OBS. After the log aggregation, SecMaster can query and analyze the data and perform intelligent modeling.
The following table lists how long SecMaster stores logs of cloud products.
|
Cloud Service |
Log Description |
Log |
Log Lifecycle |
|---|---|---|---|
|
Web Application Firewall (WAF) |
Attack logs |
waf-attack |
7 to 30 days |
|
Access logs |
waf-access |
||
|
SecMaster |
Compliance baseline log |
secmaster-baseline |
7 to 10 days |
|
Object Storage Service (OBS) |
Access logs |
obs-access |
7 to 15 days |
|
Intrusion Prevention System (IPS) |
Attack logs |
nip-attack |
7 to 30 days |
|
Identity and Access Management (IAM) |
Audit logs |
iam-audit |
7 to 30 days |
|
Host Security Service (HSS) |
HSS alarms |
hss-alarm |
7 to 30 days |
|
HSS vulnerability scan results |
hss-vul |
7 days |
|
|
HSS security logs |
hss-log |
7 to 15 days |
|
|
Data Security Center (DSC) |
Alarm logs |
dsc-alarm |
7 to 30 days |
|
Anti-DDoS |
Attack logs |
ddos-attack |
7 to 30 days |
|
Database Security Service (DBSS) |
Alarm logs |
dbss-alarm |
7 to 30 days |
|
Cloud Trace Service (CTS) |
CTS logs |
cts-audit |
7 to 30 days |
|
Cloud Firewall (CFW) |
Access control logs |
cfw-block |
7 to 30 days |
|
Traffic logs |
cfw-flow |
7 to 15 days |
|
|
Attack event logs |
cfw-risk |
7 to 30 days |
|
|
API Gateway (APIG) |
Access logs |
apig-access |
7 to 30 days |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
