RockCloud-基石云安全-官方博客
DDoS Attack Incoming: Don't Let Your Business Crash While 'Waiting for Response' — RockCloud Emergency Response Manual
When your business suffers a sudden DDoS attack, every second lost means lost users and revenue. This article summarizes an emergency avoidance guide during an attack and explores how RockCloud's high-defense CDN enables 'minute-level' rapid onboarding, hiding the origin server while integrating defense and acceleration to help your business run smoothly through the storm.
How to Tell If Your Website Is Under DDoS or CC Attack: Four-Step Diagnosis and Response
When a website suddenly goes down, three things can roughly distinguish the cause: whether bandwidth and packet volume spike, whether you can still log in to the server, and whether access logs show a flood of requests.
Your Website Is Under a Large-Scale Attack: Fast CDN Onboarding Order and Lockdown Essentials
When an attack is already underway, mounting a CDN isn't just about registering an account. This article lays out the actual hands-on order: configure origin pull and certificates on the CDN side, verify the path with hosts, then switch DNS, then lock down the origin firewall or change IPs, and finally enable edge emergency mode—plus handling exceptions like TTL caching, API services that can't go through challenges, and an origin that's already been blackholed.
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.
