<?xml version="1.0" encoding="UTF-8"?>
<wiki>
  <body>&lt;p&gt;In general, the &lt;span class=&quot;caps&quot;&gt;SMS&lt;/span&gt; protocol is insecure because items are sent in plain text. For many situations (&lt;span class=&quot;caps&quot;&gt;RSS&lt;/span&gt; readers, broadcast information) this is perfectly legitimate. However when interacting with private/personal information a new strategy has to be employed. Use cases for banking and commerce data should also be developed.&lt;/p&gt;
&lt;h2&gt;Use Cases&lt;/h2&gt;
&lt;p&gt;These use cases focus on health data used in rural &lt;span class=&quot;caps&quot;&gt;HIV&lt;/span&gt; clinics and a strategy for keeping the information private.&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Collect demographic information (given name, family name, location, number) without exposing this information in plain text, and or without connecting this identifying information to private/personal data.&lt;/li&gt;
	&lt;li&gt;Submit &lt;span class=&quot;caps&quot;&gt;HIV&lt;/span&gt; status information for a specific person identifier without allowing proximity to reveal the associated person.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In the first case it would be very easy to listen to insecure communications and recover names and locations of patients with specific &lt;span class=&quot;caps&quot;&gt;HIV&lt;/span&gt; statuses. In the second, one would assume that the demographic information is secured (using unique identifiers) however if only one person enters a testing booth and the &lt;span class=&quot;caps&quot;&gt;HIV&lt;/span&gt; status is broadcast, it would be easy to determine which person the status referred to. This suggests that not only incoming, but outgoing (source) &lt;span class=&quot;caps&quot;&gt;SMS&lt;/span&gt; need to be secured.&lt;/p&gt;
&lt;h2&gt;Strategies&lt;/h2&gt;
&lt;p&gt;Assuming that no application can be deployed to the phone, an out-of-band encryption solution needs to be adopted. Possible approaches include:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Use of pre-printed identifiers&lt;/li&gt;
	&lt;li&gt;Use of simplified one-time pads (http://en.wikipedia.org/wiki/One-time_pad)&lt;/li&gt;
	&lt;li&gt;Use of biometrics (facial recognition, iris detection, fingerprinting)&lt;/li&gt;
	&lt;li&gt;Use of a code word or pass-phrase or pin&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Pre-printed identifiers&lt;/h3&gt;
&lt;p&gt;In most public health scenarios you do not need demographic (name, number, address) information except for longitudinal identification. Typically having the name and address is useful for cross-checking identifiers and for when patients lose identifiers. Suppose that the community healthcare worker was given a set of pre-printed patient identifiers (as barcoded labels for health passports) that they took into the field. When they wanted to enter information for new patient, they would issue the health passport and utilize one of the stickers. They could then submit information for the patient based on their identifier.&lt;/p&gt;
&lt;p&gt;Pros:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Uses a unique identifier for longitudinal care&lt;/li&gt;
	&lt;li&gt;Sends information against a private, unidentifiable identifier instead of demographic information&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Cons:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Patients could lose their passports and identifiers which would result in loss of followup&lt;/li&gt;
	&lt;li&gt;Crosschecking of identifiers with demographic information would not be possible&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It is still possible that certain demographics could be collected including: gender, birthdate, location&lt;/p&gt;
&lt;h3&gt;Simplified One-time pads&lt;/h3&gt;
&lt;p&gt;In cryptography the only form of perfect secrecy is the use of a one-time pad. Originally these were actual pads of paper that would have a new set of keys on each page generated randomly. By entering the pad number and then using the cipher, the recipient could use the corresponding pad to decrypt the message. Typically one-time pads are time consuming to utilize manually. Simplifying this process, one could use &amp;#8220;one-time&amp;#8221; pads for specific sets of sensitive questions. Imagine that the following is printed and given to the community healthcare worker before they went on their visits:&lt;/p&gt;
Pad 3452
Is the person &lt;span class=&quot;caps&quot;&gt;HIV&lt;/span&gt; positive (Enter &amp;#8220;a&amp;#8221; for yes, &amp;#8220;m&amp;#8221; for no)
&lt;p&gt;and&lt;/p&gt;
Pad 3671
Is the person &lt;span class=&quot;caps&quot;&gt;HIV&lt;/span&gt; positive (Enter &amp;#8220;p&amp;#8221; for yes, &amp;#8220;d&amp;#8221; for no)
&lt;p&gt;For each patient they could be asked, &amp;#8220;Please enter the pad number&amp;#8221;, followed by &amp;#8220;Is the person &lt;span class=&quot;caps&quot;&gt;HIV&lt;/span&gt; positive?&amp;#8221;. Or users could be trained to submit an answer like &amp;#8220;3452m&amp;#8221;. If pad numbers were reused by mistake the answer could be rejected.&lt;/p&gt;
&lt;p&gt;Pros:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Very secure, even given proximity an eavesdropper could not determine the status without the one time pad&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Cons:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Confusing, may require additional training and may increase the burden of work&lt;/li&gt;
	&lt;li&gt;Requires papers to be printed and carried by the community healthcare workers&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Use of Biometrics&lt;/h3&gt;
&lt;p&gt;In many distributed environments, the use of bio-metric information allows you to create a secure reproducible identifiers that can be replicated in the field and at the primary location. Biometrics are being used widely in sub-saharan Africa for health, micro-finance banking and the like. Newer phones have the ability to utilize their cameras to detect irises and use this as an identifier (Android). Connecting to devices to phones also provides a possibility (especially given Bluetooth). However, if you become reliant on a specific device or software for the device, you may as well implement a full encryption system and utilize traditional demographic information.&lt;/p&gt;
&lt;p&gt;Pros:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Reproducible identifier that the patient cannot &amp;#8220;lose&amp;#8221;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Cons:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Requires additional equipment or specialized phones and software&lt;/li&gt;
	&lt;li&gt;Fingerprints for farm workers tend to be difficult to read, early infant fingerprints have been shown to change&lt;/li&gt;
	&lt;li&gt;Facial recognition and iris scanning require high resolution and may not be suitable for patients with ocular diseases and side effects&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Non-traditional facial recognition might be possible if it is combined with [[contacts]] syncing and semi-permanent identifiers.&lt;/p&gt;
&lt;h3&gt;Use of Codewords, Pass-phrases and Pins&lt;/h3&gt;
&lt;p&gt;In addition to the typical set of demographic identifiers, a pass-phrase could be employed as a mechanism of cross checking known information (such as birthdate, location, and gender). Typically these systems work best when it is a personal piece of information that will not change over time, will not be forgotten, and is not common. In the United States a common example of this to ask your &amp;#8220;Mother&amp;#8217;s maiden name&amp;#8221; or &amp;#8220;What city were you born in&amp;#8221;. Unfortunately this information can be learned and now has gained a significant importance/privacy all its own. Many web systems have a list of questions such as &amp;#8220;Who was your first grade teacher&amp;#8221; or &amp;#8220;What was your first pet&amp;#8217;s name&amp;#8221;. In many cases in rural Africa these questions are not applicable.&lt;/p&gt;
&lt;p&gt;Pros:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Would allow a person to be somewhat reliably re-identified&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Cons:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Applicable questions with answers that are not common, will not be forgotten, and will not change over time are hard to find&lt;/li&gt;
	&lt;li&gt;Possibly not useful for infants (the time-horizon of the identifier may need to be specified)&lt;/li&gt;
	&lt;li&gt;Difficult for patients that have died&lt;/li&gt;
&lt;/ul&gt;</body>
  <created-at type="datetime">2008-10-27T09:17:46-07:00</created-at>
  <id type="integer">73026</id>
  <permalink>security</permalink>
  <repository-id type="integer">67852</repository-id>
  <title>Security</title>
  <updated-at type="datetime">2008-10-27T10:28:39-07:00</updated-at>
  <user-id type="integer">4064</user-id>
</wiki>
