1. K-State home
  2. »Policies
  3. »PPM
  4. »3400 Computing and Information Technology
  5. »PPM Chapter 3432: Operations and Management Security Policy


Questions relating to the information in each chapter of the Policies and Procedures Manual should be directed to the office issuing the chapter.

That information is usually located at the end of each chapter.

For policy update questions, please contact policy@ksu.edu.

Operations and Management Security Policy

Chapter 3432
Issued December 4, 2009; Revised January 9, 2023

Table of Contents

.010 Purpose
.020 Scope
.030 Effective Date
.040 Authority
.050 Policy
.060 Definitions
.070 Roles and Responsibilities
.080 Implementing Procedures
.100 Questions/Waivers

.010 Purpose

The purpose of this policy is to help ensure the secure operation of K-State information systems and proper management of K-State's IT security program and technologies.

.020 Scope

This policy applies to all university colleges, departments, administrative units, and affiliated organizations that use university information technology resources to create, access, store or manage University Data to perform their business functions.

.030 Effective Date

This policy became effective on November 13, 2009.

.040 Authority

The State of Kansas, ITEC  Information Technology Policy 5300, Revision 1: Business Contingency Planning, requires all state agencies, including Regents institutions, to develop "business continuity plans to ensure that all entities can continue critical operations during any disruption and resume normal operations within a reasonable period of time."

The State of Kansas, ITEC Information Technology Security Standards Policy 7230A (PDF), requires all State of Kansas branches, boards, commissions, departments, divisions, agencies, and third parties used to process transmit or provide business capabilities on behalf of Kansas state government to perform a risk assessment.

050 Policy

  1. Business continuity plan - K-State must have a business continuity plan to guide recovery from disasters or other major disruptions to service in a manner that maintains the security of K-State information systems and ensures timely restoration of services.
  2. Configuration management - the configuration of servers, workstations, network devices, firewalls and other enterprise security technologies should be managed in a way that provides consistent setup, documents changes, and ensures security requirements are maintained when the configuration is changed.
  3. Data backups - University Data must be backed up regularly and backup media stored securely, commensurate with the classification of the data.
  4. Firewalls
    1. All connections to networks outside the K-State campus, such as the Internet and Internet2, must be protected with a firewall that filters both incoming and outgoing network traffic against common threats.
    2. All enterprise information systems and any K-State system hosting confidential data must be protected by a network firewall and a host-based software firewall, both configured in "default deny" mode for incoming traffic and enforcing documented trust relationships for those systems.
    3. All university computers connected to the university network must have a host-based firewall configured appropriately for the security requirements of the system and the classification of data stored therein.
    4. Logging should be enabled for all firewalls and periodically reviewed for anomalous events.
    5. Configuration of network firewalls and host-based firewalls on enterprise information systems should be audited periodically to ensure consistency with the security requirements of the system(s) they protect.
  5. Security event logging and auditing
    1. Audit logs recording user activities, exceptions (i.e., errors or failures), and information security events should be generated commensurate with the security requirements of the system being monitored. Audit logs should be retained for at least 30 days.
    2. Enterprise information systems must log system administrator activities, such as the use of privileged accounts (e.g., supervisor, administrator, or root).
    3. Audit logs should be periodically reviewed to detect security violations.
    4. Security event log data must be protected against unauthorized access and alteration.
    5. Clocks of systems being monitored should be synchronized regularly from an accurate time source.
  6. Security management - K-State's IT security program and policies must be monitored and periodically assessed to ensure their continued effectiveness. The Chief Information Security Officer (CISO) or designee must perform an annual IT security self-assessment and submit a summary report to the Kansas Board of Regents office, as required by state of Kansas information technology policy.

.060 Definitions

Process of verifying one's digital identity. For example, when someone logs into Webmail, the password verifies that the person logging in is the owner of the eID. The verification process is called authentication.

Confidential data
Highly sensitive data intended for limited, specific use by a workgroup, department, or group of individuals with a legitimate need-to-know. See K-State's Data Classification and Security Policy for an expanded definition and examples.

Default Deny
A firewall ruleset that begins with blocking all network traffic, both incoming and outgoing, then only allowing specific network traffic required for the effective and secure operation of the system(s) protected by the firewall.

Enterprise information system
An information system and/or server providing services commonly needed by the University community and typically provided by central IT units. Departmental information systems provide services specific to the mission and focus of individual Colleges, departments, administrative units, or affiliated organizations and are typically provided by distributed IT staff in those units.

A specialized device or software program that controls the flow of network traffic between networks or hosts to enforce security policies and provide protection for the resources on those networks or hosts. For the purposes of this policy, a router with Access Control Lists (ACLs) is not considered a firewall.

Trust relationships
A specification of the level of access granted to computer systems and/or applications that are trusted to access resources on a server and its associated data and applications. This applies to access controls between systems, not access rights for individual users or roles.

University Computer
Any computer considered to be the property of Kansas State University.

University Data
Any data related to Kansas State University ("University") functions that are:
  1. Stored on University information technology systems.
  2. Maintained by K-State faculty staff, or students.
  3. Related to institutional processes on or off campus.

This applies to any format or media (in other words, it is not limited to electronic data).

University Network
Any part of K-State's data network physically located on the Manhattan or Salina campus. This includes devices on the network assigned any routable and non-routable IP addresses, typically 129.130.X.X or 10.X.X.X, respectively, and applies to K-State's wireless network and the network serving K-State's student residence halls and Jardine Apartments.

.070 Roles and Responsibilities

  1. Chief Information Security Officer (CISO) - Coordinates the development of guidelines, standards, and/or procedures related to this policy as well as the identification, implementation, and assessment of common security controls needed for this policy; monitors and periodically assesses K-State's overall IT security program and policies; and ensures completion of an annual IT security self-assessment and report.
  2. Enterprise IT Security Analyst - Ensures the application of appropriate operational security controls for an information system; coordinates with the CISO in the identification, implementation, and assessment of common security controls; ensures that backups are being performed regularly and stored securely; and ensures that components of an information system have an appropriate system of configuration management in place. This role may be filled by someone directly involved with the development, maintenance, and/or operation of the information system.

.080 Implementing Procedures

  • Security event logging and auditing
    1. Audit logs should include the following information, when relevant:
      1. eID or username
      2. Date and time of event
      3. Type of event
      4. Description of the event
      5. Network addresses and protocols involved
      6. Files accessed
      7. Commands/processes executed
    2. K-State information systems should consider logging the following events and any others deemed appropriate for tracking important or suspicious actions:
      1. Successful and unsuccessful login or authentication attempts
      2. Access to confidential data
      3. Changes to access privileges for confidential data
      4. Activation and de-activation of security systems such as firewalls, anti-virus systems, and intrusion detection systems, and alerts from these systems.
      5. Privileged operations such as the use of privileged accounts (e.g., supervisor, administrator, or root), system start-up and stop, and I/O device attachment/detachment.
      6. System and network alerts and failure messages.
      7. Changes to, or attempts to change, system security settings and controls.

.090 Related Laws, Regulations, or Policies

  1. Existing K-State IT security operations and management policies
  2. Other related laws, regulations, or policies
    1. K-State's Data Classification and Security Policy
    2. State of Kansas, ITEC Information Technology Policy 5300, Revision 1: Business Contingency Planning
    3. State of Kansas, ITEC Information Technology Security Standards Policy 7230A, Revision 1: General Information Technology Enterprise Security Policy (PDF)
    4. ISO/IEC 27002:2013, Information technology - Security techniques - Code of practice for information security controls, published by the International Standards Organization. This is an international security standard that specifies security requirements for controlling access to ensure "the correct and secure operation of information processing facilities."
    5. NIST Special Publication 800-41 Revision 1: Guidelines on Firewalls and Firewall Policy

.100 Questions/Waivers

The Vice President for Information Technology and Chief Information Officer (CIO) is responsible for this policy. The CIO or designee must approve any exception to this policy. Questions relating to this policy should be directed to the Chief Information Security Officer (CISO).