CCR Communications Plan
- Hersberger, Mark (Deactivated)
Objective:
Create general awareness among PIs and administrators regarding CCR and provoke certification submissions.Â
Audience
Primary: All Principal Investigators (PIs) at UC San Diego (including Health Sciences)
Secondary: High risk labs; Distributed tech community, Deans, Chairs,Â
Goals
Have all PIs complete certification by Dec. 31, 2022Â
General Approach
- Communicate frequently via Chairs and Deans and distributed tech communityÂ
- Avail ourselves to attend as many department meetings as possible - either existing periodic faculty meetings or on-demand meetings
- Equip chairs, deans and distributed tech community to educate their PIs on CCR program and steps to completionÂ
Messages
- Complete the Cybersecurity for Research Certification (CCR) process. CCR
- Guides you through simple-yet-effective cybersecurity practices endorsed by the Office of Information Assurance
- Ensures IT security specialists can provide immediate assistance if a hack or data theft occurs
- Includes implementation help when you need itÂ
Channels
- totalcampusdeans-l@ucsd.edu
- totalcampuschairs-l@ucsd.edu
- sysadmin-l@ucsd.eduÂ
- High-risk lab mailing listÂ
- Workshops (self conducted and hosted in conjunction with RCI)
Related Needs
- "Scorecard" to track progress and communications effectiveness - to be reviewed periodically (weekly or monthly)
- DIY PPT for chairs and distributed tech to present at meetings
| Action | Message | Audience | Person | |
|---|---|---|---|---|
| March 21 - 25 | ||||
 | RCI hot topics workshop | Program tutorial and live demo | Mike / Claire | |
 | Obtain list of RCI attendees | Mike / Claire | ||
 | Draft 3/30 follow up email to RCI attendees | Reminder to complete certification, email ccr-support@ucsd.edu for help | Mark / Mike / Claire | |
 | Draft 3/30 email to deans/ chairs | Describe program and urge all PIs to complete Inform we're available for department or other meetings Emphasize that completing CCR is the best thing they can do to secure their lab and get help if an attack or breach does occur. Provide info to forward that:
| Mark / Mike | |
 | Draft 3/30 email to sysadmin-l | Mention that we contacted deans and chairs and high-risk labs and we're urging PIs to complete ASAP. Request to coordinate with chairs/deans to distribute information Inform of 3/23 RCI workshop and encourage their PIs to attend Contact Mike or Claire to schedule a specialized workshop for their area | Mark / Mike | |
 | Draft 3/30 email to high risk | Describe CCR and explain why it's extra important to complete (best way to protect lab and be prepared if incident does occur). Mention 4/13 RCI workshop Direct to assure.ucsd.edu and/or ccr-support@ucsd.edu | Mark / Mike | |
 | Pull email list of high risk labs | Daniel | ||
| March 28 - April 1 | ||||
 | Email deans and chairs | see above | Mike | |
 | Email campus tech community | see above | sysadmin-l@ucsd.edu | Mike |
 | Email high risk labs | see above | High risk list | Mike (Mark email blast program) |
 | Email to 3/23 RCI attendees | see above | RCI attendees | Mike/Claire |
 | Draft 4/6 email to RCI attendees | Reminder to complete and email ccr-support@ucsd.edu if assistance needed | Mike/Mark/Claire | |
| April 4 - 8Â | ||||
 | Email to RCI attendees | Reminder to complete certification | Claire | |
 | Draft 4/14 email to deans and chairs | Thank for previous support; update on completed certifications.  Remind we're available for department or other meetings Emphasize that completing CCR is the best thing they can do to secure their lab and get help if an attack or breach does occur. Provide info to forward that:
| Mike/Mark | |
 | Draft 4/14 email to high risk | Thank those who have started process or contact CCR-support@ucsd.edu Remind of program importance, procedures and how to get help | Mike/Mark | |
 | Draft 4/14 email to sysadmin-l | Reinforce messages to chairs/deans and high risk Remind we're available for meetings and workshops | Mike/Mark | |
April 11 - April 15 | ||||
 | RCI Hot Topics Workshop | Provide program overview and hands-on workshop to complete certification | Mike/Claire | |
 | Obtain list of RCI attendees | Mike/Claire | ||
 | Email to Deans and Chairs | see above | ||
 | Email to high risk | see above | ||
 | Email to sysadmin | see above | ||
 | Draft 4/20 follow up to RCI attendees | Thank for attending; encourage to complete; remind to contact ccr-support@uscd.edu | Mark/Mike/Claire | |
| April 18 - 22 | ||||
 | Email to RCI attendees | See above | Mike/Claire | |
| April 25 - 29 | ||||
 | Email to RCI attendees | see above | ||
 | Email to 4/13 RCI attendees | Reminder to complete certification | Mike / Claire | |
 | Draft 5/4 email to RCI attendees | Mark/Mike/Claire | ||
| May 2 - 6 | ||||
 | Email to 4/13 RCI attendees | Final reminder | Mike/Claire | |
 | Draft 5/11 email to deans/chairs | Remind about program; provide information to forward; avail ourselves for customized meetings; mention 5/18 workshop | ||
 | Draft 5/11 email to high risk | Urge to complete; remind about help channels; mention 5/18 workshop | ||
 | Draft 5/11 email to tech community | Reinforce deans/chairs email and high risk email | ||
| May 9 - 13 | ||||
 | Email to deans chairs | Program update and reminder. Mention 5/18 workshop | ||
 | Email to high risk | Program update and reminder. Mention 5/18 workshop | ||
 | Email to sysadmin | Reinforce deans/chairs and high-risk emails | ||
 | Draft follow up for 5/18 workshop | |||
| May 16 - 20 | ||||
 | Conduct how-to workshop | Mike/Claire/Daniel | ||
May 23 - 27 | ||||
 | Email to 5/18 attendees | Mike/Claire | ||