Last modified: January 20, 2025

This article is written in: 🇺🇸

SELinux

Security-Enhanced Linux (SELinux) is a robust security module integrated into the Linux kernel that provides a mechanism for supporting access control security policies. Unlike traditional discretionary access control (DAC) systems where users have control over their own files and processes, SELinux implements mandatory access control (MAC), ensuring that the system enforces security policies regardless of user actions.

SELinux works by assigning labels, or security contexts, to all processes and objects (like files and sockets) on the system. These contexts are then used to make decisions about whether a process can access a resource. By enforcing least privilege, SELinux confines user programs and system services to the minimum required permissions, greatly reducing the potential damage from malicious or misconfigured software.

Developed by the United States National Security Agency (NSA) and released to the open-source community, SELinux has become a cornerstone of Linux security, particularly in environments where security is paramount, such as servers handling sensitive data or systems exposed to the internet.

Overview of SELinux Architecture

Understanding the architecture of SELinux is key to leveraging its full potential. SELinux operates within the kernel and works alongside existing Linux security mechanisms to enforce its policies.

Architecture Diagram

+---------------------------------------------------+
|                   User Process                    |
|             (e.g., Web Server, SSH Daemon)        |
+----------------------+----------------------------+
                           |
                           | 1. Access Request (Read/Write)
                           v
+----------------------+----------------------------+
|               SELinux Security Server             |
|          (Policy Decision Point - PDP)            |
+----------------------+----------------------------+
                           |
                           | 2. Policy Decision (Allow/Deny)
                           v
+----------------------+----------------------------+
|          SELinux Object Manager and AVC           |
|          (Policy Enforcement Point - PEP)         |
+----------------------+----------------------------+
                           |
                           | 3. Enforce Decision
                           v
+----------------------+----------------------------+
|                    Linux Kernel                   |
|             (Executes Allowed Operations)         |
+---------------------------------------------------+

Detailed Explanation

I. User Process (Subject):

• Any running application or service, such as a web server (httpd), an SSH daemon (sshd), or a user application.
• The process attempts to perform an action, like reading a file, writing to a socket, or executing a program.
• This action is considered an access request to an object (resource).

II. SELinux Security Server (Policy Decision Point - PDP):

• Intercepts the access request and consults the loaded SELinux policies.
• Determines whether the requested action is permitted based on the security contexts of the subject and object.
• Allow or Deny.

III. SELinux Object Manager and Access Vector Cache (AVC) (Policy Enforcement Point - PEP):

• Enforces the policy decision by either permitting or denying the action.
• Caches previous decisions to optimize performance, reducing the overhead of policy checks.

IV. Linux Kernel:

• If the action is allowed, the kernel proceeds to execute the operation.
• If denied, the kernel blocks the operation and logs the denial.

SELinux Modes of Operation

SELinux can operate in different modes, allowing administrators to balance security enforcement with system usability.

Mode Comparison Table

+------------------+------------------+------------------+
|  Enforcing Mode  | Permissive Mode  |  Disabled Mode   |
+------------------+------------------+------------------+
| Policies Enforced| Policies Not     | Policies Not     |
|                  | Enforced         | Loaded           |
| Denials Blocked  | Denials Logged   | No SELinux       |
| and Logged       |                  | Functionality    |
+------------------+------------------+------------------+

Note: Switching between modes can impact system security and functionality. Always ensure that mode changes are intentional and understood.

SELinux Policy Types

SELinux policies define the rules that govern how processes and resources interact. There are two main policy types:

• Targeted Policy is recommended for most users due to its balance between security and usability.
• Strict Policy offers more security but requires extensive configuration and may impact system functionality.

SELinux Contexts and Labels

SELinux uses security contexts (also known as labels) to make decisions about access control. Every object and process in the system has a context consisting of:

Example Context

system_u:object_r:httpd_sys_content_t:s0

• system_u: SELinux user identity.
• object_r: Role indicating it's an object.
• httpd_sys_content_t: Type for HTTP server content.
• s0: Sensitivity level.

Importance of Correct Labeling: Incorrect contexts can cause SELinux to deny access to resources, even if UNIX permissions allow it. Proper labeling ensures that policies are enforced as intended.

Managing SELinux Modes

Checking the Current Mode

Use getenforce to check the current SELinux mode:

getenforce

Possible Outputs:

• Enforcing
• Permissive
• Disabled

Example:

$ getenforce
Enforcing

Temporarily Changing the Mode

To temporarily switch between enforcing and permissive modes:

sudo setenforce [Enforcing|Permissive|1|0]

• Enforcing or 1: Enables enforcing mode.
• Permissive or 0: Enables permissive mode.

Example:

sudo setenforce 0   # Switch to permissive mode

Verification:

getenforce

Permanently Changing the Mode

Edit the SELinux configuration file /etc/selinux/config:

sudo nano /etc/selinux/config

Change the line:

SELINUX=enforcing

Options:

• enforcing
• permissive
• disabled

Note: Reboot the system to apply changes.

Example:

SELINUX=permissive

Working with SELinux Contexts

Viewing Contexts

List files with their SELinux contexts:

ls -Z /path/to/file

Sample Output:

-rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/passwd

List processes with their contexts:

ps -eZ | grep sshd

Sample Output:

system_u:system_r:sshd_t:s0-s0:c0.c1023  1234 ? 00:00:00 sshd

Using chcon

Change the type of a file:

sudo chcon -t httpd_sys_content_t /var/www/html/index.html

Explanation:

• -t: Specifies the new type.
• Changes are immediate but not persistent across relabels.

Restoring Default Contexts

Use restorecon to reset contexts to their default values:

sudo restorecon -Rv /var/www/html/

• -R: Recursively apply to all files in the directory.
• -v: Verbose output.

Using semanage fcontext for Persistent Changes

Add a context mapping:

sudo semanage fcontext -a -t httpd_sys_content_t "/srv/mywebsite(/.*)?"

Apply the context:

sudo restorecon -Rv /srv/mywebsite/

Explanation:

• semanage fcontext adds a persistent mapping.
• restorecon applies the mapping to existing files.

SELinux Booleans

Booleans allow administrators to modify SELinux policy behavior without writing new policies.

Listing Booleans

List all Booleans and their statuses:

sudo getsebool -a

Filter Booleans:

sudo getsebool -a | grep httpd

Temporarily Changing a Boolean

sudo setsebool httpd_enable_cgi on

Permanently Changing a Boolean

sudo setsebool -P httpd_enable_cgi on

• -P makes the change persistent across reboots.

Common Booleans:

• httpd_can_network_connect: Allows HTTPD scripts and modules to connect to the network.
• ftp_home_dir: Allows FTP to read and write files in user home directories.

SELinux Troubleshooting

Audit Log

• Location: /var/log/audit/audit.log
• Contains: Detailed records of all SELinux denials and other security events.

Access Vector Cache (AVC) Messages

• Contain: Denied access attempts.
• Example Entry:

type=AVC msg=audit(1609459200.123:456): avc:  denied  { read } for  pid=1234 comm="nginx" name="index.html" dev="sda1" ino=56789 scontext=system_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:default_t:s0 tclass=file

ausearch

Search for AVC denials:

sudo ausearch -m avc -ts today

• -m avc: Search for AVC messages.
• -ts today: Start time of today.

sealert

Analyzes SELinux denials and provides recommendations:

sudo sealert -a /var/log/audit/audit.log

Requires the setroubleshoot package.

Common Troubleshooting Steps

I. Identify Denials

Use ausearch or check /var/log/audit/audit.log for recent denials.

II. Understand Denials

Use sealert or audit2why to get explanations.

sudo cat /var/log/audit/audit.log | audit2why

III. Adjust Contexts

Ensure files and directories have correct contexts.

sudo restorecon -Rv /path/to/directory

IV. Modify Booleans

Enable relevant Booleans if necessary.

sudo setsebool -P httpd_can_network_connect on

V. Create Custom Policies

As a last resort, use audit2allow to generate custom policies.

sudo grep nginx /var/log/audit/audit.log | audit2allow -M nginx_custom
sudo semodule -i nginx_custom.pp

Caution: Review custom policies carefully to avoid security risks.

Practical Example: Allowing Nginx to Serve Content from a Custom Directory

You have Nginx installed and want it to serve content from /srv/mywebsite/. However, accessing the site results in a 403 Forbidden error, and SELinux is suspected to be the cause.

1. Verify SELinux Denials

Check for AVC denials related to Nginx:

sudo ausearch -m avc -c nginx

Sample Output:

type=AVC msg=audit(1609459200.123:456): avc:  denied  { open } for  pid=1234 comm="nginx" path="/srv/mywebsite/index.html" dev="sda1" ino=56789 scontext=system_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:default_t:s0 tclass=file

2. Assign the Correct Context

Define the context mapping:

sudo semanage fcontext -a -t httpd_sys_content_t "/srv/mywebsite(/.*)?"

Apply the context:

sudo restorecon -Rv /srv/mywebsite/

3. Verify the Context

ls -Z /srv/mywebsite/

Sample Output:

-rw-r--r--. root root unconfined_u:object_r:httpd_sys_content_t:s0 index.html

4. Check for Remaining Denials

sudo ausearch -m avc -c nginx

• If no denials are found, the issue is resolved.

5. Adjust Booleans if Necessary

If Nginx requires additional permissions (e.g., connecting to the network):

sudo setsebool -P httpd_can_network_connect on

Challenges

1. Research and compare Discretionary Access Control (DAC) and Mandatory Access Control (MAC). Create a document explaining how each is implemented in Linux, with a specific focus on SELinux as an example of MAC. Describe how DAC and MAC contribute to system security, and provide examples of when each control method is applied.
2. Write a short guide on the three SELinux modes: Enforcing, Permissive, and Disabled. For each mode, include scenarios or use cases where it is most suitable, and explain the benefits and potential risks associated with using each mode. Discuss the implications of switching modes on system security and stability.
3. Create a file and directory on a Linux system with SELinux enabled, then change their SELinux contexts using both chcon and semanage fcontext commands. Document the process and explain the differences between temporary and persistent changes to SELinux contexts. Discuss scenarios where modifying the SELinux context is essential, such as configuring web server directories.
4. Simulate a common SELinux issue, like a service being denied access to a directory, and troubleshoot the problem using /var/log/audit/audit.log and sealert. Document your troubleshooting steps, including identifying the source of the issue and suggesting a solution. Reflect on how SELinux logs provide valuable insight into system security.
5. Devise a scenario where a Linux server, such as a web server, is exposed to the internet and at risk of unauthorized access. Create an outline for an SELinux policy that could mitigate these risks. Describe the types of rules and policies you would enforce, and explain how they improve security by restricting services and limiting access to critical files.
6. On a test Linux system, switch between the different SELinux modes—Enforcing, Permissive, and Disabled—and observe the system’s behavior and the logs generated in each mode. Document how each mode impacts system security and performance, and discuss why Enforcing mode is recommended for production environments.
7. Write a basic custom SELinux policy module for a specific application, such as a web server or a custom application. Compile and apply the policy on your Linux system, then test the application to ensure it functions as expected. Document any issues encountered and explain how the policy enhances the security of the application.
8. Analyze audit logs from an SELinux-enabled system and identify policy violations or security anomalies. Propose adjustments to existing SELinux policies or system configurations to resolve these issues, such as refining rules or modifying SELinux booleans. Explain how these changes would prevent similar issues in the future.
9. List and describe common SELinux file types and contexts, such as httpd_sys_content_t and user_home_t. Create a few files with different contexts and discuss the importance of correctly assigning file contexts based on their intended use. Explain how improper contexts can impact system functionality and security.
10. Research the semanage boolean command and list several SELinux booleans commonly used to configure services like HTTP and FTP. Enable and disable specific booleans related to web server security, such as allowing access to the home directory, and observe how they affect system behavior. Document your findings and explain the significance of SELinux booleans for managing service permissions.