The foundation of any security program should be based on risk. When security is addressed as a theoretical exercise, it is often a self defeating proposition. I have seen both in an academic setting where instructors teach security concepts as absolutes and in a professional setting when that absolutist approach lead to conflict, resentment and backlash. A risk-based approach to security is a practical approach to security. One must first, however, explore two crucial questions: What is risk and risk to what? The answers vary from enterprise to enterprise and each organization must go through the process of determining for itself the answers. In the absence of this, organizations tend to seek out “best practices” and follow them without contemplating their necessity.
Risk is an ever changing probability that a vulnerability, weakness, or lack of security control will be exploited by threat agent ( hacker, careless employee, natural disaster, etc ) leading to negative consequences to an organization. Simply put, the chances that something bad will happen. There will always be some degree of risk however a robust security program must be able to reduce it to a level acceptable to the organization’s management. That is referred to as risk management. I recently had a consultation with a small account firm that was about to lose its “IT guy”. He handled everything technical from configuring outlook on desktops to managing the company’s server which host their mission critical applications and was co-located “somewhere”. He visited the server several times a month apparently and no one knew why he went or what he did there. There was no documentation of any kind. He was about to leave in less than a week and they were in a state trying to find a replacement. As seen in this example, single person dependencies are par for the course in small enterprises such as this but that leads to considerable risk, especially when the person is unhappy and leaving. My first advice to them was to have him document ( as best he could ) everything he did on a daily basis and why. Hopefully a lesson learned here would be to have his replacement do the same routinely.
As to the object of this risk, we have to refer to the three main principles of security: Confidentiality, Integrity and Availability. A security program, regardless of the size of the enterprise, should protect against the risk of unauthorized disclosure and modification of an organization’s data and ensure that it’s data and resources are available as needed. Risk management should include data, personnel, processes and physical and technical assets.
With those two concepts as a foundation, in this series, I will seek to outline steps to achieving practical security management.

