Server Security Policy
Server Security Policy
| Field | Value |
|---|---|
| Document ID | POL-020 |
| Classification | Internal |
| Owner | CTO (interim CISO) |
| Effective Date | April 2026 |
| Review Cycle | Annual |
1. Overview
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.
2. 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 Wealthy.
Effective implementation of this policy will minimize unauthorized access to Wealthy proprietary information and technology.
3. Scope
All employees, contractors, consultants, temporary and other workers at Wealthy and its subsidiaries must adhere to this policy.
This policy applies to server equipment that is:
- Owned, operated, or leased by Wealthy
- Registered under a Wealthy-owned internal network domain
4. Policy
4.1 General
All internal servers deployed at Wealthy 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.
Server Registration Requirements
Servers must be registered within the management system. At a minimum, the following information is required to positively identify the point of contact:
| Information | Description |
|---|---|
| Server contact(s) | Primary and backup contact |
| Location | Physical or virtual location |
| Hardware | Hardware specifications |
| Operating System/Version | OS and version information |
| Main functions and applications | If applicable |
Additional Requirements
- Information in the 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
4.2 Configuration Requirements
| Requirement | Description |
|---|---|
| Operating System | Configuration should be in accordance with approved InfoSec guidelines |
| Unnecessary Services | Services and applications that will not be used must be disabled where practical |
| Access Logging | Access to services should be logged and/or protected through access-control methods such as a web application firewall, if possible |
| Security Patches | 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 | 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 |
| Least Privilege | Always use standard security principles of least required access to perform a function. Do not use root when a non-privileged account will do |
| Secure Channels | 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) |
| Physical Location | Servers should be physically located in an access-controlled environment. All access should be done through gateways or jump servers |
| Prohibited Locations | Servers are specifically prohibited from operating from uncontrolled cubicle areas |
4.3 Monitoring
Log Retention Requirements
All security-related events on critical or sensitive systems must be logged and audit trails saved as follows:
| Log Type | Retention Period |
|---|---|
| Security related logs (online) | Minimum 1 week |
| Daily incremental tape backups | At least 1 month |
| Weekly full tape backups | At least 1 month |
| Monthly full backups | Minimum 2 years |
Security Event Reporting
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
- Evidence of unauthorized access to privileged accounts
- Anomalous occurrences that are not related to specific applications on the host
5. Policy Compliance
5.1 Compliance Measurement
The Infosec team will verify compliance to this policy through various methods, including but not limited to, business tool reports, internal and external audits, and feedback to the policy owner.
5.2 Exceptions
Any exception to the policy must be approved by the Infosec team in advance.
5.3 Non-Compliance
-
An employee found to have violated this policy may be subject to disciplinary action, up to and including termination of employment.
-
A violation of this policy by a temporary worker, contractor or vendor may result in the termination of their contract or assignment with Wealthy.
-
Any program code or application that is found to violate this policy must be remediated within a 90 day period.