The Device Access example demonstrates use of the Privilege Separation pattern.
Example architecture
The example contains the following three programs: Device, LoginManager and Storage.
In this example, the Device program queries the Storage program to receive information and queries the LoginManager program for authorization.
The Device program obtains access to the Storage program after successful authorization.

This example demonstrates the capability to separate the authorization logic and the data access logic into independent components. This separation guarantees that data access can be opened only after successful authorization. The security module monitors whether authorization was successfully completed. This architecture also enables independent development and testing of the authorization logic and the data access provision logic.
A security policy in the Device Access example has the following characteristics:
Device program has the capability to query the LoginManager program for authorization.GetInfo() method of the Storage program are managed by methods of the Flow security model:session object configuration has two states: unauthenticated and authenticated.unauthenticated.unauthenticated to authenticated and vice versa are allowed.session object is created when the Device program is started.Device program successfully calls the Login() method of the LoginManager program, the state of the session object changes to authenticated.Device program successfully calls the Logout() method of the LoginManager program, the state of the session object changes to unauthenticated.Device program calls the GetInfo() method of the Storage program, the current state of the session object is verified. The call is allowed only if the current state of the object is authenticated.Example files
The code of the example and build scripts are available at the following path:
/opt/KasperskyOS-Community-Edition-<version>/examples/device_access
Building and running example
See Building and running examples section.
Page top