Security Center has the following limits on threat detection and log storage.
Threat detection limits
| Limit | Details |
|---|---|
| Detection warm-up period | After you install the Security Center agent on a server, the defense process takes time to become fully active. During this period, Security Center cannot block threats such as ransomware and DDoS trojans. |
| Unknown threat detection | Security Center cannot guarantee real-time detection of all unknown threats. Attacks and malware evolve continuously, and workloads run in diverse environments. |
To strengthen your security posture, use Security Center alerting, vulnerability detection, baseline checks, and configuration assessment alongside other services. For broader network and application protection, add Cloud Firewall and Web Application Firewall (WAF) to your setup. Install the latest security patches on your servers regularly.
Important
Security Center is most effective as part of a layered defense strategy. Relying on it alone does not guarantee complete protection against all threats.
Logstore limits
All Security Center logs are stored in a dedicated Logstore. The following limits apply to this Logstore.
| Limit | Details |
|---|---|
| Data import | You cannot use the Log Service API or SDK to import data into the dedicated Logstore. |
| Attribute modification | You cannot use the Log Service API or SDK to modify Logstore attributes, such as the retention period. |
| Default reports | Default reports may be updated in later versions. |
| Queries, statistics, alerts, and streaming consumption | No limits. |
| Charges | The Logstore does not incur charges as long as your Log Service account has no overdue payments. |
该文章对您有帮助吗？