In this network security policy, it is defined as a formal
statement of rules for people who are granted access to the organization
resources to abide (Temasek
Polytechinc, n.d.).
Since threats are ever-growing and ever-changing, hence network security policy
is a continuous cycle. In this cycle, it is divided into 4 phase, namely
secure, monitor, test and improve.
In secure stage, it will begin to implement things to
prevent any possible loss of information (Temasek Polytechinc, n.d.). This includes requiring
constant change of password and implementing firewall in the network.
In monitoring stage, it will be detecting any violation to
the policy (Temasek
Polytechinc, n.d.).
It normally involves the use of the Intrusion Detection System (IDS) to flag
any violations to network adminstrator.
In test stage, the organization will be performing
penetration testing or auditing the network system (Temasek Polytechinc, n.d.).
After gathering information from both monitoring and test
stage, the organization will be improving or create a new security policies
based on any vulnerability that is being surfaced in the organization (Temasek Polytechinc, n.d.). This stage is also known as
the improve stage.
Figure 1 (Security policy life cycle)
When developing security policy, the organization can decide
in three ways according to RFC 2196. Firstly, "Services offered versus
security provided." In this concept, the network administrator can decide
whether to provide the service (carries more security risks) or not to provide
the service (least benefits) (Tittel, 2003).
Secondly, "Ease of use versus security." Network
administrator can also decide between the ease of use (less secure) or
“user-unfriendly” interface (most secure). Hence, depending on the situation,
the network administrator will be deciding between these two extremities (Tittel, 2003).
Lastly, "Cost of security versus risk of loss."
Network administrator can decide between the costs of security (in terms of
performance, ease of use and cost) and loss when they didn’t implement. These
include the loss of information, privacy and service (Tittel, 2003).
References:
[Information security policy]. Retrieved
April 27, 2012, from: http://trustedtoolkit.blogspot.com/2007/07/information-security-policy-101_03.html
Temasek Polytechinc. (n.d.). L02 - Laws and ethics.
Singapore, Singapore, Singapore. Retrieved from SearchSecurity.
Temasek Polytechinc. (n.d.). Overview of
internetworking security. Singapore, Singapore, Singapore.
Tittel, E. (2003, August). The security policy
document library: site security handbook. Retrieved April 27, 2012, from
SearchSecurity:
http://searchsecurity.techtarget.com/tip/The-security-policy-document-library-Site-Security-Handbook