You’ve heard it before: information security isn’t easy. There’s no perfect security policy or piece of technology that will protect your business from all attacks. However, security is a process and processes can always be improved.
When choosing your email provider, the security of your users’ data should be a top priority. Email routinely contains confidential and proprietary information both to your business and to individual users. It’s likely there is information about your business plans, financial projections and human resource data residing in a string of emails. How can you make sure this information remains private and only accessible to the intended recipients? Can you risk hours or even days of email downtime due to a virus that employees unknowingly spread?
Recent activity with the Heartbleed vulnerability has the industry reeling and re-evaluating their security controls. We recently posted about the Rackspace response to this event, but while security is top-of-mind we’d like to share a new white paper on the topic of “Cloud Security in an Agile World.”
Part of our Fanatical Support promise is to ensure the security and health of your systems. It is of the utmost importance to us. So when the entire Linux Community, including Rackspace, was notified yesterday of the “Heartbleed” vulnerability within OpenSSL (CVE-2014-0160), the encryption software found in many Linux systems, we began plans to proactively patch your affected servers where we could.
At Rackspace, Fanatical Support is part of everything we do, especially when it comes to security. We work hard to secure your environment using tools, technology, policies, procedures and different teams with different specializations and skills.
We’ve all experienced it before – an inadvertent change that caused a cascading failure. It could be the change of a file’s headers that caused a script to fail. Or the removal of a node from a load balancer that is causing high response times. Or even the new guy who cuts his teeth by deleting a production server accidentally.
Time-based access tools are a great way to give someone temporary access to your code or service. It’s like going on vacation and giving your neighbor the keys to your house; the only difference is the keys automatically stop working when you get back from your trip. There are several tools that developers can use if they want to grant access based on a time restriction.