HomeCorona-Warn-App
Last modified by Michiel Leenaars on 2020/09/30 11:23
- The short name or acronym of the project
-
Corona-Warn-App
- The release version of the software application. If there is no official version number, use 20YY-MM-DD-unstable
-
1.3.1
- Main organisation(s) behind the technology
-
Cispa
Fraunhofer Institut
Healthy Together
Helmholtz
Robert Koch Institut
SAP
Telecom
TÜViT - The web address of the source code of the project
-
https://github.com/corona-warn-app
- Are all components of the project publicly available under an OSI Approved Licence?
-
No
-
- Pointers to other sources of information, e.g. whitepapers, architectural designs
-
https://www.coronawarn.app/en/
- Official description of the data flow and the overall architecture
-
https://github.com/corona-warn-app/cwa-documentation/blob/master/scoping_document.md
-
Symptom reporting Exposure notification
-
- Upload the logo of the project if available. Non-essential, but pretty.
-
-
General principles
E.g. Bluetooth, Bluetooth Low Energy, Near-Ultrasound, Ultrasound, LIDAR, 802.11x, Zigbee, infrared, visible light, UV. More than one answer is possible. -
Bluetooth Low Energy
- Select the technical protocol(s) supported by the application. If the protocol is not yet inthis list, please save this page, navigate to the protocols list and add before proceeding.
-
Apple-Google TCN DP-3T
- Is the application based on a published technical specification for contact tracing (eg DP3T, BlueTrace, Google-Apple)?
-
No
-
https://www.coronawarn.app/en/#privacy The architecture follows a decentralized approach – based on the DP-3T and TCN protocols, as well as the Privacy-Preserving Contact Tracing specifications by Apple and Google.
- Is there evidence of the (epidemiological) effectivity of the application? Please add any links to information on studies or trial runs that showcase that the technology proposed .
-
-
Legal/licensing information
Are all components of the project publicly available under OSI Approved Licence(s)? If you know which license(s), please use SPDX identifiers. -
https://github.com/corona-warn-app/cwa-app-android/blob/master/LICENSE
https://github.com/corona-warn-app/cwa-app-android/blob/master/THIRD-PARTY-NOTICES
- If not all components used are open source, please provide a technical description of these components suitable for publication, and any third party security analysis. Provide contact details of each technology supplier.
-
- If the project is known to be encumbered by (software) patents or other intellectual property claims by any of its creators or known third parties, please indicate which. Also, feel free to list any defensive publications.
-
-
Platforms, build environment
On which platforms can the application(s) run? -
-
- Location(s) of the app(s) in various app stores (F-Droid, Google Play, Apple Store, Jolla Store, etc).
-
https://play.google.com/store/apps/details?id=de.rki.coronawarnapp (Google Play)
- What external libraries and SDKs does the application depend on?
-
- Which tools (IDE, etc.) are necessary to build the application from the available sources?
-
- Do different builds of the application yield the same bits?
-
-
- Is the user in control when some or all bits of the application are replaced?
-
-
- Is the update mechanism compatible with the requirements of TUF (https://theupdateframework.io/security), including resilience against rollback attacks, extraneous dependencies attacks and handling vulnerability to key compromises?
-
-
Security
-
- If the developers have published or adopted a dedicated threat model for their app, provide a web link.
-
- If there have been in-depth security analyses of the application(s) and/or underlying protocols, provide web links to publicly available reports. One line per report.
-
- If there are known security weaknesses or shortcomings that are currently unresolved, please provide a link to CVE's/bug reports or other available sources.
-
- Is the temporary data stored by the solution protected by modern, strong cryptographic means
-
No
-
- Exposure of interfaces with critical system level security flaws.
-
-
Privacy
General impact assessment
Has a Data Privacy Impact Assessment (DPIA) or equivalent privacy analysis been conducted in relation to the technologies used or proposed by the project? A DPIA is a formal assessment of privacy risks users are to be exposed to. Provide a link to the outcome of this assessment, and any updates or responses or mitigations that have been implemented since in response to the findings of the DPIA. : Provide web addresses of the DPIA and any follow ups. -
- Provide links to other noteworthy articles and reports regarding or mentioning the project.
-
- Are there any special provisions made for protection of the information of minors, or legally incompetent people?
-
-
Mobile app specific questions
Does the solution have complete governance/run-time control over client-side hardware while in deployment, including the OS? Or is there shared tenancy, and are there other applications running? -
-
- Use of the solution does not require the use of an online account which is traceable to individuals. E.g. a vendor account which needs to be activated before a mobile phone can be used.
-
No
-
- Is use of the solution tied in any way to the use of (an) account(s) with any third party, other than national?
-
No
-
- Does the application make use of fixed, traceable, device specific identifiers or accounts, like phone numbers, IMEI, etc?
-
-
- Is the solution free from telemetry/tracking?
-
No
-
- Does the application request/require OS privileges to e.g. recent contacts, the address book, location based services, the camera, etc.?
-
-
- For each of the requested permissions explain how the data or the funcitonality that can be accessed through that permission is used by the application. Specify whether this access is merely local, or whether information obtained through this is shared centrally.
-
- Is there any location data (or equivalent) stored?
-
No
-
- Does the application or device have a built-in kill-switch where it ceases to function after a predetermined point in time, to avoid unnecessary risk exposure?
-
No
-
- Users can choose to expose whether or not they are infected, even under pressure or threat
-
No
-
- Can the user determine when data is uploaded
-
-
Privacy (Bluetooth related)
-
- Is the privacy and the security of the user of the solution safe from compromise related to external observability of device-specific Bluetooth identifiers?
-
No
-
- Is a fixed Wifi MAC address broadcast by the solution?
-
No
-
- Is the Bluetooth ID of the user (or a derivation that can be easily linked back to it) broadcast?
-
No
-
Detailed privacy related attributes
-
- The application only shares anonymous attributes.
-
No
-
- Can the user of the app review and redact their data, or decide to not upload some data?
-
No
-
-
No
-
- Does the application request/require privileges to e.g. recent contacts, the address book or other user-specific data?
-
No
-
- Is the real identity (or a strongly linked attribute) stored outside of the user device?,
-
No
-
- Is the phone number of the user (or a derivation that can be easily linked back to it) stored outside of the user device?
-
No
-
-
No
-
- Is there any location data (or equivalent) stored externally?
-
No
-
- Is the wifi mac addres of the user (or a derivation that can be easily linked back to it) stored outside of the user device?
-
No
-
- Is the Bluetooth ID of the user (or a derivation that can be easily linked back to it) stored outside of the user device?
-
No
-
- The solution is guaranteed to never leak information about IP addresses of users to the backend.
-
No
-
Available third party analysis
-
- Relevant publications on the judicial aspects of the application(s) and protocol(s)
-
- Studies and analyses of the technical aspects of the application
-
-
Customization and usability aspects
Is the application ready to be used with multiple languages (i18n) if translated strings are provided? -
No
-
- Give the web address of any accessiblity certifications by an accreditated certifcation instance. If there are more than one, put each link on a new line.
-
- Has the assistive technology been designed to not expose users with disabilities with additional privacy risks?
-
No
-
Backend
-
- Select where and how the data produced by the solution is hosted
-
- If an external back-end technology is used in conjunction with the application or device, please provide a link to its repository or home page
-
- Any other relevant remarks and considerations
