• Home
  • About Us
  • Guest Posts
  • Share Your UC Care Story

Thursday, February 4, 2016

Thursday, February 4, 2016
The following is a letter sent to Colleagues by the UCSB Faculty Association calling for opposition to the proposed new pension tier.










Dear Colleagues:
We are gratified by the strong response at the Town Hall of the faculty, resisting the unsound pension that UC is proposing to offer new hires starting July 1. Over 1,000 faculty have signed the petition opposing the new tier proposals. We are resending this message to give you an opportunity to join your colleagues by signing the petition if you have not done so. The deadline for making known your opinions regarding these changes is February 16.
Allow us to share with you our reasons for objecting to the current proposal:
1) We share the task force chair's bleak account of the "negative effects of the PEPRA cap on retention and timely retirement" (A guide to reviewing the recommendations of the Retirement Options Task Force, p. 7). In other words, the future of the institution is at stake.
2) We take issue with the fact that while the acceptance of the PEPRA cap is presented as UC's side of the deal with the governor and the legislature, the latter's part of the deal has not been fulfilled:
a) UCRP has NOT been acknowledged as a permanent state obligation;
b) the State's promise "of $436 M for the UCRP over the next three years" to help finance the Unfunded Accrued Actuarial Liability (p.4 of the Task Force report) is a misrepresentation. As Michael Meranze has underlined, the Legislature actually has "not engaged in any multi-year promise". In addition, of the $10.7B or 12B UAAL (numbers depending on market-value or actuarial-value), the hypothetical sum of $436 is only a very small percentage, not accomplishing much. In sum, we object to completing our side of a (bad) deal, when there is no actual commitment on the other side.
3) We take issue with the top-down way this complex issue has been handled. The Task Force had to begin from a declared reality that no one in the UC system other than President Napolitano had a hand in ratifying. This is not shared governance. In addition, the fact that the recommendations of the Task Force, whatever their merit, can be taken or left by President Napolitano further erodes whatever good faith and intellectual effort went into these proposals.
4) We are not convinced by the Task Force's arguments that introducing a Defined Contribution option is fiscally advantageous. No credible empirical evidence exists in the report or in recent economic history to support the assertion. Moreover, the proposed options, in their concern for portability, favor short-term employees over long-term employees, further undermining faculty loyalty to the institution or a commitment to public service.
5) We object to the ramifications of adding a new tier to retirement benefits that creates financial divides between those hired before 2016 and those hired thereafter. Even more, we see these changes as part of a broader national trend to eviscerate tenure and full-time employment. Having to acknowledge such systematic differentials to new hires reduces not only our ability to recruit young faculty but also our pride in doing so as well as our willingness to encourage our students to become university professors.
For more information on this issue, please visit our website at ucsbfa.org.

We urge you to sign the petition to express your opposition to proposed changes to the UC Retirement Plan.
UCOP has also set up a comment link where you can provide your feedback on the task force recommendations. We urge you to express your concerns about the plan there. If you do, please also send a copy of your comments to us at newtier@cucfa.org.
Thank you for your attention to this important matter.
The Board of the Santa Barbara Faculty Association
Julie Carlson
Jorge Castillo
Nelson Lichtenstein
Constance Penley
Erika Rappaport
Elisabeth Weber
Robert Williams
Posted by Michael Meranze | Comments: 0

Saturday, January 30, 2016

Saturday, January 30, 2016
The San Francisco Chronicle has coverage of an issue that has been circulating on faculty email networks at UC Berkeley for a few days.  The piece, "Cal professors fear UC bosses will snoop on them," is behind a paywall. The first sentence reads, "UC Berkeley faculty members are buzzing over news that University of California President Janet Napolitano ordered the installation of computer hardware capable of monitoring all e-mails going in and out of the UC system."   UC's Chief Operating Officer says "that UC policy “forbids the university from using such data for nonsecurity purposes.”  UC Berkeley's Senate chair replies, "What has upset a lot of the faculty was that the surveillance was put in place without consulting the faculty. In fact, the people installing the system were under strict instructions not to reveal it was taking place."  On the blog's Facebook page, we've had some debate about how new this capability is, with some faculty from various universities saying they've always assumed their university email could be monitored at any time, and others saying this is a new level of intrusion.

Here are two communications from UC Berkeley faculty, one about how faculty there came to know about the program, and the other a timeline of events.  


EMAIL 1: January 28, 2016:



In recent weeks The Senate-Administration Joint Committee on Campus Information Technology (JCCIT) has learned that UCOP installed hardware on the campus network designed to monitor and possibly record all network traffic coming or going to the campus.

This secret monitoring is on-going.

 UCOP would like these facts to remain secret.  However, the  tenured faculty on the JCCIT are in agreement that continued silence on our part would make us complicit in what we view as a serious violation of shared governance and a serious threat to the academic freedoms that the Berkeley campus has long cherished.


 Some salient facts:


 - The UCOP had this hardware installed last summer. 

 - They did so over the objections of our campus IT and security experts. 

 - For many months UCOP required that our  IT staff keep these facts secret from faculty and others on  the Berkeley campus.

  - The intrusive hardware is not under the control of local IT staff--it sends data on network activity to UCOP and to the vendor.  Of what these data consists we do not know.

 - The intrusive device is capable of capturing and analyzing all network traffic to and from the  Berkeley campus, and has enough local storage to save over 30 days of  *all* this data ("full packet capture").  This can be presumed to include your email, all the websites you visit, all the  data you  receive from off campus or data you  send off campus.

 - UCOP defends their actions by relying on secret legal determinations and painting lurid pictures of "advanced persistent threat actors" from which we must be kept safe.  They further promise not to invade our privacy unnecessarily, while the same time implementing systems designed to do exactly that.  

-- It is very far from clear that UCOP has a better plan or better qualified IT security people or infrastructure than does the Berkeley campus, and they've shut these qualified people out of the picture.
EMAIL 2: January 29, 2016

According to other members of the Senate-Administration Joint Committee on Campus Information Technology (JCCIT):

A network security breach was discovered at the UCLA Medical Center around June 2015.

UCOP began monitoring of campus in networks around August 2015.

ONLY AFTER this monitoring, on August 27, 2015, did UCOP issue a new cybersecurity policy online under the heading of "Coordinated Monitoring Threat Response." The policy describes how UCOP would initiate "Coordinated Monitoring" of campus networks even though it is believed that such monitoring was already underway prior to the announcement of the new policy.  


On Dec. 7, 2015, several UC Berkeley faculty heard that UCOP had hired an outside vendor to operate network monitoring equipment at all campuses beginning as early as August 2015. The process was apparently shrouded in secrecy and staff were instructed not to talk about it because of "attorney-client privilege" although it remains unclear how attorney-client privilege applies in this situation.  Extensive monitoring and storage of inbound and outbound Internet traffic at UC Berkeley was being performed, including storage and possible transmission to the outside vendor of packet headers with URLs and email metadata (to-from fields). The Berkeley campus IT staff does not collect this type of information because it violates UC Berkeley IT Privacy policy.


 On Dec. 18, 2015, those UC Berkeley faculty sent a letter to UC President Janet Napolitano requesting more information and asking that the monitoring cease.


On Dec. 21, 2015, UC Vice President and CIO Tom Andiola met with most of the faculty who signed the Dec. 18, 2015 letter and Berkeley Assoc. Vice Chancellor and CIO Larry Conrad, and Berkeley Academic Senate chair Ben Hermalin.  Tom confirmed that monitoring equipment was installed at the Berkeley campus by an outside vendor and that it would be removed promptly and publicly disclosed by UCOP.


 On Jan. 12, 2016, The Berkeley Joint Committee on Campus Information Technology (JCCIT) met with Larry Conrad and others.  The committee was informed that contrary to the Dec. 21, 2015 statements, UCOP had decided to continue the outside monitoring and not disclose any aspects of it to students or faculty.  The Senior faculty members of JCCIT met privately after the meeting and deliberated carefully about options, concluding it was their duty to come forward. To protect staff, administrators, and non-tenured faculty, it was decided an open letter should come from a group of tenured faculty, stating that "We are UC Berkeley faculty who have reason to believe that extensive monitoring and storage of inbound and outbound Internet traffic at UC Berkeley is being performed by an outside vendor at the request of the UC Office of the President, with no disclosure to UC Berkeley faculty or students...." A draft open letter "To Whom It May Concern" was circulated to all senior faculty who signed the Dec. 18, 2015 letter, stating our intentions to forward this to the New York Times.  Eleven senior faculty signed it.


On Jan. 15, 2016, the letter was sent to the New York Times and reached reporter Steve Lohr. Senior campus administrators in the Chancellor's office and UCOP were also sent copies.


On Jan. 19, 2016, UCOP Exec. VP and COO Rachael Nava sent a letter to those who signed the Jan. 15, 2016 letter.  The original version was marked "CONFIDENTIAL: DO NOT DISTRIBUTE" and invoked "Attorney-Client privilege". After several recipients responded to her via email questioning who is the client and why her letter must be kept secret, a revised version of the letter was sent the next day removing that language, stating: "All: Please accept my apologies with regard to the confusion on the attorney client privilege language on the letter.  It was a clerical error and was not intentional. Please find a revised version of the letter with the language removed." The letter admits that extensive monitoring is being performed by an outside vendor but does not provide a rationale for continuing this monitoring six months after it was initiated nor for the ongoing lack of disclosure from UCOP to students and faculty.

UPDATE: the Nava letter of 1/19/16:



EXECUTIVE VICE PRESIDENT - CHIEF OPERATING OFFICER
OFFICE OF THE PRESIDENT

1111 Franklin Street, 12th Floor

Oakland, California 94607



January 19, 2016

Dear Colleagues:

I am writing to follow up on earlier discussions about cybersecurity matters across the UC system and to share to the fullest extent possible the principles and considerations that guide the University’s efforts to respond to cyber attacks.

First, I want to thank you for sharing your concerns that we maintain the privacy protections enshrined in University policy even as we significantly strengthen our cybersecurity posture. As explained below, I do not believe these imperatives conflict, in fact, they reinforce one another in crucial ways. I would like to share some key principles and practices that help ensure that privacy protections are consistently upheld in the context of network security activities, some observations about the serious cyber attack we experienced at UCLA, and information about increasingly challenging attacks that are rising at academic institutions across the country.

As you know, on July 17, 2015, UCLA publicly announced that it had suffered a serious cyber attack. The attack appears consistent with the work of an Advanced Persistent Threat actor, or APT. An APT generally emanates from an organized, highly skilled group or groups of attackers that orchestrate sustained, well-planned attacks on high value targets. Today, much effort in the cybersecurity industry is focused on APT attacks because they are difficult to detect and highly destructive. While there is no evidence that cyber attackers actually accessed or acquired any individual’s personal or medical information at UCLA, the University decided to notify stakeholders. UCLA notified 4.5 million patients about the cyber attack. Within days, several lawsuits were filed against the Regents alleging various violations of State law, all 17 of which are now pending.

The UCLA attack, while exceptional in some respects, is part of an increasing trend of cyber attacks against research universities and health care systems. Institutions of higher education are increasingly targets of APT attacks because academic research networks hold valuable data and are generally more open. Indeed, the mission of our University is to promote knowledge sharing and research collaboration, which involves responsibly sharing data. A recent report from Verizon described educational institutions as experiencing “near-pervasive infections across the majority of underlying organizations,” and observed that educational institutions have, on average, more than twice the number of malware attacks than the financial and retail sectors combined.

APTs seek to illicitly harvest credentials across academic networks and then use those credentials, and the trust relationships among systems, to move laterally to other nodes in a given network. There are techniques to address such attacks, but I share these points to underscore the seriousness of the threat posed by APT attackers and the fact that, for cybersecurity purposes, a risk to what appears to be an isolated system at only one location may in some circumstances create risk across locations or units.
In recognition of these realities, President Napolitano has initiated a series of system-wide actions to strengthen the University’s ability to prevent, detect, and respond to such attacks. I believe these efforts are consistent with the reasonable expectations of the University community -our students, faculty, staff, patients, research sponsors, and academic partners- that we undertake serious efforts to protect sensitive data from malicious attacks. I also believe these actions are fundamental to realizing the University’s commitment to privacy. The following actions were taken:

   A leading cybersecurity firm was engaged to assist the University in responding to the cyber attack, in part by analyzing network activity at all UC locations to detect and respond to any APT activity
   Every location submitted a 120-day cybersecurity action plan to harden systems and improve administrative and physical safeguards
   A Cyber-Risk Governance Committee (CRGC) was established, with representation from across the system, including the Academic Senate, to oversee and guide system-wide strategies and plans related to cybersecurity. The CRGC has met several times already and is identifying key ways to strengthen our security posture while honoring the University’s commitment to academic freedom, privacy, and responsible fiscal stewardship
   A system-wide incident escalation protocol was developed to ensure that the appropriate governing authorities are informed in a timely way of major incidents, and
   Mandatory cybersecurity training was rolled out to all UC employees by October 1, 2015.

Several faculty members have requested detailed, technical information about the UCLA attack and the specific security measures taken in its immediate aftermath. I understand that some are concerned that such measures may have exceeded the University’s policies governing privacy. I believe such actions were well within the operational authority of the University and in alignment with policy. It is regrettable that as long as the UCLA incident remains the subject of pending legal matters, I cannot publicly share additional information that might correct some of these misimpressions. As a policy matter, however, I wish to address the privacy and governance concerns that arise in the context of data security, without any express or implied reference to the UCLA attack.

With respect to privacy, the letter and structure of the University’s Electronic Communications Policy (ECP) reflect the principle that privacy perishes in the absence of security. While the ECP establishes an expectation of privacy in an individual’s electronic communications transmitted using University systems, it tempers this expectation with the recognition that privacy requires a reasonable level of security to protect sensitive data from unauthorized access. For this reason, the ECP expressly permits routine analysis of network activity “for the purpose of ensuring reliability and security of University electronic communications resources and services.” (ECP, IV.C.2.b.) It expressly permits analysis of “network traffic” to “confirm malicious or unauthorized activity that may harm the campus network or devices connected to the network.” (ECP, V.B.) Significantly, “consent is not required for these routine monitoring practices.” (Emphasis added.) In short, the ECP reflects that, in some circumstances, the protection of privacy actually requires limited examination of electronic communications. (ECP, Attachment 1, V.A (noting that failure to prevent unauthorized access itself undermines privacy and confidentiality).) This is consistent with fair information practice principles and the University’s duties under laws and regulations that require the use of physical, technical, and administrative safeguards to secure sensitive information.

The University takes great care to ensure that its practices reflect the balance outlined in the ECP. I would like to illustrate significant measures that we undertake to honor privacy rights in responding to a cybersecurity threat.
Even in time-sensitive circumstances, privacy impacts are typically evaluated before undertaking a coordinated network security effort. Appropriate privacy protection measures are embedded into the underlying scope of work both at the planning and execution stages of a network security effort. Such analysis typically includes an evaluation of the specific technical and analytic techniques to be used and whether they are consistent with the ECP. It also often means defining an appropriately limited scope for network analysis activity, focusing such analysis on known signatures for APT activity and related indicators of compromise. For vendors, the ECP requires scope discipline to be enforced by contract. (See ECP, IV.A (requiring vendors to be contractually bound to honor University policy).)

Layered review is another privacy-enhancing measure used in appropriate circumstances.1 Layered review requires security alerts to be resolved in tiers, with each tier representing a limit on the type and amount of data to be reviewed. A layered review starts at the lowest tier, using automated review and basic metadata to resolve the security alert at that level. In circumstances where a security threat cannot be resolved at a lower tier or with automated means alone, the human-readable content of an underlying communication may be reviewed. The ECP limits such inspection to the “least perusal” necessary to resolve the concern. (ECP, IV.C.2.b & V.B.) To inspect content beyond what can be examined through “least perusal,” the ECP requires user consent or access without consent under a campus’s procedures, which typically involves a decision from the campus’s senior management.

I understand that some faculty members may be concerned about storage and use of data collected through network security analysis, including questions about data being used by the University for other, unrelated purposes. The ECP forbids the University from using such data for non-security purposes, (ECP, II.E.2, IV.A, & IV.C.2.b (prohibiting University employees from seeking out, using, or disclosing personal data observed in the course of performing university network security duties)), and violators are subject to discipline.2 With respect to storage, much data collected through network analysis may already be stored elsewhere within the University’s network ecosystem (or even with third party cloud or other providers), independent of any network analysis activity. Data collected or aggregated specifically for network security purposes is only stored for a limited time, segregated in a highly secure system, and forensically obliterated thereafter. In some circumstances, a preservation of certain data related to litigation may be required by law, which may result in a longer storage period for a limited amount of network analysis data subject to such a mandate. With respect to third party requests for such data, the University has a long history of defending against improperly intrusive requests, including requests under the Public Records Act.3

Governance is also a critical aspect of this discussion. Ensuring that all stakeholders are fully enrolled in developing the University’s cybersecurity policies going forward is essential. As you know, the President has launched a coordinated system-wide initiative to ensure that responsible UC authorities are appropriately informed about risks, that locations act in a consistent and coordinated way across the entire institution, and that the University can sustain action to manage cyber-risk. A number of structures have been put in place to elevate the importance of cybersecurity within University governance, some of which I described above but elaborate here for emphasis:

   The President asked the Chancellors to each appoint a single executive to lead efforts to review and improve cybersecurity at their location. These positions are the Cyber-Risk Responsible Executives (CREs), and each position reports directly to the Chancellor or location chief officer.
   A single escalation protocol has been implemented across the UC system to facilitate appropriate notification and handling of cybersecurity incidents. The protocol is intended to drive consistent analysis and response to cybersecurity incidents. It is being piloted and will be reviewed for effectiveness by the CRGC after six months.
   In addition to establishing the CRGC described above, the President has appointed a Cyber-Risk Advisory Board, composed of six internal and external expert advisors, to support the CRGC and provide information and advice about emerging issues and best practices in cybersecurity, and to help develop aggressive and effective approaches to managing cyber-risk, consistent with UC’s teaching, research, and public service mission.
   Finally, a Cyber Coordination Center is being launched to help coordinate a variety of activities across the locations.
With specific reference to faculty governance, the President has reinforced with senior management the need for ongoing dialogue with our faculty and Senate leadership. The Senate has a robust presence at the CRGC, and I believe the CRGC is the best forum to develop mechanisms and policies for further ensuring that Senate leadership is fully engaged in policy development and briefed in a timely way regarding ongoing security matters and practices.
I also welcome a discussion about how to harmonize broader cybersecurity efforts with existing, campus-specific information governance guidelines. Some campus-level guidelines, established as part of system-wide information governance initiatives, limit the specific technologies and methods that may be used for network security activities, including some methods in ordinary use at other University locations and use of which may be necessary to comply with legal duties or to effectively evaluate a specific threat that may implicate multiple locations.

Given the difficult and shifting challenges worldwide in terms of cybersecurity, there is no monopoly on wisdom here. It is my intention to approach these issues with humility and openness, believing that our efforts will only be enriched by an exchange of ideas and viewpoints. I welcome your engagement on these issues and look forward to a deeper, joint effort to protect the privacy of our users and the security of the University’s systems.

Sincerely,
Rachael Nava
Executive Vice President -
Chief Operating Officer

cc: Academic Senate Vice Chair Jim Chalfant

Vice President Tom Andriola

Deputy General Counsel Rachel Nosowsky

Associate Chancellor, Nils Gilman

UCB Professor of Business and Economics, Ben Hermalin
______________________________________________
1 A layered review is not actually required by the ECP and may not be appropriate in all cases, but it illustrates the types of measures used to rigorously observe privacy principles.
2 The ECP creates a specific exception for circumstances where an employee incidentally observes obvious illegal activity in the course of performing routine network security activities. (ECP, IV.C.2.b (defining exception for disclosure of incidentally viewed evidence of illegal conduct or improper governmental activity).)


3 Public Records Act requesters may seek far more intrusive access to the content of faculty or staff records than what the ECP permits for network security monitoring. The limits on the University’s own access to electronic communications under the ECP do not apply to Public Records Act requests.

2 February Updates

 

Suhauna Hussain. “A Web of Cyber Controversy: UC Monitoring of Campus Network Traffic Sparks Outrage among Faculty.” The Daily Californian, February 2, 2016.


Steve Lohr,  “At Berkeley, a New Digital Privacy Protest.” The New York Times, February 1, 2016

Statement from UC Berkeley CIO, 2 February:

We believe that the existing UC Berkeley policy that has been in place for a number of years strikes a privacy-security policy balance, is robust and reflects this University's best traditions and values. It is the result of a collaborative campus effort that included both staff and faculty, and like them the Berkeley administration believes that all IT policies and procedures, whether system-wide or local, should be transparent and accountable.

Larry Conrad

Chief Information Officer

UC Berkeley

3 February UPDATES:


  • The UCSB Faculty Association requested clarification on the surveillance program from Santa Barbara Divisional Senate Chair



Dear Kum Kum,
    We write because we are deeply disturbed by the recent report that UCOP has installed surveillance software “capable of monitoring all e-mails going in and out of the UC system”
(http://www.sfchronicle.com/bayarea/matier-ross/article/Cal-professors-fear-UC-bosses-will-snoop-on-them-6794646.php?t=1c3d144ee43ba53be4&cmpid=twitter-premium%20via%20@sfchronicle).   While we are aware that officials at UCOP have sent a letter explaining the context and rationale for installing this software, we do not find that the letter addresses adequately the potential threat that taking such measures poses to academic freedom and shared governance.   As the Board of the UCSB Faculty Association, we request that you ask Chancellor Yang for an immediate and full accounting of all electronic surveillance capabilities now in existence and/or in operation at UCSB, and that you make that information available to all members of the UCSB Academic Senate.
  With thanks,
 Julie Carlson
Jorge Luis Castillo
Nelson Lichtenstein
Constance Penley
Erika Rappaport
Elisabeth Weber
Robert Williams

  • UCSB Chancellor Henry Yang sent a modified version of COO Nava's 1/19 memo, which you can read here.

  • The UC Academic Senate Committee on Academic Computing and Communications has issued a statement we've posted here.  Although the object to the end-run around shared governance in the name of urgent security matters, they give a pass to the surveillance itself--see the final 2 bullet points in particular.


Posted by Chris Newfield | Comments: 25