<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>CIS Blog</title>
	<atom:link href="http://blogs.brown.edu/cis/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.brown.edu/cis</link>
	<description>Status Updates, News, and Features from Computing and Information Systems at Brown University</description>
	<lastBuildDate>Tue, 18 Jun 2013 18:32:39 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Brown Wireless Network Access</title>
		<link>http://blogs.brown.edu/cis/2013/06/18/brown-wireless-network-access/</link>
		<comments>http://blogs.brown.edu/cis/2013/06/18/brown-wireless-network-access/#comments</comments>
		<pubDate>Tue, 18 Jun 2013 18:32:39 +0000</pubDate>
		<dc:creator>Richard A. Lawson</dc:creator>
				<category><![CDATA[Outages & Alerts]]></category>

		<guid isPermaLink="false">http://blogs.brown.edu/cis/?p=12040</guid>
		<description><![CDATA[We are aware of a problem with Wireless Access  and are working to identify and resolve the issue. Between 2:10 and 2:25 pm there were brief wireless outages at various locations throughout campus.  Functionality that may be impacted by this problem includes: connection to the Brown wireless network.]]></description>
				<content:encoded><![CDATA[<p>We are aware of a problem with Wireless Access  and are working to identify and resolve the issue. Between 2:10 and 2:25 pm there were brief wireless outages at various locations throughout campus.  Functionality that may be impacted by this problem includes: connection to the Brown wireless network.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.brown.edu/cis/2013/06/18/brown-wireless-network-access/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Resolved: Wowza Audio and Video Streaming not accessible at this time</title>
		<link>http://blogs.brown.edu/cis/2013/06/17/wowza-audio-and-video-streaming-not-accessible-at-this-time/</link>
		<comments>http://blogs.brown.edu/cis/2013/06/17/wowza-audio-and-video-streaming-not-accessible-at-this-time/#comments</comments>
		<pubDate>Mon, 17 Jun 2013 20:11:36 +0000</pubDate>
		<dc:creator>dmbello@brown.edu</dc:creator>
				<category><![CDATA[Outages & Alerts]]></category>

		<guid isPermaLink="false">http://blogs.brown.edu/cis/?p=12032</guid>
		<description><![CDATA[Update: 6/17 7:55pm &#8211; RESOLVED We are aware of a problem with Wowza Audio &#38; Video Streaming and are working to identify and resolve the issue. This includes playback of Echo 360 captures. Functionality that may be impacted by this problem includes: access to and use of audio and video streaming. We will be posting [...]]]></description>
				<content:encoded><![CDATA[<p>Update: 6/17 7:55pm &#8211; RESOLVED</p>
<p>We are aware of a problem with Wowza Audio &amp; Video Streaming and are working to identify and resolve the issue. This includes playback of Echo 360 captures. Functionality that may be impacted by this problem includes: access to and use of audio and video streaming.</p>
<p>We will be posting all updates, including the resolution of the problem, on the CIS blog at http://blogs.brown.edu/cis &#8211; please check the blog regularly for updates.</p>
<p>If you experience problems other than the ones mentioned above, or problems with another service, please report them to the Help Desk at (401) 863-4357.  We apologize for any inconvenience this may cause.</p>
<p>Thank you for your patience,<br />
Computing and Information Services</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.brown.edu/cis/2013/06/17/wowza-audio-and-video-streaming-not-accessible-at-this-time/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Resolved: Issue with Echo360 video streaming and campus video streaming services</title>
		<link>http://blogs.brown.edu/cis/2013/06/17/issue-with-echo360-video-streaming-and-campus-video-streaming-services/</link>
		<comments>http://blogs.brown.edu/cis/2013/06/17/issue-with-echo360-video-streaming-and-campus-video-streaming-services/#comments</comments>
		<pubDate>Mon, 17 Jun 2013 19:34:59 +0000</pubDate>
		<dc:creator>dmbello@brown.edu</dc:creator>
				<category><![CDATA[Outages & Alerts]]></category>

		<guid isPermaLink="false">http://blogs.brown.edu/cis/?p=12028</guid>
		<description><![CDATA[Update: 6/17 7:55pm &#8211; RESOLVED &#160; We are aware of a problem with Lecture Capture &#8211; Echo 360 and are working to identify and resolve the issue.  Functionality that may be impacted by this problem includes: instructor recording of lecture audio, video and/or PowerPoint or other computer program display outputs. We will be posting all [...]]]></description>
				<content:encoded><![CDATA[<p>Update: 6/17 7:55pm &#8211; RESOLVED</p>
<p>&nbsp;</p>
<p>We are aware of a problem with Lecture Capture &#8211; Echo 360 and are working to identify and resolve the issue.  Functionality that may be impacted by this problem includes: instructor recording of lecture audio, video and/or PowerPoint or other computer program display outputs.</p>
<p>We will be posting all updates, including the resolution of the problem, on the CIS blog at http://blogs.brown.edu/cis &#8211; please check the blog regularly for updates.</p>
<p>If you experience problems other than the ones mentioned above, or problems with another service, please report them to the Help Desk at (401) 863-4357.  We apologize for any inconvenience this may cause.</p>
<p>Thank you for your patience,<br />
Computing and Information Services</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.brown.edu/cis/2013/06/17/issue-with-echo360-video-streaming-and-campus-video-streaming-services/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;Resource 25 Access Restored&#8221; email message</title>
		<link>http://blogs.brown.edu/cis/2013/06/11/resource-25-access-restored-email-message/</link>
		<comments>http://blogs.brown.edu/cis/2013/06/11/resource-25-access-restored-email-message/#comments</comments>
		<pubDate>Tue, 11 Jun 2013 18:58:52 +0000</pubDate>
		<dc:creator>jasdeep b.</dc:creator>
				<category><![CDATA[Outages & Alerts]]></category>

		<guid isPermaLink="false">http://blogs.brown.edu/cis/?p=12016</guid>
		<description><![CDATA[If you received an email regarding Resource 25, it was sent in error. You can disregard the email. It is not spam and/or a phishing attempt, and will not harm your computer. Simply delete the email. Please accept our apologies, Computing and Information Services &#160;]]></description>
				<content:encoded><![CDATA[<p>If you received an email regarding Resource 25, it was sent in error. You can disregard the email.<br />
It is not spam and/or a phishing attempt, and will not harm your computer. Simply delete the email.</p>
<p>Please accept our apologies,<br />
Computing and Information Services</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.brown.edu/cis/2013/06/11/resource-25-access-restored-email-message/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Tip: Forms Update</title>
		<link>http://blogs.brown.edu/cis/2013/06/11/google-tip-forms-update/</link>
		<comments>http://blogs.brown.edu/cis/2013/06/11/google-tip-forms-update/#comments</comments>
		<pubDate>Tue, 11 Jun 2013 18:21:31 +0000</pubDate>
		<dc:creator>sobodda@brown.edu</dc:creator>
				<category><![CDATA[Tips & Tricks]]></category>
		<category><![CDATA[google]]></category>

		<guid isPermaLink="false">http://blogs.brown.edu/cis/?p=12008</guid>
		<description><![CDATA[Google Forms recently updated to be more consistent with other Google Drive document types. Two helpful new features are auto save and real-time collaboration. The new format is fairly intuitive, but you should be aware of one major change &#8211; form responses do not get collected in a spreadsheet by default. To indicate that you [...]]]></description>
				<content:encoded><![CDATA[<p>Google Forms <a href="http://googleenterprise.blogspot.com/2013/01/google-forms-refreshed.html">recently updated</a> to be more consistent with other Google Drive document types. Two helpful new features are auto save and real-time collaboration. The new format is fairly intuitive, but you should be aware of one major change &#8211; form responses do not get collected in a spreadsheet by default.</p>
<p>To indicate that you would like to collect responses in a spreadsheet, click the &#8220;Choose response destination&#8221; button at the top while editing the form.</p>
<p><a href="http://blogs.brown.edu/cis/files/2013/06/Screen-Shot-2013-06-11-at-2.14.32-PM.jpg" rel="shadowbox[sbpost-12008];player=img;"><img class="alignnone size-full wp-image-12009" alt="Choose Response Destination" src="http://blogs.brown.edu/cis/files/2013/06/Screen-Shot-2013-06-11-at-2.14.32-PM.jpg" width="213" height="51" /></a><br />
Next, you will be prompted to name the spreadsheet in which the responses will be collected. You will also see an option to always create new spreadsheets for forms.</p>
<p><a href="http://blogs.brown.edu/cis/files/2013/06/Screen-Shot-2013-06-11-at-2.16.15-PM.jpg" rel="shadowbox[sbpost-12008];player=img;"><img class="alignnone  wp-image-12010" alt="Always create a new spreadsheet for forms" src="http://blogs.brown.edu/cis/files/2013/06/Screen-Shot-2013-06-11-at-2.16.15-PM.jpg" width="267" height="158" /></a></p>
<p><a href="https://support.google.com/drive/answer/2917686?p=forms_response&amp;rd=1">More information about response destinations<br />
</a><a href="http://googleenterprise.blogspot.com/2013/01/google-forms-refreshed.html">More information about the recent updates to Google Forms</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.brown.edu/cis/2013/06/11/google-tip-forms-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>KeyServer to a new host</title>
		<link>http://blogs.brown.edu/cis/2013/06/10/keyserver-to-a-new-host/</link>
		<comments>http://blogs.brown.edu/cis/2013/06/10/keyserver-to-a-new-host/#comments</comments>
		<pubDate>Mon, 10 Jun 2013 18:54:42 +0000</pubDate>
		<dc:creator>Bobby Sengchanthavong</dc:creator>
				<category><![CDATA[Outages & Alerts]]></category>

		<guid isPermaLink="false">http://blogs.brown.edu/cis/?p=12004</guid>
		<description><![CDATA[UPDATE: 6.13.20.13 : The KeyServer migration planned for Thursday (6-13-13) has been reschedule for Friday (6-14-13). See posting from Monday (6-10-13) for further details. On Thursday 6/13/2013 we will be migrating the KeyServer to a new host which will also involve upgrading the shadow/backup servers after the primary server is complete. This migration will start at 6am and should be complete by 9am. Please do not install [...]]]></description>
				<content:encoded><![CDATA[<p><strong>UPDATE: 6.13.20.13 : </strong>The KeyServer migration planned for Thursday (6-13-13) has been reschedule for Friday (6-14-13). See posting from Monday (6-10-13) for further details.</p>
<p>On Thursday 6/13/2013 we will be migrating the KeyServer to a new host which will also involve upgrading the shadow/backup servers after the primary server is complete. This migration will start at 6am and should be complete by 9am. Please do not install or update any clients during this time since the process will fail if the primary server is off-line. Shadow/Backup servers should handle any requests for license keys during this period for existing clients.</p>
<p>If you experience problems other than the ones mentioned above, or problems with another service, please report them to the Help Desk at <a href="http://blogs.brown.edu/cis/page/2/%28401%29%20863-4357" target="_blank">(401) 863-4357</a>.  We apologize for any inconvenience this may cause.</p>
<p>Thank you for your patience,<br />
Computing and Information Services</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.brown.edu/cis/2013/06/10/keyserver-to-a-new-host/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Phishing Alert: Notice from IRS</title>
		<link>http://blogs.brown.edu/cis/2013/06/06/phishing-alert-notice-from-irs/</link>
		<comments>http://blogs.brown.edu/cis/2013/06/06/phishing-alert-notice-from-irs/#comments</comments>
		<pubDate>Thu, 06 Jun 2013 15:47:42 +0000</pubDate>
		<dc:creator>pfalcon</dc:creator>
				<category><![CDATA[Outages & Alerts]]></category>
		<category><![CDATA[Phishing & Malware Alerts]]></category>
		<category><![CDATA[Safe Computing]]></category>

		<guid isPermaLink="false">http://blogs.brown.edu/cis/?p=11997</guid>
		<description><![CDATA[ISG and the Help Desk have received multiple reports of a phishing email supposedly from the IRS asking you to update your information due to an upgrade of its servers. While it is obviously a phishing attempt, the incident is a good reminder to stay vigilant as emails like these arrive from a variety of [...]]]></description>
				<content:encoded><![CDATA[<p><a href="http://blogs.brown.edu/cis/files/2011/03/fish_sml_w1.jpg" rel="shadowbox[sbpost-11997];player=img;"><img class="alignright size-full wp-image-6935" alt="Fish on a plate" src="http://blogs.brown.edu/cis/files/2011/03/fish_sml_w1.jpg" width="153" height="90" /></a>ISG and the Help Desk have received multiple reports of a phishing email supposedly from the IRS asking you to update your information due to an upgrade of its servers. While it is obviously a phishing attempt, the incident is a good reminder to stay vigilant as emails like these arrive from a variety of senders (some from compromised Brown addresses) with different messages, but generally all with the same purpose:  to convince you to give up personal information or direct you to a site where your account may be compromised.</p>
<p><span id="more-11997"></span>If you received this email (example below) and have not already deleted it, please report it as phishing (in the email click on the down arrow to the right of the REPLY button and select “Report phishing”) to send that message to the GMail Team for analysis and filtering. <a href="http://blogs.brown.edu/cis/2012/04/17/phishing-alert-your-mailbox-has-exceeded/#more-9327"><em>Read more about how to spot a phish</em></a>.</p>
<p>&#8212;&#8212;&#8212;- SAMPLE EMAIL &#8212;&#8212;&#8212;-<br />
From: IRS.gov* &lt;XXX_XXX@brown.edu&gt;<br />
Date: Wed, Jun 5, 2013 at 3:38 PM<br />
Subject: ***NOTICE: Re-Validate your IRS Information NOW.<br />
To:</p>
<p>This is to inform you that the IRS is upgrading its servers and we would like you to update your IRS information with the current and correct information by clicking on the link below and inputting the correct information.</p>
<p>To Re-Validate- &lt; Click Here &gt;<br />
Make sure you fill the correct data to update your current IRS filing status.<br />
NOTE: That Failure to comply may result in the loss of your information from the IRS Master File within the next 48 hours.</p>
<p>Signed,<br />
Director, Office of Privacy,Governmental Liaison and Disclosure<br />
Internal Revenue Service<br />
Room 7050 OS:P<br />
1111 Constitution Ave. NW<br />
Washington, DC 20224</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.brown.edu/cis/2013/06/06/phishing-alert-notice-from-irs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unencrypted Connection Error</title>
		<link>http://blogs.brown.edu/cis/2013/06/03/unencrypted-connection-error/</link>
		<comments>http://blogs.brown.edu/cis/2013/06/03/unencrypted-connection-error/#comments</comments>
		<pubDate>Mon, 03 Jun 2013 15:44:50 +0000</pubDate>
		<dc:creator>sobodda@brown.edu</dc:creator>
				<category><![CDATA[Outages & Alerts]]></category>
		<category><![CDATA[Web and Online Collaboration]]></category>

		<guid isPermaLink="false">http://blogs.brown.edu/cis/?p=11986</guid>
		<description><![CDATA[When logging into some restricted Brown websites, you might see a pop-up with the following error: &#8220;Although this page is encrypted, the information you have entered is to be sent over an unencrypted connection and could easily be read by a third party.&#8221; This error may appear on some Brown websites which use Shibboleth, Brown&#8217;s [...]]]></description>
				<content:encoded><![CDATA[<p dir="ltr">When logging into some restricted Brown websites, you might see a pop-up with the following error: &#8220;Although this page is encrypted, the information you have entered is to be sent over an unencrypted connection and could easily be read by a third party.&#8221;</p>
<p><b><b><a href="http://blogs.brown.edu/cis/files/2013/06/Screen-Shot-2013-06-03-at-11.42.37-AM.jpg" rel="shadowbox[sbpost-11986];player=img;"><img class="alignnone  wp-image-11989" alt="Screen Shot 2013-06-03 at 11.42.37 AM" src="http://blogs.brown.edu/cis/files/2013/06/Screen-Shot-2013-06-03-at-11.42.37-AM.jpg" width="462" height="129" /></a><br />
</b></b></p>
<p dir="ltr">This error may appear on some Brown websites which use <a href="http://www.brown.edu/cis/services/shibboleth/welcomeshib.html">Shibboleth</a>, Brown&#8217;s newer method of controlling access to a web page. As web owners across the University convert websites to Shibboleth, website visitors may see this error more often because Shibboleth requires that the web pages be secure, i.e., https:// instead of http://. Therefore, old links or bookmarks to the http:// (instead of https://) address of a website will now cause this error to appear.</p>
<p>If you are simply viewing a page, there is no need to worry about this error. However, if you see it on a page on which you are submitting sensitive and/or personal information, you should contact the website owner. If you are the owner of a Brown website and visitors are seeing this message on your site, you can contact the <a href="http://www.brown.edu/cis/support/help_desk/">CIS Help Desk</a> for a fix which prevents the message from appearing.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.brown.edu/cis/2013/06/03/unencrypted-connection-error/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RESOLVED: CIS Service Alert: Listserv, 6/02 3:27 PM</title>
		<link>http://blogs.brown.edu/cis/2013/06/02/cis-service-alert-listserv-602-327-pm/</link>
		<comments>http://blogs.brown.edu/cis/2013/06/02/cis-service-alert-listserv-602-327-pm/#comments</comments>
		<pubDate>Sun, 02 Jun 2013 19:37:54 +0000</pubDate>
		<dc:creator>sdillon@brown.edu</dc:creator>
				<category><![CDATA[Outages & Alerts]]></category>

		<guid isPermaLink="false">http://blogs.brown.edu/cis/?p=11980</guid>
		<description><![CDATA[We are aware of a problem with Listserv and are working to identify and resolve the issue. Functionality that may be impacted by this problem includes: sending mail to a Listserv, managing membership of a Listserv &#8211; bulk e-mail service for community and course announcement lists is NOT affected. We will be posting all updates, [...]]]></description>
				<content:encoded><![CDATA[<p>We are aware of a problem with Listserv and are working to identify and resolve the issue. Functionality that may be impacted by this problem includes: sending mail to a Listserv, managing membership of a Listserv &#8211; bulk e-mail service for community and course announcement lists is NOT affected.</p>
<p>We will be posting all updates, including the resolution of the problem, on the CIS blog at http://blogs.brown.edu/cis &#8211; please check the blog regularly for updates.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.brown.edu/cis/2013/06/02/cis-service-alert-listserv-602-327-pm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CISO Memo: Broadening Connections &amp; Multiple Hats</title>
		<link>http://blogs.brown.edu/cis/2013/05/30/ciso-memo-broadening-connections-multiple-hats/</link>
		<comments>http://blogs.brown.edu/cis/2013/05/30/ciso-memo-broadening-connections-multiple-hats/#comments</comments>
		<pubDate>Thu, 30 May 2013 12:50:37 +0000</pubDate>
		<dc:creator>pfalcon</dc:creator>
				<category><![CDATA[Current Edition]]></category>
		<category><![CDATA[Newsletters]]></category>
		<category><![CDATA[Safe Computing]]></category>
		<category><![CDATA[Summer 2013 Edition]]></category>

		<guid isPermaLink="false">http://blogs.brown.edu/cis/?p=11783</guid>
		<description><![CDATA[Many people have asked me recently about how information security is evolving.  More and more CISOs now have a broader, risk-based focus on information protection, and many have privacy and compliance responsibilities as well. This rapid maturation is both welcome and daunting for security pros, and as a result we look to the larger community [...]]]></description>
				<content:encoded><![CDATA[<p><a href="http://blogs.brown.edu/cis/2013/05/30/ciso-memo-broadening-connections-multiple-hats/"><img class="alignleft size-full wp-image-7477" alt="David Sherry" src="http://blogs.brown.edu/cis/files/2011/06/dsherry_mdm_w.jpg" width="100" height="133" /></a>Many people have asked me recently about how information security is evolving.  More and more CISOs now have a broader, risk-based focus on information protection, and many have privacy and compliance responsibilities as well. This rapid maturation is both welcome and daunting for security pros, and as a result we look to the larger community for support, guidance and networking. I’d like to share with you some of the connections that I have through Brown.</p>
<p><span id="more-11783"></span>Security professionals are very willing to engage in information sharing, all for the betterment of our profession and our institutions. I have the luxury of have three distinct security groups that I can go to for information, including our Ivy+ community, the New England Higher Ed Security Officers Forum, and a wider group from throughout the northeast known as the <a href="http://www.nox.org/">Northern Crossroads</a>. More broadly, I also participate in <a href="http://www.educause.edu">EDUCAUSE</a> working groups, as well as the yearly <a href="http://www.educause.edu/events/security-professionals-conference/">Security Professionals Conference</a>. This conference is the go-to event for me, as it is specifically for higher education, and great in content, solution providers and networking.</p>
<p>There are also external groups that provide great value to me and Brown. These include industry groups such as the <a href="http://www.isc2.org">ISC2</a>, <a href="http://www.isaca.org/">ISACA</a> and <a href="http://www.issa.org">ISSA</a>, as well as organizations such as the <a href="https://cloudsecurityalliance.org/">Cloud Security Alliance</a> and <a href="https://www.infragard.org/">FBI-InfraGard</a>.</p>
<p>Why am I sharing this? To let you know that Brown desires to stay on top of security, privacy and compliance issues, and for me to glean this all on my own would be impossible. Higher ed is a sharing and open community, and because of this, we are all in a better state of security.</p>
<p>This is impacting my role here at Brown as well, which I’ve written about in past articles.  For my recent viewpoint on the changing role of a CISO, see my article at TechTarget Security called “<a href="http://searchsecurity.techtarget.com/opinion/CISOs-From-no-seat-to-multiple-hats">From No Seat to Multiple Hats</a>”.</p>
<p>As always, I welcome your comments and feedback. Please feel free to reach out to me directly at <a href="mailto:david_sherry@brown.edu">david_sherry@brown.edu</a>, or the group at <a href="mailto:isg@brown.edu">ISG@brown.edu</a>. Let me know how we are doing, areas of concern you may have, or questions on protecting your identity or personal computing security. And remember, sec_rity is not complete without U!</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.brown.edu/cis/2013/05/30/ciso-memo-broadening-connections-multiple-hats/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->