SCT Banner Student / Release Guide / 7.0

Section 4 New Value-Based Security and Personally Identifiable Information Security Using Fine-Grained Access Control - FunctionalUsing This Enhancement with Banner StudentDomain Code Driver Table PII Column NameSB_FACULTY_PII SIBINST SIBINST_PIDMSB_HOUSING_PII SLBRMAP SLBRMAP_PIDMSB_RECRUIT_PII SARADAP SRBRECR_PIDMSB_ADMISSIONS_PII SARADAP SARADAP_PIDMSB_GENSTUDENT_PII SGBSTDN SGBSTDN_PIDMSB_REGISTRATION_PII SFBETRM SFBETRM_PIDMSB_TRANSFER_PII SHRTTRM SHRTTRM_PIDMBanner Student Institutional Example for PIIThe process used for defining VBS using FGAC is found in the SCT Banner General7.0 Release Guide. This example is an overview of the kinds of security that can beemployed when using Banner FGAC.The goal of this example is to restrict access to ID and name information based onthe work location of the user and the functional location of data for the ID.• Staff members in the Admissions, Registration, Student Billing, and StudentDean's offices are assigned to the functional locations of Admissions,Enrollment, and General Student.• Staff members in the Payroll area are assigned to the functional locations ofApplicant, Benefits, and Beneficiary.• When the staff members in the Admissions office open a Banner form andenter an ID that does not have a record in Admissions, Enrollment, or GeneralStudent, it will appear as if the ID does not exist in the system.• When staff members in the Payroll area open a Banner form and enter an IDthat does not have a record in any of the Human Resources areas, it will againappear as if the ID does not exist for the system.Typically, the Student System administrative offices do not have access to Payrolltype forms, and the Payroll area may not have access to Student Systemadministrative forms. That alone prevents access to the data in those products. PIIgoes one step farther and prevents these offices from viewing the lists of people thatexist for the other products.January 2005 Student Release 7.0Confidential Release Guide 115