Kaspersky Lab - Finally, Our Own OS – Oh Yes!

  • Thread starter Deleted member 2913
  • Start date
Status
Not open for further replies.
D

Deleted member 2913

Thread author
Kaspersky Labs Blog: Finally, Our Own OS – Oh Yes! | Nota Bene: Eugene Kaspersky's Official Blog

At last – we’ve done it!

I’ve anticipated this day for ages – the day when the first commercially available mass market hardware device based our own secure operating system landed on my desk. And here she is, the beaut.

This unassuming black box is a protected layer 3 switch powered by Kaspersky OS and designed for networks with extreme requirements for data security.

And there’s plenty more in the pipeline where this came from too, meaning the tech will be applied in other Internet-connected bits of kit, aka the Internet of Things (IoT). Why? Because this OS just so happens to be ideal for applications where a small, optimized and secure platform is required.

The operating system boasts several distinctive features. Let me run through the main ones briefly…

First, it’s based on microkernel architecture, which allows to assemble ‘from blocks’ different modifications of the operating system depending on a customer’s specific requirements.

Second, there’s its built-in security system, which controls the behavior of applications and the OS’s modules. In order to hack this platform a cyber-baddie would need to break the digital signature, which – any time before the introduction of quantum computers – would be exorbitantly expensive.

Third, everything has been built from scratch. Anticipating your questions: not even the slightest smell of Linux. All the popular operating systems aren’t designed with security in mind, so it’s simpler and safer to start from the ground up and do everything correctly. Which is just what we did.

And just the other day we celebrated the birth of this new OS!

The very first meeting held regarding this project took place 14 (fourteen!) years ago almost to the day – on November 11! Not that we’ve been diligently coding and testing since then; in that amount of time with sufficient resources you could see several projects through to the end and update and improve them all several times over!

No, in the first several years not a single line of code was written. We met from time to time, discussed technical details, architecture, and drew pretty pictures on large sheets of paper. Then we built up a team – very slowly, since OS specialists are few and far between. And onwards we move, slowly but surely. Fast forward several years, and today we aren’t simply celebrating the latest team discussion, but our first commercial hardware device actually ready!

November 11 is of course easy to remember as it’s 11-11. Which is birthday of our big, ambitious project. Indeed, within the company the project is known simply as ’11-11′.

14 years is a serious age for any project. Looking back it seems so quaint now how at the start we argued about the architecture and the basic parameters of the future OS and felt a little bit like… alchemists with compasses trying to make squares out of circles.

The question to which we were searching for an answer was this: how can we build an operating system that will be impossible to hack in principle? Is it possible in practice? Meanwhile, all around this alchemy folks were fairly astonished: just what were we thinking? We’d decided to make an unhackable platform and ruin our other security business model?!

Indeed, we were often asked why such an OS is really necessary. Here’s why:

Once, cyberthreats targeting critical infrastructure, telecoms and other modern-life-essential systems looked mostly like science fiction. No one – besides us paranoids (actually, and also the most advanced hackers, cyber-spies and cyber-militaries) really had any idea that data security could directly affect physical security. Nor were they aware that literally all digital systems in existence around the world can be hacked. After all, we started our project long before Stuxnet, and even before Die Hard 4, where the cyber-baddies hacked and wrecked critical infrastructure. But as time has passed the general level of understanding of the threats has gradually – and increasingly conspicuously – risen…

The serious problem of security of critical infrastructure started to be discussed at high-profile international conferences. Then, gradually, the topic started to spread into the imaginations of Hollywood (Die Hard 4, Skyfall…). Next, literally in the last year to 18 months, attention has risen still further – exponentially – to finally make the topic of cybersecurity one of the main topics at various top-level international summits and meetings of world leaders. Meanwhile, quietly in the background all this time, alchemists KL experts were toiling away in their workshops edging ever nearer to the unveiling of our very own OS!

We realized that the operating system needed to have lots of different applications.

First, it should provide a basis for the development of protected industrial control systems.

Second, it should provide a basis for the development of protected embedded devices, including the IoT. Btw, the recent DDoS attack on Dyn’s DNS servers, which brought down sites like Amazon and Twitter, was carried out by a botnet that had infected ‘smart’ (actually, rather stupid:) devices like IP-cameras. The attack generated an astounding 1.2 terabytes a second – the biggest DDoS in history.

So, I’m hoping it’s obvious by now how protecting the IoT and, of course, critical infrastructure (industry, transport, telecoms, etc.) from IT threats is simply mandatory. I also hope it’s clear that it’s better – no matter how difficult – to build IoT/infrastructure devices from the very beginning in such a way that hacking them is practically impossible. Indeed, that is a fundamental goal with Kaspersky OS.

That was all mostly a teaser really. Coming up soon – more details about our secure operating system.

Kaspersky Labs Blog: Finally, Our Own OS – Oh Yes! | Nota Bene: Eugene Kaspersky's Official Blog
 
Last edited by a moderator:

RoboMan

Level 35
Verified
Top Poster
Content Creator
Well-known
Jun 24, 2016
2,400
This good news! I hope they make it compatible for common-enterprise-software like document editors, access control, etc. So every small business/enterprise buys it and we can breath a little more on matter of ransomware/general malware directed to businesses.
 

tim one

Level 21
Verified
Honorary Member
Top Poster
Malware Hunter
Jul 31, 2014
1,086
Well, a microkernel use the essential stuff to interface with the hardware, and then all of the services (system calls) are written in user space, they communicate directly with the microkernel, all the other applications in user space can decide whether to use the system calls or to report directly to the microkernel.

The approach is definitely the most secure and easy to program but less efficient from the point of view of performance because the communication between the system calls and the kernel has to be via an exchange of messages that weighs down the whole system.
But probably Kaspersky has resolved this problem.
 
W

Wave

Thread author
I place down my bets that they at least read from the following resources before they even started the project:
Expanded Main Page - OSDev Wiki
Bona Fide OS Developer - learn to write your own operating system from scratch
Bran's Kernel Development Tutorial: Introduction
BrokenThorn Entertainment

Very useful resources for anyone who wants to become further educated on OS development, but bear in mind you'll be required to start with 16-bit Assembly for the start boot-loader, since you cannot make use of x86 ASM before you enable the A20 line and setup the Global Descriptor Table (which can be a pain to do if you've no previous experience on it); basically you need to enter Protected Mode to access more memory, also. (16-bit OS will be very limited with memory compared to entering protected mode and making it 32-bit).

You can use Bochs, Qemu or even VirtualBox/VMWare to test an OS after you've had it compiled/linked properly. However, you can make a disk image to allow supporting off a real system without a VM... Although I don't recommend doing this.

Of course Kaspersky have been developing a proper useful OS as opposed to a useless home-made OS project, but above is useful for anyone here who is secretly urging to make an OS. Have fun, because it'll be hard to not smash up your PC in rage when you end up getting a link error or a kernel-crash during testing :D :p
 

Fritz

Level 11
Verified
Top Poster
Well-known
Sep 28, 2015
543
You wouldn't need to, it's intended for Industrial systems, not home computers.

Considering industrial espionage is an important field for intelligence services, I sure wouldn't use foreign stuff in my industry if possible. ;)
 
  • Like
Reactions: shukla44 and XhenEd

tim one

Level 21
Verified
Honorary Member
Top Poster
Malware Hunter
Jul 31, 2014
1,086
Very useful resources for anyone who wants to become further educated on OS development, but bear in mind you'll be required to start with 16-bit Assembly for the start boot-loader, since you cannot make use of x86 ASM before you enable the A20 line and setup the Global Descriptor Table (which can be a pain to do if you've no previous experience on it); basically you need to enter Protected Mode to access more memory, also. (16-bit OS will be very limited with memory compared to entering protected mode and making it 32-bit).
In this regard, the real vulnerability (those worst ) are inherent in the boot/bios system and the memory system..
If they want a secure system (virtually secure) then it would be necessary to redesign the computer from scratch with different concepts, and then make a new OS
If they spend years of study for a OS that will be like the previous ones... considering that the Assembly cannot be that the one already in use, it is not possible to solve the problem because sooner or later someone will find the flaw to exploit the system.
 
Last edited:
  • Like
Reactions: shukla44 and XhenEd
Status
Not open for further replies.

About us

  • MalwareTips is a community-driven platform providing the latest information and resources on malware and cyber threats. Our team of experienced professionals and passionate volunteers work to keep the internet safe and secure. We provide accurate, up-to-date information and strive to build a strong and supportive community dedicated to cybersecurity.

User Menu

Follow us

Follow us on Facebook or Twitter to know first about the latest cybersecurity incidents and malware threats.

Top