Many website owners don’t pay enough attention to their site’s security. They often think “why would anyone target my site?”  But, it can happen. Websites are compromised all the time. There are several ways to help keep your site safe.

Make sure all your software is up to date.  This applies to both the server operating system and any software you may be running on your website such as a CMS or forum. Hackers are quick to attempt to abuse them when security holes are found in software. WordPress and many other content management systems notify you of available system updates when you log in. If you are hosting with a hosting company they should take care of this.

Use strong passwords to access your websites. Place scripts and tools in password protected directories.

Keep your error messages vague. Don’t give away too much info by providing hints. You should use generic messages like “Incorrect username or password” as not to specify when a user got half of the query right. If an attacker knows one of the fields is correct then they know they have one of the fields and can concentrate on the other field.
File uploads can be a big security risk.  Even the most innocent looking of files can contain a script that puts your website /server at risk. Don’t assume hidden files are secure.  It is recommended that you prevent direct access to uploaded files all together. Store the file outside of your document root. Create a separate directory and use it to store uploaded files.

Use an SSL Certificate. SSL is a protocol used to provide security over the Internet. It is a good idea to use a security certificate whenever you are passing personal information between the website and web server or database. Potential attackers could be searching for this information and if the communication medium is not secure use this information to gain access to user accounts and other personal data.
It is important to play it safe to keep both your website and servers secure.  Pay attention to passwords, files and software. In doing so you just might avoid a security disaster.



Over the course of the past decade, organizations have begun to rely significantly more on information technology (IT) systems to support business-critical applications. Organizations such as banks, telecommunications companies, internet service providers, and cloud/co-location facilities rely heavily on the availability of their data centers as many of their customers are paying a premium for access to a variety of IT applications.

Because of this reliance, the cost of downtime can be detrimental, and costly, to an organization. It was recently analyzed that the average cost of data center downtime was about $5600 per minute.

Additionally, based on an average reported incident length of 90 minutes, the average cost of a single downtime incident was about $505,500. These expenditures are based on many factors including data loss/corruption, productivity losses, equipment damage, root-cause detection and recovery actions, legal and regulatory repercussions, revenue loss and more. Costs such as losses in end-user and IT productivity also had a significant impact on the cost of an average downtime event. Human error is a fact of life. We should anticipate it; try to understand it; and make sure we learn from past mistakes so that we can minimize its occurrence and impact on our critical systems.



Recently, industry panelists described a world in which the increased standardization via  open sourcing, would lead  to the open data center community improving energy efficiency, reducing costs, and improving reliability.

Yet the discussion focused greatly on the improvements that the Open Source approach could bring. Once panelist said, “Innovation is a friend, gratuitous differentiation is our enemy.” The panelists also noted the customized approach to data center construction typical in the industry has led to a number of efficiencies that could be eliminated.

The open source approach is new to data centers, and significant organizational work remains to be done. The panel took several strides to developing a community, but many large players remain outside the circle for now, the group’s financial plan needs to be detailed, and most importantly, protocols need to be developed for the handling of intellectual property, both to protect the community and the organization that will be formed to evaluate new projects.


Page 1 of 13