Pages

Friday, October 16, 2009

More on Website Security Plans

I recently read an article by Gary Kessler, professor at Champlain College. In his article on Securing your Website, Mr. Kessler recommends that we ask ourselves five questions:

  • “What are you trying to protect?
  • From whom are you protecting it?
  • What is the likelihood of an attack and what kind of attack is most likely?
  • What are the possible results of an attack or compromise?
  • How much protection can I afford?”

While some of the answers to these questions may seem obvious, it is essential and very useful to reflect on the issues and clarify the answers. The assessment process with provide an opportunity to review and analyze the current state of security, and identify the assets to be protected, which include hardware, software, data, documentation and people. Categorizing information and establishing a sensitivity scale will be helpful in this process. It is essential to reflect on threats and evaluate the exposure for assets and services. The formula

R (Risk) = A (Asset) *T (Threat) * V (vulnerability)

is helpful in assessing a site’s changing security risk. Even though there are risks for every server, there is no “package deal” for security. While there are recommendations for network and web server security, each organization has individual and specific needs. It is essential to asses these individual needs and develop a security plan in accordance.

The planning process is likely to take time and in the meantime it is crucial to develop an interim plan to protect a network and web server.

According to Microsoft’s Publication Security Guide for Small Business “A good plan today is better than a perfect plan tomorrow. Planning for security is a cyclical and repetitive process so it makes sense to execute a quick plan now and refine it later.” During this process it is important to remember that “the objective is not to eliminate all risks regardless of the cost, but to minimize the risk as much as possible. There are three main tradeoffs:

  • Factuality versus security needed
  • Ease of use versus security
  • Cost of security versus risk of loss” (Microsoft p.50, Creating a Security Plan).

During the planning stages it is likely for a team to collaborate and establish guidelines and recommendations, as well as document the process of planning. Many organizations use checklists, such as the Rutgers State University of New Jersey resource. This checklists provides a series of questions regarding many aspect of network and server security. Some of the most obvious questions may prove to be the most difficult, and possibly the easiest to overlook. The checklist approach may provide “baseline” security information, which would allow a security department to review this information and establish further recommendations to departments. Security questionnaires should include questions about hardware, software, network and environmental risks, as well as duties and responsibilities, users, and user security, physical security and network configuration security. Disaster planning and continuity, as well as backup and recovery, patching, software licensing, anti virus software, and network security should also be included. It is also crucial to include plans for disaster recovery and a plan for dealing with a security breach. One of the most important (and most frequently overlooked) aspects is ongoing user training and support.