https://www.rsbac.org/ 2026-05-12T20:57:11+00:00 https://www.rsbac.org/ https://www.rsbac.org/lib/tpl/rsbac/images/favicon.ico text/html 2007-03-10T20:57:30+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.rsbac.org/documentation/rsbac_handbook/architecture_implementation/framework_components?rev=1173560250&do=diff Framework Components What follows is an architectural diagram of the way RSBAC works internally. We will first describe here each step RSBAC goes through, when a new event occurs (or if you prefer, an action is performed on the system). You do not need to understand everything right away, as separate parts of RSBAC will be explained in more details further on, but keep this page as reference. text/html 2013-08-17T14:14:41+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.rsbac.org/documentation/rsbac_handbook/architecture_implementation/requests_targets?rev=1376748881&do=diff Requests Types Before access to a target (i.e. an object) is granted, a request call to the Access Control Decision facility (ADF) is performed. Based on the request type and the target, the access will be granted or denied. So, what is a request ? Well, each time a process (i.e. a subject) wants to get access to a text/html 2013-08-17T09:02:11+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.rsbac.org/documentation/rsbac_handbook/architecture_implementation/subjects_objects?rev=1376730131&do=diff Subjects and Objects Put in a simple manner, RSBAC restricts the access a subject has on different objects. The subjects are in fact processes (and associated libraries), acting on the behalf of users. And every process runs as a user. The objects can be filesystem objects (files, directories,