Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

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.
How Attackers Infiltrate the Supply Chain & What to Do About It
Shay Nahari, Head of Red-Team Services at CyberArk,  7/16/2019
US Mayors Commit to Just Saying No to Ransomware
Robert Lemos, Contributing Writer,  7/16/2019
The Problem with Proprietary Testing: NSS Labs vs. CrowdStrike
Brian Monkman, Executive Director at NetSecOPEN,  7/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12551
PUBLISHED: 2019-07-22
In SweetScape 010 Editor 9.0.1, improper validation of arguments in the internal implementation of the Memcpy function (provided by the scripting engine) allows an attacker to overwrite arbitrary memory, which could lead to code execution.
CVE-2019-12552
PUBLISHED: 2019-07-22
In SweetScape 010 Editor 9.0.1, an integer overflow during the initialization of variables could allow an attacker to cause a denial of service.
CVE-2019-3414
PUBLISHED: 2019-07-22
All versions up to V1.19.20.02 of ZTE OTCP product are impacted by XSS vulnerability. Due to XSS, when an attacker invokes the security management to obtain the resources of the specified operation code owned by a user, the malicious script code could be transmitted in the parameter. If the front en...
CVE-2019-10102
PUBLISHED: 2019-07-22
tcpdump.org tcpdump 4.9.2 is affected by: CWE-126: Buffer Over-read. The impact is: May expose Saved Frame Pointer, Return Address etc. on stack. The component is: line 234: "ND_PRINT((ndo, "%s", buf));", in function named "print_prefix", in "print-hncp.c". Th...
CVE-2019-10102
PUBLISHED: 2019-07-22
aubio 0.4.8 and earlier is affected by: null pointer. The impact is: crash. The component is: filterbank. The attack vector is: pass invalid arguments to new_aubio_filterbank. The fixed version is: after commit eda95c9c22b4f0b466ae94c4708765eaae6e709e.