Security server

1.0 Destination
The aim is to establish standards for the basic configuration of internal server equipment That is Owned and / or operated by “Company Name”. owned and / or operated by “Company Name”. Effective implementation of this policy will from minimized Effective implementation of this policy will minimize unauthorized access to “Company Name” proprietary information and technology. possession of unauthorized access “Company Name” and information technology.

2.0 Scope 2.0 Scope
This policy applies to server equipment Owned and / or operated by “Company Name”, and to servers This policy applies to server equipment owned and / or operated by “Company Name”, and to the server registered under any “Company-Owned Name” internal domain network. listed under each domain's internal network “Company Name“. This policy is specifically for equipment on the internal network “Company Name”. This policy specifically for network equipment in the “Name internal Company”. To secure safe for configuration of equipment external to “Company Name” on the the DMZ, refer to the Internet to the DMZ configuration of external devices “Company Name” in the DMZ, refer to the DMZ Internet Equipment Policy. Policy tools.

3.0 Policy 3.0 Policies
3.1 Ownership and Responsibilities.
All internal servers deployed at “Company Name” must be Owned by an operational group That Is All internal servers are placed in “Company Name” must be owned by an operational group responsible for system administration. responsible for system administration. Approved server configuration guides must be established and guidelines Approved server configuration should be built and
Maintained by Each operational group, based on business needs and approved by InfoSec. managed by each operational group, based on business needs and approved by InfoSec. Operational Operational Should groups monitor configuration compliance and implement an exception policy tailored to on their groups should monitor configuration compliance and implement an exception policy tailored to their environment. environment. Each operational group must establish a process for changing the configuration guides, Which Each operational group must establish a process to change the configuration wizard, which includes the review and approval by InfoSec. includes review and approval by InfoSec.

• Servers must be registered within the corporate enterprise management system. Servers must be registered in the corporate enterprise management system. At a minimum, the very least, the
Following information is required to positively identify the point of contact: The following information is needed to positively identify the point of contact.
• Server contact (s) and location, and a backup contact contact server (the Company) and location, and contacts backup
• Hardware and Operating System / Hardware Version and Operating System / Version..
• Main functions and applications, if applicable functions and the main application, if applicable.
• Information in the corporate enterprise system management must be kept up-to-date. The information in corporate enterprise management system must be kept up-to-date.
• Configuration changes for production servers must follow the appropriate change management configuration changes for production servers must follow the appropriate change management Procedures. procedure.

3.2 General Configuration General Configuration Guide Guidelines.

• Configuration Operating System Should be in accordance with guidelines approved InfoSec. Operating System configuration should be in accordance with guidelines approved by InfoSec.
• That will of Services and applications must not be Used Nowhere disabled be practical. Services and applications will not be used must be disabled where practical.
• Access to services Should be logged and / or protected through access-control methods TCP Poor 'Access to services should be logged and / or protected through access control methods such as TCP Wrappers, if possible. Packaging, if possible.
• The most recent security patches must be installed on the system as soon as practical, only the most recent security patches must be installed on the system as soon as possible, the only Pls exception being the immediate application would interfere with business requirements. exception being when immediate application would interfere with business requirements.
• Trust relationships Between systems are a security risk, and on their use-Should be avoided. Trust relationships between systems is a security risk, and its use should be avoided. Do not No Pls use a trust relationship Some other method of communication will from do. using the trust relationship when some other methods of communication will be done.
• Always use the security standard principles of least required access to perform a function. Always use standard security principles of minimal access required to perform the function.
• Do not use root when a non-privileged account will do.
• If a methodology for secure channel connection is available (ie, Technically feasible), privileged If a methodology for secure channel connection is available (ie, technically feasible), privileged access must be Performed over secure channels, (eg, encrypted network connections using SSH access should be made through secure channels, (eg, encrypted network connections using SSH or IPSec). or IPSec).
• Servers Should be physically located in an access-controlled environment. Servers must be physically located in access-controlled environment.
• Servers are specifically prohibited from operating from uncontrolled cubicle areas. Server specifically banned from uncontrolled cubicle areas.

• 3.3 Monitoring 3.3 Monitoring

• All security-related events on critical or sensitive systems must be logged and audit trails saved as all activities related to security at critical or sensitive systems must be logged and stored as an audit trail Mutation of the following:
• The Daily incremental tape backups will from be retained for at least 1 month. additional daily tape backups will be stored for at least 1 month. Weekly full tape backups of logs will from be retained for at least 1 month. Weekly full tape backups of logs will be stored for at least 1 month.
• Monthly full backups will from be retained for a minimum of 2 years. Monthly full backups will be retained for a minimum of 2 years.
• Security-related events will from be reported to InfoSec, Who Will review logs and report incidents to IT Security Related events will be reported to InfoSec, who will review logs and incident reports to the IT management. management. Corrective measures will from be prescribed as needed. corrective action will be set according to requirement. Security-related events include, Related Security events include, BUT are not limited to:, but not limited to:
• Port-scan attacks, port scan attack
• Evidence of unauthorized access to privileged accounts Evidence of unauthorized access to personal account.
• That anomalous occurrences are not related to specific applications on the host. Anomalous events that are not related to specific applications on the host.

thanks... Please give advice.