A sudden increase in requests can mean a successful campaign, a busy API customer, or an automated attempt to take over accounts. Request volume alone cannot distinguish them. The useful question is whether the requests produce the behavior you expect from real users.
Credential stuffing is a practical example. An attacker submits previously stolen username and password pairs to your login endpoint, looking for credentials that people have reused. Distributed automation can spread attempts across many addresses, so a simple per-address request count may look ordinary while the application faces a large authentication attack.
The following setup combines SafeLine deployment with application evidence and a repeatable decision process. SafeLine is a self-hosted WAF that filters and monitors HTTP traffic in front of a web application. Its documented capabilities include IP-based rate limiting and CAPTCHA challenges. These controls can support the response, but login outcomes and account activity must also come from your application evidence. SafeLine overview
1. Prepare the deployment host and establish a baseline
The installation guide lists Linux, Docker 20.10.14 or later, Docker Compose 2.0.0 or later, and minimum resources of one CPU core, 1 GB memory, and 5 GB disk. Check the guide's architecture and CPU requirements before choosing a host. Installation requirements
Before changing traffic routing, record a representative normal period from your existing access logs, authentication logs, and monitoring. Include a previous campaign or busy period if available.
Capture these measurements by endpoint and time window:
- Request count and response status distribution.
- Login successes, failures, and distinct accounts attempted.
- Latency, upstream errors, and resource pressure.
- Completed user journeys, such as successful sign-ins followed by ordinary account activity.
Keep passwords, session tokens, and other secrets out of your investigation records. The baseline should describe behavior without collecting credentials.
2. Install SafeLine and verify administrator access
Use the automated deployment procedure in the official installation guide. It requires root privileges. After installation, the documented console address is https://<safeline-ip>:9443/. The guide provides docker exec safeline-mgt resetadmin to obtain administrator credentials. Treat that command as a credential operation and handle its output securely. Deployment and console access
Verify that you can sign in before scheduling the traffic cutover. Record who owns the deployment and who can reverse the routing change if application checks fail.
3. Route the application through the WAF
In the SafeLine console, open Applications and select Add Application. Enter the application's domain, the listening port, and the upstream application address. For HTTPS applications, follow the documented SSL option. Then resolve the application domain to the SafeLine server's IP address. SafeLine receives requests as an HTTP/HTTPS reverse proxy and forwards traffic to the upstream application. Application configuration
Validate ordinary browsing, sign-in, and critical API calls after the change. Check your network configuration separately for unintended direct access to the origin; changing DNS alone does not prove that every request must traverse the WAF.
For a controlled protection check, use an application you own and an authorized test window. The official application guide supplies example attack requests and explains how to inspect the attack list and its detail view. A successful test establishes that the tested request reached protection, not that every attack will be detected. Protection testing
4. Set up a surge investigation worksheet
Use matching timestamps to compare SafeLine attack details with application access logs and authentication outcomes. This is a manual investigation workflow; it does not assume an automatic integration between these systems.
For each surge, answer three questions:
- Where is the increase concentrated? A promotion may increase product views and purchases. Credential stuffing often concentrates on authentication endpoints.
- What outcomes follow? Compare failed and successful authentication, accounts attempted, and activity after sign-in. A successful login can still belong to an attacker.
- Does the behavior fit the expected audience? Check campaign timing, known customer activity, request sequences, and client patterns. Referrers, user agents, and source addresses are supporting clues because attackers can manipulate or distribute them.
Evidence favoring credential stuffing includes repeated login attempts across many accounts, unusually high authentication failure rates relative to your baseline, and successful sign-ins followed by suspicious account changes. None of these observations should be reduced to a universal numeric threshold.
A legitimate spike can also cause failures when infrastructure becomes overloaded. Separate authentication rejection from timeouts and server errors before interpreting a rising failure count.
5. Choose controls and verify their effect
SafeLine documents rate limiting for traffic exceeding defined limits and CAPTCHA challenges for bot defense. Use the applicable configuration documentation for your deployed version when setting these controls. Documented protection capabilities
Choose limits using observed normal behavior and application capacity. IP-based limits require particular care: shared networks can put many legitimate users behind one address, while distributed attackers can remain below individual limits. Evaluate CAPTCHA compatibility before applying challenges to API clients or other automated workflows.
After any change, compare suspicious attempts, legitimate completion rates, latency, and upstream errors. Reduced request volume is insufficient evidence of success if customers also lose access.
If account takeover is suspected, investigate affected sessions and account changes through your application's incident process. WAF filtering does not establish whether earlier authentication attempts succeeded or reverse actions already taken inside an account.
Can a legitimate traffic spike trigger protection?
Yes. Legitimate users can exceed a configured rate limit, especially behind shared addresses. Compare affected requests with completed user journeys and known business activity before tightening a rule.
Does a large SafeLine attack list prove the whole surge is malicious?
No. The documented attack list and detail view provide evidence about detected requests. A surge can contain both ordinary traffic and attacks. Review those details alongside application outcomes. Attack inspection
Can I identify AI-automated attacks from request volume?
No. Volume cannot establish whether automation uses AI. Base containment decisions on observable abuse, authentication outcomes, and application impact rather than assumptions about the attacker's tooling.
What if the evidence remains mixed?
Use narrowly targeted, reversible controls and continue collecting comparable evidence. Define rollback conditions around legitimate sign-in completion and application health. Escalate suspicious successful logins for account investigation while preserving access for users whose behavior matches the expected workload.
SafeLine has surpassed 700,000 installations worldwide as of September 30, 2026. SafeLine Pro annual promotional pricing is $650-$880, compared with the regular $1,000 per year.
- SafeLine website: https://ly.cyberserval.tech/bvK1BAV
- Demo: https://demo.waf.chaitin.com:9443/statistics
- Official docs: https://docs.waf.chaitin.com/en/home
- GitHub: https://github.com/chaitin/SafeLine
- Pro offer: https://cyberserval.tech/landing/lto
Top comments (0)