Maintenance
Overview
This updated standard is to help align existing practices within Office of Information Technology (OIT) around maintenance controls to the requirements in NIST 800-171 (MA | 3.7.x) as well as industry best practices. This document does not give full coverage of 3.7.x controls within 171 due to existing limitations and other requirements that are specific to CUI.
What is in this document:
- Patching requirements
- Access control tie-in for remote maintenance
- Security requirements for third party repairs
What is NOT in this document:
- Patching procedures or methods
- Remote maintenance procedures or methods
- Approved third party repair providers
Policy Reference
APM 30.11 University Data Classification and Standards
APM 30.12 Acceptable Use of Technology Resources
APM 30.14 Cyber Incident Reporting and Response
APM 30.15 Password and Authentication Policy
Purpose
This Identification and Authentication standard supports APM 30.11 University Data Classification and Standards, and other relevant university policies.
Scope
These Standards are the minimum baseline for all managed and unmanaged systems that access, store, or process University of Idaho data (see APM 30.14 C-6) or using University of Idaho technology resources (see APM 30.12 C-1) at the Low, Moderate or High risk levels (see APM 30.11) not otherwise covered by an approved system security plan.
Standards
Only run operating systems which are currently supported and patched. Apply security patches to address flaws in systems and applications automatically, or within 10 days.
- Patches may be applied in a timeframe approved through a risk-based vulnerability assessment process approved by the OIT Security Office and all affected data and system owners.
Applies to: Low / Moderate / High
Authentication for remote maintenance must go through authenticated channels compliant with Access Control and Identification and Authentication standards.
Applies to: Low / Moderate / High
- Prior to sending equipment back to vendors or third parties for repairs that are unable to be done in-house, systems must be sanitized using the standards described in Media Protection
Applies to: High
- Prior to sending equipment back to vendors or third parties for repairs that are unable to be done in-house, systems must be either encrypted using OIT-Managed encryption or sanitized using the standards described in Media Protection.
Applies to: Moderate
- Keys, passwords or other authentication secrets for accessing university technology resources must not be shared with third parties, as required by APM 30.15.
Applies to: Low / Moderate / High
- Temporary credentials assigned only to vendor must be used if access is required to perform or validate repairs.
- Any maintenance on site by third parties must be supervised unless operating under an approved contract.
Applies to: Moderate / High
Other References
1. NIST SP800-171r2 (February 2020)
2. NIST SP800-53r5 (September 2020)
Definitions
1. Security patches
Updates or fixes released by vendors to resolve a security vulnerability.
2. Remote maintenance
Accessing a system via a network connection for the purpose of working on the system itself.
3. Third party
Any entity that is not an owner, user or otherwise authorized individual within a system. This may include university affiliates that are not authorized for a specific system.
Standard Owner
OIT Security is responsible for the content and management of these standards.
To request an exception to this standard.
Contact: oit-security@uidaho.edu
Revision History
3/1/2024 — Minor updates
- Minor formatting/wording/reference changes.
6/23/2023 — Original standard
- Full re-write to align with NIST 800-171r2