About Cloud Security 2.0
최신 업데이트：2026-08-19 19:00:30
Reading time: About 3 minutes
Cloud Security 2.0 is an all-in-one web security protection platform deployed on CDN edge nodes. All traffic passes through security inspection at the edge nodes before it reaches your origin, so attacks are blocked at the network edge and never consume your origin resources.
Which Threats Does Cloud Security 2.0 Protect You Against
| Threat Type | Corresponding Cloud Security 2.0 Capability | Typical Scenario |
|---|---|---|
| Web application attacks (SQL Injection, XSS, etc.) | WAF Managed Rules | An attacker attempts to compromise your database |
| Large-scale DDoS attacks | DDoS Protection | A traffic flood overwhelms your servers |
| Malicious scrapers and automated attacks | Bot Management | A competitor scrapes your pricing data |
| API abuse | API Security | An API is maliciously called in bulk |
| Traffic abuse | Anomaly Traffic Detection | Illegitimate requests run up your CDN traffic bill |
| High-frequency brute-force attacks | Rate Limiting | Accounts are targeted by mass credential stuffing |
| Known malicious IPs | Threat Intelligence | Attack sources listed in the global threat database |
How Protection Works
User request
↓
[Edge node]
├── Network-layer (L3/4) DDoS protection
├── Whitelist
├── IP/Geo Firewall
├── Application-layer (L7) DDoS protection
├── Custom Rules
├── Rate Limiting
├── Bot detection
├── Threat Intelligence matching
├── WAF rule inspection
└── API security
↓
Legitimate requests that pass inspection → Your origin
Core Concepts at a Glance
- Security Policy: A set of protection rules applied to a specific hostname, including the configurations of the DDoS, WAF, Bot, and other submodules.
- Observation Mode: The policy inspects requests but does not block them and only logs events. Use it to validate a new policy before it goes live.
- Security Action: The operation the system performs when a request triggers a rule (block, allow, verify, monitor, and so on).
- Whitelist: A set of request conditions that bypass all security inspection and are allowed directly.
- Exception: A set of request conditions that bypass only a specific policy’s inspection, while all other policies continue to inspect the request normally.
- Deployment: Deploying configuration changes to all edge nodes, which typically takes 2–3 minutes.
이 문서의 내용이 도움이 되었습니까?
예
아니오