Linux Security Principle: Containment of Failure

Everyone who ever used Windows 95, is familiar with the concept of failure. Fortunately, Linux systems have a strong foundation and use containment of failure.


Everyone who used Windows 95 or 98 in the past is familiar with the concept of failure. One crashing application was enough to bring the system to a halt. Fortunately, Linux systems have a strong foundation, including privilege separation and memory management. When things go wrong, the impact is reduced to a minimum. This is called containment. Linux Memory Management Memory is like your the storage capacity of your brain. Every bit should be stored properly, or otherwise you will do strange things.

Simplifying Security: Choose the Right Toolkit, not Tool.

Too often we select security products based on the amount of features, instead of smart combinations. Don't think tools, but start building up a toolkit.


I applaud many of our customers for being smart. Not to say other people are not, but they have made a specific choice in the past based on an understanding. They understand that a single security solution to make your IT environment safe, simply does not exist. It is the combination of tools, or your toolkit, which does. For this same reason, a carpenter has a tool chest, not a single tool.

5 Basic Principles of Linux System Security

With 5 basic security principles we can improve system security of almost any Linux system.


It is still common that people do not know where to start when it comes to information security. With 5 basic principles we can improve the Linux system security and question ourselves if we have done enough. 1. Know your system(s) The first principle is about knowing what your system is supposed to do. What is its primary role, what software packages does it need and who needs access? By knowing the role of the system you can better defend it against known and unknown threats.