The Pennsylvania State University - Administrative Information Services, a unit of Information Technology Services

Update Adhoc Access

Goals:

  • To develop a formal process to request adhoc update access to production data
  • To put controls in place to minimize risks

New Adhoc Update Library:

  • New Adhoc Batch and Online Update Libraries (AA07500U and AP07500U)
  • Read Access to all files (similar to the AA07500/AP07500 libraries)
  • Update Access to requested files only (temporary basis)
  • Link to library by individual user-id (temporary basis)

Steps to Follow:

  1. The adhoc update program is stored in the developer’s personal library.
  2. The developer submits the Update Access to Production Data Request form to the Data Steward for approval.
  3. The Data Steward forwards the approved request to the AIS Security and Accounts office.
  4. The AIS Security and Accounts office will assign the requested access to the Adhoc Update Library for the specified date and send an e-mail to the developer informing them that the access has been granted.
  5. The adhoc update program is executed from the Adhoc Update Library.
  6. The AIS Security and Accounts office will remove the requested access to the Adhoc Update Library on the requested end date.

Notes:

  • If the update program involves multiple steward areas, then it is the responsibility of the IT Manager to gain approval from the other areas. (Check box in the e-mail indicating that this has occurred.)
  • For auditing purposes, the AIS Security and Accounts office will maintain a file of these requests.

Content Questions: ISIS Team | Support Questions: AIS Support
Page Last Updated or Reviewed: Friday, May 20, 2011