Technology and Security Policy

“Cyber Strong UC” is a collaborative project of the systemwide Information Security Awareness Workgroup, which includes representatives from 13 UC locations. Its focus is to develop informational campaigns, materials, and other resources that all UC locations can use to promote good cybersecurity habits and information security awareness year‐round. The specific goals of this project are to:

The recent IT Rationalization at UCR presented an opportunity to completely revamp the central IT helpdesk to an effective and trusted campus partner. This transformation required us to focus on ourselves as people, our processes and the tools used in our daily service delivery. Following ITIL Service Framework, the transformation was highly data-driven, providing immediate feedback and exposing service pain-points, while fostering a culture of accountability and innovation.

Description:
This session looks at an active project at UC San Diego that has developed into:

Test Automation and Continuous Integration are two pillars of a robust DevOps culture. But how to get started?

Join us for this session as we:

We will describe our test planning and execution experiences in the UCPath Pilot conversion project. How we successfully used borrowed campus resources from HR, Academic Personnel, Payroll and Finance to plan, execute and validate each test phase. We will show you how we tracked our progress and most importantly give you our lessons learned so that other UC locations can use this information in their upcoming implementation.

The General Data Protection Regulation (GDPR) is a European law that UC must adhere to. GDPR has numerous requirements for data privacy and security, many of which impact requirements for systems and applications. Developers and system integrators need to understand what the GDPR regulations are, and what they must do to comply. Failure to comply is not an option. Accordingly, security and privacy features must be developed to meet GDPR requirements. Some of those requirements, such as the right of erasure, are technically challenging.

If you had access to a fully featured integration platform, with no need for an extensive RFI or RFP process, yet had increasing support and backing of multiple campuses behind it.....would you use it? Would immediate access to an integration platform have made a difference to your previous projects? 

How many times have you been involved in an RFI or RFP involving an integration platform....but didn't implement? 

Is the Service Portfolio for your organization growing? Is your organization taking a cloud first strategy? Have you ever wondered how you will manage access between all your on premises and cloud services? Come see how UCLA and UCSC are tackling their role and access management challenges.

The University of California has been contributing to an EDUCAUSE Center for Analysis (ECAR) working group that is examining the ITSM concepts of a “service owner”. A service owner is accountable for the delivery of an IT service and ensures that the service receives strategic attention and appropriate resources to support the mission and needs of the Institution. The service owner is responsible for the service as a whole through its entire lifecycle and is accountable to the person in charge of overall IT service delivery. 

Dearly beloved,

We gather here today to honor the memory of our friend, paperwork. To paperwork's friends, paperwork was also known as the faxed letter requirement. To others, paperwork was the person who responded to email when they felt like it. While to some others, it was the manual data-entry into spreadsheets. To us, paperwork was many things, but to me, I knew paperwork as inefficiency.