7 Habits of Highly Secure Organizations Part I
Posted in Other, Security on August 26th, 2010 by Robin – Be the first to commentHi everyone!
One of the presentations I make to the IBM i community is coyly entitled “7 Habits of Highly Secure Organizations.” Although the title is just a play on the name of the famous series of books by motivational speaker Stephen R. Covey, its message is intended to identify several important habits that companies need to consider as part of an overall strategy for becoming secure, and then compliant. I am not really suggesting that these are the only habits you’ll need, but these ones are imperative for those organizations struggling to get started.
I have listed all seven of the habits below, and over the next few weeks I will give an explanation of what I feel each of them might mean to your organization.
- Habit 1: Break The Ostrich Syndrome
- Habit 2: Develop a Security Policy
- Habit 3: Assess Current Standing
- Habit 4: Perform Security Event Logging and Review
- Habit 5: Use Existing “Best-of-Breed” Technologies
- Habit 6: Monitor For Ongoing Compliance
- Habit 7: Plan For The Future
Habit 1: Break the Ostrich Syndrome
The first habit to adopt—or break, depending on how you look at it—is to realize and acknowledge that the IBM i server is NOT inherently secure. Realize that I said secure and not securable, and the distinction comes from the fact that the server ships from the factory with its security configuration pretty much wide-open. To be fair, IBM has never said that you are going to be secure simply by plugging your IBM i into an AC outlet, but it’s staggering how many assessments we perform showing critical application data openly accessible to users of tools like Microsoft Excel or FTP.
Application developers often do not put much thought into that aspect of their programs; even many commercial application vendors add very little value when it comes to securing the data within their application.
Mitigation of security risk usually takes money, often takes time, and definitely takes expertise, but we all know that these three factors—money, time, and skill—are not things that just fall from the sky. Habit #1 requires us to acknowledge that there is some level of risk, and that we need to plan for the appropriate application of all three factors to bring that risk to an acceptable level.
After that, rest assured that the IBM i is one of the most securable servers on the market!
Habit 2: Develop a Security Policy
If you don’t have a policy to oversee the numerous security controls and procedures in your environment—both for IBM i and beyond—then you stand very little chance of being able to maintain a clean configuration for any period of time. The bottom line is that computer servers don’t secure themselves! Even with the best of intentions, we are only human and usually become complacent unless we have controls and procedures in place to keep us true to those intentions.
Consider starting out by developing a policy based on industry best-practices. From there, customize the policy in conjunction with an assessment of the level of compliance of your current environment. This allows the determination of an appropriate balance between allowing the business to function, and affording it the security that prevents it from being abused.
It’s important that the security policy not be designed and implemented only by the IT department. This is not unusual, but to be successful there needs to be executive sponsorship and management buy-in. This ensures that the standards contained within the policy are consistent with the corporate directives and can be enforced; It’s tough to enforce strong password rules when the CEO doesn’t agree and writes his down on a post-it note!
Don’t make the mistake of having executives involved in technical decisions—they may not understand nor care—but instead place the responsibility for interpreting and documenting how to secure specific systems in the hands of a security officer, and task the security administrator with setting and monitoring the configuration involved to be compliant with the security policy.
The security policy should be a dynamic document with a defined lifespan. This helps to ensure that it stays abreast of changes in your business, your industry, and the types of technologies that your organization leverages.
Join me here next week, when we’ll discuss more habits of highly secure organizations.
Drop me a line at robin.tatam@powertech.com for more information about PowerTech, or visit www.powertech.com.
Cheers!
- rt

Last weekend, I spent a few days up at the (much) cooler Lake Superior—a quick 2 hour drive from the Twin Cities. Although the drive along the North shore is renowned for its spectacular Fall colors, the scenery along the way was still very beautiful and afforded me the two photographic images included here. The first is of the dramatic
One of the initiatives that the PowerTech staff is currently working on is to give our open-source security policy a facelift. This popular document will continue to be a free resource to the IBM i security community, and we invite anyone to download, edit, and return the changes to us for possible (and credited) inclusion in a future edition. If you do not currently have a security policy—and a surprising number of ‘i’ shops don’t—then this is a great place to get started. Look for the announcement of the publication of this updated document in a future blog/twitter/newsletter posting.
Robin Tatam is the Director of Security Technologies for
Jill Martin