<?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>Creeva&#039;s World 2.0 &#187; Smart Card</title>
	<atom:link href="http://creeva.com/tag/smart-card/feed/" rel="self" type="application/rss+xml" />
	<link>http://creeva.com</link>
	<description>My life unfolding and being told online - 1 byte of information at a time.</description>
	<lastBuildDate>Thu, 09 Feb 2012 18:30:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>The Kiosk Series &#8211; Part Two &#8211; Management Considerations For Your Environment</title>
		<link>http://creeva.com/2008/04/08/the-kiosk-series-part-two-management-considerations-for-your-environment/</link>
		<comments>http://creeva.com/2008/04/08/the-kiosk-series-part-two-management-considerations-for-your-environment/#comments</comments>
		<pubDate>Tue, 08 Apr 2008 16:15:26 +0000</pubDate>
		<dc:creator>Creeva</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Centralize]]></category>
		<category><![CDATA[Centralized Management]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[Environment]]></category>
		<category><![CDATA[Kiosk]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[Smart Card]]></category>
		<category><![CDATA[Symantec]]></category>
		<category><![CDATA[Test]]></category>
		<category><![CDATA[Updates]]></category>

		<guid isPermaLink="false">http://creeva.com/?p=2685</guid>
		<description><![CDATA[Recently I&#8217;ve been put forth to design a kiosk solution for our internal environment.   This is the second part of my kiosk series which is going to examine testing and deployment of such a system.  To read the first section go to Part One &#8211; Choices For Your Environment. Kiosk System Management Strategy There are [...]]]></description>
			<content:encoded><![CDATA[<p>Recently I&#8217;ve been put forth to design a kiosk solution for our internal environment.   This is the second part of my kiosk series which is going to examine testing and deployment of such a system.  To read the first section go to<a title="Article-Link (Permalink)" rel="bookmark" href="http://creeva.com/2008/04/08/the-kiosk-series-part-one-choices-for-your-environment"> Part One &#8211; Choices For Your Environment</a>.</p>
<p>Kiosk System Management Strategy</p>
<p>There are multiple issues involved with managing a “kiosk system&#8221;.   We have to look at the problems we will face whether they are considered to be internal or external.  From a security and management scope of this document we are going to assume they are located on the company guest network.  If the machines are located within the internal network the current maintenance procedures will apply.</p>
<p>While this is still in the design period the final abilities of both the kiosk system and the where it falls have not been decided upon.   Until another strategy is decided upon we are going to assume that these systems will be a member of the domain.</p>
<p><strong>Hotfixing and Patching:</strong> Within the internal network we currently use a mixture of <a href="http://technet.microsoft.com/en-us/wsus/default.aspx">WSUS</a>, <a href="http://www.microsoft.com/smserver/default.mspx">SMS</a>, and <a href="http://www.symantec.com">Antivirus</a> servers to keep computers up to date.   Something similar would have to be replicated either on the guest or <a href="http://creeva.com/wp-admin/compnetworking.about.com/cs/networksecurity/g/bldef_dmz.htm">DMZ</a> network.   If it is located on the DMZ network controls would have to be in place that the communication is pushed to the client for updates instead of the client pulling the information.  If the information absolutely must be pulled, this will be addressed in the section below titled “Securing Connections”.</p>
<p><strong>Break/Fix Issues: </strong> Next to the computer there will have to be a phone located so users can report any issues that a kiosk should have.   Upon receiving the call and logging it, normal break/fix procedures would apply.</p>
<p><strong>Remote Desktop: </strong> Going from the DMZ to the guest network we should be able to <a href="http://en.wikipedia.org/wiki/Remote_Desktop_Protocol">RDP</a> into the kiosk unit.</p>
<p><strong>Remote Monitoring:</strong> For the best security standpoint all of these units should include full auditing.   The audit trail could be maintained locally with a remote server from the DMZ pulling in the logs via either a script or an off the shelf utility designed for pulling log files off of the machine.</p>
<p><strong>Utilization Report:</strong> Similar to the Audit log we can get a utility that monitors the utilization with these units and pull them into the internal network.  This can be done after tracking down a third party program that allows for utilization monitoring or by parsing the audit log and turning that into a utilization report.</p>
<p><strong>Seat Type:</strong> A new seat type would have to be established to accommodate the additional costs incurred from the environment set up and maintenance of these units including but not limited the additional costs possibly incurred by having a phone nearby to inform the help desk of any issues.</p>
<p><strong>Security Plan:</strong> A new security plan would have to be established since there will configuration settings that do not fit into the current security plans that the company has established.  While these will fall under a site security plan, none of our existing would not be able to fit these systems under their configuration options.</p>
<p><strong>Privacy Controls:</strong> Depending on the kiosk solution we go with – whether it be a login based solution where they have a full application suite or a web kiosk something must be done to maintain user privacy.   After an inactivity time (amount to be specified later) which would either clear the process from memory or log the user out of the kiosk completely depending on which kiosk method we are using in a couple methods. One would be an off the shelf software product to this, at this point I would assume we would use all of their privacy and utilization reports. Another option would be to setup a script to kill the process or automatically log out the user and utilize the screensaver in the kiosk to run this functionality and monitor idle time.</p>
<p><strong>Securing Connections:</strong> If the machines must pull information from the machines in the DMZ, then the best method would be to utilize <a href="http://en.wikipedia.org/wiki/IPsec ">IPSEC</a>.  This would limit the amount of ports needed and allow us to lockdown communication to only the specific server that the kiosk would need to talk to.</p>
]]></content:encoded>
			<wfw:commentRss>http://creeva.com/2008/04/08/the-kiosk-series-part-two-management-considerations-for-your-environment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Kiosk Series &#8211; Part One &#8211; Choices For Your Environment</title>
		<link>http://creeva.com/2008/04/08/the-kiosk-series-part-one-choices-for-your-environment/</link>
		<comments>http://creeva.com/2008/04/08/the-kiosk-series-part-one-choices-for-your-environment/#comments</comments>
		<pubDate>Tue, 08 Apr 2008 16:07:47 +0000</pubDate>
		<dc:creator>Creeva</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Centralize]]></category>
		<category><![CDATA[Centralized Management]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[Environment]]></category>
		<category><![CDATA[Kiosk]]></category>
		<category><![CDATA[Sad]]></category>
		<category><![CDATA[Sites]]></category>
		<category><![CDATA[Smart Card]]></category>
		<category><![CDATA[Test]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://creeva.com/?p=2684</guid>
		<description><![CDATA[Recently I&#8217;ve been put forth to design a kiosk solution for our internal environment.   This is the first part of my kiosk series which is going to examine testing and deployment of such a system. Kiosk Options When discussing kiosk system we need to discuss the scope, security issues, and functionality requirements that we must [...]]]></description>
			<content:encoded><![CDATA[<p>Recently I&#8217;ve been put forth to design a kiosk solution for our internal environment.   This is the first part of my kiosk series which is going to examine testing and deployment of such a system.</p>
<p style="text-align: center;"><strong>Kiosk Options</strong></p>
<p>When discussing kiosk system we need to discuss the scope, security issues, and functionality requirements that we must maintain to achieve a successful deployment.   There are many types of kiosk systems that we can implement within the Company network.   The solutions we are going to describe in this document are based on product literature that we have received after scope is finalized actual product testing will be done so we can verify that all the features work as described and will function within the deployed environment.</p>
<p>For the sake of categorization the following options were identified as possible for use within a kiosk environment.   This list is not meant to be all encompassing but rather a list of desired features that we feel can be accomplished from the products we are looking at.</p>
<p>·    Internal Websites – company Designated<br />
·    External Websites – Completely open from a kiosk standpoint<br />
·    SSL VPN – For access to the internal network<br />
·    Citrix – for terminal server capabilities<br />
·    Printing – locally attached print<br />
·    Sound – for hearing active embedded media<br />
·    USB Mounting – for USB memory sticks<br />
·    Run Apps Locally (Read Only) – from either the memory stick or kiosk directly<br />
·    Run Apps Locally (Read / Write) – from either the memory stick or kiosk directly<br />
·    Write to USB Memory Stick – from kiosk<br />
·    Access to User Documents<br />
·    No Login – completely is designed to start being used without login<br />
·    Boiler Plate Website – standard start page<br />
·    Full application list<br />
·    Internal – Authentication<br />
·    External &#8211; No Authentication<br />
·    Browser Plug-ins – for enhanced compatibility<br />
·    Restricted To Certain Web Sites – Company Designated</p>
<p>Kiosk mode systems come in a variety of shapes, sizes, and functions.   To help narrow the design gap for our needs we have devised eight categories in which we can work around design structures for:</p>
<p>·    Full web only access kiosk on the company guest network<br />
·    Limited web access on the company guest network with a locked down browser<br />
·    Full web only access kiosk on the internal network<br />
·    Limited web access on the internal network with a locked down browser<br />
·    Limited seat with security controls on the company guest network<br />
·    Limited seat with security controls on the internal network<br />
·    Full seat with security controls on the company guest network<br />
·    Full seat open use office solution &#8211; internal network<br />
·    Full seat with security Controls open use office on the internal network</p>
<p>Each solution has its own benefits and concerns for deployment.  We will be going over these one by one to analyze and work with company to implement the correct and desired solution.  The analysis will include which functions identified above can be implemented, target placement, target users, benefits and disadvantages of each solutions, and possible security concerns.</p>
<p>Full web only access kiosk on the company guest network:</p>
<p>Description: This would be a fully open web kiosk with an address bar located at the top with the web browser being the only application available to the end user.  All functions must be done within the browser.</p>
<p>Possible targeted functions:</p>
<p>·    Internal Websites – via SSL VPN<br />
·    External Websites –<br />
·    SSL VPN<br />
·    Citrix – via SSL VPN<br />
·    Printing – locally attached print<br />
·    Sound – for hearing active embedded media<br />
·    Access to My Docs – Via SSL VPN<br />
·    No Login – completely is designed to start being used without login<br />
·    Boiler Plate Website – standard start page<br />
·    External &#8211; No Authentication<br />
·    Browser Plug-ins – for enhanced compatibility</p>
<p>Target placement:</p>
<p>·    Public areas where guests are most likely</p>
<p>Target users:</p>
<p>·    Visitors<br />
·    Visiting Contractors<br />
·    Local Contractors<br />
·    Company Employees</p>
<p>Benefits:</p>
<p>·    Allows users access to information at placement points<br />
·    User will not have access to the local computer beyond the web browser</p>
<p>Disadvantages:</p>
<p>·    All functions must be performed must be performed within a browser<br />
·    Won’t be able to perform other application tasks</p>
<p>Security concerns:</p>
<p>·    If a user leaves an authenticated session up there will be a time delay before the profile resets, risking possible exposure of private data or company data if the SSL VPN was used.<br />
·    Unsigned Active-X controls could cause issues and it would be recommended denying unsigned Active-X controls.</p>
<p>Limited web access on the company guest network with a locked down browser:</p>
<p>Description: This solution can be configured with or without an address bar allowing the option to restrict this to certain web sites.   Active X would be disabled.</p>
<p>Possible targeted functions:</p>
<p>·    External Websites<br />
·    Printing<br />
·    Sound<br />
·    No Login<br />
·    Boiler Plate Website External &#8211; No Authentication<br />
·    Restricted To Certain Web Sites</p>
<p>Target placement:</p>
<p>·    Public areas where guests are most likely</p>
<p>Target users:</p>
<p>·    Visitors<br />
·    Visiting Contractors<br />
·    Local Contractors<br />
·    Company Employees</p>
<p>Benefits:</p>
<p>·    Tighter Security Controls<br />
·    Limited Risk Exposure<br />
·    Option of controlling where the users can go via the browser</p>
<p>Disadvantages:</p>
<p>·    SSL VPN will not work if active-x controls are disabled<br />
·    All functions must be performed must be performed within a browser<br />
·    Won’t be able to perform other application tasks<br />
·    With no SSL-VPN – no access to internal company data</p>
<p>Security concerns:</p>
<p>·    If a user leaves an authenticated session up there will be a time delay before the profile resets, risking possible exposure of private data.</p>
<p>Full web only access kiosk on the internal network:</p>
<p>Description: While not recommended this is being offered as an option for choice.  It has the same features as the Full web only access kiosk on the company guest network, but would require user authentication due to the network access it has.</p>
<p>Possible targeted functions:</p>
<p>·    Internal Websites<br />
·    External Websites<br />
·    Citrix<br />
·    Printing<br />
·    Sound<br />
·    Access to My Docs<br />
·    Boiler Plate Website<br />
·    Internal<br />
·    Browser Plug-ins</p>
<p>Target placement:</p>
<p>·    Public sites within company buildings that are not commonly visited by the large amounts of visitors at once.  This would be to limit the amount of time that authenticated data is available if a user walks away from the kiosk.<br />
·    Would not be recommended at location that the general public has access to</p>
<p>Target users:</p>
<p>·    Local Contractors<br />
·    Company Employees</p>
<p>Benefits:</p>
<p>·    Company employees would be able to access their Webmail from anywhere these are placed<br />
·    Company employees would be able to access a terminal server session from anywhere these are placed</p>
<p>Disadvantages:</p>
<p>·    All functions must be performed must be performed within a browser<br />
·    Won’t be able to perform other application tasks</p>
<p>Security concerns:</p>
<p>·    Possible information leakage due to open Webmail or terminal server session.<br />
·    Unsigned Active-X controls could cause issues and it would be recommended denying unsigned Active-X controls.</p>
<p>Limited web access on the internal network with a locked down browser:</p>
<p>Description: While not recommended this is being offered as an option for choice.  It has the same features as the limited access kiosk on the company guest network, but would require user authentication due to the network access it has.</p>
<p>Possible targeted functions:</p>
<p>·    External Websites<br />
·    Printing<br />
·    Sound<br />
·    No Login<br />
·    Boiler Plate Website External &#8211; No Authentication<br />
·    Restricted To Certain Web Sites</p>
<p>Target placement:</p>
<p>·    Public sites within company buildings that are not commonly visited by the large amounts of visitors at once.  This would be to limit the amount of time that authenticated data is available if a user walks away from the kiosk.<br />
·    Would not be recommended at location that the general public has access to</p>
<p>Target users:</p>
<p>·    Local Contractors<br />
·    Company Employees</p>
<p>Benefits:</p>
<p>·    Company employees would be able to access their Webmail from anywhere these are placed<br />
·    Company employees would be able to access a terminal server session from anywhere these are placed<br />
·    Tighter Security Controls<br />
·    Limited Risk Exposure<br />
·    Option of controlling where the users can go via the browser</p>
<p>Disadvantages:</p>
<p>·    All functions must be performed must be performed within a browser<br />
·    Won’t be able to perform other application tasks<br />
·    Some sites won’t work due to Active-X being disabled</p>
<p>Security concerns:</p>
<p>·    Possible information leakage due to open Webmail or terminal server session.</p>
<p>Limited seat with security controls on the company guest network:</p>
<p>Description: This would be a scenario where we would have an open standard windows desktop for the user to access.  It would allow only certain applications to run but will give the user access to a portable memory stick for use.</p>
<p>Possible targeted functions:</p>
<p>·    Internal Websites – via SSL VPN<br />
·    External Websites<br />
·    SSL VPN<br />
·    Citrix – via SSL VPN<br />
·    Printing<br />
·    Sound<br />
·    Access to My Docs – Via SSL VPN<br />
·    No Login<br />
·    Boiler Plate Website<br />
·    External<br />
·    Browser Plug-ins<br />
·    USB Mounting<br />
·    Write to USB Memory Stick<br />
·    No Login<br />
·    Boiler Plate Website<br />
·    Browser Plug-ins<br />
·    Restricted To Certain Web Sites – company Designated</p>
<p>Target placement:</p>
<p>·    Public open use office space</p>
<p>Target users:</p>
<p>·    Visiting Contractors<br />
·    Local Contractors<br />
·    Company Employees</p>
<p>Benefits:</p>
<p>·    Allows users access to information at placement points<br />
·    Access to certain designated applications<br />
·    Controlled environment</p>
<p>Disadvantages:</p>
<p>·    Won’t be able to perform non designated application tasks</p>
<p>Security concerns:</p>
<p>·    Possible information leakage due to open Webmail or SSL VPN session.<br />
·    Unsigned Active-X controls could cause issues and it would be recommended denying unsigned Active-X controls.<br />
·    Possible application vulnerabilities could compromise the unit</p>
<p>Limited seat with security controls on the internal network:</p>
<p>Description: Same as the limited seat on the company guest network but designed for internal GRC employees.   Smart card access would be recommended and roaming profiles blocked.</p>
<p>Possible targeted functions:</p>
<p>·    Internal Websites<br />
·    External Websites<br />
·    Citrix<br />
·    Printing<br />
·    Sound<br />
·    Access to My Docs<br />
·    Boiler Plate Website<br />
·    Browser Plug-ins<br />
·    USB Mounting<br />
·    Write to USB Memory Stick<br />
·    Boiler Plate Website<br />
·    Internal – Authentication<br />
·    Browser Plug-ins<br />
·    Restricted To Certain Web Sites – company Designated</p>
<p>Target placement:</p>
<p>·    Public open use office space</p>
<p>Target users:</p>
<p>·    Local Contractors<br />
·    Company Employees</p>
<p>Benefits:</p>
<p>·    Allows users access to information at placement points<br />
·    Access to certain designated applications<br />
·    Controlled environment</p>
<p>Disadvantages:</p>
<p>·    Won’t be able to perform non designated application tasks<br />
·    Large threat to data being exposed</p>
<p>Security concerns:</p>
<p>·    Unsigned Active-X controls could cause issues and it would be recommended denying unsigned Active-X controls.<br />
·    Possible information leakage due to be on the open internal network<br />
·    Large data exposure footprint<br />
·    Possible application vulnerabilities could compromise the unit</p>
<p>Full seat with security controls on the company guest network:</p>
<p>Description: This option would give users to the same standard applications as their normal desktop.   The hard drive would not be written to for data storage.  Roaming profiles would be blocked.  These seat would also have full security controls applied to it.</p>
<p>Possible targeted functions:</p>
<p>·    Internal Websites<br />
·    External Websites<br />
·    SSL VPN<br />
·    Citrix<br />
·    Printing<br />
·    Sound<br />
·    USB Mounting<br />
·    Run Apps Locally (Read Only)<br />
·    Run Apps Locally (Read / Write)<br />
·    Write to USB Memory Stick<br />
·    Access to My Docs<br />
·    No Login – completely is designed to start being used without login<br />
·    Boiler Plate Website<br />
·    Full Application Suite<br />
·    External &#8211; No Authentication<br />
·    Browser Plug-ins<br />
·    Restricted To Certain Web Sites – company Designated</p>
<p>Target placement:</p>
<p>·    Public open use office space</p>
<p>Target users:</p>
<p>·    Local Contractors<br />
·    company Employees</p>
<p>Benefits:</p>
<p>·    Users are able to function as they would at their desks<br />
·    Allows users access to information at placement points</p>
<p>Disadvantages:</p>
<p>·    No login requirements<br />
·    Possible data exposure</p>
<p>Security concerns:</p>
<p>·    Unsigned Active-X controls could cause issues and it would be recommended denying unsigned Active-X controls.<br />
·    Possible information leakage due to open Webmail or SSL VPN session.</p>
<p>Full seat open use office solution on the internal network:</p>
<p>Description: Standard full seat for user to use on the internal network located at open access points for any user to access.  Security settinga would be applied and user profile data removed upon log out.   It is recommended to require smart card access to these units.</p>
<p>Possible targeted functions:</p>
<p>·    Internal Websites<br />
·    External Websites<br />
·    Citrix<br />
·    Printing<br />
·    Sound<br />
·    USB Mounting<br />
·    Run Apps Locally (Read Only)<br />
·    Run Apps Locally (Read / Write)<br />
·    Write to USB Memory Stick<br />
·    Access to My Docs<br />
·    Boiler Plate Website<br />
·    Full Application Suite<br />
·    Internal Authentication<br />
·    Browser Plug-ins</p>
<p>Target placement:</p>
<p>·    Public open use office space</p>
<p>Target users:</p>
<p>·    Local Contractors<br />
·    Company Employees</p>
<p>Benefits:</p>
<p>·    Users are able to function as they would at their desks<br />
·    Allows users access to information at placement points</p>
<p>Disadvantages:</p>
<p>·    Requires smart card<br />
·    No access to local profiles</p>
<p>Security concerns:</p>
<p>·    Possible information leakage due to open sessions.</p>
]]></content:encoded>
			<wfw:commentRss>http://creeva.com/2008/04/08/the-kiosk-series-part-one-choices-for-your-environment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

