The security of IoT networks is a challenge that needs to be addressed at a global scale. This blog will uncover some risks associated with IoT network security.

The state of data streaming in the manufacturing industry explores case studies from BMW, Mercedes, Michelin, and Siemens powered by Apache Kafka.

To get more clarity about ISR in Apache Kafka, we should first carefully examine the replication process in the Kafka broker.

How does a data service company build its data warehouse? Simplicity is the best policy. See how we increased data writing efficiency by 75%.

The art of creating rule-based prompts for ChatGPT is accelerating the development of apps and services for any industry, and in this article, I share how to do it.

In this detailed article, you will learn how to carry out data ingestion and analysis using Azure Synapse Serverless SQL Pool along with sample datasets.

As machine learning (ML) is revolutionizing an enterprise's digital transformation, the path to successful ML implementation comes with its own set of challenges.

In this post, the author explains how to launch an Amazon EMR cluster and how to deploy a Kedro project to run a Spark job.

Follow a simplified demo implementation of the competing Consumers pattern using Java, Spring Boot, and Hazelcast's distributed queue.

In this article, we will explore how to use two popular Python libraries, Pandas and Matplotlib, to perform EDA.

The developer experience is changing faster than ever. Here's a primer on where things stand right now and what developers can expect.

Like the calculator, the spreadsheet, and the internet, AI-driven LLM tools are likely to change HOW we do our work, but not the fact that humans will still be the ones doing the work in the first place.

The third article of this series presents a deep-dive into how efficiently we can use Snowflake tables and warehouses and how data sharing occurs across accounts.

In the Sparkplug specification, an MQTT broker is an indispensable component to incorporate the five conceptual capabilities.

Here’s how you can simplify test-driven development and continuous integration with Redpanda and Testcontainers and Quarkus.

This article explores the intersection of PHP development and IoT, highlighting the benefits, challenges, and real-life use cases.

In industrial settings, vision AI means high-end quality control of manufacturing tasks and enhanced automation capabilities.

This guide explores how to auto-scale your Kinesis Data Streams consumer applications on Kubernetes so you can save on costs and improve resource efficiency.

Everybody's trying to get in on the big-money future of IoT, and now "everybody" includes Microsoft with Windows 10. Larry Dignan at ZDNet put together a look at Windows 10's role in IoT - as it's been described by Microsoft CEO Satya Nadella at the Gartner Symposium ITXpo, at least - which suggests that the new OS will be a central platform for IoT systems of all types. Specifically: Windows will be able to run on everything from sensors to wearables to whatever computing shift emerges. Or, as Patrick Thibodeau at ComputerWorld interpreted it: [Nadella] sees the company's upcoming operating system Windows 10 as integral in managing every aspect of the IoT, from the sensors, mechanical systems, to the applications and analytics that underlie it. Those are some pretty big promises, but as Nadella said, Windows 10 is "the first step in a new generation of Windows as opposed to just another release after Windows 8." After all, that would be Windows 9, right? Check out Dignan and Thibodeau's coverage of Nadella at the Gartner Symposium ITXpo for more details on Windows 10 in general. It looks like a promising future: Yo Ebola, I'ma let you finish but #Windows10 is gonna have the greatest virus of all time #WindowsTillIDie — Bill Gates (@BillKingGates) October 6, 2014

As the Internet of Things becomes a ubiquitous idea and a fact of life, what happens to all the aging and increasingly insecure Things? According to Wired's Robert Mcmillan, responding to a recent question on the security of IoT from Dan Geer, this may be a serious problem [1][2]. The solution, Mcmillan suggests, is to design these devices with an expiration date. In other words: they need to be programmed to die. The problem may not be too severe now, but the future of the Internet of Things will look different than it does now. Security will likely loosen, because software will be a part of everything, and it tends to be the case that things mass produced to that degree experience a bit of a drop in quality. That, Mcmillan argues, presents a problem: ...all code has bugs, and in the course of time, these bugs are going to be found and then exploited by a determined attacker. As we build more and more devices like thermostats and lightbulbs and smart trashcans that are expected to last much longer than a PC or a phone, maybe we need to design them to sign off at the point where they’re no longer supported with software patches. Otherwise, we’re in for a security nightmare. A similar argument came from Bruce Schneier's interview with Scott Berinato about how future bugs like Heartbleed could impact IoT [3]. Schneier's conclusion is that processes must be built into IoT devices and development to allow for regular patching and securing of embedded systems. How practical is that, though? Mcmillan points to some recent scenarios where these fears have already come true: the lack of support for Linksys routers infected with Moon Worm, for example. Long-term patching would solve these issues, but will the increasing number of organizations developing IoT products be forward-thinking enough to care? It's also not as if the problem will fade as the products become less popular, Mcmillan says: Researchers have studied the way that security vulnerabilities are discovered, and what they’ve found is that security bugs will keep cropping up, long after most software is released... in fact, they’ll only get worse. Open sourcing technology as it ages may also be a solution, Mcmillan says. However, even that is imperfect and requires a lot of cooperation from companies who may not be enthusiastic about such cooperation, as well as a base of developers interested enough in the technology to maintain it. So, creating devices with an expiration date may be one of the most practical solutions. Otherwise, what happens when IoT is everywhere? What happens when we stop taking care of the things that we build? [1] http://www.wired.com/2014/05/iot-death/ [2] http://geer.tinho.net/geer.secot.7v14.txt [3] https://dzone.com/articles/heartbleed-iot-how-much-worse