Networking

01:51 PM
Natalie Timms
Natalie Timms
Commentary
50%
50%
Repost This

Secure Networks: How To Develop An Information Security Policy

A security policy is the foundation of a secure network, but it must balance security with business needs. Here are some guidelines for successful security policy development.

Security is often referred to as an overlay to a network topology. While security methods provide protection for access and infrastructure, these methods should be the result of a carefully defined security policy. An effective security policy integrates well-known protection methods into a network in a way that meets both security standards and the goals of the entity being secured.

An information security policy builds the foundation for a secure network, but it must be seen as valuable to an entity. The selling point for a security policy is showing how it maps to key business drivers such as:

• Improved efficiency through streamlined security processes that reduce operational expenses in terms of time, money and personnel.

• Increased productivity through well-defined and applied policies that correctly balance the level of access with perceived risk.

• Better agility, allowing for efficiency with respect to the implementation of compliance and regulatory objectives, migration strategies and risk mitigation techniques.

The deployment of network security features is the result of the approved security policy. Here are some important considerations that should be taken into account in security policy development:

• Remember that each entity will have its own objectives. To win support, a security policy's benefits must be apparent to each specific entity.

• It's critical to understand what you are trying to secure and why; if you don’t understand the underlying network, how can you secure it? Network addressing schemes, choice of routing protocol, and correct mapping of physical connections, such as switch ports to logical configurations, are basic components that must be understood.

• Clearly define network objectives in terms of business requirements and goals, for example: Performance and availability, including SLA requirements, capacity and potential growth, and efficient bandwidth usage; audit and logging requirements; monitoring/troubleshooting, including cost of downtime and acquisition of management tools; and provisioning model (for example, consider the need for multiple levels of control and change management processes.)

• Identify the type and levels of security required. Consider regulatory compliance requirements such as SOX and HIPAA.

[Read why information security pros should take the time to teach their friends and neighbors about security best practices in Be The Security Good Samaritan."]

• Identify applicable network best practices, both general and industry specific, such as IETF RFCs (1918, 3330, 2827, 3704), ISO frameworks (27001, 27002), and COBIT IT security standards.

• Integrate tools and technologies that can be mapped to a business objective. Areas to consider include authentication and encryption requirements for confidentiality, bandwidth management, application-level security, and multi-vendor versus single-vendor designs.

While security policy may be seen as the blueprint for applying protection over the network topology, in actuality it facilitates a layered view, allowing security to be integrated into the network by identifying key areas of a network design such as:

• Network devices, their placement, roles and capabilities.

• Software and hardware requirements for feature support, capacity, maintainability and migration strategies.

• Logical views mapped to physical plans.

• Addressing and identifiers used for identification of policy elements.

• Routing and forwarding methods for efficiency and applicability.

I plan to drill down into these areas in terms of secure design in upcoming blog posts.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
NatalieTimms
50%
50%
NatalieTimms,
User Rank: Apprentice
1/30/2014 | 4:13:18 PM
re: Secure Networks: How To Develop An Information Security Policy
If a security policy is clearly linked to what is of value to a business there is more likelihood of its longevity. Compliance requirements that are audited, reduction in IT fire-drills and of course measurable cost savings are some tangible measures of policy effectiveness. The reason most things fail are: too complicated, unrealistic implementation plans and lack of risk/reward analysis as it pertains to that specific organization. The other thing is to regularly review your policy, the threat landscape is always changing, if policy is not keeping pace it will be deemed ineffective.
NatalieT444
50%
50%
NatalieT444,
User Rank: Apprentice
1/30/2014 | 4:13:18 PM
re: Secure Networks: How To Develop An Information Security Policy
If a security policy is clearly linked to what is of value to a business there is more likelihood of its longevity. Compliance requirements that are audited, reduction in IT fire-drills and of course measurable cost savings are some tangible measures of policy effectiveness. The reason most things fail are: too complicated, unrealistic implementation plans and lack of risk/reward analysis as it pertains to that specific organization. The other thing is to regularly review your policy, the threat landscape is always changing, if policy is not keeping pace it will be deemed ineffective.
Guest
50%
50%
Guest,
User Rank: Apprentice
1/30/2014 | 4:10:14 PM
re: Secure Networks: How To Develop An Information Security Policy
As
with most things, there are no guarantees people with stick with the
program. That said, if a security policy is clearly linked to what is of
value to a business there is more likelihood of its longevity.
Compliance requirements that are audited, reduction in IT fire-drills
and of course measurable cost savings are some tangible measures of
policy effectiveness. The reason most things fail are: too complicated,
unrealistic implementation plans and lack of risk/reward analysis as it
pertains to that specific organization. The other thing is to regularly
review your policy, the threat landscape is always changing, if policy
is not keeping pace it will be deemed ineffective.
Drew Conry-Murray
50%
50%
Drew Conry-Murray,
User Rank: Apprentice
1/29/2014 | 4:13:50 PM
re: Secure Networks: How To Develop An Information Security Policy
Any advice on how to make sure the security policy doesn't just get shelved after it's written?
NatalieT444
50%
50%
NatalieT444,
User Rank: Apprentice
1/24/2014 | 5:44:26 PM
re: Secure Networks: How To Develop An Information Security Policy
I would focus on these 3 points to start:
1) Outline business objectives.
2) Identify compliance, regulatory and other security standard requirements and mandates.
3) Build a security policy rule set in terms of mapping users to services, and assigning actions to these flows.
Always understand the problem that needs to be solved.
NatalieTimms
50%
50%
NatalieTimms,
User Rank: Apprentice
1/24/2014 | 5:44:26 PM
re: Secure Networks: How To Develop An Information Security Policy
I would focus on these 3 points to start:
1) Outline business objectives.
2) Identify compliance, regulatory and other security standard requirements and mandates.
3) Build a security policy rule set in terms of mapping users to services, and assigning actions to these flows.
Always understand the problem that needs to be solved.
Marcia Savage
50%
50%
Marcia Savage,
User Rank: Apprentice
1/24/2014 | 12:50:34 AM
re: Secure Networks: How To Develop An Information Security Policy
Thanks for these guidelines Natalie. What should organizations focus on as a first step to developing a security policy?
More Blogs from Commentary
SDN: Waiting For The Trickle-Down Effect
Like server virtualization and 10 Gigabit Ethernet, SDN will eventually become a technology that small and midsized enterprises can use. But it's going to require some new packaging.
IT Certification Exam Success In 4 Steps
There are no shortcuts to obtaining passing scores, but focusing on key fundamentals of proper study and preparation will help you master the art of certification.
VMware's VSAN Benchmarks: Under The Hood
VMware touted flashy numbers in recently published performance benchmarks, but a closer examination of its VSAN testing shows why customers shouldn't expect the same results with their real-world applications.
Building an Information Security Policy Part 4: Addresses and Identifiers
Proper traffic identification through techniques such as IP addressing and VLANs are the foundation of a secure network.
SDN Strategies Part 4: Big Switch, Avaya, IBM,VMware
This series on SDN products concludes with a look at Big Switch's updated SDN strategy, VMware NSX, IBM's hybrid approach, and Avaya's focus on virtual network services.
Hot Topics
3
Converged Infrastructure: 3 Considerations
Bill Kleyman, National Director of Strategy & Innovation, MTM Technologies,  4/16/2014
2
Heartbleed's Network Effect
Kelly Jackson Higgins, Senior Editor, Dark Reading,  4/16/2014
White Papers
Register for Network Computing Newsletters
Cartoon
Current Issue
Video
Slideshows
Twitter Feed