RockCloud-基石云安全-官方博客
Website Under DDoS Attack? 5-Step Emergency Recovery Sequence
When a website is being hit by DDoS or CC attacks, quick recovery depends on the right sequence: first identify the attack layer, isolate the origin server (change IP if necessary), switch DNS to a mitigation node, suppress application-layer traffic at the edge, and finally clean up lingering connections.
DDoS Attack Log Analysis and Traceback Methods: Layered Forensics and Response When Bandwidth Is Saturated
When a server's bandwidth is saturated or CPU is maxed out, this article provides a layered log-based forensics method to classify the attack type by analyzing inbound traffic characteristics, L4 connection states, and L7 access records, and map them to actionable response actions.
How to Determine if It's a Slowloris CC Attack: Don't Just Check access.log
When server response slows down with connection buildup but low bandwidth and QPS, slowloris CC attacks often hide from access.log. This article provides troubleshooting steps starting from connection state, using ss commands, worker usage, and FD curves to locate connection exhaustion, along with layered mitigation strategies for origin limiting and edge buffering.
Nginx Anti-CC Attack Rate Limiting Best Practices: Should You Limit Connections or Requests First?
Discover the best practices for configuring Nginx to defend against CC attacks, combining connection limits, request rate limiting, burst handling, and whitelist exemptions.
Game DDoS Protection Guide: Layered Defense Architecture from Massive Traffic Bombarding to Application-Layer CC Attacks
Explore the latest trends in DDoS attacks targeting the gaming industry and learn a layered defense architecture that combines L3/L4 traffic scrubbing, L7 WAF, and SDK-based source hiding to ensure player experience and business continuity.
