Vulnerabilities / Threats

2/4/2019
04:30 PM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail
50%
50%

6 Security Tips Before You Put a Digital Assistant to Work

If you absolutely have to have Amazon Alexa or Google Assistant in your home, heed the following advice.
Previous
1 of 7
Next

Image Source: Adobe Stock: bht2000

Image Source: Adobe Stock: bht2000

Experienced security pros like Amy DeMartine simply won't allow a digital assistant into her home.

DeMartine, a principal analyst who serves security and risk professionals for Forrester, says last year's reports of so-called "voice squatting" (aka "skill squatting") – where attackers create malicious Amazon Alexa "skills" that appear to be legitimate applications – has her thinking twice about any of these digital assistants. 

"People have to decide what their risk threshold is and configure Alexa or any other digital assistant accordingly," DeMartine says.

According to Candid Wueest, senior principal threat researcher at Symantec, consumers should start by asking the following questions: Do I really need the device, and, if so, what do I need it for? Do I want the device to have a camera to check in on my dog, or am I OK with no camera? And since I already have several devices in my home, do I want to stick with one brand because it's easier to integrate?

Another $64 million question, and this is the big one: Do I trust the vendor?

"This is not an easy one to answer, but, ultimately, you have to trust that the vendor will safeguard your data," Wueest says. 

So if you absolutely have to have Alexa or Google Assistant in your home, heed the following advice from DeMartine, Wueest and Jessica Ortega, a website security research analyst at SiteLock. And if you're a security pro, be sure to educate your customers, too.  

 

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio

Previous
1 of 7
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
michaelmaloney
50%
50%
michaelmaloney,
User Rank: Apprentice
2/21/2019 | 1:24:26 AM
Too complacent too dangerous
Sometimes consumers are just too complacent about the ready benefits that are being laid out in front of them. Every individual surely knows how to take advantage of each and every single one of them without considering the possible implications underneath. They are willing to forgo any potential risks because somehow the era of IT today has given them the trust they need.
NathanDavidson
50%
50%
NathanDavidson,
User Rank: Apprentice
2/19/2019 | 1:50:29 AM
Beware the Coming of the Robot Age
I would g et an Alexa or AI for the house just to test it out and have a little bit of fun with it. But I'm also a little worried what might happen if I really leave the management of my house up to this little device. It's not so much about the security of it, but about the age of the robots and all that! Haha!
t_madison
50%
50%
t_madison,
User Rank: Apprentice
2/18/2019 | 3:26:51 AM
Good advice
Thanks for the advice, it is very useful.
jgallman
50%
50%
jgallman,
User Rank: Apprentice
2/8/2019 | 9:23:31 AM
Grammar please!
You lose me when the very first sentence is as poorly constructed as this one is.  Her should be their.
New Free Tool Scans for Chrome Extension Safety
Dark Reading Staff 2/21/2019
Making the Case for a Cybersecurity Moon Shot
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  2/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-6485
PUBLISHED: 2019-02-22
Citrix NetScaler Gateway 12.1 before build 50.31, 12.0 before build 60.9, 11.1 before build 60.14, 11.0 before build 72.17, and 10.5 before build 69.5 and Application Delivery Controller (ADC) 12.1 before build 50.31, 12.0 before build 60.9, 11.1 before build 60.14, 11.0 before build 72.17, and 10.5...
CVE-2019-9020
PUBLISHED: 2019-02-22
An issue was discovered in PHP before 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1. Invalid input to the function xmlrpc_decode() can lead to an invalid memory access (heap out of bounds read or read after free). This is related to xml_elem_parse_buf in ext/xmlrpc/libxmlrpc...
CVE-2019-9021
PUBLISHED: 2019-02-22
An issue was discovered in PHP before 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1. A heap-based buffer over-read in PHAR reading functions in the PHAR extension may allow an attacker to read allocated or unallocated memory past the actual data when trying to parse the file...
CVE-2019-9022
PUBLISHED: 2019-02-22
An issue was discovered in PHP 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.2. dns_get_record misparses a DNS response, which can allow a hostile DNS server to cause PHP to misuse memcpy, leading to read operations going past the buffer allocated for DNS data. This affects php_parser...
CVE-2019-9023
PUBLISHED: 2019-02-22
An issue was discovered in PHP before 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1. A number of heap-based buffer over-read instances are present in mbstring regular expression functions when supplied with invalid multibyte data. These occur in ext/mbstring/oniguruma/regcom...