IT Security Policy 106 - System Configuration

Status: Draft
Last Revision Date: September 21, 2023

Statement of Purpose

Computing devices are susceptible to vulnerabilities in their operating systems, hardware, and configurations. Manufacturers release recommended configurations, patches, and upgrades to mitigate security risks. This policy ensures that Clackamas Community College ITS support staff remain informed of these requirements and maintain all computing devices with the latest versions, patches, configurations, and industry best practices.

Policy Summary

All servers, network devices, and other computing resources within Clackamas Community College networks—whether managed internally or by third parties—must be built and deployed following documented System Configuration Standards. This policy is subject to and superseded by applicable laws and regulations.

Policy

General Compliance

  1. All computing systems, including virtual servers or appliances, must be assigned a single primary purpose where feasible (e.g., web servers, database servers, and DNS servers should be deployed separately).

    • When multiple functions are hosted on a single server, they must be closely related or serve the needs of a single department or division.

  2. Operating system configurations must be reviewed to ensure services are minimized and security is maintained.

    • Externally facing devices must be hardened according to published hardening standards, where available.

  3. All systems must conform to Clackamas Community College’s Information Security configuration standards before deployment in a production environment.

  4. Clackamas Community College must conduct internal and external network vulnerability scans at least quarterly and after significant network or security changes.

  5. External penetration tests must be conducted at both the application and network layers biannually or after major changes to the security environment.

  6. Identified vulnerabilities from scans and penetration tests must be assessed for risk and compared against acceptable risk thresholds. Any vulnerabilities exceeding acceptable risk levels must be assigned to the appropriate personnel for remediation.

  7. Remote access to computing systems must adhere to Clackamas Community College Remote Access Standards and minimize security risks to an acceptable level.

  8. Procedures for accessing and modifying critical systems, configurations, and files must be documented in alignment with regulatory standards and industry best practices.

  9. The Information Security Team must stay informed about security issues and vulnerabilities affecting Clackamas Community College computing systems and communicate necessary updates to relevant parties.

  10. Security and system configuration standards must be updated as needed to address vulnerabilities, updates, regulatory requirements, and evolving risk tolerance levels.

  11. A structured patching schedule must be in place for all applications, operating systems, firmware, and other updatable components. Critical vulnerabilities must be patched in a timely manner based on the associated risk. ITS leadership must maintain a documented plan to phase out components that can no longer receive security updates due to end-of-life or end-of-support status.

  12. The Chief Information Security Officer (CISO) must oversee a formal risk assessment process to identify and address existing or emerging threats and vulnerabilities to Clackamas Community College assets.

  13. The CISO must approve and track the activation and deactivation of remote access paths and accounts.

Mobile and Remote Access Security

  1. Any computer or laptop used for remote access to non-public Clackamas Community College resources via the Internet must have the following CISO-approved security controls enabled:

    • Personal firewall software

    • Anti-virus software, as specified in Policy 107

    • Clackamas Community College’s authentication solution with a VPN client supporting the user's requirements

  2. All remote users connecting to Clackamas Community College networks must be authenticated in accordance with Policy 102.

Exemptions

None.

Exceptions

Exceptions to this policy require prior written approval from the Chief Information Officer (CIO).