IP/Geo Firewall

최신 업데이트:2026-03-23 11:14:32

Configuring IP/Geo Firewall Rules

Reading time: About 5 minutes
Prerequisites: None

How This Differs from Other Policies

Policy Use When
IP/Geo Firewall A specific IP or region is confirmed to have no legitimate users — block it directly
Threat Intelligence Automatically identify known malicious IPs (no manual list maintenance needed)
Rate Limiting Limit the request frequency of a single IP rather than blocking it entirely
Whitelist Allow specific IPs to bypass all security checks

Navigation path: Security Settings > Policies > [Target Hostname] > IP/Geo Firewall

Creating a Block Rule

IP Block

  1. Go to Security Settings > Policies > [Target Hostname] > IP/Geo Firewall, and click Add Rule.
  2. Select IP Blocking as the rule type, then enter the target to block. The following formats are supported:
    • Single IP: 1.2.3.4
    • IP range (CIDR): 1.2.3.0/24
    • IP range: 1.2.3.1–1.2.3.100
  3. Click Save and confirm that the configuration has taken effect.

Usage recommendations:

  • A single high-frequency attack IP that appears repeatedly in the attack logs → Single IP blocking
  • Attack IPs are concentrated within a specific IP range (sharing the same data center or AS number) → CIDR blocking

Geo Block

  1. Go to Security Settings > Policies > [Target Hostname] > IP/Geo Firewall.
  2. Select Geo Block as the rule type, then choose the country or region to block.
  3. Click Save and confirm that the configuration has taken effect.

Important: Geo blocking affects all users in the selected region, including your legitimate users. Use this only when:

  • Your product explicitly does not serve that region
  • The proportion of attack requests from that region is extremely high and there are no legitimate users

User experience after blocking: When users in the blocked region try to access your site, they will see the page you configured in Custom Response (a 403 response is returned by default). It is recommended to customize the response page to inform users why the service is unavailable and avoid confusion.

Operational Recommendations

  1. Try Threat Intelligence first: Automatically blocks known malicious IPs without manual maintenance
  2. Extract attack IPs from attack logs: Check Top Attack Sources and manually add block rules for IPs that are persistently attacking
이 문서의 내용이 도움이 되었습니까?
아니오
정상적으로 제출되었습니다.피드백을 주셔서 감사합니다.앞으로도 개선을 위해 노력하겠습니다.