Whitelist
최신 업데이트：2026-03-25 16:26:15
Reading time: About 3 minutes
Prerequisites: The target hostname has been onboarded to the protection service.
Whitelist vs. Exceptions
| Whitelist | Exception | |
|---|---|---|
| Purpose | Skips all security policy checks and allows the traffic directly | Skips the inspection of a specific policy |
| Use when | Fully trusted internal IPs, fixed IPs of partner organizations | A rule generates false positives for legitimate requests |
| Security Risk | Higher (no protection at all) | Low (other rules still function normally) |
Principle: Use whitelists with caution. Only use a whitelist when you are 100% certain that a source is absolutely trustworthy. For false positive scenarios, use the Exception feature of each module instead.
When to Use a Whitelist
- Fixed public IPs or IP segments of partner organizations with a signed security agreement
- Public IPs of authorized penetration testing or security scanning services
- Your own office egress public IPs (for internal employee testing or management operations)
Configuration Steps
The following example uses a partner’s fixed IP segment (203.0.113.0/24).
- Go to Security Settings > Policies, and click the target hostname to enter the policy details page.
- Click the Whitelist tab, then click Add.
- Set the match condition: IP/CIDR belongs to
203.0.113.0/24. - Click Save to complete the configuration.
Review whitelist entries periodically. If a partner’s IP changes, an employee leaves, or a VPN configuration is updated, promptly update or delete the corresponding whitelist entry to avoid long-standing security coverage gaps.
이 문서의 내용이 도움이 되었습니까?
예
아니오