9.6.18


Interred in the Internet of Everything
The security implications of devices connecting and sharing data
I received a request from a student for commentary relevant to his final project on ‘Botnets and the Internet of Everything’, asking what risks botnets pose for the devices (cars, watches, TVs) it includes, in terms of payload and ability to spread.
He quoted an estimate that in 2020 there will be around 50 billion devices forming part of the Internet of Everything (IoE), and another estimate that right now, 75% of IoE devices do not conform to good security practices. How well are these figures likely to reflect the situation in 2020, and what is the impact of IoE botnets likely to be?
These are interesting questions. In fact, even as I was putting the last touches to this article, an article on the Talos blog made it very clear that the risk from IoT malware is far from hypothetical. Talos estimates that at least 500,000 networking devices in at least 54 countries have been compromised.
I may return to IoT- and IoE-related issues in a longer article in due course, but in the meantime, here is a slightly expanded version of my response.
Superset, Supernet
We hear a lot about the Internet of Things (IoT), but not so much about the Internet of Everything, which might be described (and indeed often is) as a superset of the IoT. My understanding that it consists not only of the interconnected devices that make up the IoT, but also includes the people who benefit (or hope to benefit) from that interconnection, the data that are shared across those connections, and the processes by which information derived from those data are delivered to where they should be. Well, that’s the theory.
Like everyone else in the security industry, I’m concerned about the implications of (non-)security in devices that are included in both these categories. Indeed, I have been for a long time.
The bioinformatic imperative
In the 1980s through to the early 2000s I worked in bioinformatics, though on the side of system support and security rather than being directly concerned with the manipulation of biological data. Although the term IoT wasn’t heard much (if at all) then (and the term IoE even less), it was already hardly possible to work effectively in bioinformatics without being aware of the risks of compromise posed to (or by way of) medical devices. (The risks incurred by reliance on more obvious resources such as servers and network devices were already reasonably well understood, if not always adequately addressed, then or now.)
The first time I remember hearing about what would later be known as the Internet of Things was probably a reference to the by-then-legendary ‘Internet Coke Machine‘ of 1982, but I don’t remember fretting about its security implications. After all, the status of a vending machine in Pittsburgh had little impact on a medical research facility over 3,700 miles away in London.
However, computing and my own career have both undergone many changes since I first sat at a computer keyboard in 1986, or even in the 1990s, when my job title first changed to include the word ‘security’, and nowadays I suppose I see security issues everywhere. (If only I saw as many decisive solutions to security issues!)
My current concerns basically arise from the expansion of the IoT attack surface through (1) the addition of internet connectivity to objects that don’t necessarily need to be connected (2) the fact that such connectivity has been implemented by groups with little understanding or experience of internet security and privacy (3) the ‘rush to market’ and competitive pricing pressures that put the technical and psychosocial aspects of security so far into the shade as to be effectively invisible. Consider, for instance, the ill-considered addition of connectivity to so many toys and games.
Ifs and bots
I’m less concerned (right now, at any rate) with the specific risk from botnets, though that doesn’t mean there is no risk. We’ve already seen it encapsulated in the use of the Mirai and BASHLITE botnets to implement DDoS attacks. In principle, DDoS is very ‘suitable’ for an IoT botnet because it tends not to demand much in the way of operational functionality from the recruited device. On the other hand, the more features a device’s underlying operating system has – especially if the OS is fully implemented (e.g. Linux, Android) – the wider the range of attacks that might be possible using a network of compromised devices.
There are mitigating factors: some devices implement only the smallest necessary subset of functions; some are regularly patched (or at least patches are made available); some have a proprietary operating system that is less likely to attract the attention of the hacking fraternity, except maybe those black hats who are very specialized – not that I’m advocating that anyone rely on security through obscurity. What’s more, while Windows is less of a monoculture than is often assumed, out in the world of ‘smart’ devices and connected-but-not-all-that-smart devices, monoculture may be even less of an aid to the bad guys. There may be a wide range of devices doing much the same job, and they certainly won’t all be running Windows®. But then, the ancient myth that security flaws are the exclusive property of Microsoft operating systems and applications is no truer in the IoT context than it is elsewhere. Talos reports that the family of malware that ESET detects as Linux/VPNFilter.* is affecting network devices from “…Linksys, MikroTik, NETGEAR and TP-Link” as well as “QNAP network-attached storage (NAS) devices.”
Data versus devices
Here’s a slightly edited excerpt from my article in ESET’s 2018 Trends Report. There may well be other useful commentary in there, of course, if you’re looking for similar content and opinions.
Looking at attacks on smartphones and other mobile devices, these tend to be less focused on data and more on denying the use of the device and the services it facilitates. Which is quite bad enough where the alternative to paying the ransom may be to lose settings and other data, especially as more people have come to use mobile devices in preference to personal computers and even laptops, so that a wider range of data might be threatened.
As the Internet of Unnecessarily Networked Things becomes less avoidable, the attack surface increases, with networked devices and sensors embedded into unexpected items and contexts: from routers to fridges to smart meters, from TVs to toys, from power stations to pacemakers to petrol stations. As everything gets ‘smarter’, the number of services that might be disrupted by malware (whether or not a ransom is demanded) becomes greater.
In previous years we’ve discussed the possibilities of what my colleague Stephen Cobb calls the Ransomware of Things. There are fewer in-the-wild examples to date of such threats than you might expect, given the attention they attract. That could easily change, though, especially if more conventional ransomware becomes less effective as a means of making a quick buck. Though I’m not sure that’s going to happen for a while…
On the other hand, there’s not much indication that Internet of Things security is keeping pace with IoT growth. We are already seeing plenty of hacker interest in the monetization of IoT insecurity. It’s not as simple as the media sometimes assume to write and distribute malware that will affect a wide range of IoT devices and beyond, so there’s no cause for panic, but we shouldn’t underestimate the digital underworld’s tenacity and ability to come up with surprising twists.
Dinosaurs in Tomorrow’s World
And here – since I haven’t changed my opinion much in the interim – is a lengthy quote from an article I wrote for ITSecurity UK a couple of years ago.
I don’t know how many people have internet-connected fridges, lighting systems and televisions, but I don’t … It’s not just a matter of my being afflicted with the characteristic paranoia of the old-school security researcher. Well, not entirely. I won’t be connecting anything to my own networks that doesn’t need to be connected to function, and part of that is normal caution. I don’t particularly want to have to worry about whether my doorbell might give away my WiFi password. But the fact is, a smart doorbell or a connected kitchen appliance simply doesn’t meet any need I have right now, so I’m not going to pay extra for that functionality … personally I’m quite happy to live in Today’s World rather than Tomorrow’s. Though sometimes I wouldn’t mind going back to Yesterday’s.
But we dinosaurs do worry about a time … when we don’t have a choice about whether our devices are connected, as may already be starting to happen with TVs, for instance. Will we be able to choose whether we enable that connectivity? And … the number of people currently affected by real-world vulnerabilities may be far smaller than the PR avalanches indicate. But … IoT ‘represents an ever-widening attack surface.’ And if you’re one of a relatively small segment of the population affected by a vulnerability in a medical device, for example, you may not be reassured by the fact that it won’t affect most people. And as my colleague Pablo Ramos has pointed out, IoT is an issue that is likely to extend beyond the home and into the workplace. But maybe not immediately.
However, Nick FitzGerald, my colleague at ESET, points out that 5G is being developed and positioned in such a way that it’s not going to be possible indefinitely to avoid 5G “connected” devices. He believes that persistent 5G will be embedded into nearly everything that runs on or generates electricity, probably with no means of disabling it.
How much should we worry about this? Well, it’s an evolution of how things are at the moment, in a world where tracking by Cookie Monster is the lifeblood of the internet retail industry and social media (in some respects the same thing). Electronic appliance manufacturers will not be reluctant to take advantage of the control and monitoring opportunities offered by mandatory interconnectivity, comparable to that already enjoyed by major service providers through software and consumer electronics such as entertainment, communications and productivity devices. In essence, this trend further facilitates the extension of these opportunities from ‘brown goods’ to ‘white goods’ (aids to housekeeping such as dishwashers and refrigerators).
You may not be too concerned about the possibility that your kettle or light-fixtures may compromise your privacy, but consider this. When the internet was a playground for the State and academia, security breaches had comparatively little impact on the rest of the world. As interconnectivity spread to commercial enterprises and trickled down to small businesses and home users, the threat surface increased dramatically. While corporates are likely to have access to some in-house or outsourced security knowledge, this was (and still is) less likely to be the case for SMBs, sole proprietors, and private individuals using home networks. As home users have moved away from old-school home computers (in the sense of desktops and laptops) to handheld devices, we’ve seen more and more reliance on those devices for sensitive transactions. Yet those transactions are by no means always adequately and universally protected by the services and systems that support them. In a 5G world, the attack surface will increase dramatically, and I don’t envisage a correspondingly dramatic rise in standards of security and privacy, or in the general level of customer understanding of the risks.
Right now, it’s still possible (though not always easy) to do your shopping and banking in the real world rather than online. And you still have the option in many cases of avoiding unnecessary or unsafe connectivity. But for how long?
VPNFilter
In view of the current issues with routers vulnerable to the VPNFilter malware, here a few ESET links with information from Stephen Cobb that seems particularly relevant right now.
Stephen Cobb: Router reboot: How to, why to, and what not to do – “The FBI say yes but should you follow this advice? And if you do follow it, do you know how to do so safely?”
Stephen Cobb: VPNFilter update: More bad news for routers 
“New research into VPNFilter finds more devices hit by malware that’s nastier than first thought, making rebooting and remediating of routers more urgent.”
You can find these and many more links about the Internet of (not always necessary) things on an AVIEN page here.

7.6.18


VPNFilter update: More bad news for routers

New research into VPNFilter finds more devices hit by malware that’s nastier than first thought, making rebooting and remediating of routers more urgent.
At the bottom of this article is a revised list of routers believed to be at particular risk from the malicious code known as VPNFilter, according to ongoing research by Cisco’s Talos Intelligence Group. These latest findings underscore the importance of rebooting routers, as described at length in this WeLiveSecurity article.
With 56 additional models and five new vendors impacted, it is increasingly likely that even more will be identified. This reinforces previous advice: you should take action regardless of the make or model of router you are using (unless you have received solid assurances from your ISP or vendor that your specific router is not vulnerable).
What’s going on here?
Hundreds of thousands of routers in more than 50 countries have been compromised by malware dubbed VPNFilter. When placed on a router, this malicious code can spy on traffic passing through the router. The malware can also “brick” the device it runs on, rendering it inoperative.
Like a lot of malware, VPNFilter is modular and can communicate over the internet with a Command and Control (C2) system to download additional modules. Research into VPNFilter’s capabilities is ongoing.
Routers are specialized computing devices that direct traffic between networks, for example, between the network in your office and the global network known as the internet. Routers have three places to store code and information: regular memory, which is “volatile” and loses its contents when it loses power; non-volatile memory that retains its contents even when the power is turned off; and firmware, the contents of which are relatively difficult to change.
Much of VPNFilter’s code resides in volatile memory and is wiped out by a reboot or “cycling the power” (i.e. power it off – wait 30 seconds – then power it on again). That is why the security experts and the FBI recommend rebooting your router.
However, a reboot does not remove code that VPNFilter may have written to non-volatile memory. Clearing non-volatile memory requires a device reset, but you should NOT perform a reset unless you know what you are doing (see the instructions and advice in this related WeLiveSecurity article).
If your router is supplied by your ISP you should contact them for instructions if they have not already alerted you and advised you of the situation.
Other steps to consider are upgrading your router to the latest firmware, changing the default administration password, and disabling remote administration. Instructions to perform these functions can be found on the router maker’s website.
Yes, you probably do have a router
I am sure there will be more articles related to VPNFilter and router security on WeLiveSecurity in the coming days. We already get the sense, based on questions from readers so far, that knowledge of routers and how to secure them varies considerably within the population of router users.
One basic question – do I have a router? – is actually trickier to answer than you might think. Many homes and small offices have a variety of boxes that work together to deliver the internet to their computers, smartphones, tablets, smart TVs, clever thermostats, and so on.
Read the complete article on

30.5.18

UNICEF now using cryptocurrency mining for fundraising



So far in 2018, the NGO has launched two charity campaigns with the aim of raising funds through cryptocurrency mining.
Many cryptocurrencies have been associated with cybercrime, especially Monero, which has led to many people considering them unethical. And the fact that cryptocurrency miners are at the top of the worldwide ranking of threats only worsens their image.
A few months ago we tried to explain why mining scripts were being detected as “potentially unwanted applications”, since these scripts are not malicious by themselves, but when used without the required permission and in an unethical way they can be troublesome for users. No tool is good or bad —it all depends on who uses it and what they use it for.
And so this article explores a case in which cryptocurrency mining is being used for a noble act and a good cause. As is the case for UNICEF, which has discovered a pioneering new way of raising funds for its humanitarian causes. This year, the NGO launched two campaigns in which it does not ask for direct money donations, but rather computer resources and processing power for cryptocurrency mining.
The first campaign was launched in February, 2018 under the “Game Chaingers” program, and ran until March 31. It was an initiative of UNICEF France, and its aim was to raise funds for children in Syria who are severely affected by the humanitarian crisis and the war. This campaign ended on March 31.
The second campaign is currently active, and was launched by UNICEF Australia on April 29. A site called “TheHopePage” was created for this campaign, with the aim of raising funds for the approximately 340,000 Burmese children who are currently refugees in Bangladesh due to the violent crisis unleashed in their home country.
Each of these charity campaigns promoted by different UNICEF offices were explored in detail by the ESET Latin America Laboratory, with the aim of making users more aware of this matter by providing relevant information. Because behind the pioneering new concepts like these, malicious campaigns always crop up that take advantage of the novelty to deceive users.
Game Chaingers: UNICEF France Campaign to Mine Ethereum and Help Syrian Children
The name “Game Chaingers” was strategically chosen to include the word “chain”, which is a reference to the blockchain technology that supports cryptocurrencies like Ethereum (the one used in this program). This campaign can be viewed on the site chaingers.io, and is aimed at eSports players, gamers, designers, and other users who have powerful computers with high-performance graphics cards, since the Ethereum mining process requires a lot of processing power.
The process of mining Ethereum for the benefit of UNICEF is really simple, since the mining client (or miner) can be downloaded with UNICEF’s wallet data preconfigured and based on your graphics card model and operating system. Once the miner is downloaded, all you have to do is run it via a shortcut to start mining.

However, taking this past campaign as an example, there are some issues to be considered before you start donating your resources. The first is the electrical consumption that this generates. According to the UNICEF website, a computer with a standard graphics card mining Ethereum consumes around 0.16 kWh, which is similar to the consumption used when playing a high-quality video game. This consumption should not be a problem if you only plan to donate a couple of hours a day, but it is definitely something that must be calculated if you plan to leave the miner running 24 hours a day.
It is also a known fact that intensively using and overloading processors can eventually damage a computer or cause some of its circuits to burn out. For this reason, you should always consider the processing percentage and power that will be used for mining.
And while UNICEF has clarified that the amount of resources assigned can be configured to avoid overloads, the fact remains that, by default, the miner is configured to use 100% of the processing power.

Miner start-up script
This last image shows the values configured in the miner at 100%. The parameters GPU_MAX_ALLOC_PERCENT and GPU_SINGLE_ALLOC_PERCENT indicate the processing percentage of the graphics card to be used, while GPU_MAX_HEAP_SIZE indicates the amount of memory. And while these values can be edited within the script, changing them could be cumbersome for some users who want to just run the file without taking such precautions.
TheHopePage: UNICEF Australia’s Campaign to Mine Monero and Help Refugee Children in Bangladesh
This is the current campaign launched by UNICEF Australia, which aims to raise funds for Burmese children who are refugees in Bangladesh as a result of the crisis. This campaign is aimed at all users, since it uses Monero mining scripts through a browser.
To collaborate in this initiative, simply visit the site TheHopePage.org and click on the “Start Donating” button.
Read the complete article at:

26.5.18

Facebook refines 2FA setup, adds authenticator app support




Do try this at home! If you haven’t taken advantage of the extra protection that two-factor authentication offers, now is a great time to do so. And you don’t even need to hand over your phone number.
Facebook has eliminated the need for users to register a phone number in order to set up two-factor authentication (2FA) in a move intended to get more users to add in another layer of security, according to a press release by Facebook’s product manager Scott Dickens.
To authenticate logins, the social network now enables users to employ a third-party app such as Google Authenticator or Duo Security on both desktop and mobile. The company has also revamped its 2FA feature with a “streamlined setup flow that guides you through the process”.
“Two-factor authentication is an industry best practice for providing additional account security and we just made it easier to set up,” wrote Dickens.
Text messages are the most common second factor although, due to the vulnerability of text messages to a number of threats, security professionals have been advising against using SMS for verification for a long time. Facebook has been offering SMS-based 2FA for a while now and will continue to do so, but using other means such as a hardware device or an authenticator app is generally viewed as safer.
There is no word on how many Facebook users actually use 2FA. On Google accounts, for example, the data are rather grim, as fewer than one in ten Google account holders utilize 2FA.
What to do?
To enable two-factor authentication on your Facebook profile, navigate to “Settings”, then to “Security and Login”, and then to the “Use two-factor authentication” section, where you can choose and set up your 2FA method of choice. While you’re at it, you may also want to peruse your other privacy and security settings.
Many online services, including the biggest players, nowadays offer at least one of the 2FA methods. The availability of 2FA on various online services can be checked on this site.
While not a cure-all, the extra authentication factor offers a valuable additional layer of protection in exchange for very little effort. It is safe to say that 2FA would have prevented countless account break-ins over the years had the legitimate account holders turned it on.
That said, it should not detract from the importance of having a strong and unique password or, even better, passphrase.

25.5.18


Google déploie des domaines .app avec HTTPS intégré

Google a déployé .app, un nouveau domaine de premier niveau (ou TLD, pour top-level domain) qui est le premier à exiger des connexions HTTPS cryptées pour tous les sites Web.app, selon une annonce faite par Ben Fried, directeur des systèmes d’information (DSI) de l’entreprise. Le 1er mai dernier, la société a ouvert des domaines .app
Google a déployé .app, un nouveau domaine de premier niveau (ou TLD, pour top-level domain) qui est le premier à exiger des connexions HTTPS cryptées pour tous les sites Web.app, selon une annonce faite par Ben Fried, directeur des systèmes d’information (DSI) de l’entreprise.
Le 1er mai dernier, la société a ouvert des domaines .app pour l’enregistrement dans le cadre du Programme d’accès hâtif (Early Access Program) sur Google Registry. Les domaines seront accessibles au grand public par l’intermédiaire d’autres bureaux d’enregistrement à partir du 8 mai.
« L’un des principaux avantages du domaine .app est que la sécurité est intégrée pour vous et vos utilisateurs. La grande différence est que HTTPS est nécessaire pour se connecter à tous les sites Web .app, ce qui contribue à la protection contre les logiciels malveillants et l’injection de suivi par les FAI, en plus de la protection contre l’espionnage sur les réseaux WiFi ouverts », peut-on lire dans le communiqué de presse.
Le domaine s’adresse en particulier aux développeurs d’applications. Néanmoins, Domain Name Wire cite un représentant de Google, qui déclarait en mars que ce domaine ne leur était pas réservé exclusivement. Certains des premiers adoptants des domaines .app sont présentés sur get.app.
 « Même si vous passez vos journées de travail dans le monde des applications mobiles, vous pouvez toujours bénéficier d’un repère sur le Web. Avec un nom de domaine .app mémorable, il est facile pour les gens de trouver et d’en savoir plus sur votre application. Vous pouvez utiliser votre nouveau domaine comme page d’atterrissage pour partager des liens de téléchargement fiables, tenir les utilisateurs à jour et des liens profonds vers le contenu de l’application », selon l’annonce.
Google, qui a déboursé 25 millions de dollars pour .app en 2015, contrôle un total de 45 TLD, y compris .comment, .papa, .eat, .soya ou .google. Selon l’autorité mondiale en matière de noms de domaine ICANN, l’Internet comptait 1543 TLD au 4 mai.
Le changement participe à la vision HTTPS de Google : partout dans le monde pour l’Internet. En février, par exemple, la société a annoncé que Chrome 68, prévu pour juillet de cette année, marquera tous les sites Web HTTP comme étant « non sécurisés ».
Petite note en terminant : le HTTPS (ou Hypertext Transfer Protocol Secure) chiffre le trafic Web, en s’assurant que les données soumises sont à l’abri des regards indiscrets pendant la transmission. Il est donc important, lorsque nous soumettons des données sensibles sur un site Web, de vérifier la présence de HTTPS dans la barre d’adresse du navigateur. Cependant, la présence du protocole à elle seule ne garantit pas automatiquement la sécurité contre un certain nombre d’autres menaces. Même un site qui affiche le HTTPS peut être malveillant : les sites d’hameçonnage, par exemple, ont de plus en plus adopté HTTPS.

GDPR: One rule to rule them all – legally


It’s here but what are the legal ramifications of the new legislation for businesses
There is a certain similarity between J. R. R. Tolkien’s The Lord of the Rings trilogy and General Data Protection Regulation (GDPR) coming to force tomorrow, May 25 2018. As weird as it may sound, the regulation puts in place standards identical to those of the One Ring – GDPR is here to rule the world of data protection the same way the One Ring ruled the others.
In real life, this could be directly linked to unifying the different levels of the data protection legislation in each of the European Union (EU) countries. Except in this case, the One Ring is replaced by the single set of data protection rules across the EU. Thus, the regulation aims to protect any information that relates to “an identified or identifiable person” – addressing the export of personal data outside of Europe as well.
WeLiveSecurity spoke with Tomáš Mičo, ESET Data Protection Officer, to clarify the essentials the regulation brings to businesses. “In Slovakia, where the cybersecurity firm ESET is based, we’ve already had, by law the possibility to appoint a Data Protection Officer, so applying GDPR for businesses inside countries with similar requirements of legislation shouldn’t have any significant impediments,” he says.
According to Mičo, businesses have already invested significant time and energy into mapping all the processes and reviewing all the agreements as recommended by data protection professionals. “Moreover, as GDPR has so-called ‘downstream’ effect, businesses need to apply the same principles to all their arrangements including those with third-party processors and sub-contractors,” explains Mičo.
The main purpose of the new regulation is to minimize the unnecessary collection of personal data, including steps that prevent storing data that does not need to be stored, and securing the entire journey of the personal data in the company. However, the biggest challenges for businesses lie with the requirements for Privacy by Design, Privacy by Default, Right to Erasure, Right to be Forgotten and Breach Notification.
The computer security companies around the globe are rightfully using this opportunity, offering solutions to mitigate the main risks connected to the regulation – selling encryption, two-factor authentication and other solutions to close any possible path for cybercriminals to get to the personal data that must be protected under GDPR.
That’s not all. Although businesses are successfully deploying cybersecurity solutions to make sure personal data are properly processed and protected inside your company, there are other legal responsibilities that must be completed. One of them is to offer an easy-to-understand explanation of data processing, so customers are transparently informed about their rights resulting from this new regulation.
“Businesses have to make sure they have consent, contract or other legal basis for processing all of the personal data protected by the regulation, for all their end users. For a middle size business, it can as well mean spending countless hours retroactively contacting all of them if their legal basis is not GDPR valid – including end users that businesses gained through third parties or sub-contractors,” adds Mičo.
In addition, individuals have as well the right to request a detailed listing of all their personal data that is being processed, and request it from any vendor that works with the personal data of EU located customers, even if the company is not physically located in the EU. This is especially hard for all the e-commerce businesses and businesses that work with cloud services. And that is the reason why the majority of newsletters in last couple of weeks start with We have updated our privacy policy.
Moreover, businesses must have the information about the individual available at any time and keep it protected – encrypted – to be GDPR compliant. “This way the personal data, even when the company suffers a breach or is hacked, stay protected,” says Mičo. Perharps the greatest onus in the Breach Notification requirement, which forces businesses to have processes in place that will ensure the information about the data breach will make it to the appropriate data protection authority within 72 hour after it was discovered.
If nothing else, penalties for non-compliance are quite a bite to swallow – looking at 2% to 4% of the company’s global annual turnover, which is an expense no company can afford to take lightly. A recent survey by IDC, however, reveals that for noncompliance, “regulators are more likely to focus on progress toward the goal than penalizing those not quite finished with GDPR conformity”.
In time, we’ll see if the famous one rule to rule them all will find them all and and bind them as the legislators have predicted, or if everyone will meet in an unfulfilled GDPR Land of Mordor.
For more information on GDPR, ESET has a dedicated page to help ensure that you have all the information needed to cope with GDPR. To read more articles like this one, please follow WeLiveSecurity.

23.5.18

Amazon Rekognition a possible threat to the civil rights of citizens




Use of software by law enforcement as a surveillance tool is a real concern for groups
Amazon has come under fire from civil rights groups in the US that say their online service that identifies faces in images could be abused by law enforcement.
The American Civil Liberties Union (ACLU) released a statement on Tuesday asking the tech giant to refrain from selling Amazon Rekognition to law enforcement agencies as they fear it will be used to unfairly target protesters along with individuals that the police view as suspicious.
The ACLU is leading a group of more than two dozen other civil rights organizations that are worried that the product will be used by law enforcement as a surveillance tool.
This claim was reinforced on Tuesday when the ACLU released a collection of public records that detailed how Amazon has been selling the software to those law enforcement agencies.
The statement released on the ACLU website stressed how the software threatens the freedom of citizens to go about their daily lives, “People should be free to walk down the street without being watched by the government”.
“By automating mass surveillance, facial recognition systems like Rekognition threaten this freedom, posing a particular threat to communities already unjustly targeted in the current political climate. Once powerful surveillance systems like these are built and deployed, the harm will be extremely difficult to undo”.

In a letter addressed to Jeff Bezos, Amazon’s chief executive, the group outlined its fears about the misuse of the software and also their concern that “Amazon Rekognition is primed for abuse in the hands of governments”.
They also implored the company to move fast, stating, “Amazon must act swiftly to stand up for civil rights and civil liberties, including those of its own”.
Police in Orlando, Florida and in Oregon’s Washington County are currently using Rekognition.
A report by the The Washington Post has stated that the Washington County Sheriff department pays something in the range of $6 and $12 a month for the service.
Amazon spokeswoman Nina Lindsey did not directly address the concerns outlined by the civil rights groups stating that Amazon would require all customers to “comply with the law and be responsible when they use AWS services.”
She also said that the software could be used for many positive purposes, including finding abducted people and could also help locate children that become separated from their parents in crowded areas.
The product was introduced by Amazon as part of Amazon Web Services in late 2016 and claimed it “can process millions of photos per day”.
This concern by citizens over the use of Artificial Intelligence (AI) as a surveillance tool by government agencies was also highlighted recently when it was reported that thousands of Google employees signed an internal petition requesting that the company end its controversial contract with the Pentagon. A partnership with the US Department of Defense, named Project Maven, that promised to speed up the analysis of drone footage by assessing images for photos or objects.
Google were quick to downplay any fears of misuse, “the technology flags images for human review, and is for non-offensive uses only,” a Google spokeswoman said. “Military use of machine learning naturally raises valid concerns. We’re actively discussing this important topic internally and with others as we continue to develop policies and safeguards around the development and use of our machine learning technologies.”
https://www.welivesecurity.com/2018/05/23/amazon-rekognition-threat-civil-rights/?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+eset%2Fblog+%28ESET+Blog%3A+We+Live+Security%29