Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Sign up!
EnGarde Community
What is the most important Linux security technology?
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Latest Newsletters
Linux Security Week: March 30th, 2015
Linux Advisory Watch: March 27th, 2015
LinuxSecurity Newsletters
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

Think before deploying Security-Enhanced Linux in RHEL 4 Print E-mail
User Rating:      How can I rate this item?
Source: SearchEnterpriseLinux - Posted by Pax Dickinson   
Host Security One of the most exciting new features in RHEL v.4 is the implementation of Security-Enhanced Linux (SELinux). In this tip, we'll look at how you can use it to beef up system security.

SELinux is an open source project sponsored by the National Security Agency, to help implement mandatory access control. It is a subsystem which provides a much more secure framework to Linux, then can be achieved from the operating systems level. It implements mandatory access controls that give you finer granularity in terms of security measures and is made up of both kernel and user-space components.

In SELinux, privileges are specified rather then relying on the typical Unix/Linux method of doing things, which is by user and group. This is done by using role based access controls. The two common roles are the user_r role and the system_r, for system administrators.

Be forewarned, if you are have servers (Web or DNS) that are exposed to the Internet, then one should look very strongly into how SELinux might help. If you are just running things like Oracle servers internally, with no external access, you may not want to go through the trouble, as there is a lot to learn and more to do. One might even need a special type security type administrator, as security will no longer just be the domain of the user that handles their files alone, it could be managed centrally by this administrator. If you use Linux as your firewall, think about putting it here as well. The key word here is think before you deploy.

Read this full article at SearchEnterpriseLinux

Only registered users can write comments.
Please login or register.

Powered by AkoComment!

< Prev   Next >


Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2015 Guardian Digital, Inc. All rights reserved.