<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Securing IP Cameras</title>
	<atom:link href="http://managedvideoblog.com/2008/12/26/securing-ip-cameras/feed/" rel="self" type="application/rss+xml" />
	<link>http://managedvideoblog.com/2008/12/26/securing-ip-cameras/</link>
	<description>The place to learn about and discuss Managed Video as a Service</description>
	<lastBuildDate>Fri, 26 Feb 2010 21:51:22 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dloher</title>
		<link>http://managedvideoblog.com/2008/12/26/securing-ip-cameras/comment-page-1/#comment-281</link>
		<dc:creator>dloher</dc:creator>
		<pubDate>Mon, 29 Dec 2008 18:30:18 +0000</pubDate>
		<guid isPermaLink="false">http://managedvideoblog.com/?p=1228#comment-281</guid>
		<description>Hi John,    There are certainly differences in vendors, in part due to the methods they implement for getting video.  I can say that securing an IP camera network is not at all automatic and the &quot;threat profile&quot; of an IP video capture network is significantly larger than analog video capture.      That being said, I&#039;d like to re-iterate that there are still ways make IP camera systems secure.  It&#039;s a matter of how much security you need, how you&#039;re willing to restrict access and how much network expertise one has available to implement and maintain security.      I&#039;ll give a few examples:    Some vendors for example only implement HTTP and TFTP protocols for transmitting video which do not implement encryption.  TFTP doesn&#039;t even implement userid&#039;s and passwords.   Other vendors support FTP, which adds userid&#039;s and passwords, but still no encryption.      RTSP is probably the best protocol to use for transmitting video between an NVR and an IP Camera.  But it too does not support encryption.  RTSPS (modeled after HTTPS, the standard for web based encryption) is a defined standard, but I don&#039;t know of anyone who implements it.      HTTPS (for JPEG image push) is available, but I don&#039;t know of any camera manufacturers who implement it for video transmission.  (Axis implements HTTP to secure administrative communication in newer firmware versions, but not for video as far as I know)    Now, not everyone needs encryption between the NVR and IP Camera.  By configuring VLAN&#039;s and port based access control, one can minimize the exposure due to unencrypted traffic.  Like most IT security, how much security you need depends on your requirements.      Note, in order to be PCI DSS compliant, to protect cardholder (ie: credit card) information one MUST encrypt any data which includes information that reveals credit card data and the card holder.  I interpret this to mean if one can read a credit card number in a video stream, that video stream now contains cardholder data and needs to be encrypted and protected.  While generally not an issue with analog cameras, this could become an issue with megapixel cameras.      Envysion pretty much automates security up to an &quot;enterprise level&quot;.   We can do that because we know all the in&#039;s and outs of our IP enabled DVR (EnVR) and have comprehensive protection for the EnVR.   It&#039;s easier to secure 400 IP DVR&#039;s with 8 analog cameras each than it is to secure 400 IP DVR&#039;s and 3200 IP cameras.  Reducing the number of NVR&#039;s doesn&#039;t help much.  It&#039;s all those IP cameras that become difficult to secure and monitor for security.  The &quot;threat profile&quot; is so much larger with IP cameras that if one has significant security requirements, one has to work pretty hard to meet them.      </description>
		<content:encoded><![CDATA[<p>Hi John,    There are certainly differences in vendors, in part due to the methods they implement for getting video.  I can say that securing an IP camera network is not at all automatic and the &quot;threat profile&quot; of an IP video capture network is significantly larger than analog video capture.      That being said, I&#039;d like to re-iterate that there are still ways make IP camera systems secure.  It&#039;s a matter of how much security you need, how you&#039;re willing to restrict access and how much network expertise one has available to implement and maintain security.      I&#039;ll give a few examples:    Some vendors for example only implement HTTP and TFTP protocols for transmitting video which do not implement encryption.  TFTP doesn&#039;t even implement userid&#039;s and passwords.   Other vendors support FTP, which adds userid&#039;s and passwords, but still no encryption.      RTSP is probably the best protocol to use for transmitting video between an NVR and an IP Camera.  But it too does not support encryption.  RTSPS (modeled after HTTPS, the standard for web based encryption) is a defined standard, but I don&#039;t know of anyone who implements it.      HTTPS (for JPEG image push) is available, but I don&#039;t know of any camera manufacturers who implement it for video transmission.  (Axis implements HTTP to secure administrative communication in newer firmware versions, but not for video as far as I know)    Now, not everyone needs encryption between the NVR and IP Camera.  By configuring VLAN&#039;s and port based access control, one can minimize the exposure due to unencrypted traffic.  Like most IT security, how much security you need depends on your requirements.      Note, in order to be PCI DSS compliant, to protect cardholder (ie: credit card) information one MUST encrypt any data which includes information that reveals credit card data and the card holder.  I interpret this to mean if one can read a credit card number in a video stream, that video stream now contains cardholder data and needs to be encrypted and protected.  While generally not an issue with analog cameras, this could become an issue with megapixel cameras.      Envysion pretty much automates security up to an &quot;enterprise level&quot;.   We can do that because we know all the in&#039;s and outs of our IP enabled DVR (EnVR) and have comprehensive protection for the EnVR.   It&#039;s easier to secure 400 IP DVR&#039;s with 8 analog cameras each than it is to secure 400 IP DVR&#039;s and 3200 IP cameras.  Reducing the number of NVR&#039;s doesn&#039;t help much.  It&#039;s all those IP cameras that become difficult to secure and monitor for security.  The &quot;threat profile&quot; is so much larger with IP cameras that if one has significant security requirements, one has to work pretty hard to meet them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Honovich</title>
		<link>http://managedvideoblog.com/2008/12/26/securing-ip-cameras/comment-page-1/#comment-280</link>
		<dc:creator>John Honovich</dc:creator>
		<pubDate>Fri, 26 Dec 2008 22:03:09 +0000</pubDate>
		<guid isPermaLink="false">http://managedvideoblog.com/?p=1228#comment-280</guid>
		<description>Hi Darren,    Great post. As you are surveying and testing IP cameras for Envysion to support, do you see major differences between camera vendors? As in, do you think some vendors are significantly more secure than others?    From a network/IT management perspective, would this be an important factor in deciding on cameras to recommend?    Thanks,    John  </description>
		<content:encoded><![CDATA[<p>Hi Darren,    Great post. As you are surveying and testing IP cameras for Envysion to support, do you see major differences between camera vendors? As in, do you think some vendors are significantly more secure than others?    From a network/IT management perspective, would this be an important factor in deciding on cameras to recommend?    Thanks,    John</p>
]]></content:encoded>
	</item>
</channel>
</rss>
