ࡱ> dfc% gbjbj%% ",GGMl...8f$$!r(fqhqhqhqhqhqhq$s uqq q8 fq fq ) mfq oѓaAn.E <&pFfqqH!rlp}v }vfq NOAO 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 NOAO. Effective implementation of this policy will minimize unauthorized access to NOAO proprietary information and technology. 2.0 Scope This policy applies to server equipment owned and/or operated by NOAO. This policy is specifically for equipment on the internal NOAO network, whether available directly from outside the NOAO network via the public Internet or devices specifically configured or firewalled as internal-to-NOAO access only. Desktop machines and Lab equipment are not relevant to the scope of this policy. 3.0 Policy 3.1 Ownership and Responsibilities All internal servers deployed at NOAO must be owned by an operational group that is responsible for system administration. If the server is operated by a group outside the two CIS departments, information about the server, particularly a point-of-contact, will be provided to the CIS Departments and kept up to date.Approved server configuration guides must be established and maintained by each operational group, based on business needs and approved by the CIS Departments. 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 the CIS Departments. 3.1.1 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: 3.1.1.1 Server contact(s) and location, and a backup contact 3.1.1.2 Hardware and Operating System/Version 3.1.1.3 Main functions and applications, if applicable 3.1.2 Information in the corporate enterprise management system must be kept up-to-date. 3.2 General Configuration Guidelines 3.2.1 Operating System configuration should be done in collaboration with CIS.in accordance with approved CIS Departments guidelines. 3.2.2 Services and applications that will not be used must be uninstalled or disabled where practical. 3.2.3 Access to services should be logged and/or protected through access-control methods such as TCP Wrappers, if possible. 3.2.4 The most recent security patches must be installed on the system as soon as practical, the only exception being when the immediate application of patches/updates would interfere with business requirements. 3.2.5 Trust relationships between systems are a security risk, and their use should be avoided. Do not use a trust relationship when some other method of communication will do (i.e., use ssh instead of rsh). 3.2.6 Always use standard security principles of least required access to perform a function, i.e., do not use root when a non-privileged account will do. 3.2.7 If a methodology for secure channel connection is available (i.e., technically feasible), privileged access must be performed over secure channels, (e.g., encrypted network connections using ssh or IPSec). 3.2.8 Servers should be physically located in an access-controlled environment. 3.2.9 Servers are specifically prohibited from operating in uncontrolled cubicle areas. 3.2.10 Servers will be backed up according to the NOAO Backup Policy. 3.3 Monitoring 3.3.1 All security-related events on critical or sensitive systems must be logged and audit trails saved. as follows: 3.3.1.1 All security related logs will be kept online for a minimum of 1 year. 3.3.1.2 Weekly full backups of logs will be retained for at least 1 month. 3.3.1.3 Monthly full backups of logs will be retained for a minimum of 2 years. 3.3.2 Security-related events will be reported to the CIS Department, who will review logs and report incidents. Corrective measures will be prescribed as needed. Security-related events include, but are not limited to: 3.3.2.1 Port-scan attacks 3.3.2.2 Evidence of unauthorized access to privileged accounts 3.3.2.3 Anomalous occurrences that are not related to specific applications on the host. 3.4 Compliance 3.4.1 Audits will be performed on a regular basis by the CIS Departments.authorized organizations within NOAO. 3.4.2 The internal audit group of the CIS Departments, in accordance with the NOAO Audit Policy, will manage audits. The CIS Departments will filter findings not related to a specific operational group and then present the findings to the appropriate support staff for remediation or justification. 3.4.23 Every effort will be made to prevent audits from causing operational failures or disruptions. 4.0 Revision History Updated: May 16, 2006 Updated November 19, 2006 First Edition: March 15, 2007Updated: February 19, 2007 Revised: September 16, 2009     NOAO Server Security Policy Page  PAGE 2 of  NUMPAGES 2 +hl~9GQB  C b  V ο顿钃teOJPJQJ^JcHdhrfHhsfOJPJQJ^JOJPJQJ^JcHdhnfOJPJQJ^JcHdhofHhofOJPJQJ^JOJPJQJ^JcHdh{fOJPJQJ^JcHdhmfOJPJQJ^JcHdhlf5OJPJQJ\^JOJPJQJ^J5CJOJPJQJ\^J#+:GQ  O P ^ 8^8`^`^` 8^8`$a$fV X ;NQ`)`o stν碓uduUFFUFOJPJQJ^JcHdhvfHhvfOJPJQJ^J OJPJQJ]^JcHdhufOJPJQJ^JcHdhufOJPJQJ^JcHdhwfOJPJQJ^JcHdhtfHhtfOJPJQJ^J5OJPJQJ\^J Hhzf6OJPJQJ^JHhyfOJPJQJ^JOJPJQJ]^JOJPJQJ^JOJPJQJ^JcHdhqf Y @ ^ PQ`)v ,^`,^L8xC$Eƀyf^8`x 8x^8`x_`o tuCEƀE& 8x^8`x^  ^tu "#%CGHNȷȭzuuuuj]L?0JCJOJQJ^JaJ!j0JCJOJQJU^JaJCJOJPJQJ^JaJCJOJPJQJ^J jU OJPJQJ\^JcHdhvf HhvfOJPJQJ\^J HhDFOJPJQJ\^JOJPJQJ\^J OJPJQJ\^JcHdhDF OJPJQJ\^JcHdhCF#5OJPJQJ\^JcHdhCF5OJPJQJ\^JOJPJQJ^J!"$%defgDC$Eƀvf NOPQUV`abcdfgOJPJQJ\^JCJOJQJ^J0JCJOJQJ^JaJ#0JCJOJQJ^JaJmHnHu!j0JCJOJQJU^JaJ 1h/ =!"#$% i8@8 NormalCJ_HaJmH sH tH <A@< Default Paragraph Font<Z@< Plain TextCJOJQJ^JaJ,, Header  !, @, Footer  !&)@!& Page Number@2@  Balloon TextCJOJQJ^JaJg,+:GQOPY@  ^ P Q ` )v_`o tu!$deh00000000000000000000000000000000000000000000000000000000@0@0@0@0@0@0 0 LLLOV tNg  gf.57<GIO!8@0(  B S  ? M P !"$%ehYh@ J  " ^ l ` j o|!"$%eh333333333333333333 Sue HayesY:\server_security.doc Sue Hayes%Y:\admin\cybersec\server_security.doc SwNBad  " =}F͠38?%["`qdzL T`/$F7&TQ)kZjS)zF77 *5tJ<+5>+y=|h/~>d,h!@&uDTBE >L*PB[NJ4QlR@dPVdLQlRdPVS)E5uH_Q)y=`/$ >+qd ,Ubn0}BESw"?@ABCDEFGHIJKLMNOPQRTUVWXYZ\]^_`abeRoot Entry FoѓaAg1Table}vWordDocument",SummaryInformation(SDocumentSummaryInformation8[CompObjjObjectPooloѓaAoѓaA  FMicrosoft Word Document MSWordDocWord.Document.89q