<?xml version="1.0" encoding="utf-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns="http://purl.org/rss/1.0/">




    



<channel rdf:about="https://cis-india.org/search_rss">
  <title>Centre for Internet and Society</title>
  <link>https://cis-india.org</link>
  
  <description>
    
            These are the search results for the query, showing results 11 to 23.
        
  </description>
  
  
  
  
  <image rdf:resource="https://cis-india.org/logo.png"/>

  <items>
    <rdf:Seq>
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/governing-id-kenya2019s-huduma-namba-programme"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/governing-id-introducing-our-evaluation-framework"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/governing-id-india2019s-unique-identity-programme"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/governing-id-a-framework-for-evaluation-of-digital-identity"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/governing-id-2028use-of-digital-id-for-verification"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/do-we-really-need-an-app-for-that-examining-the-utility-and-privacy-implications-of-india2019s-digital-vaccine-certificates"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/news/digital-id-forum-2019"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/digtial-identities-research-plan"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/digital-identity/shruti-trikanand-and-amber-sinha-september-13-2019-core-concepts-processes"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/comments-to-the-id4d-practitioners2019-guide"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/comments-on-the-report-of-the-committee-on-digital-payments-dec-2016"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/blog/appropriate-use-of-digital-identity-alliance-announcement"/>
        
        
            <rdf:li rdf:resource="https://cis-india.org/internet-governance/information-security-practices-of-aadhaar-or-lack-thereof-a-documentation-of-public-availability-of-aadhaar-numbers-with-sensitive-personal-financial-information-1"/>
        
    </rdf:Seq>
  </items>

</channel>


    <item rdf:about="https://cis-india.org/internet-governance/blog/governing-id-kenya2019s-huduma-namba-programme">
    <title>Governing ID: Kenya’s Huduma Namba Programme</title>
    <link>https://cis-india.org/internet-governance/blog/governing-id-kenya2019s-huduma-namba-programme</link>
    <description>
        &lt;b&gt;&lt;/b&gt;
        
&lt;p&gt;In our fourth case-study, we use our Evaluation Framework for Digital ID to examine the use of Digital ID in Kenya.&lt;/p&gt;
&lt;p&gt;Read the &lt;a class="external-link" href="https://digitalid.design/evaluation-framework-case-studies/kenya.html"&gt;case-study&lt;/a&gt; or download as &lt;a href="https://cis-india.org/internet-governance/digital-id-kenya-case-study" class="internal-link" title="Digital ID Kenya Case Study"&gt;PDF&lt;/a&gt;.&lt;/p&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/governing-id-kenya2019s-huduma-namba-programme'&gt;https://cis-india.org/internet-governance/blog/governing-id-kenya2019s-huduma-namba-programme&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>amber</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>internet governance</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Digital Identity</dc:subject>
    

   <dc:date>2020-03-02T13:19:15Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/governing-id-introducing-our-evaluation-framework">
    <title>Governing ID: Introducing our Evaluation Framework</title>
    <link>https://cis-india.org/internet-governance/blog/governing-id-introducing-our-evaluation-framework</link>
    <description>
        &lt;b&gt;&lt;/b&gt;
        
&lt;div class="content"&gt;
&lt;p&gt;With the rise of national digital identity systems (Digital ID) across the world, there is a growing need to examine their impact on human rights. In several instances, national Digital ID programmes started with a specific scope of use, but have since been deployed for different applications, and in different sectors. This raises the question of how to determine appropriate and inappropriate uses of Digital ID. In April 2019, our research began with this question, but it quickly became clear that a determination of the legitimacy of uses hinged on the fundamental attributes and governing structure of the Digital ID system itself. Our evaluation framework is intended as a series of questions against which Digital ID may be tested. We hope that these questions will inform the trade-offs that must be made while building and assessing identity programmes, to ensure that human rights are adequately protected.&lt;/p&gt;
&lt;h4&gt;Rule of Law Tests&lt;/h4&gt;
&lt;p&gt;Foundational Digital ID must only be implemented along with a 
legitimate regulatory framework that governs all aspects of Digital ID, 
including its aims and purposes, the actors who have access to it, etc. 
In the absence of this framework, there is nothing that precludes 
Digital IDs from being leveraged by public and private actors for 
purposes outside the intended scope of the programme. Our rule of law 
principles mandate that the governing law should be enacted by the 
legislature, be devoid of excessive delegation, be clear and accessible 
to the public, and be precise and limiting in its scope for discretion. 
These principles are substantiated by the criticism that the Kenyan 
Digital ID, the Huduma Namba, was met with when it was legalized through
 a Miscellaneous Amendment Act, meant only for small or negligible 
amendments and typically passed without any deliberation. These set of 
tests respond to the haste with which Digital ID has been implemented, 
often in the absence of an enabling law which adequately addresses its 
potential harms.&lt;/p&gt;
&lt;h4&gt;Rights based Tests&lt;/h4&gt;
&lt;p&gt;Digital ID, because of its collection of personal data and 
determination of eligibility and rights of users, intrinsically involves
 restrictions on certain fundamental rights. The use of Digital ID for 
essential functions of the State, including delivery of benefits and 
welfare, and maintenance of civil and sectoral records, enhance the 
impact of these restrictions. Accordingly, the entire identity 
framework, including its architecture, uses, actors, and regulators, 
must be evaluated at every stage against the rights it is potentially 
violating. Only then will we be able to determine if such violation is 
necessary and proportionate to the benefits it offers. In Jamaica, the 
National Identification and Registration Act, which mandated citizens’ 
biometric enrolment at the risk of criminal sanctions, was held to be a 
disproportionate violation of privacy, and therefore unconstitutional.&lt;/p&gt;
&lt;h4&gt;Risk based Tests&lt;/h4&gt;
&lt;p&gt;Even with a valid rule of law framework that seeks to protect 
rights, the design and use of Digital ID must be based on an analysis of
 the risks that the system introduces. This could take the form of 
choosing between a centralized and federated data-storage framework, 
based on the effects of potential failure or breach, or of restricting 
the uses of the Digital ID to limit the actors that will benefit from 
breaching it. Aside from the design of the system, the regulatory 
framework that governs it should also be tailored to the potential risks
 of its use. The primary rationale behind a risk assessment for an 
identity framework is that it should be tested not merely against 
universal metrics of legality and proportionality, but also against an 
examination of the risks and harms it poses. Implicit in a risk based 
assessment is also the requirement of implementing a responsive 
mitigation strategy to the risks identified, both while creating and 
governing the identity programme.&lt;/p&gt;
&lt;p&gt;Digital ID programmes create an inherent power imbalance 
between the State and its residents because of the personal data they 
collect and the consequent determination of significant rights, 
potentially creating risks of surveillance, exclusion, and 
discrimination. The accountability and efficiency gains they promise 
must not lead to hasty or inadequate implementation.&lt;/p&gt;
&lt;/div&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/governing-id-introducing-our-evaluation-framework'&gt;https://cis-india.org/internet-governance/blog/governing-id-introducing-our-evaluation-framework&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Shruti Trikanad</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>internet governance</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Digital Identity</dc:subject>
    

   <dc:date>2020-03-02T08:03:49Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/governing-id-india2019s-unique-identity-programme">
    <title>Governing ID: India’s Unique Identity Programme</title>
    <link>https://cis-india.org/internet-governance/governing-id-india2019s-unique-identity-programme</link>
    <description>
        &lt;b&gt;&lt;/b&gt;
        
&lt;div class="content"&gt;
&lt;p&gt;In our second case-study, we use our Evaluation Framework for Digital ID to assess India’s Unique Identity Programme.&lt;/p&gt;
&lt;p&gt;Read the &lt;a class="external-link" href="https://digitalid.design/evaluation-framework-case-studies/india.html"&gt;case-study&lt;/a&gt; or download as &lt;a href="https://cis-india.org/internet-governance/digital-id-india-case-study" class="internal-link" title="Digital ID India Case Study"&gt;PDF&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/governing-id-india2019s-unique-identity-programme'&gt;https://cis-india.org/internet-governance/governing-id-india2019s-unique-identity-programme&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Vrinda Bhandari</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>internet governance</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Digital Identity</dc:subject>
    

   <dc:date>2020-03-02T11:38:51Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/governing-id-a-framework-for-evaluation-of-digital-identity">
    <title>Governing ID: A Framework for Evaluation of Digital Identity</title>
    <link>https://cis-india.org/internet-governance/blog/governing-id-a-framework-for-evaluation-of-digital-identity</link>
    <description>
        &lt;b&gt;&lt;/b&gt;
        
&lt;p&gt;As governments across the globe implement new and foundational 
digital identification systems (Digital ID), or modernize existing ID 
programs, there is an urgent need for more research and discussion about
 appropriate uses of Digital ID systems. This significant momentum for 
creating Digital ID has been accompanied with concerns about privacy, 
surveillance and exclusion harms of state-issued Digital IDs in several 
parts of the world, resulting in campaigns and litigations in countries,
 such as UK, India, Kenya, and Jamaica. Given the sweeping range of 
considerations required to evaluate Digital ID projects, it is necessary
 to formulate evaluation frameworks that can be used for this purpose.&lt;/p&gt;
&lt;p&gt;This work began with the question of what the appropriate uses
 of Digital ID can be, but through the research process, it became clear
 that the question of use cannot be divorced from the fundamental 
attributes of Digital ID systems and their governance structures. This 
framework provides tests, which can be used to evaluate the governance 
of Digital ID across jurisdictions, as well as determine whether a 
particular use of Digital ID is legitimate. Through three kinds of 
checks — Rule of Law tests, Rights based tests, and Risks based tests — 
this scheme is a ready guide for evaluation of Digital ID.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://cis-india.org/internet-governance/image-governing-id-principles-for-evalution/" alt="null" width="100%" /&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;View the &lt;a class="external-link" href="https://digitalid.design/evaluation-framework-02.html"&gt;framework&lt;/a&gt; or download as&amp;nbsp;&lt;a href="https://cis-india.org/internet-governance/governing-id-principles-for-evalution" class="internal-link" title="Governing ID: Principles for Evalution"&gt;PDF&lt;/a&gt;.&lt;/p&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/governing-id-a-framework-for-evaluation-of-digital-identity'&gt;https://cis-india.org/internet-governance/blog/governing-id-a-framework-for-evaluation-of-digital-identity&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Vrinda Bhandari, Shruti Trikanad, and Amber Sinha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>internet governance</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Digital Identity</dc:subject>
    

   <dc:date>2020-03-02T13:22:43Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/governing-id-2028use-of-digital-id-for-verification">
    <title>Governing ID:  Use of Digital ID for Verification</title>
    <link>https://cis-india.org/internet-governance/blog/governing-id-2028use-of-digital-id-for-verification</link>
    <description>
        &lt;b&gt;&lt;/b&gt;
        
&lt;p&gt;This is the first in a series of case studies, using our recently-published &lt;a href="https://digitalid.design/evaluation-framework-02.html"&gt;Evaluation Framework for Digital ID&lt;/a&gt;. It looks at the use of digital identity programmes for the purpose of verification, often using the process of deduplication.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://cis-india.org/internet-governance/image-governing-id-use-of-digital-id-for-verification/" alt="null" width="100%" /&gt;&lt;/p&gt;
Read the &lt;a class="external-link" href="https://digitalid.design/evaluation-framework-case-studies/verification.html"&gt;case-study&lt;/a&gt; or download as &lt;a href="https://cis-india.org/internet-governance/use-of-digital-id-for-verification" class="internal-link" title="Use of Digital ID for Verification"&gt;PDF.&lt;/a&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/governing-id-2028use-of-digital-id-for-verification'&gt;https://cis-india.org/internet-governance/blog/governing-id-2028use-of-digital-id-for-verification&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Shruti Trikanad</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>internet governance</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Digital Identity</dc:subject>
    

   <dc:date>2020-03-02T11:16:19Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/do-we-really-need-an-app-for-that-examining-the-utility-and-privacy-implications-of-india2019s-digital-vaccine-certificates">
    <title>Do We Really Need an App for That? Examining the Utility and Privacy Implications of India’s Digital Vaccine Certificates</title>
    <link>https://cis-india.org/internet-governance/blog/do-we-really-need-an-app-for-that-examining-the-utility-and-privacy-implications-of-india2019s-digital-vaccine-certificates</link>
    <description>
        &lt;b&gt;We examine the purported benefits of digital vaccine certificates over regular paper-based ones and analyse the privacy implications of their use.&lt;/b&gt;
        
&lt;p&gt;&lt;em&gt;This blogpost was edited by Gurshabad Grover, Yesha Tshering Paul, and Amber Sinha.&lt;br /&gt;It was originally published on &lt;a href="https://digitalid.design/vaccine-certificates.html"&gt;Digital Identities: Design and Uses&lt;/a&gt; and is cross-posted here.&lt;br /&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In an experiment to streamline its COVID-19 immunisation drive, India has adopted a centralised vaccine administration system called CoWIN (or COVID Vaccine Intelligence Network). In addition to facilitating registration for both online and walk-in vaccine appointments, the system also allows for the &lt;a href="https://verify.cowin.gov.in/" target="_blank"&gt;digital verification&lt;/a&gt; of vaccine certificates, which it issues to people who have received a dose. This development aligns with a global trend, as many countries have adopted or are in the process of adopting “vaccine passports” to facilitate safe movement of people while resuming commercial activity.
    &lt;br /&gt;&lt;br /&gt;Some places, such as the &lt;a href="https://www.schengenvisainfo.com/news/all-your-questions-on-eus-covid-19-vaccine-certificate-answered/" target="_blank"&gt;EU&lt;/a&gt;, have constrained the scope of use of their vaccine certificates to international travel. The Indian government, however, has so far &lt;a href="https://www.livemint.com/opinion/columns/vaccination-certificates-need-a-framework-to-govern-their-use-11618160385602.html" target="_blank"&gt;skirted&lt;/a&gt; important questions around where and when this technology should be used. By allowing &lt;a href="https://verify.cowin.gov.in/" target="_blank"&gt;anyone&lt;/a&gt; to use the online CoWIN portal to scan and verify certificates, and even providing a way for the private-sector to incorporate this functionality into their applications, the government has opened up the possibility of these digital certificates being used, and even mandated, for domestic everyday use such as going to a grocery shop, a crowded venue, or a workplace.
    &lt;br /&gt;&lt;br /&gt;In this blog post, we examine the purported benefits of digital vaccine certificates over regular paper-based ones, analyse the privacy implications of their use, and present recommendations to make them more privacy respecting. We hope that such an analysis can help inform policy on appropriate use of this technology and improve its privacy properties in cases where its use is warranted.
    &lt;br /&gt;&lt;br /&gt;We also note that while this post only examines the merits of a technological solution put out by the government, it is more important to &lt;a href="https://www.accessnow.org/cms/assets/uploads/2021/04/Covid-Vaccine-Passports-Threaten-Human-Rights.pdf" target="_blank"&gt;consider&lt;/a&gt; the effects that placing restrictions on the movement of unvaccinated people has on their civil liberties in the face of a vaccine rollout that is inequitable along many lines, including &lt;a href="https://thewire.in/gender/women-falling-behind-in-indias-covid-19-vaccination-drive" target="_blank"&gt;gender&lt;/a&gt;, &lt;a href="https://www.thehindu.com/sci-tech/science/will-25-covid-19-vaccines-for-private-hospitals-aggravate-inequity/article34799098.ece" target="_blank"&gt;caste-class&lt;/a&gt;, and &lt;a href="https://scroll.in/article/994871/tech-savvy-indians-drive-to-villages-for-covid-19-vaccinations-those-without-smartphones-lose-out" target="_blank"&gt;access to technology&lt;/a&gt;.&lt;/p&gt;
&lt;h4&gt;How do digital vaccine certificates work?&lt;/h4&gt;
&lt;p&gt;Every vaccine recipient in the country is required to be registered on the CoWIN platform using one of &lt;a href="https://www.cowin.gov.in/faq" target="_blank"&gt;seven&lt;/a&gt; existing identity documents. [1] &lt;a name="ref1"&gt;&lt;/a&gt; Once a vaccine is administered, CoWIN generates a vaccine certificate which the recipient can access on the CoWIN website. The certificate is a single page document that contains the recipient’s personal information — their name, age, gender, identity document details, unique health ID, a reference ID — and some details about the vaccine given.&lt;a name="ref2"&gt;&lt;/a&gt; [2] It also includes a “secure QR code” and a link to CoWIN’s verification &lt;a href="https://verify.cowin.gov.in/" target="_blank"&gt;portal&lt;/a&gt;.
  &lt;br /&gt;&lt;br /&gt;The verification portal allows for the verification of a certificate by scanning the attached QR code. Upon completion, the portal displays a success message along with some of the information printed on the certificate.
  &lt;br /&gt;&lt;br /&gt;Verification is done using a cryptographic mechanism known as &lt;a href="https://en.wikipedia.org/wiki/Digital_signature" target="_blank"&gt;digital signatures&lt;/a&gt;, which are encoded into the QR code attached to a vaccine certificate. This mechanism allows “offline verification”, which means that the CoWIN verification portal or any private sector app attempting to verify a certificate does not need to contact the CoWIN servers to establish its authenticity. It instead uses a “public key” issued by CoWIN beforehand to verify the digital signature attached to the certificate.
  &lt;br /&gt;&lt;br /&gt;The benefit of this convoluted design is that it protects user privacy. Performing verification offline and not contacting the CoWIN servers, precludes CoWIN from gleaning sensitive metadata about usage of the vaccine certificate. This means that CoWIN does not learn about where and when an individual uses their vaccine certificate, and who is verifying it. This closes off a potential avenue for mass surveillance. [3] However, given how certificate revocation checks are being implemented (detailed in the privacy implications section below), CoWIN ends up learning this information anyway.&lt;/p&gt;
&lt;h4&gt;Where is digital verification useful?&lt;/h4&gt;
&lt;p&gt;The primary argument for the adoption of digital verification of vaccine certificates over visual examination of regular paper-based ones is security. In the face of vaccine hesitancy, there are concerns that people may forge vaccine certificates to get around any restrictions that may be put in place on the movement of unvaccinated people. The use of digital signatures serves to allay these fears.
&lt;br /&gt;&lt;br /&gt;In its current form, however, digital verification of vaccine certificates is no more secure than visually inspecting paper-based ones. While the “secure QR code” attached to digital certificates can be used to verify the authenticity of the certificate itself, the CoWIN verification portal does not provide any mechanism nor does it instruct verifiers to authenticate the identity of the person presenting the certificate. This means that unless an accompanying identity document is also checked, an individual can simply present someone else’s certificate.
&lt;br /&gt;&lt;br /&gt;There are no simple solutions to this limitation; adding a requirement to inspect identity documents in addition to digital verification of the vaccine certificate would not be a strong enough security measure to prevent the use of duplicate vaccine certificates. People who are motivated enough to forge a vaccine certificate, can also duplicate one of the seven ID documents which can be used to register on CoWIN, some of which are simple paper-based documents. [4] Requiring even stronger identity checks, such as the use of Aadhaar-based biometrics, would make digital verification of vaccine certificates more secure. However, this would be a wildly disproportionate incursion on user privacy — allowing for the mass collection of metadata like when and where a certificate is used — something that digital vaccine certificates were explicitly designed to prevent. Additionally, in Russia, people were &lt;a href="https://www.washingtonpost.com/world/europe/moscow-fake-vaccine-coronavirus/2021/06/26/0881e1e4-cf98-11eb-a224-bd59bd22197c_story.html" target="_blank"&gt;found&lt;/a&gt; issuing fake certificates by discarding real vaccine doses instead of administering them. No technological solution can prevent such fraud.
&lt;br /&gt;&lt;br /&gt;As such, the utility of digital certificates is limited to uses such as international travel, where border control agencies already have strong identity checks in place for travellers. Any everyday usage of the digital verification functionality on vaccine certificates would not present any benefit over visually examining a piece of paper or a screen.&lt;/p&gt;
&lt;h4&gt;Privacy implications of digital certificates&lt;/h4&gt;
&lt;p&gt;In addition to providing little security utility over manual inspection of certificates, digital certificates also present privacy issues, these are listed below along with recommendations to mitigate them:
&lt;br /&gt;&lt;br /&gt;&lt;em&gt;(i) The verification portal leaks sensitive metadata to CoWIN’s servers:&lt;/em&gt; An analysis of network requests made by the CoWin verification portal reveals that it conducts a ‘revocation check’ each time a certificate is verified. This check was also found in the source &lt;a href="https://github.com/egovernments/DIVOC/blob/e667697b47a50a552b8d0a8c89a950180217b945/interfaces/vaccination-api.yaml#L385" target="_blank"&gt;code&lt;/a&gt;, which is made openly available&lt;a name="ref5"&gt;&lt;/a&gt;.
[5]&lt;/p&gt;
&lt;p&gt;Revocation checks are an important security consideration while using digital signatures. They allow the issuing authority (CoWIN, in this case) to revoke a certificate in case the account associated with it is lost or stolen, or if a certificate requires correction. However, the way they have been implemented here presents a significant privacy issue. Sending certificate details to the server on every verification attempt allows it to learn about where and when an individual is using their vaccine certificate.
&lt;br /&gt;&lt;br /&gt;We note that the revocation check performed by the CoWIN portal does not necessarily mean that it is storing this information. Nevertheless, sending certificate information to the server directly contradicts claims of an “offline verification” process, which is the basis of the design of these digital certificates.
&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Recommendations:&lt;/strong&gt; Implementing privacy-respecting revocation checks such as Certificate Revocation Lists, [6] or Range Queries [7] would mitigate this issue. However, these solutions are either complex or present bandwidth and storage tradeoffs for the verifier.
&lt;br /&gt;&lt;br /&gt;&lt;em&gt;(ii) Oversharing of personally identifiable information:&lt;/em&gt; CoWIN’s vaccine certificates include more personally identifiable information (name, age, gender, identity document details and unique health ID) than is required for the purpose of verifying the certificate. An examination of the vaccine certificates available to us revealed that while the Aadhaar number is appropriately masked, other personal identifiers such as passport number and unique health ID were not masked. Additionally, the inclusion of demographic details, such as age and gender, provides little security benefit by limiting the pool of duplicate certificates that can be used and are not required in light of the security analysis above.
&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Recommendation:&lt;/strong&gt; Personal identifiers (such as passport number and unique health ID) should be appropriately masked and demographic details (age, gender) can be removed.
&lt;br /&gt;&lt;br /&gt;The minimal set of data required for identity-linked usage for digital verification, as described above, is a full name and masked ID document details. All other personally identifying information can be removed. In case of paper-based certificates, which is suggested for domestic usage, only the details about vaccine validity would suffice and no personal information is required.
&lt;br /&gt;&lt;br /&gt;&lt;em&gt;(iii) Making information available digitally increases the likelihood of collection:&lt;/em&gt; All of the personal information printed on the certificate is also encoded into the QR code. This is &lt;a href="https://www.bbc.com/news/uk-scotland-57208607" target="_blank"&gt;necessary&lt;/a&gt; because the digital signature verification process also verifies the integrity of this information (i.e. it wasn’t modified). A side effect of this is that the personal information is made readily available in digital form to verifiers when it is scanned, making it easy for them to store. This is especially likely in private sector apps who may be interested in collecting demographic information and personal identifiers to track customer behaviour.
&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Recommendation:&lt;/strong&gt; Removing extraneous information from the certificate, as suggested above, mitigates this risk as well.&lt;/p&gt;
&lt;h4&gt;Conclusion&lt;/h4&gt;
&lt;p&gt;Our analysis reveals that without incorporating strong, privacy-invasive identity checks, digital verification of vaccine certificates does not provide any security benefit over manually inspecting a piece of paper. The utility of digital verification is limited to purposes that already conduct strong identity checks.
&lt;br /&gt;&lt;br /&gt;In addition to their limited applicability, in their current form, these digital certificates also generate a trail of data and metadata, giving both government and industry an opportunity to infringe upon the privacy of the individuals using them.
&lt;br /&gt;&lt;br /&gt;Keeping this in mind, the adoption of this technology should be discouraged for everyday use.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h4&gt;References&lt;/h4&gt;
&lt;p&gt;[1] Exceptions &lt;a href="https://web.archive.org/web/20210511045921/https://www.mohfw.gov.in/pdf/SOPforCOVID19VaccinationofPersonswithoutPrescribedIdentityCards.pdf" target="_blank"&gt;exist&lt;/a&gt; for people without state-issued identity documents.&lt;/p&gt;
&lt;p&gt;[2] This information was gathered by inspecting three vaccine certificates linked to the author’s CoWIN account, which they were authorised to view, and may not be fully accurate.&lt;/p&gt;
&lt;p&gt;[3] This design is similar to Aadhaar’s “&lt;a href="https://resident.uidai.gov.in/offline-kyc" target="_blank"&gt;offline KYC&lt;/a&gt;” process.&lt;/p&gt;
&lt;p&gt;[4] “Aadhaar Card: UIDAI says downloaded versions on ordinary paper, mAadhaar perfectly valid”, &lt;em&gt;Zee Business&lt;/em&gt;, April 29 2019, &lt;em&gt;https://www.zeebiz.com/india/news-aadhaar-card-uidai-says-downloaded-versions-on-ordinary-paper-maadhaar-perfectly-valid-96790&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;[5] This check was also verified to be present in the reference &lt;a href="https://github.com/egovernments/DIVOC/blob/261a61093b89990fe34698f9ba17367d4cb74c34/public_app/src/components/CertificateStatus/index.js#L125" target="_blank"&gt;code&lt;/a&gt; made available for private-sector applications incorporating this functionality, suggesting that private sector apps will also be affected by this.&lt;/p&gt;
&lt;p&gt;[6] &lt;a href="https://en.wikipedia.org/wiki/Certificate_revocation_list" target="_blank"&gt;Certificate Revocation Lists&lt;/a&gt; allow the server to provide a list of revoked certificates to the verifier, instead of the verifier querying the server each time. This, however, can place heavy bandwidth and storage requirements on the verifying app as this list can potentially grow long.&lt;/p&gt;
&lt;p&gt;[7] Range Queries are described in this &lt;a href="https://www.ics.uci.edu/~gts/paps/st06.pdf" target="_blank"&gt;paper&lt;/a&gt;. In this method, the verifier requests revocation status from the server by specifying a range of certificate identifiers within which the certificate being verified lies. If there are any revoked certificates within this range, the server will send their identifiers to the verifier, who can then check if the certificate in question is on the list. For this to work, the range selected must be sufficiently large to include enough potential candidates to keep the server from guessing which one is in use.&lt;/p&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/do-we-really-need-an-app-for-that-examining-the-utility-and-privacy-implications-of-india2019s-digital-vaccine-certificates'&gt;https://cis-india.org/internet-governance/blog/do-we-really-need-an-app-for-that-examining-the-utility-and-privacy-implications-of-india2019s-digital-vaccine-certificates&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>divyank</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Privacy</dc:subject>
    
    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Covid19</dc:subject>
    
    
        <dc:subject>Appropriate Use of Digital ID</dc:subject>
    

   <dc:date>2021-08-03T05:13:28Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/news/digital-id-forum-2019">
    <title>Digital ID Forum 2019</title>
    <link>https://cis-india.org/internet-governance/news/digital-id-forum-2019</link>
    <description>
        &lt;b&gt;Sunil Abraham was one of the panelists at this event at Chulalongkorn University on July 3, 2019.&lt;/b&gt;
        &lt;p&gt;&lt;img src="https://cis-india.org/home-images/DigitalID.png" alt="Digital ID" class="image-inline" title="Digital ID" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Click to &lt;/span&gt;&lt;a class="external-link" href="http://cis-india.org/internet-governance/files/digital-id-forum"&gt;view the agenda&lt;/a&gt;&lt;span&gt;. Also see &lt;/span&gt;&lt;a class="external-link" href="https://en.wikipedia.org/wiki/Asia_Source"&gt;Wikipedia page&lt;/a&gt;&lt;/p&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/news/digital-id-forum-2019'&gt;https://cis-india.org/internet-governance/news/digital-id-forum-2019&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Admin</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Privacy</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Appropriate Use of Digital ID</dc:subject>
    
    
        <dc:subject>Digital Identity</dc:subject>
    

   <dc:date>2019-08-07T14:09:16Z</dc:date>
   <dc:type>News Item</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/digtial-identities-research-plan">
    <title>Design and Uses of Digital Identities - Research Plan</title>
    <link>https://cis-india.org/internet-governance/blog/digtial-identities-research-plan</link>
    <description>
        &lt;b&gt;In our research project about uses and design of digital identity systems, we ask two core questions: a) What are appropriate uses of ID?, and b) How should we think about the technological design of ID? Towards the first research question, we have worked on first principles and will further develop definitions, legal tests and applications of these principles. Towards the second research question, we have first identified a set of existing and planned digital identity systems that represent a paradigm of how such a system can be envisioned and implemented, and will look to identify key design choices which are causing divergence in paradigm.&lt;/b&gt;
        
&lt;h4&gt;Read the research plan &lt;a class="external-link" href="https://digitalid.design/research-plan.html"&gt;here&lt;/a&gt;.&lt;/h4&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/digtial-identities-research-plan'&gt;https://cis-india.org/internet-governance/blog/digtial-identities-research-plan&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Amber Sinha and Pooja Saxena</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Privacy</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Appropriate Use of Digital ID</dc:subject>
    
    
        <dc:subject>Digital Identity</dc:subject>
    

   <dc:date>2019-08-17T07:58:44Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/digital-identity/shruti-trikanand-and-amber-sinha-september-13-2019-core-concepts-processes">
    <title>Core Concepts and Processes</title>
    <link>https://cis-india.org/internet-governance/digital-identity/shruti-trikanand-and-amber-sinha-september-13-2019-core-concepts-processes</link>
    <description>
        &lt;b&gt;When we embarked on this research project, we began with the primary questions of what constitutes a digital identity system. In the last few years, with the rise in national digital identity projects, there has been significant academic and media attention to the idea, benefits and risks of a digital identity system.&lt;/b&gt;
        &lt;p style="text-align: justify; "&gt;However, there have been relatively few attempts to critically look at what makes an identity system digital, and what are its defining elements and characteristics. Through a preliminary study of existing identity systems, we have arrived at these core set of concepts and processes that mark a digital identity system. In arriving at this list, we have relied upon and referred to the works by &lt;a href="http://www.chyp.com/wp-content/uploads/2016/07/Digital-Identity-Issue-Analysis-Report.pdf" target="_blank"&gt;Dave Birch et al&lt;/a&gt;, &lt;a href="http://documents.worldbank.org/curated/en/248371559325561562/pdf/ID4D-Practitioner-Guide-Draft-for-Consultation.pdf" target="_blank"&gt;World Bank’s ID4D initiative&lt;/a&gt;, &lt;a href="https://www.semanticscholar.org/paper/Becoming-Artifacts-Medieval-Seals%2C-Passports-and-of-Chango/42cf3a5a5a2db067327298e7d8c540c9691171d2" target="_blank"&gt;Mawaki Chango&lt;/a&gt;, &lt;a href="https://identitywoman.net/domains-of-identity/" target="_blank"&gt;Kaliya Young&lt;/a&gt; and &lt;a href="https://medium.com/@kezike/the-evolution-of-digital-identity-6c13aca128c0" target="_blank"&gt;Kayode Ezike&lt;/a&gt;.&lt;/p&gt;
&lt;p class="indent" style="text-align: justify; "&gt;By publishing this, we hope to arrive at a shared vocabulary to discuss and critically analyse digital identity systems, both within our team and in engagements with other stakeholders. This illustrated and interactive glossary can serve as an easy reference for anyone seeking an introduction to the core aspects of digital identity. Even though this is essentially a list of definitions with examples, it does not follow an alphabetical order like most glossaries, but the logical flow of concepts as they build upon each other in a working identity system. We have paid special emphasis to the core processes of &lt;a href="https://digitalid.design/core-concepts-processes.html#identification-diagram"&gt;Identification&lt;/a&gt; and &lt;a href="https://digitalid.design/core-concepts-processes.html#authentication-diagram"&gt;Authentication&lt;/a&gt;, elucidating them through diagrams.&lt;/p&gt;
&lt;p class="indent"&gt;&lt;a class="external-link" href="https://digitalid.design/core-concepts-processes.html"&gt;Click to read more&lt;/a&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;Credentials:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt; Research by Shruti Trikanad and Amber Sinha &lt;/li&gt;
&lt;li&gt; Conceptualization by Pooja Saxena and Amber Sinha &lt;/li&gt;
&lt;li&gt;Illustrations by Akash Sheshadri and Pooja Saxena&lt;/li&gt;
&lt;/ul&gt;
        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/digital-identity/shruti-trikanand-and-amber-sinha-september-13-2019-core-concepts-processes'&gt;https://cis-india.org/internet-governance/digital-identity/shruti-trikanand-and-amber-sinha-september-13-2019-core-concepts-processes&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Shruti Trikanand and Amber Sinha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Digital Identity</dc:subject>
    

   <dc:date>2019-10-17T16:06:54Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/comments-to-the-id4d-practitioners2019-guide">
    <title>Comments to the ID4D Practitioners’ Guide</title>
    <link>https://cis-india.org/internet-governance/blog/comments-to-the-id4d-practitioners2019-guide</link>
    <description>
        &lt;b&gt;&lt;/b&gt;
        
&lt;p&gt;This post presents our comments to the ID4D Practitioners’ Guide: Draft For Consultation released by ID4D in June, 2019. CIS has conducted research on issues related to digital identity since 2012. This submission is divided into three main parts. The first part (General Comments) contains the high-level comments on the Practitioners’ Guide, while the second part (Specific Comments) addresses individual sections in the Guide. The third and final part (Additional Comments) does not relate to particulars in the Practitioners' Guide but other documents that it relies upon. We submitted these comments to ID4D on August 5, 2019.&amp;nbsp;Read our comments &lt;a class="external-link" href="https://digitalid.design/comments-ID4D-practitioners-guide.html"&gt;here&lt;/a&gt;.&lt;/p&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/comments-to-the-id4d-practitioners2019-guide'&gt;https://cis-india.org/internet-governance/blog/comments-to-the-id4d-practitioners2019-guide&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Yesha Tshering Paul, Prakriti Singh, and Amber Sinha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Privacy</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Appropriate Use of Digital ID</dc:subject>
    
    
        <dc:subject>Digital Identity</dc:subject>
    

   <dc:date>2019-08-08T10:25:13Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/comments-on-the-report-of-the-committee-on-digital-payments-dec-2016">
    <title>Comments on  the Report of the Committee on Digital Payments (December 2016)</title>
    <link>https://cis-india.org/internet-governance/blog/comments-on-the-report-of-the-committee-on-digital-payments-dec-2016</link>
    <description>
        &lt;b&gt;The Committee on Digital Payments constituted by the Ministry of Finance and chaired by Ratan P. Watal, Principal Advisor, NITI Aayog, submitted its report on the "Medium Term Recommendations to Strengthen Digital Payments Ecosystem" on December 09, 2016. The report was made public on December 27, and comments were sought from the general public. Here are the comments submitted by the Centre for Internet and Society.&lt;/b&gt;
        
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h3&gt;&lt;strong&gt;1. Preliminary&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;1.1.&lt;/strong&gt; This submission presents comments by the Centre for Internet and Society (“CIS”) &lt;strong&gt;[1]&lt;/strong&gt; in response to the report of the Committee on Digital Payments, chaired by Mr. Ratan P. Watal, Principal Advisor, NITI Aayog, and constituted by the Ministry of Finance, Government of India (“the report”) &lt;strong&gt;[2]&lt;/strong&gt;.&lt;/p&gt;
&lt;h3&gt;&lt;strong&gt;2. The Centre for Internet and Society&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;2.1.&lt;/strong&gt; The Centre for Internet and Society, CIS, is a non-profit organisation that undertakes interdisciplinary research on internet and digital technologies from policy and academic perspectives. The areas of focus include digital accessibility for persons with diverse abilities, access to knowledge, intellectual property rights, openness (including open data, free and open source software, open standards, and open access), internet governance, telecommunication reform, digital privacy, and cyber-security.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2.2.&lt;/strong&gt; CIS is not an expert organisation in the domain of banking in general and payments in particular. Our expertise is in matters of internet and communication governance, data privacy and security, and technology regulation. We deeply appreciate and are most inspired by the Ministry of Finance’s decision to invite entities from both the sectors of finance and information technology. This submission is consistent with CIS’ commitment to safeguarding general public interest, and the interests and rights of various stakeholders involved, especially the citizens and the users. CIS is thankful to the Ministry of Finance for this opportunity to provide a general response on the report.&lt;/p&gt;
&lt;h3&gt;&lt;strong&gt;3. Comments&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;3.1.&lt;/strong&gt; CIS observes that the decision by the Government of India to withdraw the legal tender character of the old high denomination banknotes (that is, Rs. 500 Rs. 1,000 notes), declared on November 08, 2016 &lt;strong&gt;[3]&lt;/strong&gt;, have generated &lt;strong&gt;unprecedented data about the user base and transaction patterns of digital payments systems in India, when pushed to its extreme use due to the circumstances&lt;/strong&gt;. The majority of this data is available with the National Payments Corporation of India and the Reserve Bank of India. CIS requests the authorities concerned to consider &lt;strong&gt;opening up this data for analysis and discussion by public at large and experts in particular, before any specific policy and regulatory decisions are taken&lt;/strong&gt; towards advancing digital payments proliferation in India. This is a crucial opportunity for the Ministry of Finance to embrace (open) data-driven regulation and policy-making.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.2.&lt;/strong&gt; While the report makes a reference to the European General Data Protection Directive, it does not make a reference to any substantive provisions in the Directive which may be relevant to digital payments. Aside from the recommendation that privacy protections around the purpose limitation principle be relaxed to ensure that payment service providers be allowed to process data to improve fraud monitoring and anti-money laundering services, the report is silent on significant privacy and data protection concerns posed by digital payments services. &lt;strong&gt;CIS strongly warns that the existing data protection and security regulations under Information Technology (Reasonable security practices and procedures and sensitive personal data or information), Rules are woefully inadequate in their scope and application to effectively deal with potential privacy concerns posed by digital payments applications and services.&lt;/strong&gt; Some key privacy issues that must be addressed either under a comprehensive data protection legislation or a sector specific financial regulation are listed below. The process of obtaining consent must be specific, informed and unambiguous and through a clear affirmative action by the data subject based upon a genuine choice provided along with an option to opt out at any stage. The data subjects should have clear and easily enforceable right to access and correct their data. Further, data subjects should have the right to restrict the usage of their data in circumstances such as inaccuracy of data, unlawful purpose and data no longer required in order to fulfill the original purpose.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.3.&lt;/strong&gt; The initial recommendation of the report is to “[m]ake regulation of payments independent from the function of central banking” (page 22). This involves a fundamental transformation of the payment and settlement system in India and its regulation. &lt;strong&gt;We submit that a decision regarding transformation of such scale and implications is taken after a more comprehensive policy discussion, especially involving a wider range of stakeholders&lt;/strong&gt;. The report itself notes that “[d]igital payments also have the potential of becoming a gateway to other financial services such as credit facilities for small businesses and low-income households” (page 32). Thus, a clear functional, and hence regulatory, separation between the (digital) payments industry and the lending/borrowing industry may be either effective or desirable. Global experience tells us that digital transactions data, along with other alternative data, are fast becoming the basis of provision of financial and other services, by both banking and non-banking (payments) companies. We appeal to the Ministry of Finance to adopt a comprehensive and concerted approach to regulating, enabling competition, and upholding consumers’ rights in the banking sector at large.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.4.&lt;/strong&gt; The report recognises “banking as an activity is separate from payments, which is more of a technology business” (page 154). Contemporary banking and payment businesses are both are primarily technology businesses where information technology particularly is deployed intimately to extract, process, and drive asset management decisions using financial transaction data. Further, with payment businesses (such as, pre-paid instruments) offering return on deposited money via other means (such as, cashbacks), and potentially competing and/or collaborating with established banks to use financial transaction data to drive lending decisions, including but not limited to micro-loans, it appears unproductive to create a separation between banking as an activity and payments as an activity merely in terms of the respective technology intensity of these sectors. &lt;strong&gt;CIS firmly recommends that regulation of these financial services and activities be undertaken in a technology-agnostic manner, and similar regulatory regimes be deployed on those entities offering similar services irrespective of their technology intensity or choice&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.5.&lt;/strong&gt; The report highlights two major shortcomings of the current regulatory regime for payments. Firstly “the law does not impose any obligation on the regulator to promote competition and innovation in the payments market” (page 153). It appears to us that the regulator’s role should not be to promote market expansion and innovation but to ensure and oversee competition. &lt;strong&gt;We believe that the current regulator should focus on regulating the existing market, and the work of the expansion of the digital payments market in particular and the digital financial services market in general be carried out by another government agency, as it creates conflict of interest for the regulator otherwise.&lt;/strong&gt; Secondly, the report mentions that Payment and Settlement Systems Act does not “focus the regulatory attention on the need for consumer protection in digital payments” and then it notes that a “provision was inserted to protect funds collected from customers” in 2015 (page 153). &lt;strong&gt;This indicates that the regulator already has the responsibility to ensure consumer protection in digital payments. The purview and modalities of how this function of course needs discussion and changes with the growth in digital payments&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.6.&lt;/strong&gt; The report identifies the high cost of cash as a key reason for the government’s policy push towards digital payments. Further, it mentions that a “sample survey conducted in 2014 across urban and rural neighbourhoods in Delhi and Meerut, shows that despite being keenly aware of the costs associated with transacting in cash, most consumers see three main benefits of cash, viz. freedom of negotiations, faster settlements, and ensuring exact payments” (page 30). It further notes that “[d]igital payments have significant dependencies upon power and telecommunications infrastructure. Therefore, the roll out of robust and user friendly digital payments solutions to unelectrified areas/areas without telecommunications network coverage, remains a challenge.” &lt;strong&gt;CIS much appreciates the discussion of the barriers to universal adoption and rollout of digital payments in the report, and appeals to the Ministry of Finance to undertake a more comprehensive study of the key investments required by the Government of India to ensure that digital payments become ubiquitously viable as well as satisfy the demands of a vast range of consumers that India has&lt;/strong&gt;. The estimates about investment required to create a robust digital payment infrastructure, cited in the report, provide a great basis for undertaking studies such as these.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.7.&lt;/strong&gt; CIS is very encouraged to see the report highlighting that “[w]ith the rising number of users of digital payment services, it is absolutely necessary to develop consumer confidence on digital payments. Therefore, it is essential to have legislative safeguards to protect such consumers in-built into the primary law.” &lt;strong&gt;We second this recommendation and would like to add further that financial transaction data is governed under a common data protection and privacy regime, without making any differences between data collected by banking and non-banking entities&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.8.&lt;/strong&gt; We are, however, very discouraged to see the overtly incorrect use of the word “Open Access” in this report in the context of a payment system disallowing service when the client wants to transact money with a specific entity &lt;strong&gt;[4]&lt;/strong&gt;. This is not an uncommon anti-competitive measure adopted by various platform players and services providers so as to disallow users from using competing products (such as, not allowing competing apps in the app store controlled by one software company). &lt;strong&gt;The term “Open Access” is not only the appropriate word to describe the negation of such anti-competitive behaviour, its usage in this context undermines its accepted meaning and creates confusion regarding the recommendation being proposed by the report.&lt;/strong&gt; The closest analogy to the recommendation of the report would perhaps be with the principle of “network neutrality” that stands for the network provider not discriminating between data packets being processed by them, either in terms of price or speed.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.9.&lt;/strong&gt; A major recommendation by the report involves creation of “a fund from savings generated from cash-less transactions … by the Central Government,” which will use “the trinity of JAM (Jan Dhan, Adhaar, Mobile) [to] link financial inclusion with social protection, contributing to improved Social and Financial Security and Inclusion of vulnerable groups/ communities” (page 160-161). &lt;strong&gt;This amounts to making Aadhaar a mandatory ID for financial inclusion of citizens, especially the marginal and vulnerable ones, and is in direct contradiction to the government’s statements regarding the optional nature of the Aadhaar ID, as well as the orders by the Supreme Court on this topic&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.10.&lt;/strong&gt; The report recommends that “Aadhaar should be made the primary identification for KYC with the option of using other IDs for people who have not yet obtained Aadhaar” (page 163) and further that “Aadhaar eKYC and eSign should be a replacement for paper based, costly, and shared central KYC registries” (page 162). &lt;strong&gt;Not only these measures would imply making Aadhaar a mandatory ID for undertaking any legal activity in the country, they assume that the UIDAI has verified and audited the personal documents submitted by Aadhaar number holders during enrollment.&lt;/strong&gt; A mandate for &lt;em&gt;replacement&lt;/em&gt; of the paper-based central KYC agencies will only remove a much needed redundancy in the the identity verification infrastructure of the government.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.11.&lt;/strong&gt; The report suggests that “[t]ransactions which are permitted in cash without KYC should also be permitted on prepaid wallets without KYC” (page 164-165). This seems to negate the reality that physical verification of a person remains one of the most authoritative identity verification process for a natural person, apart from DNA testing perhaps. &lt;strong&gt;Thus, establishing full equivalency of procedure between a presence-less transaction and one involving a physically present person making the payment will only amount to removal of relatively greater security precautions for the former, and will lead to possibilities of fraud&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.12.&lt;/strong&gt; In continuation with the previous point, the report recommends promotion of “Aadhaar based KYC where PAN has not been obtained” and making of “quoting Aadhaar compulsory in income tax return for natural persons” (page 163). Both these measures imply a replacement of the PAN by Aadhaar in the long term, and a sharp reduction in growth of new PAN holders in the short term. &lt;strong&gt;We appeal for this recommendation to be reconsidered as integration of all functionally separate national critical information infrastructures (such as PAN and Aadhaar) into a single unified and centralised system (such as Aadhaar) engenders massive  national and personal security threats&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.13.&lt;/strong&gt; The report suggest the establishment of “a ranking and reward framework” to recognise and encourage for the best performing state/district/agency in the proliferation of digital payments. &lt;strong&gt;It appears to us that creation of such a framework will only lead to making of an environment of competition among these entities concerned, which apart from its benefits may also have its costs. For example, the incentivisation of quick rollout of digital payment avenues by state government and various government agencies may lead to implementation without sufficient planning, coordination with stakeholders, and precautions regarding data security and privacy&lt;/strong&gt;. The provision of central support for digital payments should be carried out in an environment of cooperation and not competition.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.14.&lt;/strong&gt; CIS welcomes the recommendation by the report to generate greater awareness about cost of cash, including by ensuring that “large merchants including government agencies should account and disclose the cost of cash collection and cash payments incurred by them periodically” (page 164). It, however, is not clear to whom such periodic disclosures should be made. &lt;strong&gt;We would like to add here that the awareness building must simultaneously focus on making public how different entities shoulder these costs. Further, for reasons of comparison and evidence-driven policy making, it is necessary that data for equivalent variables are also made open for digital payments - the total and disaggregate cost, and what proportion of these costs are shouldered by which entities&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.15.&lt;/strong&gt; The report acknowledges that “[t]oday, most merchants do not accept digital payments” and it goes on to recommend “that the Government should seize the initiative and require all government agencies and merchants where contracts are awarded by the government to provide at-least one suitable digital payment option to its consumers and vendors” (page 165). This requirement for offering digital payment option will only introduce an additional economic barrier for merchants bidding for government contracts. &lt;strong&gt;We appeal to the Ministry of Finance to reconsider this approach of raising the costs of non-digital payments to incentivise proliferation of digital payments, and instead lower the existing economic and other barriers to digital payments that keep the merchants away&lt;/strong&gt;. The adoption of digital payments must not lead to increasing costs for merchants and end-users, but must decrease the same instead.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.16.&lt;/strong&gt; As the report was submitted on December 09, 2016, and was made public only on December 27, 2016, &lt;strong&gt;it would have been much appreciated if at least a month-long window was provided to study and comment on the report, instead of fifteen days&lt;/strong&gt;. This is especially crucial as the recently implemented demonetisation and the subsequent banking and fiscal policy decisions taken by the government have rapidly transformed the state and dynamics of the payments system landscape in India in general, and digital payments in particular.&lt;/p&gt;
&lt;h3&gt;&lt;strong&gt;Endnotes&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;[1]&lt;/strong&gt; See: &lt;a href="http://cis-india.org/"&gt;http://cis-india.org/&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;[2]&lt;/strong&gt; See: &lt;a href="http://finmin.nic.in/reports/Note-watal-report.pdf"&gt;http://finmin.nic.in/reports/Note-watal-report.pdf&lt;/a&gt; and &lt;a href="http://finmin.nic.in/reports/watal_report271216.pdf"&gt;http://finmin.nic.in/reports/watal_report271216.pdf&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;[3]&lt;/strong&gt; See: &lt;a href="http://finmin.nic.in/cancellation_high_denomination_notes.pdf"&gt;http://finmin.nic.in/cancellation_high_denomination_notes.pdf&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;[4]&lt;/strong&gt; Open Access refers to “free and unrestricted online availability” of scientific and non-scientific literature. See: &lt;a href="http://www.budapestopenaccessinitiative.org/read"&gt;http://www.budapestopenaccessinitiative.org/read&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/comments-on-the-report-of-the-committee-on-digital-payments-dec-2016'&gt;https://cis-india.org/internet-governance/blog/comments-on-the-report-of-the-committee-on-digital-payments-dec-2016&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Sumandro Chattapadhyay and Amber Sinha</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>UID</dc:subject>
    
    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Big Data</dc:subject>
    
    
        <dc:subject>Digital Economy</dc:subject>
    
    
        <dc:subject>Digital Access</dc:subject>
    
    
        <dc:subject>Privacy</dc:subject>
    
    
        <dc:subject>Digital Security</dc:subject>
    
    
        <dc:subject>Data Revolution</dc:subject>
    
    
        <dc:subject>Digital Payment</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Digital India</dc:subject>
    
    
        <dc:subject>Data Protection</dc:subject>
    
    
        <dc:subject>Demonetisation</dc:subject>
    
    
        <dc:subject>Homepage</dc:subject>
    
    
        <dc:subject>Featured</dc:subject>
    
    
        <dc:subject>Aadhaar</dc:subject>
    

   <dc:date>2017-01-12T12:32:22Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/blog/appropriate-use-of-digital-identity-alliance-announcement">
    <title>Announcement of a Three-Region Research Alliance on the Appropriate Use of Digital Identity</title>
    <link>https://cis-india.org/internet-governance/blog/appropriate-use-of-digital-identity-alliance-announcement</link>
    <description>
        &lt;b&gt;Omidyar Network has recently announced its decision to invest in establishment of a three-region research alliance — to be co-led by the Institute for Technology &amp; Society (ITS), Brazil, the Centre for Intellectual Property and Information Technology Law (CIPIT) , Kenya, and the CIS, India — on the Appropriate Use of Digital Identity. As part of this Alliance, we at the CIS will look at the policy objectives of digital identity projects, how technological policy choices can be thought through to meet the objectives, and how legitimate uses of a digital identity framework may be evaluated.&lt;/b&gt;
        
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;As governments across the globe are implementing new, digital foundational identification systems or modernizing existing ID programs, there is a dire need for greater research and discussion about appropriate design choices for a digital identity framework. There is significant momentum on digital ID, especially after the adoption of UN Sustainable Development Goal 16.9, which calls for legal identity for all by 2030. Given the importance of this subject, its implications for both the development agenda as well its impact on civil, social and economic rights, there is a need for more focused research that can enable policymakers to take better decisions, guide civil society in different jurisdictions to comment on and raise questions about digital identity schemes, and provide actionable material to the industry to create identity solutions that are privacy enhancing and inclusive.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h4&gt;Excerpt from the &lt;a href="https://www.omidyar.com/blog/appropriate-use-digital-identity-why-we-invested-three-region-research%C2%A0alliance" target="_blank"&gt;blog post by Subhashish Bhadra&lt;/a&gt; announcing this new research alliance&lt;/h4&gt;
&lt;p&gt;...In the absence of any widely-accepted thinking on this issue, we run the risk of digital identity systems suffering from mission creep, that is being made mandatory or being used for an ever-expanding set of services. We believe this creates several risks. First, people may be excluded from services if they do not have a digital identity or because it malfunctions. Second, this approach creates a wider digital footprint that can be used to create a profile of an individual, sometimes without consent. This can increase privacy risk. Third, this approach increases the power of institutions versus individuals and can be used as rationale to intentionally deny services, especially to vulnerable or persecuted groups.&lt;/p&gt;
&lt;p&gt;Three exceptional research groups have undertaken the effort of answering this complex and important question. Over the next six months, these think tanks will conduct independent research, as well as involve experts from across the globe. Based in South America, Africa, and Asia, these institutions represent the collective wisdom and experiences of three very distinct geographies in emerging markets. While drawing on their local context, this research effort is globally oriented. The think tanks will create a set of recommendations and tools that can be used by stakeholders to engage with digital identity systems in any part of the world...&lt;/p&gt;
&lt;p&gt;This research will use a collaborative and iterative process. The researchers will put out some ideas every few weeks, with the objective of seeking thoughts, questions, and feedback from various stakeholders. They will participate in several digital rights and identity events across the globe over the next several months. They will also organize webinars to seek input from and present their interim findings to interested communities from across the globe. Each of these provide an opportunity for you to provide your thoughts and help this research program provide an independent, rigorous, transparent, and holistic answer to the question of when it’s appropriate for digital identity to be used. We need a diversity of viewpoints and collaborative dissent to help solve the most pressing issues of our times.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/blog/appropriate-use-of-digital-identity-alliance-announcement'&gt;https://cis-india.org/internet-governance/blog/appropriate-use-of-digital-identity-alliance-announcement&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>amber</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Appropriate Use of Digital ID</dc:subject>
    
    
        <dc:subject>Featured</dc:subject>
    
    
        <dc:subject>Digital Identity</dc:subject>
    
    
        <dc:subject>Homepage</dc:subject>
    

   <dc:date>2019-05-13T09:06:23Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>


    <item rdf:about="https://cis-india.org/internet-governance/information-security-practices-of-aadhaar-or-lack-thereof-a-documentation-of-public-availability-of-aadhaar-numbers-with-sensitive-personal-financial-information-1">
    <title>(Updated) Information Security Practices of Aadhaar (or lack thereof): A documentation of public availability of Aadhaar Numbers with sensitive personal financial information</title>
    <link>https://cis-india.org/internet-governance/information-security-practices-of-aadhaar-or-lack-thereof-a-documentation-of-public-availability-of-aadhaar-numbers-with-sensitive-personal-financial-information-1</link>
    <description>
        &lt;b&gt;Since its inception in 2009, the Aadhaar project has been shrouded in controversy due to various questions raised about privacy, technological issues, welfare exclusion, and security concerns. In this study, we document numerous instances of publicly available Aadhaar Numbers along with other personally identifiable information (PII) of individuals on government websites. This report highlights four government projects run by various government departments that have made sensitive personal financial information and Aadhaar numbers public on the project websites.
&lt;/b&gt;
        
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h4&gt;Read the updated report: &lt;a class="external-link" href="https://cis-india.org/internet-governance/information-security-practices-of-aadhaar-or-lack-thereof/" target="_blank"&gt;Download&lt;/a&gt; (pdf)&lt;/h4&gt;
&lt;h4&gt;Read the first statement of clarification (May 16, 2017): &lt;a class="external-link" href="https://cis-india.org/internet-governance/clarification-on-information-security-practices-of-the-aadhaar-report/" target="_blank"&gt;Download&lt;/a&gt; (pdf)&lt;/h4&gt;
&lt;h4&gt;Read the second statement of clarification (November 05, 2018): &lt;a class="external-link" href="https://cis-india.org/internet-governance/blog/clarification-on-the-information-security-practices-of-aadhaar-report" target="_blank"&gt;Link to page&lt;/a&gt; (html)&lt;/h4&gt;
&lt;hr /&gt;
&lt;p&gt;&lt;em&gt;We are grateful to Yesha Paul and VG Shreeram for research support.&lt;/em&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;In the last month, there have been various reports pointing out instances of the public disclosure of Aadhaar number through various databases, accessible easily on Twitter under the hashtag #AadhaarLeaks. Most of these public disclosures reported contain personally identifiable information of beneficiaries or subjects of the non UIDAI databases containing Aadhaar numbers of individuals along with other personal identifiers. All of these public disclosures are symptomatic of a significant and potentially irreversible privacy harm, however we wanted to point out another large fallout of such events, those that create a ripe opportunity for financial fraud. For this purpose, we identified benefits disbursement schemes which would require its databases to store financial information about its subjects. During our research, we encountered numerous instances of publicly available Aadhaar Numbers along with other PII of individuals on government websites. In this paper, we highlight four government projects run by various government departments with publicly available financial data and Aadhaar numbers. Our research is focussed largely on the data published by or pertaining to where Aadhaar data is linked with banking information. We chose major government programmes using Aadhaar for payments and banking transactions. We found sensitive and personal data and information very easily accessible on these portals.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;

        &lt;p&gt;
        For more details visit &lt;a href='https://cis-india.org/internet-governance/information-security-practices-of-aadhaar-or-lack-thereof-a-documentation-of-public-availability-of-aadhaar-numbers-with-sensitive-personal-financial-information-1'&gt;https://cis-india.org/internet-governance/information-security-practices-of-aadhaar-or-lack-thereof-a-documentation-of-public-availability-of-aadhaar-numbers-with-sensitive-personal-financial-information-1&lt;/a&gt;
        &lt;/p&gt;
    </description>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Amber Sinha and Srinivas Kodali</dc:creator>
    <dc:rights></dc:rights>

    
        <dc:subject>Digital ID</dc:subject>
    
    
        <dc:subject>Privacy</dc:subject>
    
    
        <dc:subject>NDSAP</dc:subject>
    
    
        <dc:subject>Data Protection</dc:subject>
    
    
        <dc:subject>Accountability</dc:subject>
    
    
        <dc:subject>Featured</dc:subject>
    
    
        <dc:subject>Data Governance</dc:subject>
    
    
        <dc:subject>Aadhaar</dc:subject>
    
    
        <dc:subject>Digitisation</dc:subject>
    
    
        <dc:subject>Homepage</dc:subject>
    
    
        <dc:subject>Internet Governance</dc:subject>
    
    
        <dc:subject>Data Management</dc:subject>
    

   <dc:date>2019-03-13T00:29:01Z</dc:date>
   <dc:type>Blog Entry</dc:type>
   </item>




</rdf:RDF>
