Connect with us

Security

Why is my keyboard connected to the cloud?

Published

on


(Image: Getty Images/iStockphoto)

Everything is becoming a thing connected to the internet, but some things really shouldn’t be.

First cab off that rank should be input devices, because what sort of maniac thinks the advantages of a roaming cloud-based configuration outweighs the potential explosion in surface area to attack and compromise? That maniac is called Razer, and it has been connecting keyboards to its Synapse software for years.

At last week’s CES, Razer took it a step further when it announced it is adding support for users to use Alexa to control their peripherals.

“Alexa, ask Chroma to change my lighting profile to FPS mode,” Razer cheerily proclaims as an example of its upcoming functionality.

More from CES: CES 2019 Las Vegas (CNET) | CES 2019: A first look at the cool tech (TechRepublic)

For this to work, the software that usually controls keyboard and mice settings needs to be connected to Amazon Alexa.

It’s a 2-for-1 cloud connection, because once you embrace the idea of Razer’s servers being secure, then you’ve already accepted a more risky proposition than using just Amazon.

Last month, Razer faced blowback when it launched a cryptocurrency mining application called Cortex, where users would be rewarded with its Silver funny money.

“The new app to put[s] snoozing machines to work, solving blockchain puzzles in the background in exchange for sweet, sweet Silver,” Razer said at the time.

Enter Tavis Ormandy, security researcher for Google Project Zero and scourge of buggy software makers, who took a look at the software and was stunned.

“Holy moly, I just installed this. WHY IS CEF (chromium embedded) REMOTE DEBUGGING ENABLED AND LISTENING BY DEFAULT (!?!?!?!),” Ormandy tweeted.

“I don’t have any razer hardware to test, but they probably (like, *right now*) need to fix that.”

To Razer’s credit, the company fixed the issue within 24 hours; on the other hand, it allowed remote command execution in the first place.

Also in Razer’s favour is that it acknowledged it was responsible, which is more than can be said for Gigabyte.

On December 18, SecureAuth detailed an exchange of when it discovered that software utilities for Gigabyte and Aorus motherboards had privilege escalation vulnerabilities.

“There is ring0 memcpy-like functionality … allowing a local attacker to take complete control of the affected system,” SecureAuth said.

In trying to resolve what was clearly a serious issue, the security company could not locate a proper contact within Gigabyte, and headed over to its technical support team.

“Gigabyte is a hardware company and they are not specialized in software,” Gigabyte told SecureAuth on two different occasions in May.

In the end, SecureAuth said Gigabyte eventually responded by saying its products did not have any issues.

If a vendor with the experience and sales of Gigabyte responds by denying responsibility for its software, it doesn’t bode well for smaller players.

Gigabyte should stop distributing software as long as it keeps on throwing out the excuse that it is a hardware company.

And it is no small matter, because the utilities that the Taiwanese manufacturer puts out are built to manipulate hardware settings, and flash BIOSes.

If a bad actor was looking for a shortcut into a modern Windows system, trying to find your way in via Microsoft’s code will be time wasting when the camembert-like underbelly of a modern system is likely to be crap software from peripheral makers.

That tactic is not new, but with connectivity exploding, things are likely to get worse before it gets better, as with most things in the cyber realm.

ZDNET’S MONDAY MORNING OPENER:

The Monday Morning Opener is our opening salvo for the week in tech. Since we run a global site, this editorial publishes on Monday at 8:00am AEST in Sydney, Australia, which is 6:00pm Eastern Time on Sunday in the US. It is written by a member of ZDNet’s global editorial board, which is comprised of our lead editors across Asia, Australia, Europe, and North America.

PREVIOUSLY ON MONDAY MORNING OPENER:



Source link

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Security

Managing Vulnerabilities in a Cloud Native World

Published

on

This free 1-hour webinar from GigaOm Research brings together experts in Cloud Native Vulnerability Management, featuring analyst Iben Rodriguez and special guest from Palo Alto Networks, John Morello. The discussion will focus on optimizing cloud security posture and integration with enterprise tool sets.

We will review platforms delivering Security Posture Management and Workload Protection for Microservice based and Hybrid Cloud Workloads.

Registrants will learn how new customers can benefit from Prisma Cloud to better secure their complex multi-cloud environments. Existing customers will learn about new features they can take advantage of and how to optimize their limited resources.

Register now to join GigaOm and Palo Alto Networks for this free expert webinar.

The post Managing Vulnerabilities in a Cloud Native World appeared first on Gigaom.

Continue Reading

Security

Security Tools Help Bring Dev and Security Teams Together

Published

on

Software development teams are increasingly focused on identifying and mitigating any issues as quickly and completely as possible. This relates not only to software quality but also software security. Different organizations are at different levels when it comes to having their development teams and security teams working in concert, but the simple fact remains that there are far more developers out there than security engineers.

Those factors are leading organizations to consider security tooling and automation to proactively discover and resolve any software security issues throughout the development process. In the recent report, “GigaOm Radar for Developer Security Tools,” Shea Stewart examines a roundup of security tools aimed at software development teams.

Stewart identified three critical criteria to bear in mind when evaluating developer security tools. These include:

  • Vendors providing tools to improve application security can and should also enhance an organization’s overall security posture.
  • The prevailing “shift-left” mindset doesn’t necessarily mean the responsibility for reducing risk should shift to development, but instead focusing on security earlier in the process and continuing to do so throughout the development process will reduce risk and the need for extensive rework.
  • Security throughout the entire software development lifecycle (SDLC) is critical for any organization focused on reducing risk.

Figure 1. How Cybersecurity Applies Across Each Stage of the Software Development Lifecycle *Note: This report focuses only on the Developer Security Tooling area

Individual vendors have made varying levels of progress and innovation toward enhancing developer security. Following several acquisitions, Red Hat, Palo Alto Networks, and Rapid7 have all added tooling for developer security to their platforms. Stewart sees a couple of the smaller vendors like JFrog and Sonatype as continuing to innovate to remain ahead of the market.

Vendors delving into this category and moving deeper into “DevSecOps” all seem to be taking different approaches to their enhanced security tooling. While they are involving security in every aspect of the development process, some tend to be moving more quickly to match the pace of the SDLC. Others are trying to shore up existing platforms by adding functionality through acquisition. Both infrastructure and software developers are now sharing toolsets and processes, so these development security tools must account for the requirements of both groups.

While none of the 12 vendors evaluated in this report can provide comprehensive security throughout the entire SDLC, they all have their particular strengths and areas of focus. It is therefore incumbent upon the organization to fully and accurately assess its SDLC, involve the development and security teams, and match the unique requirements with the functionality provided by these tools. Even if it involves using more than one at different points throughout the process, focus on striking a balance between stringent security and simplifying the development process.

Read more: Key Criteria for Evaluating Developer Security Tools, and the Gigaom Radar for Developer Security Tool Companies.

The post Security Tools Help Bring Dev and Security Teams Together appeared first on Gigaom.

Continue Reading

Security

Key Criteria for Evaluating User and Entity Behavior Analytics (UEBA)

Published

on

Cybersecurity is a multidisciplinary practice that not only grows in complexity annually but evolves nearly as quickly. A survey of the security landscape today would reveal concerns ranging from the classic compromised servers to the relatively new DevSecOps practices aimed at securing the rapid deployment of new code and infrastructure. However, some things remain constant no matter how much change is introduced. While technology evolves and complexity varies, there is almost always a human component in
risks presented to an organization.

User Behavior Analysis (UBA) was designed to analyze the actions of users in an organization and attempt to identify normal and abnormal behaviors. From this analysis, malicious or risky behaviors can be detected. UBA solutions identify events that are not detectable using other methods because, unlike classic security tools (an IDS or SIEM for example), UBA does not simply pattern match or apply rule sets to data to identify security events. Instead, it looks for any and all deviations from baseline user activity.

As technology advanced and evolved, and the scope of what is connected to the network grew, the need to analyze entities other than users emerged. In response, entity analysis has been added to UBA to create UEBA or User and Entity Behavior Analysis. The strategy remains the same, but the scope of analysis has expanded to include entities involving things like daemons, processes, infrastructure, and so on.

How to Read this Report

This GigaOm report is one of a series of documents that helps IT organizations assess competing solutions in the context of well-defined features and criteria. For a fuller understanding consider reviewing the following reports:

Key Criteria report: A detailed market sector analysis that assesses the impact that key product features and criteria have on top-line solution characteristics—such as scalability, performance, and TCO—that drive purchase decisions.

GigaOm Radar report: A forward-looking analysis that plots the relative value and progression of vendor solutions along multiple axes based on strategy and execution. The Radar report includes a breakdown of each vendor’s offering in the sector.

Solution Profile: An in-depth vendor analysis that builds on the framework developed in the Key Criteria and Radar reports to assess a company’s engagement within a technology sector. This analysis includes forward-looking guidance around both strategy and product.

The post Key Criteria for Evaluating User and Entity Behavior Analytics (UEBA) appeared first on Gigaom.

Continue Reading

Trending