| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
|---|
| 1 | Announcements/Updates | | | | | |
|
| 2 | Review Release Notes | | 10 | TeamGem | Alma Primo VE | | |
| 3 | Broader Security Updates | | 5 | Team | | | |
| 4 | Team Charter | | 10 | Team | Do the broad concepts make sense? Should anything be added or deleted? Typically in SILS, roles rotate each year. Do we want to do that for this group? If so, does the vice-chair automatically become chair the next year? Do we want a steering-committee to meet more often for planning purposes?
| | |
| 5 | Review Acknowledgment of Data Privacy and Security Responsibilities for Authorized Users of UC Alma Environments | Determine Next Steps | 30 | GroupTeam | Anything we need to work on before this? We had talked about starting with the scope and severity of a security incident. How do we want to approach reviewing this? Can we answer OT’s 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?”
| | |
| 6 | Next Meeting | | 10 | | No December Meeting Next Meeting January 28 | | |
| 7 | Wrap up | Review actions and decisions | 5 | GroupGem | | | |
| 8 | Parking Lot | Capture important topics for future discussion | | | How quickly must Ex Libris disclose a security incident to us? According to p.31 of our contract, Ex Libris should inform us no later than 2 business days after they “reasonably believe” a breach has or may have occurred of non-public information. How should this group work with Siren?
| | |
| 9 | | Total | x/x | | | | |