Network Security Library
Javascript Feeds    RSS Feed    Security Dashboard    SearchSecurity.com
About | Contact | Advertise | Site Map

Sample Policies


{LANG_NAVORIGIN} Security Policies Sample Policies

Subcategories


Acceptable Use Policies
Anti-Virus and Patching Policies
E-Mail Policies
Extranet Policies
Password Policies
Privacy and Confidentiality Policies
Remote Access Policies
Routing Policies
Wireless Policies



Disposal of Computer Hard Drives
Sanitization of hard drives is the process of removing sensitive information from storage media in a manner that gives assurance that the information cannot be recovered by keyboard or laboratory attack. Before the sanitization process begins, the computer should be disconnected from any external network to prevent accidental damage to the network operating system (OS) or other files on the network. In addition, when possible, users should audit the sanitizing process to ensure data is no longer retrievable. This means a knowledgeable person should witness the sanitization process and verify that the hard drive was sanitized.
By University of Arizona, 06/29/2004


Student E-mail Policy
There is an expanding reliance on electronic communication among students, faculty, staff, and administration at the University of Colorado at Boulder (CU-Boulder). This is motivated by the convenience, speed, cost-effectiveness, and environmental advantages of using e-mail rather than printed communication. Because of this increasing reliance and acceptance of electronic communication, e-mail is considered an official means for communication within CU-Boulder.
04/22/2004


Policy on Instant Messaging
IM software may be used for direct communications between individual team members. For example it may be used for working on particular tasks, to clarify issues when working on collaborative tasks and to support team working. IM may be particularly suited for short term tasks for which no archive is needed and other team members need not be involved - for example, arranging a meeting place.
04/09/2004


Vulnerability Assessment Policy
The first step in securing anything is to first assess the risk. A Vulnerability Assessment is one aspect of an overall Risk Assessment that involves actively finding insecure systems. Do to this "actively finding" nature of Vulnerability Assessments, quite a bit of coordination, management support, and information gathering has to be completed. Where are you going to find this assistance? Policy of course.
Mitchell Rowton, 02/19/2004


Server Security Policy
Defines standards for minimal security configuration for servers inside the organization’s production network, or used in a production capacity.
02/19/2004


Risk Assessment Policy
Defines the requirements and provides the authority for the information security team to identify, assess, and remediate risks to the organization’s information infrastructure associated with conducti
02/19/2004


Policy on Unauthorized Copying of Copyrighted Media
This policy states the disciplinary sanctions for violation of copyrights
02/19/2004


Policy on the Use of PennNet IP Address Space
This policy specifies the IP address registration requirements for devices connected to PennNet. It also provides "best practice" recommendations to guide local network administrators in the use of
02/19/2004


Policy on the Use of Ethernet Repeaters at PennNet Wallplates
This policy specifies the conditions under which an Ethernet repeater may be connected to a PennNet wallplate, and refers to a list of eligible locations. It also provides "best practice" recommenda
02/19/2004


Policy on the Operation of DHCP Servers on PennNet
s policy specifies the requirements for Dynamic Host Configuration Protocol (DHCP) servers and related infrastructure operating on PennNet. It also provides "best practice" recommendations for se
02/19/2004


Page: 1 23


Application Security
Architecture
Authentication
Certifications
Disaster Recovery
Encryption
Enterprise Security
Exploits
Firewall
Incident Handling
Intrusion Detection
Laws and Regulations
Malicious Code
Operating System
Security Basics
Security Management
Security Policies
Security Tools
Standards
Vulnerability Management
Web Security
Wireless Security

Newest
Highest Rated
Most Viewed
Reference

Javascript Feeds
RSS (New Papers)
Security Dashboard

About SecurityDocs
Advertise
Contact

Valid HTML 4.01!
Valid CSS!


Unless otherwise noted, all paper copyrights are owned by the author. The rest copyright 2003-2005 TechTarget

Privacy : Contact