{"id":1134,"date":"2025-08-06T16:42:52","date_gmt":"2025-08-06T16:42:52","guid":{"rendered":"https:\/\/www.prolimehost.com\/blogs\/?p=1134"},"modified":"2025-08-06T16:48:39","modified_gmt":"2025-08-06T16:48:39","slug":"common-sense-security","status":"publish","type":"post","link":"https:\/\/www.prolimehost.com\/blogs\/common-sense-security\/","title":{"rendered":"Common Sense Security"},"content":{"rendered":"

\"CommonYears ago, a well-known web host sent a message to its clients about a security breach<\/a> of one of its employee accounts. They followed that with this thread in their forum.<\/p>\n

This morning, we sent a notification to a group of our customers possibly affected by a compromised employee<\/em> account\u2019s access to our internal customer management portal. We will be sending an additional communication to all customers with information about the apparent security breach, but in the meantime, we would like to answer any additional questions about the communication in this thread.<\/em><\/p>\n

Please understand that we will not provide specifics information about the security breach due to the sensitive nature of the investigation, but we will do our best to provide as much detail as possible. As we assured in the note, based upon our security review of access logs, we do not believe any credit card information was compromised.<\/em><\/p>\n

We strongly suggest you implement a security best-practices approach by immediately taking four steps to mitigate risk:<\/em><\/p>\n

\u20221. Change your xxxxx log-in passwords immediately and do so again every 60 days.<\/em>
\n \u20222. Change your server passwords and do so again every 60 days.<\/em>
\n \u20223. Be alert to any suspicious activity on your account.<\/em>
\n \u20224. If you suspect any unusual activity, please retain your access logs along with any other information and contact us as soon as possible.<\/em><\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n