Connect with us

Infosecurity

Fixing the Internet of Broken Things: An Open, Hardware-Led Approach

Published

on

Fixing the Internet of Broken Things: An Open, Hardware-Led Approach

Our world is now woven with connected devices. They monitor our health, fly our planes, and drive our cars. Yet, beneath this convenience lies a critical flaw: the security of the Internet of Things is broken. This isn’t a theoretical risk. Vulnerabilities discovered by researchers aren’t just about stolen data; they have the potential for catastrophic, real-world harm.

The Failure of Security-by-Obscurity

For too long, many IoT manufacturers have operated on a dangerous assumption. They believe that hiding their code—security-by-obscurity—is enough. It’s a strategy that has repeatedly failed in the software world. Look at the legacy of proprietary systems like Windows, Java, or Flash. They became prime targets precisely because their closed nature didn’t guarantee safety; it often hid flaws from everyone but the attackers.

The tools available to reverse engineer device firmware are incredibly sophisticated. Malicious actors can extract code directly from hardware or find it in online updates. The idea that obscurity provides protection is a myth that needs to be retired. What’s the alternative? We must embrace openness.

Building on Open Source and Open Standards

Open source software offers a fundamentally different security model. Instead of a handful of developers scrutinizing code, you have thousands of expert eyes worldwide. Flaws are found and fixed with astonishing speed, often within hours. The community’s focus is on quality and utility, not corporate politics or commercial feature sets.

This transparency also addresses another shadowy concern: nation-state interference. History is littered with reports of governments pressuring companies to build secret backdoors into proprietary products. Such concerns rarely, if ever, touch the open-source community at large, where the code is open for all to inspect.

Open standards are equally crucial, especially for networking. Implementing complex protocols like TCP/IP is difficult. When a device engineer, unfamiliar with networking, is tasked with adding connectivity, mistakes are inevitable. Global, interoperable open standards encapsulate this complexity. They allow hardware developers to rely on robust, expert-maintained frameworks, outsourcing the trickiest security work to those who know it best.

Containing Risk with Hardware-Assisted Separation

Many embedded systems are designed as a single, monolithic environment. If a hacker breaches one component—say, the infotainment system in a car—they can often ‘move laterally’ to more critical systems like steering or brakes. This design flaw is a gift to attackers.

The solution is security by separation, enforced by hardware. Using hardware-assisted virtualization, a secure hypervisor can create isolated containers for each software function. The radio runs in one virtual box; the engine management system runs in another. From a risk perspective, assuming any software can be compromised is prudent. This architecture ensures that a breach in one container is contained, preventing it from becoming a stepping stone to the entire system.

Of course, systems need to communicate. The volume might need to increase as the car accelerates. This is managed through strictly controlled, secure channels between containers. This model isn’t just for safety; it’s essential for business. A smart TV without this separation could allow a rogue app to steal a protected video stream from Netflix, causing significant financial damage.

The Practical Path Forward

The ideal of a hardware-rooted, open security framework is the destination. Reaching it requires a journey. Not all chips today support advanced virtualization. However, progress can start now.

Manufacturers can begin with intermediate steps like Linux containers to isolate applications. Even without a dedicated ‘root of trust’ chip, firms can and must encrypt and cryptographically sign their firmware. They must commit to providing timely security patches. Waiting for perfect hardware is not an option when the vulnerabilities are present today.

The stakes couldn’t be higher. We built an internet of things without a foundation of security. To fix it, we must collectively move away from secrecy and toward openness, and away from monolithic designs and toward hardware-enforced separation. The journey is necessary, and it starts with a decision to change our approach.

Continue Reading
Click to comment

Leave a Reply

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

Infosecurity

IoT Security Challenges: The Critical Flaws Putting Connected Devices at Risk

Published

on

The False Promise of Proprietary Software

Think your device is safe because its code is a secret? History suggests otherwise. Security researchers have repeatedly dismantled that assumption by reverse engineering proprietary systems in alarming ways. Charlie Miller and Chris Valasek didn’t need a physical key to hijack a 2014 Jeep—they remotely commandeered its steering and brakes by dissecting the Uconnect system’s software.

Similar stories echo across other domains. A smart rifle was hacked to fire at a chosen target. Hospital drug infusion pumps were found vulnerable to dosage tampering. These aren’t theoretical exercises; they are documented breaches performed by experts. If they can do it, malicious actors certainly can.

The old strategy of ‘security through obscurity’ is a crumbling defense. Firmware binaries often lurk online, waiting to be found. If not, hardware debugging tools can extract software directly from the device. With disassemblers and determination, a closed system’s secrets are laid bare. Relying on proprietary code doesn’t build a fortress—it often builds the easiest path for a skilled attacker.

Network Connectivity: The Open Door

Connectivity is the superpower of the IoT. It’s also its greatest weakness. A device linked to the internet or a network provides a remote attack vector, enabling exploitation on a massive, automated scale. The problem is compounded by who’s building these systems.

Many IoT engineers are brilliant at hardware integration but lack deep expertise in network protocols and security. Implementing robust TCP/IP stacks is a specialized discipline. Expecting a mechanical engineer to also be a network security expert is unrealistic, yet that knowledge gap leaves doors wide open.

Remember the Jeep hack? A critical enabler was port 6667—left inexplicably open and unauthenticated on the vehicle’s D-BUS. This wasn’t a complex, zero-day exploit; it was a basic network oversight. When devices are designed without secure networking as a core principle, they invite trouble. Every connected device is a potential entry point, and weak implementation turns that potential into reality.

The Peril of Broken Firmware Updates

An unpatched device is a vulnerable device. Shockingly, many IoT products lack any update mechanism at all. Others have update processes so flawed they introduce new risks. The ability to patch firmware is essential, but the method must be secure.

Attackers can exploit weak update systems to gain permanent, privileged control. In the Jeep case, researchers modified the chip firmware and reflashed it, allowing arbitrary code execution. It’s like installing a top-tier home alarm, only to have a burglar replace it with their own system while you sleep. The original security becomes meaningless.

This threat is persistent. A malicious firmware implant survives reboots and grants deep access. For devices like network routers or home gateways, such a compromise means the attacker sees and controls all incoming and outgoing traffic. The very mechanism meant to fix security flaws can, if poorly designed, become the ultimate backdoor.

Systems Promiscuity and the Lack of Separation

Why do IoT breaches often spiral out of control? A common culprit is the lack of internal segmentation. Once an attacker breaches one component, they can often move laterally through the system with little resistance. This ‘promiscuity’ is a gift to cybercriminals.

In targeted data center attacks, adversaries use this strategy after an initial phishing email or stolen credential. They pivot from one system to another, escalating privileges until they reach the crown jewels. The IoT world mirrors this danger. Miller and Valasek started in the Jeep’s entertainment system (the head unit). From there, they refreshed microprocessor firmware and eventually reached the critical CAN bus controlling the vehicle’s physical functions.

Similarly, allegations suggest an researcher accessed an aircraft’s flight systems by first infiltrating its in-flight entertainment network—areas that should have been rigorously isolated. The principle of separation is security 101. Ignoring it in IoT design isn’t just disappointing; it’s a direct threat to safety when these systems control cars, medical devices, and more. Without strong internal boundaries, a single vulnerability can lead to total system compromise.

Continue Reading

Infosecurity

Cybersecurity Education: Why We Must Start with Kids and Computers

Published

on

The Case for Starting Cybersecurity Education Early

October in the D.C. area brings more than just stunning fall colors on the Blue Ridge Mountains. It marks National Cyber Security Awareness Month, a perfect time to highlight a critical shift. We’re no longer just talking to adults about cyber threats; we’re engaging the kids who will one day defend our digital world.

Every time a child boots up a computer or downloads homework, we’re looking at a future security professional. The question isn’t whether we should start young—it’s how soon we can begin. The widening workforce gap in cybersecurity isn’t a future problem; it’s a present crisis. Building a pipeline of talent requires planting seeds in elementary and middle school, not just harvesting from college graduates.

Making Cyber Cool: Beyond the Pocket Protector

For too long, cybersecurity suffered from an image problem. The stereotype of the isolated, technical genius in a dark room persists. We need a rebrand. As House Inspector General Theresa Grafenstine pointed out during a recent town hall, we must ‘slap Cinderella with a laptop.’ The field needs a marketing campaign that resonates with youth.

The goal is to replace the ‘pocket protector’ image with one of mission-driven problem-solving. Kids aren’t drawn to dry theory; they’re captivated by challenges, puzzles, and real-world impact. This new narrative is gaining traction in Congress, academia, and corporate boardrooms. The message is clear: cybersecurity is an adventure, not a lecture.

Competitions, Scholarships, and Real-World Pathways

Proof of this shift is visible in student competitions. Take the recent national Capture the Flag event joined by the (ISC)² Foundation and MITRE. Over 300 students from 73 high school and college teams battled it out. The winning teams included high schoolers, each receiving a $1,000 scholarship, an exam voucher for the Systems Security Certified Practitioner (SSCP) certification, and internship priority.

These results are telling. When properly nurtured, cyber talent doesn’t just appear in adulthood; it blossoms in adolescence. Competitions do more than test skills. They encourage systemic thinking, social responsibility, and a commitment to protecting others. They transform abstract concepts into thrilling missions.

How Schools Are Cultivating Cyber Talent

Educators are building robust foundations. At Thomas Jefferson High School for Science and Technology, Principal Dr. Evan Glazer and his team take a holistic approach. They teach operating systems, architecture, and cryptography. The key lesson? It’s the interconnectivity of these topics that makes cyber challenges real.

‘Students who enjoy cyber topics appreciate the multidisciplinary or problem-solving aspect,’ Glazer notes. He passionately advocates for extracurricular cyber activities, seeing them as essential complements to classroom learning. Other schools offer dedicated cyber curricula aligned with professional certification paths. The method may vary, but the objective is identical: equip students with tangible opportunities.

Building a Clear Career Bridge from Classroom to Career

Inspiring interest is only the first step. The professional community must then build a bridge. Students need a visible, attainable career path. Programs like the Associate of (ISC)² are designed for this very purpose. They help graduates enter the field at an entry-level and establish a clear pathway for advancement.

The responsibility doesn’t end with educators. Every organization can play a part. Supporting existing K-12 cyber competitions or launching new ones is a powerful start. Resources like the DHS Cybersecurity Division website offer ideas and frameworks for involvement.

What begins as a fun puzzle on a computer could end as a lifelong, fulfilling career. The device used to occupy a child’s afternoon might be the first tool in building our future cyber defense. The time to start is now. Look for STEM potential in the children around you. Get your organization involved. Our collective digital safety depends on the curiosity we foster today.

Continue Reading

Infosecurity

Cyber Warfare and Critical Infrastructure: The Hidden Threat in Foreign-Built Systems

Published

on

When War Changes Form

Back in 1999, two Chinese military strategists published a book called Unrestricted Warfare. Their central argument was simple yet profound. As nations move away from traditional military confrontation, conflict doesn’t disappear—it transforms.

War migrates to new arenas: politics, economics, and technology. The battlefield becomes digital. The weapons are lines of code. This shift creates a paradox. While overt military violence may decline, other forms of aggression intensify in the shadows.

The Ghost in the Machine: Foreign-Built Critical Infrastructure

My deepest concern isn’t about tanks or missiles. It’s about who builds the systems that keep a nation running. Imagine a foreign state-owned company winning a contract to construct and operate a nuclear facility on domestic soil. The physical security might be robust, with guards and fences.

But what about the digital skeleton? The facility would be packed with complex hardware and software, potentially developed and coded thousands of miles away. Can we truly audit billions of lines of proprietary code? Do we understand every backdoor, every latent function, every piece of logic that wasn’t meant for the manual?

A government minister once dismissed such fears, pointing to stringent physical security controls. That response missed the point entirely. It was a 20th-century answer to a 21st-century problem. The threat isn’t at the gate; it’s woven into the very fabric of the technology.

A Legacy of Unseen Vulnerabilities

History offers a cautionary tale. Remember the Titan Rain cyber-attacks around 2007? Western governments accused China of systematically infiltrating defense and government networks in the US, UK, and Germany. The operations were stealthy, persistent, and aimed at extracting sensitive information.

This wasn’t science fiction. It was a real-world demonstration of Unrestricted Warfare in action. The goal wasn’t destruction but access and influence. Now, consider that same strategic mindset applied to critical infrastructure built with foreign technology. The potential for control—or sabotage—is staggering.

We’re not talking about stealing blueprints. We’re talking about the ability to silently manipulate the controls of a power grid or a nuclear cooling system. The risk isn’t hypothetical; it’s embedded in the procurement choices we make today.

Navigating the Golden Era’s Digital Blind Spot

There’s a powerful political desire for a “Golden Era” of trade and cooperation with major economic partners. The ambition is understandable. But does this diplomatic push create a blind spot for national security?

Granting a foreign power, especially one with a documented history of state-sponsored cyber activity, deep integration into a nation’s critical backbone is an unprecedented gamble. We’ve seen how missteps in other strategic areas, like energy policy, can have long-lasting consequences.

Can we afford a similar miscalculation in the cyber-nuclear domain? Once these systems are integrated, there’s no easy undo button. No time machine to go back and choose a different path. The complex, opaque code becomes a permanent tenant in our national home.

The challenge is clear. We must pursue economic partnerships without compromising digital sovereignty. This means developing rigorous, independent verification standards for all code in critical systems. It means investing in our own technical audit capabilities. The integrity of our infrastructure cannot be an afterthought in the pursuit of trade deals. The stakes are simply too high.

Continue Reading

Trending