უსაფრთხოება5 წუთის საკითხავი
What we actually do about attacks, and what we do not
Filtering, rate limits, and an honest account of what a hosting provider can and cannot protect you from.
ეს სტატია ჯერ ინგლისურადაა. ვთარგმნით.
Every host advertises protection. Most of them mean the same thing: upstream filtering that drops obvious volumetric floods before they reach the machine. That is real and it is worth having. It is also not everything, and the difference is worth stating plainly.
What filtering handles
- Volumetric floods - large amounts of traffic aimed at saturating the link.
- Reflection and amplification, which is most of what a booter service actually sends.
- Malformed traffic that no legitimate client would produce.
What it does not
Traffic that looks exactly like a player is not distinguishable from a player at the network layer. An attack that opens real connections and makes real queries is an application problem, and it is solved with rate limits, query caching and a whitelist - not with a bigger pipe.
What you can do that helps more than anything we do
- Do not publish your server's address in places you would not publish your home one.
- Use the query port sparingly - server list scrapers are also how attackers find you.
- Keep RCON on a password nobody has seen, and never in a screenshot.
- If you run a community, assume someone in it will eventually be the problem.
A host that promises no downtime under any attack is selling you a sentence, not a service.