
Originally Posted by
ViAdCk
I appreciate your input but we're talking 1000s of domains and users here. We obviously remind our clients constantly about good security practices but the truth is, a lot of people just don't follow these guidelines. And that's why we need a global protection level at the server level, without causing users trouble.
UH sorry!Then it even more important to have a more secure way at default, and instructions with it, oldfashion less secure to be more customer friendly is deadly nowadays! ( only secure and mode ways should be allowed to connect annd have acces to that kind of accounts shared and so on!
Your handling for that makes it very ( to easy) for hackers and BOTS, to set up DDOS an other culprick that attacks (ouR) other servers and places.
You are the first responsible to have and set enough security on your boxes and to let yor customers in with only secure enough practices and strict folowing guidlines. ( if your boxes proofed to be hacker source or used by hackers you have also problems if your are to ..... )
Let me guess do you change automaticly/force every admin/user password after some time?
You can force some basic Content security policy's in your hosts file for example to ( friendly) force your clients to a better and safer use of their sites. ( ofcourse providing them with instructions and so on) Then shift the good/secure client and bad/unsecure clienst to different boxes be transparant and tell them on wich box they are. ( the ones with clients that respect your security guidelines, or the one that have some disrespect ( old not updating software, passwords to easy, old no more secure apps / protocols and so on )
So the can choose the be on the more secure box if they work secure themselves to!
No normal Customers wants to be on a messy BOX where to much is possible to hapen.....
Don''t take my post personal, but these kind of handling and way of using in IT is maybe the main cause of so much and Bot problems!
IN a howto ( only your users have acces) you could have default safe configs for winscp for example with custom port, path and bashshell, then they only have to supply themselves user and pass....
Blocking IP's in my opinion is only helpfull to have less .... traffic as also the brute force.., but for security itself you have to have strict rules/settings and workingpolicies!
DirectAdmin Forums...
ما را در سایت DirectAdmin Forums دنبال میکنید
برچسب: نویسنده: ایمان اصلاحی بازدید: 304 تاريخ: شنبه 7 بهمن 1396 ساعت: 13:22