Our Master Plan – The Inflection Point (Part 2)

Continuing from The Past is Prologue (Part 1).

Since our founding days, our company’s purpose is to expedite the move to new technology and approaches that enables and encourages OEMs (the people who make devices) to construct more secure devices, while also enriching their functionality, and thereby enabling further innovation.  This would in turn would provide integrators with richer products and tools to build an entire connected, and secure ecosystem.  It would enable enterprises and users to reclaim lost productivity in scenarios where security became a burden or inhibiting (eg. Enterprise mobile users are often constrained by the applications with which they can run).  The cool thing about this technology and approach is that it has very broad applicability to how we build systems (more on that another time).

The time is now.  Continue reading “Our Master Plan – The Inflection Point (Part 2)”

Our Master Plan – The Past is Prologue (Part 1)

We’ve been doing some great things at Cog Systems and have an exciting vision for the future – our master plan – so I thought I’d share it with everyone in a couple of blog posts.  It’ll be fun.  Let’s see how it pans out over the next few years – I’ll probably be way off, because one of the things we are great at is being nimble and able to adapt quickly to where we see opportunity and need.  Let’s see.

But first, before I tell you where we are heading, I wanted to share where we have come from and share some insights into our team and our performance.

Continue reading “Our Master Plan – The Past is Prologue (Part 1)”

Another day, another exploit

Many of the devices we use today, particularly those built using Android and Linux are essentially monolithic systems.  They have a huge set of APIs and a massive code base, and while this is great for functionality, it makes them prone to successful attack.

To mitigate the threat of attack, a lot of effort has gone into hardening those APIs.  Examples include SE for Android (now a part of Android), and work by companies including Samsung KNOX, Boeing, and many others.  They are all essentially taking what exists today, and adding additional functionality (occasionally removing some too) to make it harder to compromise and ultimately reduce the chance of an attack being successful. In essence, they dabble around the edges.
Continue reading “Another day, another exploit”