Releases
Current version
Git/Latestdiff: 1.5.6
Latest Snapshots
Produced after each commit or rebase to new upstream version
GIT clone e.g. at git://git.rsbac.org/linux-6.18.y
Events
No events planned
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| documentation:rsbac_handbook:configuration_basics:identify_requirements:system_base [2006/05/17 12:50] – created ao | documentation:rsbac_handbook:configuration_basics:identify_requirements:system_base [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== System Base Protection ===== | ||
| - | The following categories of objects usually have to be controlled: | ||
| - | |||
| - | * **Filesystem Structure: | ||
| - | * **Executables: | ||
| - | * **Dynamic Libraries: | ||
| - | * **Configuration Files:** Many programs are influenced by configuration files, which thus have to be protected to avoid unwanted program behaviour. | ||
| - | * **Kernel Objects:** All kernel code, like kernel images and loadable modules, is stored in files on disk. Modification of these files can provide uncontrollable access to the whole system. Additionally, | ||
| - | * **Devices: | ||
| - | * **Authentication Data:** The data used for authentication are critical for access control. They must be protected from all accesses which are not strictly necessary. | ||
| - | * **Network Resources: | ||
| - | * **Other Objects:** Some additional objects should be taken into account, like log data, boot loaders, hardware ports, etc. The actual selection depends on the system configuration. | ||