The purpose of this policy is to establish standards for the base configuration of internal server equipment that is owned and/or operated by ASCL. Effective implementation of this policy will minimize unauthorized access to ASCL proprietary information and technology.

2.0 SCOPE

This policy applies to server equipment owned and/or operated by ASCL, and to servers registered under any ASCL-owned internal network domain.

This policy is specifically for equipment on the internal ASCL network. For secure configuration of equipment external to ASCL on the DMZ, refer to the Internet DMZ Equipment Policy.

3.0 POLICY

3.1 Ownership and Responsibilities

1. All internal servers deployed at ASCL 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 the ASCL Information Security Department. 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 ASCL Information Security Department.

2. 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:
   
   
   • Server contact(s) and location, and a backup contact
     
   • Hardware and Operating System/Version
     
   • Main functions and applications, if applicable

3. Information in the corporate enterprise management system must be kept up-to-date.

4. Configuration changes for production servers must follow the appropriate change management procedures.

5. Any updation in the operating system or application running on the servers shall be done after a formal authorization from the management representative.

6. Strict control on user requests shall be as per the system capacities to prevent buffer overflow and other forms of denial of service attacks.

7. Restrictions on connection times are installed to provide additional security to high risk applications running on the server.

3.2 General Configuration Guidelines

1. Operating System configuration should be in accordance with approved InfoSec guidelines.

2. Services and applications that will not be used must be disabled where practical.

3. Access to services should be logged and/or protected through access-control methods such as TCP Wrappers, if possible.

4. The most recent security patches must be installed on the system as soon as practical, the only exception being when immediate application would interfere with business requirements.

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.

6. Always use standard security principles of least required access to perform a function.

7. Do not use root when a non-privileged account will do.

8. 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).

9. Servers should be physically located in an access-controlled environment.

10. Servers are specifically prohibited from operating from uncontrolled cubicle areas.

3.3 Monitoring

1. All security-related events on critical or sensitive systems must be logged and audit trails saved as follows:
   
   
   • All security related logs will be kept online for a minimum of 1 week.
     
   • Daily incremental tape backups will be retained for at least 1 month.
     
   • Weekly full tape backups of logs will be retained for at least 1 month.
     
   • Monthly full backups will be retained for a minimum of 2 years.

2. Security-related events will be reported to InfoSec, who will review logs and report incidents to IT management. Corrective measures will be prescribed as needed. Security-related events include, but are not limited to:

   1. Port-scan attacks

   2. Evidence of unauthorized access to privileged accounts

   3. Anomalous occurrences that are not related to specific applications on the host.

3.4 Compliance

1. Audits will be performed on a regular basis by authorized organizations within ASCL.

2. Audits will be managed by the internal audit group or the ASCL Information Security Department, in accordance with the Audit Policy. The ASCL Information Security Department 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. Every effort will be made to prevent audits from causing operational failures or disruptions.

4.0 ENFORCEMENT

Any person bound by this policy who intentionally and/or knowingly violates this policy shall be subject to action deemed fit by the Governing Board of the Asian School of Cyber Laws and shall also be liable to pay adequate and prompt compensation. Such action shall not preclude adequate civil and / or criminal remedy as per the applicable law.

5.0 DEFINITIONS

1. DMZ (De-militarized Zone): A network segment external to the corporate production network.

2. Server: For purposes of this policy, a Server is defined as an internal ASCL Server. Desktop machines and Lab equipment are not relevant to the scope of this policy.

6.0 REVISION HISTORY

This document is created on 12-02-2002 and has been last updated on 22-02-2003. Please note that this document is updated on a regular basis and the latest version can be obtained from: