|
Chris PeBenito |
efa994 |
Security Enhanced Linux (SELinux) Reference Policy
|
|
Chris PeBenito |
efa994 |
|
|
Chris PeBenito |
696b41 |
Introduction
|
|
Chris PeBenito |
efa994 |
|
|
Chris PeBenito |
efa994 |
The purpose of this document is to serve as a blueprint to policy developers
|
|
Chris PeBenito |
efa994 |
and serves as the initial means for communicating the motivations, approach and
|
|
Chris PeBenito |
efa994 |
goals of the SELinux Reference Policy development project. This document
|
|
Chris PeBenito |
efa994 |
is intended for SELinux policy developers and other members of the SELinux
|
|
Chris PeBenito |
efa994 |
development community interested in building a secure foundation upon which to
|
|
Chris PeBenito |
efa994 |
build high-assurance solutions using SELinux. The reference policy will provide
|
|
Chris PeBenito |
efa994 |
a carefully designed and consistent system security policy that can be used as
|
|
Chris PeBenito |
efa994 |
a basis for developing secure solutions using SELinux.
|
|
Chris PeBenito |
efa994 |
|
|
Chris PeBenito |
696b41 |
|
|
Chris PeBenito |
696b41 |
Background and Motivation
|
|
Chris PeBenito |
efa994 |
|
|
Chris PeBenito |
efa994 |
One of the key motivations for this project is the drive to get SELinux
|
|
Chris PeBenito |
efa994 |
mainstreamed into commercial products. True, SELinux is currently being
|
|
Chris PeBenito |
efa994 |
incorporated into various commercial distributions, but clearly, widespread
|
|
Chris PeBenito |
efa994 |
adoption of SELinux as a commercial product eventually will require the
|
|
Chris PeBenito |
efa994 |
operating system to be certified. Efforts are already underway by IBM for
|
|
Chris PeBenito |
efa994 |
SELinux to undergo a Common Criteria evaluation under the Labeled Security
|
|
Chris PeBenito |
efa994 |
Protection Profile (LSPP). Furthermore, SELinux needs a more robust policy
|
|
Chris PeBenito |
efa994 |
structure upon which to build high-assurance solutions, such as intrusion
|
|
Chris PeBenito |
efa994 |
detection systems (IDS), cross-domain solutions, etc., particularly for
|
|
Chris PeBenito |
efa994 |
government and DoD security-critical missions.
|
|
Chris PeBenito |
efa994 |
|
|
Chris PeBenito |
696b41 |
|
|
Chris PeBenito |
efa994 |
|
|
Chris PeBenito |
efa994 |
Unfortunately, the current "strict" policy for SELinux does not meet the
|
|
Chris PeBenito |
efa994 |
requirements of high security systems. The policy chooses functionality over
|
|
Chris PeBenito |
efa994 |
security, with the implicit goal of not breaking legacy application behavior.
|
|
Chris PeBenito |
efa994 |
Additionally, it has no clear security goals and those that exist are not
|
|
Chris PeBenito |
efa994 |
rigorously followed or are ignored to preserve functionality. Furthermore,
|
|
Chris PeBenito |
efa994 |
complexity is increasing in the policy and the situation is not improving.
|
|
Chris PeBenito |
efa994 |
|