Overview
The secure-delivery approach at WAFGO gives caching, traffic controls and application policies distinct roles. Build defenses around request types while preserving legitimate access and useful incident records.
Assign each risk to the right layer
Network anomalies, high-rate application traffic and malicious web input have different characteristics. Layered policies make their effects and false positives easier to understand.
Traffic and connection pressure
Assess DDoS coverage against actual protocols and normal traffic, with clear thresholds and escalation paths.
Application access and abuse
Use path, identity or source context for rate limits and challenges instead of one blanket limit for every visitor.
Malicious web input
Configure WAF policies around application inputs and common attack patterns, tuning exceptions using observed requests.
Review both origin exposure and content access
Edge protection applies to traffic that actually passes through it. Direct origin access, historical DNS records and unmanaged asset hostnames need to be reviewed too.
- Restrict origin access where appropriate while preserving required health checks and operational access.
- Validate authorization for private downloads or paid resources; referrer checks are not identity authentication.
- Scope security exceptions by path, condition and duration rather than leaving a permanent site-wide bypass.
Deploy, observe and review security policies
Assign owners and keep change records for security policies. Where supported, observe matches before enforcement, retain a rollback configuration and preserve enough context to investigate incidents.
Legitimate-traffic checks
Test login, payment, uploads, crawling and third-party callbacks instead of using blocked-request counts as a quality measure.
Incident context
Record time, hostname, path, matched rule and outcome; remove credentials and personal data from shared samples.
Recovery and review
After recovery, review false positives, bypass routes and policy coverage, then update monitoring and response contacts.
Implementation & checks
- 01
Identify exposure
Map domains, origins and business-critical entry points.
- 02
Enable controls in layers
Introduce policies by risk and monitor legitimate requests.
- 03
Practice response
Prepare alerting, policy rollback and origin-recovery procedures.