Difference between revisions of "CoronaRiskScoring (Q4684)"
Jump to navigation
Jump to search
(Created claim: interested in (P11): Apturi Covid (Q4673)) |
(Created claim: interested in (P11): Immuni (Q4489)) |
||
(8 intermediate revisions by the same user not shown) | |||
Property / interested in | |||
+ | |||
Property / interested in: Immuni / rank | |||
+ | Normal rank | ||
Property / prospect | |||
+ | |||
Property / prospect: Exodus Privacy / rank | |||
+ | Normal rank | ||
Property / prospect: Exodus Privacy / qualifier | |||
+ | comment: issues in the Android app ecosystem | ||
Property / prospect | |||
+ | |||
Property / prospect: VirusTotal / rank | |||
+ | Normal rank | ||
Property / prospect: VirusTotal / qualifier | |||
+ | comment: APK file analysis | ||
Property / prospect | |||
+ | |||
Property / prospect: EIT Digital / rank | |||
+ | Normal rank | ||
Property / prospect: EIT Digital / qualifier | |||
+ |
Latest revision as of 07:42, 4 June 2020
project documenting and explaining risk scoring algorithms in contact tracing apps
Language | Label | Description | Also known as |
---|---|---|---|
English |
CoronaRiskScoring
|
project documenting and explaining risk scoring algorithms in contact tracing apps
|
Statements
0 references
0 references
Amnesty International's Security Lab has been conducting technical analysis of many of these apps to unearth potential privacy and security issues, and better understand what collection of data are users required to concede.
0 references
while AppCensus can't really help with risk scoring directly, they can help with auditing the functioning: input data as well as what gets exfiltrated, both through the app and through Bluetooth
0 references
0 references