Security equipment for partitioning between first and second domains (1, 2), comprising: - a hardware layer, comprising a computation means, a memory storage means, and first and second interface means (21, 22) with said first and second domains; - a virtualization layer of the hardware layer, comprising a core and a hypervisor; - an application layer comprising: - a first interface component, for exchanging data with the first domain, the first interface component being of the operating system component type integrating a rich operating system, in the sense that numerous functionalities are implemented by default and it is not possible to certify it, the operating system comprising in particular a native driver; - a second interface component, for exchanging data with the second domain, the second interface component being an operating system type of component, integrating a rich operating system, in the sense that numerous functionalities are implemented by default and it is not possible to certify it, the operating system comprising in particular a native driver; - a security component forming a data exchange cell between the first and second components, characterised in that at least one interface component of the first and second interface components is associated with a driver component (41, 61), the driver component being an application type of component that it is possible to certify, the core performing a spatial partitioning such that only the driver component has exclusive access to a storage space of the memory storage means allocated to the corresponding interface means (21, 22,), and the driver component (41, 61) and the interface component exchange data by means of a shared memory space (44, 64) of the memory storage means, the driver component (41, 61) being a "PROXY" type component suitable for acting on behalf of the interface component, in such a way that, in a first data exchange direction, a function of the interface component, called by the native driver of the operating system, writes data in the memory space shared with the driver component and the driver component reads the data written in the shared memory space and launches a corresponding function to write in the storage space of the memory storage means allocated to the corresponding interface means (21, 22); and in a second data exchange direction, the driver component calls a function requiring the reading of data written in the storage space of the memory storage means allocated to the corresponding interface means (21, 22), and writes the corresponding data in the memory space shared with the interface component, and the interface component calls the corresponding function of the native driver and reads the data placed in the shared memory space, and in that the driver component (41, 61) executes service applications to control the data flow passing through the driver component. - a hardware layer, comprising a computation means, a memory storage means, and first and second interface means (21, 22) with said first and second domains; - a virtualization layer of the hardware layer, comprising a core and a hypervisor; - an application layer comprising: - a first interface component, for exchanging data with the first domain, the first interface component being of the operating system component type integrating a rich operating system, in the sense that numerous functionalities are implemented by default and it is not possible to certify it, the operating system comprising in particular a native driver; - a second interface component, for exchanging data with the second domain, the second interface component being an operating system type of component, integrating a rich operating system, in the sense that numerous functionalities are implemented by default and it is not possible to certify it, the operating system comprising in particular a native driver; - a security component forming a data exchange cell between the first and second components, - a first interface component, for exchanging data with the first domain, the first interface component being of the operating system component type integrating a rich operating system, in the sense that numerous functionalities are implemented by default and it is not possible to certify it, the operating system comprising in particular a native driver; - a second interface component, for exchanging data with the second domain, the second interface component being an operating system type of component, integrating a rich operating system, in the sense that numerous functionalities are implemented by default and it is not possible to certify it, the operating system comprising in particular a native driver; - a security component forming a data exchange cell between the first and second components,