Security Statement

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 OrgSync. It will also set forth the agreement regarding network security scanning offered by SecurityMetrics to OrgSync to perform electronic scans of Orgsync’s networks and/or firewalls on any system at OrgSync. Effective implementation of this policy aims to eliminate unauthorized access to OrgSync’s proprietary information and technology.

Audits may be conducted to:

  • Ensure integrity, confidentiality and availability of information and resources
  • Investigate possible security incidents
  • Monitor user or system activity where appropriate.

2.0 Scope

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

This policy is specifically for equipment on the internal OrgSync network. SecurityMetrics will not perform Denial of Service (DoS) activities.

3.0 Policy

When requested, and for the purpose of performing audits, consent to access OrgSync assets will be provided to SecurityMetrics. OrgSync will allow SecurityMetrics to access its networks and firewalls to the extent necessary to allow SecurityMetrics to perform the requisite scans. OrgSync shall provide protocols, addressing information, and network connections sufficient for SecurityMetrics to utilize the software to perform network scanning.

This access may include:

  • User level and/or system level access to any computing or communications device
  • Access to information (electronic, hardcopy, etc.) that may be produced, transmitted or stored on OrgSync equipment or premises
  • Access to work areas (labs, offices, cubicles, storage areas, etc.)
  • Access to interactively monitor and log traffic on OrgSync networks.

3.1 Ownership and Responsibilities

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.

3.2 General Configuration Guidelines

  • Operating System configurations should be in accordance with approved OrgSync guidelines.
  • Services and applications that are out-of-service must be disabled where practical.
  • Access to services should be logged and/or protected through access-control methods such as TCP Wrappers.
  • 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 constitute a security risk, and should be avoided where possible.
  • Always use standard security principles of least required access to perform a function.
  • Do not use root when a non-privileged account will suffice.
  • 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.

3.3 Monitoring

Significant events on all systems must be logged and audit trails saved as follows:

  • All system-related logs will be kept online for 1 week.
  • All security-related logs will be kept online for 4 weeks.
  • All application-related logs will be kept online for 5 weeks.

Any critical or sensitive-data event will automatically be reported to IT management at OrgSync, who will review log details and take appropriate action. Corrective measures and client notifications 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.

3.4 Data Retention

Point-in-time snapshots of user data will be taken hourly and persisted to allow for restoration in the unlikely event of data loss. The following number of snapshots will be retained:

  • 48 hourly snapshots
  • 14 daily snapshots
  • 6 weekly snapshots
  • 12 monthly snapshots
  • 2 yearly snapshots

3.5 Compliance

  • Audits will be performed quarterly by authorized organizations within OrgSync
  • Audits will be managed by OrgSync, in accordance with the Audit Policy. OrgSync will filter findings not related to a specific operational group and then present the findings to the appropriate support staff for remediation or justification.
  • Every effort will be made to prevent audits from causing operational failures or disruptions.

4.0 Enforcement

Any employee found to have violated this policy may be subject to disciplinary action, up to and including termination of employment.


Back To Technology