Creating a security policy for your organization
Posted in Security, Services on March 1st, 2010 by Clint – 1 CommentBy Robin Tatam
If you are responsible for securing your organization’s IBM i environment, you know there are many steps. The step that many people overlook is creating a well-defined security policy. And, without this step, you can’t really evaluate how well you’re doing with security!
The majority of large corporations have policies that address access to different types of technology, but it is still rare to find one that pertains to the required settings for IBM i. It is even more unusual for smaller organizations to have any type of formal policy beyond a simple “best practices” list.
Even if you are not legally required to set up a security policy (to comply with Sarbanes-Oxley, HIPAA, or other security regulations), everyone has a certain level of fiscal or moral responsibility (to the company’s customers, vendors, and employees) to protect the information with which you are entrusted. When you set up a policy, you create a standard that allows you to achieve or maintain compliance with your objectives.
As I mentioned earlier, large corporations often have multiple policies. There may be an overall policy and multiple sub-policies that define the requirements with more granular detail. For example, an international corporation may have a policy that defines the main purpose for even having the policy, and policy objectives at a global level. Then, each country has a lower level policy that supports the global policy, but adds more information and requirements specific to the local level.
If the impetus for creating a security policy is not coming from senior management, it is critical that you convince a manager to sponsor your effort. Without sponsorship, you will struggle to obtain the necessary capital to design and enforce the policy, and compliance is unlikely to be achieved, let alone maintained.
Creating a security policy is not solely an IT responsibility, but should be the result of a steering committee that is charged with identifying the key areas to be addressed in the policy. Once a policy is established, the IT staff is responsible for planning and implementing the technical controls necessary to adhere to the policy. An auditor determines if the controls are adequate.
If a security policy is going to provide real benefit to the organization, it must be followed. Therefore, you need to:
- Introduce the security policy to make employees aware of it.
- Distribute copies to appropriate employees.
- Outline the penalties for willful non-compliance with the policy.
- Create a schedule of audits to:
- Build a gap analysis between the policy and controls
- Identify weaknesses in the policy, the mitigating controls, or the implementation of the controls.
- Establish a defined life span for the policy.
Your security policy needs to be a living document that is reassessed at least every two to three years to ensure the policy:
- Continues to meet the needs of the organization.
- Addresses technology and business changes that occur.
Whenever the steering committee updates the policy, they must communicate changes to the appropriate audiences in a timely manner.
Additional Resources
Policy Enforcement with Compliance Monitor
To manage the compliance of system values on your IBM i system, PowerTech’s Compliance Monitor includes a security policy editor. Use this policy management tool to run a dashboard-style scorecard on your system that indicates which values are out of compliance. For more information, visit the Compliance Monitor page on the PowerTech Web site.
Open Source Security Policy
If you don’t know how to get started on your own security policy, PowerTech provides a FREE policy template available for download. You should edit this “open source” document to meet your unique corporate requirements. If you think the changes you make might be of interest to other members of the IBM i community, please send them to us and we’ll review them for inclusion in a future edition.
Live Policy Discussion
As part of our ongoing education commitment to the IBM i security community, Jill Martin, PowerTech’s Product Support Manager, will be visiting the following cities next week to conduct FREE 3-hour workshops on crafting IBM i security policies.
| Date | City | Questions or RSVP |
| March 9 | San Francisco | Katie.Carnicom@helpsystems.com |
| March 10 | Irvine | Katie.Carnicom@helpsystems.com |
| March 11 | Las Vegas | Katie.Carnicom@helpsystems.com |

