...
Item | Desired Outcome | Time | Who | Notes | Decisions | Actions | |
|---|---|---|---|---|---|---|---|
| 1 | Announcements/Updates | ||||||
| 2 | Review Release Notes | 10 | Steven and Adrian | Nothing major to talk about. Noted bug fixes for SAML and minor bug fixes for clearing history in Primo. | |||
| 3 | Broader Security Updates | 5 | Team | None | |||
| 4 |
| 30 | Team | Question: “Does the current data privacy form cover the use of patron data from all UC institutions and not just the home institution for appropriate business use?” UC Santa Cruz goes over this form with their staff to make sure they know what it means. We’re all covered by the same IC3 policies. - Some small question around retention policies. However, the question as poised, we’re all governed by the same set of documentation. When procurement was asked a similar question about financial data, they were quite clear that we’re all under the UC Regents. Current acknowledgement looks good. No additional updates needed at this time. | Yes, the current data privacy form covers the use of patron data from all UC Institutions. No updates are needed for the current form. | Gem will let OT know. | |
| 5 | Next Meeting | 10 | April 22 | Changing the meeting recurrence to quarterly. We will handle our work plan primarily asynchronously. Adrian will take lead on working on “Defines and scopes what a security incident is, and levels of severity” | Adrian will follow-up with the group via email. | ||
| 6 | Wrap up | Review actions and decisions | 5 | Gem | Gem will update calendar invite to be quarterly (done). | ||
| 7 | Parking Lot | Capture important topics for future discussion |
| ||||
| 8 | Total | x/x |
...