Unsecured and vulnerable servers continue to be a major entry point for malicious threat actors. Consistent server installation policies, ownership and configuration management are all about doing the basics well.

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

General Requirements

All internal servers deployed at CrowdFiber 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. The following items must be met:

  • 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
  • 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
  • For security, compliance, and maintenance purposes, authorized personnel may monitor and audit equipment, systems, processes, and network traffic per the Audit Policy.

Configuration Requirements

  • 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 methods such as a web application firewall, if possible.
  • 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.
  • 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 is sufficient.
  • Always use standard security principles of least required access to perform a function. Do not use root when a non-privileged account will do.
  • 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).
  • Servers should be physically located in an access-controlled environment.
  • Servers are specifically prohibited from operating from uncontrolled cubicle areas.

Monitoring

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.

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:

  • Port-scan attacks inside the internal network
  • Evidence of unauthorized access to privileged accounts
  • Anomalous occurrences that are not related to specific applications on the host