[an error occurred while processing this directive] [an error occurred while processing this directive]
[an error occurred while processing this directive]

iSIS Security Strategy

The project security team is responsible for assuring correct access to iSIS since not all users require access to all data or functions within the system. FERPA regulations will be taken into consideration when determining access levels.

PeopleSoft’s Maintain Security uses the following security definitions relating to access:

  • User Profiles (a set of data describing a particular iSIS user)
  • Roles (intermediate objects that link User Profiles to Permission Lists)
  • Permission Lists (a set of pages and allowable actions on those pages)

Maintain Security also delivers application security that restricts the data a user can attach to a student, but it does not restrict the students a user can view. Instead, row level security will be used to restrict the students a user has the ability to take actions on and view.

Student access

All students will need access to the iSIS Self-Service “Student Center” component. Students will use self-service to pre-enroll for courses, add/drop courses, view class schedule, view grades, etc.

Faculty and Instructor access

Faculty and instructors will need access to the Faculty Self-Service menus.

K-State will use the K-State Enterprise Authentication System (KEAS) LDAP server to authenticate within iSIS so end-users will use their K-State eID and password.

The Goals of Security:

  • Assign security access to a user (students, faculty, and staff) that best matches their needs.
  • Ensure that security access to data, pages, functions, etc., is appropriate for each individual, office, department, etc.
  • Establish procedures for the appropriate supervisor to grant or remove security access for any iSIS module.
  • Automate student and faculty self service access.
[an error occurred while processing this directive]