Server Security Policy

Only available on StudyMode
  • Download(s) : 17
  • Published : May 12, 2013
Open Document
Text Preview
Server Security Policy
1.0 Purpose The purpose of this policy is to establish standards for the base configuration of internal server equipment that is owned and/or operated by . Effective implementation of this policy will minimize unauthorized access to proprietary information and technology. 2.0 Scope This policy applies to server equipment owned and/or operated by , and to servers registered under any -owned internal network domain. This policy is specifically for equipment on the internal network. For secure configuration of equipment external to on the DMZ, refer to the Internet DMZ Equipment Policy. 3.0 Policy 3.1 Ownership and Responsibilities All internal servers deployed at must be owned by an operational group that is responsible for system administration. Approved server configuration guides must be established and maintained by each operational group, based on business needs and approved by InfoSec. Operational groups should monitor configuration compliance and implement an exception policy tailored to their environment. Each operational group must establish a process for changing the configuration guides, which includes review and approval by InfoSec. • Servers must be registered within the corporate enterprise management system. At a minimum, the following information is required to positively identify the point of contact: o Server contact(s) and location, and a backup contact o Hardware and Operating System/Version o Main functions and applications, if applicable Information in the corporate enterprise management system must be kept up-to-date. Configuration changes for production servers must follow the appropriate change management procedures.

• •

3.2 General Configuration Guidelines • Operating System configuration should be in accordance with approved InfoSec guidelines. • Services and applications that will not be used must be disabled where practical. • Access to services should be logged and/or protected through access-control...
tracking img