why
=>  Releases

Current version
Git/Latestdiff: 1.5.5

Latest Snapshots
Produced after each commit or rebase to new upstream version

GIT
RSBAC source code, can be unstable sometimes

=>  Events

No events planned

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
why [2006/12/27 10:18]
127.0.0.1 (old revision restored)
why [2009/01/16 11:11]
127.0.0.1 (old revision restored)
Line 1: Line 1:
 +~~NOTOC~~
 ====== What is RSBAC ====== ====== What is RSBAC ======
 +
  
 ===== Key Features ===== ===== Key Features =====
Line 6: Line 8:
   * Independent of governments and big companies   * Independent of governments and big companies
   * Several well-known and new security models, like MAC, ACL and RC   * Several well-known and new security models, like MAC, ACL and RC
-  * On-access virus scanning with the Dazuko interface 
   * Detailed control over individual user and program network accesses   * Detailed control over individual user and program network accesses
-  * Fully access controlled ​kernel level user management+  * Virtual User Management, in kernel and fully access controlled 
 +  * On-access virus scanning with the Dazuko interface
   * Any combination of security models possible   * Any combination of security models possible
   * Easily extensible: write your own model for runtime registration   * Easily extensible: write your own model for runtime registration
Line 53: Line 55:
 //To get a list and explanation of every model included in RSBAC, see the [[documentation:​rsbac_handbook:​security_models|Security Models]] section of the handbook.// //To get a list and explanation of every model included in RSBAC, see the [[documentation:​rsbac_handbook:​security_models|Security Models]] section of the handbook.//
  
-{{rsbac-flow.png}}RSBAC framework logic is based on the work done for the Generalized Framework for Access Control ([[http://​www.acsa-admin.org/​secshelf/​book001/​09.pdf|GFAC]]) by Abrams and LaPadula.+{{documentation:​rsbac_handbook:​architecture_implementation:​functional_diagram_gfac_rsbac2.png|}} 
 + 
 +RSBAC framework logic is based on the work done for the Generalized Framework for Access Control ([[http://​www.acsa-admin.org/​secshelf/​book001/​09.pdf|GFAC]]) by Abrams and LaPadula.
 All security relevant system calls are extended by security enforcement code. This code calls the central decision component, which in turn calls all active decision modules (the different modules implementing different security models) and generates a combined final decision. This decision is then enforced by the system call extensions. All security relevant system calls are extended by security enforcement code. This code calls the central decision component, which in turn calls all active decision modules (the different modules implementing different security models) and generates a combined final decision. This decision is then enforced by the system call extensions.
  
//
why.txt · Last modified: 2009/01/16 11:11 by 127.0.0.1

why.txt · Last modified: 2009/01/16 11:11 by 127.0.0.1
This website is kindly hosted by m-privacy