Security

This page deals with security in the system and best practices to make a secure system.

Security strategy

The security strategy relies on some key design concepts:

• Isolation, the components of the system are separated from each other. It means that they belong to their own virtual machine and have no direct contact with the other components. Thus the threats cannot contaminate the whole system.
• Protocol break, which means that the communication between the components use a very simple data protocol with a very low attack surface. An attack from outside the system cannot propagate inside the system using TCP-IP or USB for example as these protocols are limited to their repective components and the data flow uses another data protocol and mean.
• Collaboration, the components of the system that don't need to manipulate files or external data don't have access to them. Instead, they collaborate with other components to get the information or data they need. This reduces the risk of contaminating the core of the system.
• Simplicity, the architecture of the core is very simple and this simplicity limits configuration or design weaknesses that could be exploited by threats. This is a major design rule.

Hardening rules

This section deals with the hardening rules.

Services

The services are executed as a normal user (without privilege). The user root is never be used for any service nor application in the system.

Users and groups

The shared contents, like the storage, can be accessed R/W with a user that belongs to the group safecor. The group safecor is added to the Domain by the package safecor-domu-base (see Packages).