why
Releases
Current version
Git/Latestdiff: 1.5.6
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.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
why [2006/06/13 15:16] kang added note that this page is in handbook too |
why [2006/12/27 10:18] 127.0.0.1 (old revision restored) |
||
|---|---|---|---|
| Line 53: | Line 53: | ||
| //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 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. | + | {{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. |
| 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