<?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>IT Governance, Risk, and Compliance &#187; Transport Mode</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/it-governance/tag/transport-mode/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/it-governance</link>
	<description></description>
	<lastBuildDate>Mon, 17 Jun 2013 01:33:42 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>A Few Fundamental Features of IPv6 Internetworking – Part VI</title>
		<link>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamental-features-of-ipv6-internetworking-part-vi/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamental-features-of-ipv6-internetworking-part-vi/#comments</comments>
		<pubDate>Sat, 17 Nov 2012 01:58:18 +0000</pubDate>
		<dc:creator>Robert Davis</dc:creator>
				<category><![CDATA[Authentication]]></category>
		<category><![CDATA[Availability Management]]></category>
		<category><![CDATA[Cloud Computing]]></category>
		<category><![CDATA[Configuration Management]]></category>
		<category><![CDATA[Encapsulating Security Payload]]></category>
		<category><![CDATA[ICT]]></category>
		<category><![CDATA[Information and Communication Technology]]></category>
		<category><![CDATA[Information Technology Service Management]]></category>
		<category><![CDATA[Infrastructure Management]]></category>
		<category><![CDATA[Internet Protocol Security]]></category>
		<category><![CDATA[IPSec]]></category>
		<category><![CDATA[IT Hardware]]></category>
		<category><![CDATA[IT Security]]></category>
		<category><![CDATA[Multiprocessing]]></category>
		<category><![CDATA[Public Key Infrastructure]]></category>
		<category><![CDATA[Service Delivery]]></category>
		<category><![CDATA[Transport Mode]]></category>
		<category><![CDATA[Tunnel Mode]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-governance/?p=1685</guid>
		<description><![CDATA[Why understanding IPv6 is important to end-users Currently, the dominant internetworking protocol is Internet Protocol version 4 (IPv4). Yet, each IPv4 address is limited to a thirty-two bit field length, which corresponds to a maximum of approximately four billion unique internetworking addresses. IPv6 is the next generation of IP messaging that uses a one-hundred-twenty-eight bit [...]]]></description>
				<content:encoded><![CDATA[<p><strong>Why understanding IPv6 is important to end-users</strong></p>
<p>Currently, the dominant internetworking protocol is Internet Protocol version 4 (<a href="http://www.techterms.com/definition/ipv4">IPv4</a>). Yet, each IPv4 address is limited to a thirty-two bit field length, which corresponds to a maximum of approximately four billion unique internetworking addresses. IPv6 is the next generation of IP messaging that uses a one-hundred-twenty-eight bit field length, resulting in an enormous increase of supportable unique addresses. In fact, the new allotment will permit every person on this planet to have over four billion internetworking addresses!</p>
<p>Potential IPv6 conversion issues are internetworking device computational and/or bandwidth overhead, which in turn can impact communication performance. End-users who are planning migration to IPv6 as well as designers and implementers of IPv6, must understand the technology in order to assess the risks associated with this paradigm shift and prepare effective and efficient responses.</p>
<p><iframe width="560" height="315" src="http://www.youtube.com/embed/e406-JlLPMs" frameborder="0" allowfullscreen></iframe></p>
<p><em>Sources</em>:</p>
<p>Davis, Robert E. <em>IT Auditing: Assuring Information Assets Protection</em>. Mission Viejo, CA: Pleier Corporation, 2008. CD-ROM.</p>
<p>IBM. Armonk, New York: International Business Machines. <a href="http://publib.boulder.ibm.com/infocenter/zvm/v5r4/index.jsp?topic=/com.ibm.zvm.v54.kijl0/hcsk7b3014.htm">http://publib.boulder.ibm.com/infocenter/zvm/v5r4/index.jsp?topic=/com.ibm.zvm.v54.kijl0/hcsk7b3014.htm</a> (accessed: February 5, 2012).</p>
<p><em>IPv6 Addressing</em>. Na: IP6.com. <a href="http://ipv6.com/articles/general/IPv6-Addressing.htm">http://ipv6.com/articles/general/IPv6-Addressing.htm</a> (accessed: January 26, 2011).</p>
<p><em>Unicast IPv6 addresses</em>. Redmond, WA: Microsoft. <a href="http://technet.microsoft.com/en-us/library/cc759208(WS.10).aspx">http://technet.microsoft.com/en-us/library/cc759208(WS.10).aspx</a> (accessed: February 5, 2012).</p>
<p><em>Wikipedia</em>. San Francisco, CA: Wikimedia Foundation. <a href="http://en.wikipedia.org/wiki/Packet_switching">http://en.wikipedia.org/wiki/Packet_switching</a> (accessed: February 5, 2012).</p>
<p>&nbsp;</p>
<p><strong>Post Note</strong>: &#8220;A Few Fundamental Features of IPv6 Internetworking – Part VI&#8221; was originally published through Suite101.com under the title &#8220;A Few Fundamental Features of IPv6 Internetworking&#8221;</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamental-features-of-ipv6-internetworking-part-vi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Few Fundamental Features of IPv6 Internetworking – Part V</title>
		<link>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamental-features-of-ipv6-internetworking-part-v/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamental-features-of-ipv6-internetworking-part-v/#comments</comments>
		<pubDate>Thu, 15 Nov 2012 02:54:28 +0000</pubDate>
		<dc:creator>Robert Davis</dc:creator>
				<category><![CDATA[Authentication]]></category>
		<category><![CDATA[Availability Management]]></category>
		<category><![CDATA[Cloud Computing]]></category>
		<category><![CDATA[Configuration Management]]></category>
		<category><![CDATA[Encapsulating Security Payload]]></category>
		<category><![CDATA[ICT]]></category>
		<category><![CDATA[Information and Communication Technology]]></category>
		<category><![CDATA[Information Technology Service Management]]></category>
		<category><![CDATA[Infrastructure Management]]></category>
		<category><![CDATA[Internet Protocol Security]]></category>
		<category><![CDATA[IPSec]]></category>
		<category><![CDATA[IT Hardware]]></category>
		<category><![CDATA[IT Security]]></category>
		<category><![CDATA[Multiprocessing]]></category>
		<category><![CDATA[Public Key Infrastructure]]></category>
		<category><![CDATA[Service Delivery]]></category>
		<category><![CDATA[Transport Mode]]></category>
		<category><![CDATA[Tunnel Mode]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-governance/?p=1673</guid>
		<description><![CDATA[The IPSec model is an architecture composed of standard rules for protecting IP traffic. IPSec is also a set of protocols utilized to secure IP packet exchanges that operate at the Internet Layer of the TCP/IP reference model. IPSec utilizes certificates and Public Keys to authenticate and validate the sender and receiver. Tunnel and Transport [...]]]></description>
				<content:encoded><![CDATA[<p><a href="http://cdn.ttgtmedia.com/ITKE/uploads/blogs.dir/99/files/2012/11/4891e758d5f905abcf6b471c39ca7e74.png"><img class="aligncenter size-full wp-image-1675" src="http://cdn.ttgtmedia.com/ITKE/uploads/blogs.dir/99/files/2012/11/4891e758d5f905abcf6b471c39ca7e74.png" alt="" width="475" height="210" /></a></p>
<p>The IPSec model is an architecture composed of standard rules for protecting IP traffic. IPSec is also a set of protocols utilized to secure IP packet exchanges that operate at the Internet Layer of the TCP/IP reference model. IPSec utilizes certificates and Public Keys to authenticate and validate the sender and receiver.</p>
<p>Tunnel and Transport are the two telecommunication modes supported by IPSec. IPSec standard rules can be incorporated into transport and tunnel mode encapsulation. As a distinctive feature, Tunnel mode provides two additional header records for sending messages, thus requiring more processing. In addition, Tunnel mode is usually implemented between two gateways or a gateway and server.</p>
<p><em>Sources</em>:</p>
<p>Davis, Robert E. <em>IT Auditing: Assuring Information Assets Protection</em>. Mission Viejo, CA: Pleier Corporation, 2008. CD-ROM.</p>
<p>IBM. Armonk, New York: International Business Machines. <a href="http://publib.boulder.ibm.com/infocenter/zvm/v5r4/index.jsp?topic=/com.ibm.zvm.v54.kijl0/hcsk7b3014.htm">http://publib.boulder.ibm.com/infocenter/zvm/v5r4/index.jsp?topic=/com.ibm.zvm.v54.kijl0/hcsk7b3014.htm</a> (accessed: February 5, 2012).</p>
<p><em>IPv6 Addressing</em>. Na: IP6.com. <a href="http://ipv6.com/articles/general/IPv6-Addressing.htm">http://ipv6.com/articles/general/IPv6-Addressing.htm</a> (accessed: January 26, 2011).</p>
<p><em>Unicast IPv6 addresses</em>. Redmond, WA: Microsoft. <a href="http://technet.microsoft.com/en-us/library/cc759208(WS.10).aspx">http://technet.microsoft.com/en-us/library/cc759208(WS.10).aspx</a> (accessed: February 5, 2012).</p>
<p><em>Wikipedia</em>. San Francisco, CA: Wikimedia Foundation. <a href="http://en.wikipedia.org/wiki/Packet_switching">http://en.wikipedia.org/wiki/Packet_switching</a> (accessed: February 5, 2012).</p>
<p>&nbsp;</p>
<p><strong>Post Note</strong>: &#8220;A Few Fundamental Features of IPv6 Internetworking – Part V&#8221; was originally published through Suite101.com under the title &#8220;A Few Fundamental Features of IPv6 Internetworking&#8221;</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamental-features-of-ipv6-internetworking-part-v/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Few Fundamentals of Networking Electronically Encoded Data – Part IV</title>
		<link>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamentals-of-networking-electronically-encoded-data-part-iv/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamentals-of-networking-electronically-encoded-data-part-iv/#comments</comments>
		<pubDate>Sat, 22 Sep 2012 00:07:07 +0000</pubDate>
		<dc:creator>Robert Davis</dc:creator>
				<category><![CDATA[Central Processing Unit]]></category>
		<category><![CDATA[Configuration Management]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[ICT]]></category>
		<category><![CDATA[Information Communication Technology]]></category>
		<category><![CDATA[IT Architecture]]></category>
		<category><![CDATA[IT Configuration]]></category>
		<category><![CDATA[Multiplexor]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Service Delivery]]></category>
		<category><![CDATA[Token]]></category>
		<category><![CDATA[Transport Mode]]></category>
		<category><![CDATA[Tunnel Mode]]></category>
		<category><![CDATA[Virtual Private Network]]></category>
		<category><![CDATA[Data Communication]]></category>
		<category><![CDATA[Internetworking]]></category>
		<category><![CDATA[Transmission Controls]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-governance/?p=1510</guid>
		<description><![CDATA[In TDM (typically utilized for digital signals) a device is given a specific time slot during which it can utilize a particular channel. In contrast, with FDM (typically utilized for analog signals) the channel is subdivided into sub-channels, each with a different frequency width that is assigned to a specific signal. Through TDM incorporation, optical-fiber [...]]]></description>
				<content:encoded><![CDATA[<p>In TDM (typically utilized for digital signals) a device is given a specific time slot during which it can utilize a particular channel. In contrast, with FDM (typically utilized for analog signals) the channel is subdivided into sub-channels, each with a different frequency width that is assigned to a specific signal.</p>
<p>Through TDM incorporation, <a href="http://www.arcelect.com/fibercable.htm">optical-fiber networks</a> can use dense wavelength-division multiplexing (DWDM), also known as <a href="http://www.articlesbase.com/computers-articles/what-is-wdm-wavelength-division-multiplexing-for-fiber-optic-communication-fiber-optic-tutorial-series-451807.html">wave division multiplexing</a> (WDM)<em>, </em>in which different data signals are sent in different wavelengths of light in the fiber-optic medium.</p>
<p><iframe width="420" height="315" src="http://www.youtube.com/embed/SPqop2OykfI" frameborder="0" allowfullscreen></iframe></p>
<p><strong>How networking services are maintained by enterprises</strong></p>
<p>Network Administration is the function designated to maintain a secure as well as reliable on-line communications network and serves as liaison with user departments to resolve network needs and problems. Specifically, this function is generally responsible for maintaining network security, maintaining optimum system performance, and providing technical assistance to users. Thus, just like the &#8216;<a href="http://careers.stateuniversity.com/pages/375/Telephone-Service-Technician.html">telephone service technician</a>&#8216;, the network administrator should be considered the specialist capable of reestablishing communication if service quality is diminished.</p>
<p>“<em>View Part I of the A Few Fundamentals of Networking Electronically Encoded Data series <a href="http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamentals-of-networking-electronically-encoded-data-part-i/">here</a></em>”</p>
<p>&nbsp;</p>
<p><strong>Post Note</strong>: &#8220;A Few Fundamentals of Networking Electronically Encoded Data &#8211; Part IV&#8221; was originally published through Suite101.com under the title &#8220;A Few Fundamentals of Networking Electronically Encoded Data&#8221;</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamentals-of-networking-electronically-encoded-data-part-iv/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Few Fundamentals of Networking Electronically Encoded Data – Part III</title>
		<link>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamentals-of-networking-electronically-encoded-data-part-iii/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamentals-of-networking-electronically-encoded-data-part-iii/#comments</comments>
		<pubDate>Thu, 20 Sep 2012 01:09:51 +0000</pubDate>
		<dc:creator>Robert Davis</dc:creator>
				<category><![CDATA[Central Processing Unit]]></category>
		<category><![CDATA[Configuration Management]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[ICT]]></category>
		<category><![CDATA[Information Communication Technology]]></category>
		<category><![CDATA[IT Architecture]]></category>
		<category><![CDATA[IT Configuration]]></category>
		<category><![CDATA[Multiplexor]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Service Delivery]]></category>
		<category><![CDATA[Token]]></category>
		<category><![CDATA[Transport Mode]]></category>
		<category><![CDATA[Tunnel Mode]]></category>
		<category><![CDATA[Virtual Private Network]]></category>
		<category><![CDATA[Data Communication]]></category>
		<category><![CDATA[Internetworking]]></category>
		<category><![CDATA[Transmission Controls]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-governance/?p=1503</guid>
		<description><![CDATA[Packet assembly and disassembly between telecommunication links Input or output (I/O) channels are paths along which datum are transmitted to and from primary storage. These communication channels also handle the transfer of datum to and from I/O devices. As a result, this function can relieve the Central Processing Unit (CPU) of responsibility for data transfers [...]]]></description>
				<content:encoded><![CDATA[<p><strong>Packet assembly and disassembly between telecommunication links </strong></p>
<p>Input or output (I/O) channels are paths along which datum are transmitted to and from primary storage. These communication channels also handle the transfer of datum to and from I/O devices. As a result, this function can relieve the Central Processing Unit (CPU) of responsibility for data transfers to and from I/O devices, increase the number of input and output operations that can be performed simultaneously and reduce the time a CPU must wait for datum to arrive from, or sent to, an I/O device.</p>
<p>A common IT transmission technique for telecommunications is multiplexing. Multiplexing is the process of transmitting multiple (but separate) signals simultaneously over a single channel or line. The two main types of multiplexing methods are time-division multiplexing (TDM) and frequency-division multiplexing (FDM). Because the signals are sent in one complex transmission, the receiving end has to separate the individual signals through de-multiplexing.</p>
<p>“<em>View Part I of the A Few Fundamentals of Networking Electronically Encoded Data series <a href="http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamentals-of-networking-electronically-encoded-data-part-i/">here</a></em>”</p>
<p>&nbsp;</p>
<p><strong>Post Note</strong>: &#8220;A Few Fundamentals of Networking Electronically Encoded Data &#8211; Part III&#8221; was originally published through Suite101.com under the title &#8220;A Few Fundamentals of Networking Electronically Encoded Data&#8221;</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamentals-of-networking-electronically-encoded-data-part-iii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Few Fundamentals of Networking Electronically Encoded Data – Part II</title>
		<link>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamentals-of-networking-electronically-encoded-data-part-ii/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamentals-of-networking-electronically-encoded-data-part-ii/#comments</comments>
		<pubDate>Sat, 15 Sep 2012 00:24:41 +0000</pubDate>
		<dc:creator>Robert Davis</dc:creator>
				<category><![CDATA[Configuration Management]]></category>
		<category><![CDATA[ICT]]></category>
		<category><![CDATA[Information Communication Technology]]></category>
		<category><![CDATA[IT Architecture]]></category>
		<category><![CDATA[IT Configuration]]></category>
		<category><![CDATA[IT Infrastructure]]></category>
		<category><![CDATA[IT Service Delivery]]></category>
		<category><![CDATA[Multiplexor]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Service Delivery]]></category>
		<category><![CDATA[Token]]></category>
		<category><![CDATA[Transport Mode]]></category>
		<category><![CDATA[Tunnel Mode]]></category>
		<category><![CDATA[Virtual Private Network]]></category>
		<category><![CDATA[Data Communication]]></category>
		<category><![CDATA[Internetworking]]></category>
		<category><![CDATA[Transmission Controls]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-governance/?p=1478</guid>
		<description><![CDATA[All of the computers and other hardware connected to a particular network must follow the same rules or operations commonly called protocols. Operational rules are typically divided up into layers so a programmer or network administrator need only be concerned with the layer with which the software is communicating. In defining these layers, reference models [...]]]></description>
				<content:encoded><![CDATA[<p>All of the computers and other hardware connected to a particular network must follow the same rules or operations commonly called <em>protocols</em>. Operational rules are typically divided up into layers so a programmer or network administrator need only be concerned with the layer with which the software is communicating. In defining these layers, reference models have been created. At this level, available reference models for classifying <a title="Webopedia - communications protocol " href="http://www.webopedia.com/TERM/C/communications_protocol.html" target="_blank">communication protocols</a> and protocol suites include the: U.S. Department of Defense, Open Systems Interconnection and Berkeley University framework.</p>
<p>In order to send data over a network, the necessary programs must be executed. However, datum must be organized for transmission. Consequently, a very important networking concept is the packet. Packets are telecommunication units transmitted from a sending device to a receiving device with an appended header. Substantively, a packet header contains information that is required to transfer attached data across the network.</p>
<p><iframe width="420" height="315" src="http://www.youtube.com/embed/gzsUJjUAz84" frameborder="0" allowfullscreen></iframe></p>
<p>“<em>View Part I of the A Few Fundamentals of Networking Electronically Encoded Data series <a href="http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamentals-of-networking-electronically-encoded-data-part-i/">here</a></em>”</p>
<p>&nbsp;</p>
<p><strong>Post Note</strong>: &#8220;A Few Fundamentals of Networking Electronically Encoded Data &#8211; Part II&#8221; was originally published through Suite101.com under the title &#8220;A Few Fundamentals of Networking Electronically Encoded Data&#8221;</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-governance/a-few-fundamentals-of-networking-electronically-encoded-data-part-ii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Trans-border Communication Protection &#8211; Part IV</title>
		<link>http://itknowledgeexchange.techtarget.com/it-governance/trans-border-communication-protection-part-iv/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-governance/trans-border-communication-protection-part-iv/#comments</comments>
		<pubDate>Mon, 06 Jul 2009 19:02:31 +0000</pubDate>
		<dc:creator>Robert Davis</dc:creator>
				<category><![CDATA[Configuration Items]]></category>
		<category><![CDATA[Encapsulating Security Payload]]></category>
		<category><![CDATA[Encapsulation]]></category>
		<category><![CDATA[ESP]]></category>
		<category><![CDATA[Infrastructure]]></category>
		<category><![CDATA[Internet Protocol Security]]></category>
		<category><![CDATA[IPSec]]></category>
		<category><![CDATA[Open Systems Interconnection]]></category>
		<category><![CDATA[OSI]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Secure Socket Layer]]></category>
		<category><![CDATA[SSL]]></category>
		<category><![CDATA[Transport Mode]]></category>
		<category><![CDATA[Tunnel Mode]]></category>
		<category><![CDATA[Virtual Private Network]]></category>
		<category><![CDATA[VPN]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-governance/?p=189</guid>
		<description><![CDATA[Protection mechanism utilization should be determined by information sensitivity.]]></description>
				<content:encoded><![CDATA[<p>The primary distinguishing feature between IPSec and SSL is their respective OSI reference model protocol <a href="http://www.theiia.org/bookstore/product/it-auditing-information-assets-protection-iap-1276.cfm">communication tier levels</a>. IPSec operates at the network layer of the <a href="http://www.pleier.com/itadsweb.htm">OSI reference model</a> while SSL operates at the transport layer. Protection mechanism utilization should be determined by information sensitivity. IPSec or SSL can be combined with a VPN to limit data interception, manipulation, and redirection. Standards exist for encryption systems, such as SSL and IPSec, which ensure compatibility among various hardware and software platforms. Comparatively, regarding trans-border privacy issues, SSL VPN can be considered a viable alternative to stand-alone IPSec deployment.</p>
<p>&#8220;View Part I of the Trans-border Communication Protection series <a href="http://itknowledgeexchange.techtarget.com/it-governance/trans-border-communication-protection-part-i/">here</a>&#8220;</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-governance/trans-border-communication-protection-part-iv/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Trans-border Communication Protection &#8211; Part III</title>
		<link>http://itknowledgeexchange.techtarget.com/it-governance/trans-border-communication-protection-part-iii/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-governance/trans-border-communication-protection-part-iii/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 20:12:46 +0000</pubDate>
		<dc:creator>Robert Davis</dc:creator>
				<category><![CDATA[Configuration Items]]></category>
		<category><![CDATA[Encapsulating Security Payload]]></category>
		<category><![CDATA[Encapsulation]]></category>
		<category><![CDATA[ESP]]></category>
		<category><![CDATA[Infrastructure]]></category>
		<category><![CDATA[Internet Protocol Security]]></category>
		<category><![CDATA[IPSec]]></category>
		<category><![CDATA[Open Systems Interconnection]]></category>
		<category><![CDATA[OSI]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Secure Socket Layer]]></category>
		<category><![CDATA[SSL]]></category>
		<category><![CDATA[Transport Mode]]></category>
		<category><![CDATA[Tunnel Mode]]></category>
		<category><![CDATA[Virtual Private Network]]></category>
		<category><![CDATA[VPN]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-governance/?p=187</guid>
		<description><![CDATA[...virtual private networking requires a carrier as well as encapsulating protocol to provide tunneling functionality.]]></description>
				<content:encoded><![CDATA[<p>Generally, a VPN is recognized as a confidential data plexus that employs the public telecommunication <a href="http://www.amazon.com/Auditing-Assuring-Information-Assets-Protection/dp/1935133209/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1246565315&amp;sr=1-1">infrastructure</a> while maintaining privacy through the utilization of a tunneling protocol and security procedures. A VPN can provide remote offices and telecommuters with secure access to the connected local or wide area networks. When a VPN is introduced to the secure protocol privacy protection equation, IPSec and SSL technologies require mobile users to deploy client software on specific computers for utilization enablement. </p>
<p>Concerning secure access, virtual private networking requires a carrier as well as encapsulating protocol to provide tunneling functionality. Therefore, encryption, authentication, and data packaging usually are incorporated in a <a href="http://searchsecurity.techtarget.com/sDefinition/0,,sid14_gci1201867,00.html">SSL VPN</a>. Furthermore, below the OSI transport layer, a VPN can provide additional privacy data protection. This has many manifestations, the most popular being IPSec, typically implemented as a protected &#8216;tunnel&#8217; between two gateway routers. An IPSec &#8216;vanilla&#8217; VPN only uses the Encapsulating Security Payload (ESP) header record. However, ESP protects against IT communication eavesdropping, forgery, or replay risks.</p>
<p>&#8220;View Part I of the Trans-border Communication Protection series <a href="http://itknowledgeexchange.techtarget.com/it-governance/trans-border-communication-protection-part-i/">here</a>&#8220;</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-governance/trans-border-communication-protection-part-iii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Trans-border Communication Protection &#8211; Part II</title>
		<link>http://itknowledgeexchange.techtarget.com/it-governance/trans-border-communication-protection-part-ii/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-governance/trans-border-communication-protection-part-ii/#comments</comments>
		<pubDate>Mon, 29 Jun 2009 18:52:19 +0000</pubDate>
		<dc:creator>Robert Davis</dc:creator>
				<category><![CDATA[Configuration Items]]></category>
		<category><![CDATA[Encapsulation]]></category>
		<category><![CDATA[Internet Protocol Security]]></category>
		<category><![CDATA[IPSec]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Secure Socket Layer]]></category>
		<category><![CDATA[SSL]]></category>
		<category><![CDATA[Transport Mode]]></category>
		<category><![CDATA[Tunnel Mode]]></category>
		<category><![CDATA[Virtual Private Network]]></category>
		<category><![CDATA[VPN]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-governance/?p=185</guid>
		<description><![CDATA[For Internet communications, SSL is normally utilized in conjunction with an entity's public key infrastructure.]]></description>
				<content:encoded><![CDATA[<p>SSL is a protocol suite enabling in transit security through data encryption, server authentication, and message integrity at four Open Systems Interconnection (OSI) reference model layers. For Internet communications, SSL is normally utilized in conjunction with an entity&#8217;s <a href="http://www.theiia.org/bookstore/product/it-auditing-assuring-information-assets-protection-1381.cfm">public key infrastructure</a>. Commonly, when the trans-border privacy breach risk is low, the Hyper Text Transfer Protocol Security service is employed with SSL encryption to protect sensitive web packets. Beneficially, where SSL is integrated for required privacy related communication, applications no longer need to implement secure connectivity. Nevertheless, security managers should not interpret SSL deployment as the &#8216;bullet-proof&#8217; technology that completely defers application communication privacy issues. Specifically, SSL should initiate deployment caution when utilized for mutual application authentication, since there are two different session keys seeking connectivity authorization during bidirectional interfaces. Consequently, each key should be verified before transmitting legally protected data. </p>
<p>Alternatively, IPSec is a protocol suite that enables security at five OSI reference model layers during internetworking communications. The IPSec model is an architecture composed of standard rules for protecting Internet Protocol traffic. These standard rules can be incorporated into transport and tunnel mode encapsulation. Tunnel mode provides two additional header records for sending messages, thus requiring more processing. Neither the application nor the <a href="http://www.theiia.org/bookstore/product/it-auditing-service-delivery-and-support-1321.cfm">stacking</a> protocol needs to be cryptographically aware, since all designated traffic is encrypted regardless of origin within the entity&#8217;s information security perimeter. Possible IPSec issues are network device computational and/or bandwidth overhead.</p>
<p>&#8220;View Part I of the Trans-border Communication Protection series <a href="http://itknowledgeexchange.techtarget.com/it-governance/trans-border-communication-protection-part-i/">here</a>&#8220;</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-governance/trans-border-communication-protection-part-ii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
