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.

Endpoint Security

// // //
4/12/2019
10:54 AM
Joe Stanganelli
Joe Stanganelli
Joe Stanganelli

IoE: The Internet of Espionage

As employees live their lives across an increasingly IoT-enabled landscape (with devices often installed discreetly and with hidden functionalities), enterprise security is threatened by outside factors it cannot control.

The Internet of Things has been expanding exponentially over the years. Gartner predicts that within the next five years, there will be approximately 1.7 billion new devices per annum attaching to enterprise networks -- and, accordingly, that the number of endpoint devices that CIOs will be expected to manage will triple in that time. This in and of itself introduces enormous complexity to the security and integrity of enterprise IT environments.

IoT devices outside the organization, however, present a hidden yet no less serious threat. At home, while traveling, and on the job offsite, third parties have the capability to use IoT to spy on enterprise employees -- the things they say, the things they do, the things they look at, and even the things they type.

In some cases, this is already happening.

IoT spying at home Over the past several years, headlines have been rife with espionage-enabling vulnerabilities and exploits of smart cameras, smart appliances, smart thermostats, and even smart toys. More recent IoT controversies and snafus, however, have driven the point of the problem home.

On Wednesday, Bloomberg reported that -- instead of relying entirely on cold and distant algorithms when recording and "listening" to users of Alexa (the "smart assistant" embedded in Amazon's smart speaker, the Amazon Echo) -- Amazon "employs thousands" of living, breathing humans to listen to, transcribe, analyze, and annotate what Alexa hears.

To be sure, with machine learning in its infancy, a certain amount of direct human intervention is to be expected when it comes to maintaining and improving voice-activated IoT devices. At the same time, the recordings are hardly unidentifiable. While full names are not directly shared, Bloomberg reports that Alexa-recording reviewers can match specific recordings with the user's first name, account number, and device serial number.

Conversely, Google and Apple claim that recordings of users of their respective smart assistants are stripped of personally identifiable information -- although researchers across various disciplines and contexts have found ways of re-identifying "anonymized" data.

Google still has its own smart-assistant controversies. On February 4, the tech behemoth released an update to its "smart" home-security device, Nest, to enable smart-assistant functionality in pre-existing/pre-installed devices. The problem was that nobody outside of Google previously knew that Nest devices came equipped with a microphone -- a fact that Google conveniently "forgot" to mention.

Meanwhile, the IoT smart-home sector (variously estimated to be a $44-billion to $54-billion industry) represents a potential data-leakage threat even when what passes for full disclosure is present. Localytics, a mobile-engagement firm, calls the smart-home industry the "mother lode for mobile marketers" thanks to voluminous data generated by IoT smart-home devices themselves and additional data generated via apps and mobile devices used to manage and control IoT devices -- giving third parties access to nearly everything done and discussed in a person's sanctuary.

Personal privacy concerns aside, the upshot for the enterprise is that employees working or talking about work at home with Nest or other devices may have no idea who is watching or hearing information related to proprietary work product.

IoT spying on the road
This is a variation of what is known as the "evil maid" threat. The scenario commonly presents as a maid or other worker -- having access to the employee's quarters (whether a home or a hotel room) -- steals sensitive data, often by stealing or compromising an endpoint device. Here, however, the threat is less visible; through IoT devices that users or bystanders may not even be aware of, a hacker, a rogue employee, or even a bad-actor first-party or third-party company is potentially free to leverage any enterprise data that happens to be observed.

Away from home, too, devices are watching, listening, and tracking around the world. Last month, South Korean law enforcement busted a spycam ring that allegedly secretly recorded guests across 30 motels nationwide. More lawfully (but still disturbingly), since 2017, in-flight entertainment systems on airplanes have increasingly included cameras designed to watch passengers in turn, Orwellian style. The airlines have allegedly all but pinky-sworn to never use the cameras, but according to tech professionals, they appear ready to be enabled at any time by airlines and third parties (authorized or not) alike.

"We keep on hearing about all kinds of devices increasingly containing microphones or cameras, [and instances where IoT] devices are not apparent," Katell Thielemann, a Gartner analyst, told Security Now. "The best approach is not to allow any such device in hotel rooms or office environments -- and remove or unplug them if there are -- and to keep sensitive conversations [within] areas that can at least be visually inspected for lack of connected devices."

Related posts:

—Joe Stanganelli is managing director at research and consulting firm Blackwood King LC. In addition to being an attorney and consultant, he has spent several years analyzing and writing about business and technology trends. Follow him on Twitter at @JoeStanganelli.

 

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Improving Enterprise Cybersecurity With XDR
Enterprises are looking at eXtended Detection and Response technologies to improve their abilities to detect, and respond to, threats. While endpoint detection and response is not new to enterprise security, organizations have to improve network visibility, expand data collection and expand threat hunting capabilites if they want their XDR deployments to succeed. This issue of Tech Insights also includes: a market overview for XDR from Omdia, questions to ask before deploying XDR, and an XDR primer.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-28200
PUBLISHED: 2022-07-02
NVIDIA DGX A100 contains a vulnerability in SBIOS in the BiosCfgTool, where a local user with elevated privileges can read and write beyond intended bounds in SMRAM, which may lead to code execution, escalation of privileges, denial of service, and information disclosure. The scope of impact can ext...
CVE-2022-32551
PUBLISHED: 2022-07-02
Zoho ManageEngine ServiceDesk Plus MSP before 10604 allows path traversal (to WEBINF/web.xml from sample/WEB-INF/web.xml or sample/META-INF/web.xml).
CVE-2022-32411
PUBLISHED: 2022-07-01
An issue in the languages config file of HongCMS v3.0 allows attackers to getshell.
CVE-2022-32412
PUBLISHED: 2022-07-01
An issue in the /template/edit component of HongCMS v3.0 allows attackers to getshell.
CVE-2022-34903
PUBLISHED: 2022-07-01
GnuPG through 2.3.6, in unusual situations where an attacker possesses any secret-key information from a victim's keyring and other constraints (e.g., use of GPGME) are met, allows signature forgery via injection into the status line.