Linux in Government: Security Enhanced Linux - The Future is Now
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- Linux Systems Administrator
- Senior Perl Developer
- Technical Support Rep
- New Products
- UX Designer
- Web & UI Developer (JavaScript & j Query)
- Designing Electronics with Linux
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Using Salt Stack and Vagrant for Drupal Development
- Evernote is much more...
47 min 59 sec ago - Reply to comment | Linux Journal
9 hours 33 min ago - Dynamic DNS
10 hours 7 min ago - Reply to comment | Linux Journal
11 hours 5 min ago - Reply to comment | Linux Journal
11 hours 56 min ago - Not free anymore
15 hours 58 min ago - Great
19 hours 45 min ago - Reply to comment | Linux Journal
19 hours 53 min ago - Understanding the Linux Kernel
22 hours 7 min ago - General
1 day 37 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
also - systrace?
I'm also interested in a comparison to systrace. Systrace is what OpenBSD uses - and they are not exactly known for not knowing security. It should also be less intrusive, and less ressource-intensive.
What about the TCO hit because of SELinux?
Dear All (these are just my 2c worth):
While SELinux contributes greatly to the technology side of the coin, itfails to address the economics of security. The litmus test is definitely how many nodes will actually RUN SELinux. However, the classification of why they CANNOT run it is also an important piece of information.
SELinux comes out of National Defense paradigm, namely: Achieve the goal no matter what the cost, because there is (relatively) infinite money and infinite resources. This is not practical for a normal business which has cost constraints.
IMHO SELinux doesn't address vital ROI and TCO concerns. I would've liked to see questions regarding that direction in this interview - and i haven't zipped through the book ;) so i am not sure if the good Author has touched on this topic.
Cheers,
Ahmed
targeted policy solves this
The "targeted" policy which is in Fedora Core 3 and will be in Red Hat Enterprise Linux 4 solves this. It restricts only the daemons that are at most danger (network facing daemons initially but as we progress we will add other daemons to the list). This stops quite a number of attack vectors while having no restrictions on users who login to the system. Of course this means that targeted policy doesn't prevent a local user from attacking the system, but that is a trade-off that the administrator can make for ease of use.
A system running the targeted policy should in most cases be indistinguishable from a non-SE system. The only reported problems of the targeted policy are related to Apache - a daemon that needs protection but is very difficult to write policy for because it's so configurable.
In Fedora Core 3 and Red Hat Enterprise Linux 4 SE Linux is enabled by default and installed with only the targeted policy. In Fedora you can convert the system to "strict" policy after completing the install if you desire better security and are happy to trade-off some ease of use to get it.
The standard support agreements for RHEL will only include targeted policy. This does not prevent you from using strict policy on a RHEL system, but the support agreement does not cover problems with strict policy.
Currently we have no plans to make future releases of either Fedora or RHEL default to strict policy.
Hi, It is a good interview
Hi,
It is a good interview but why there are no questions about alternative of SElinux like grsecurity. It would be interesting to have the opinion of Bill about the advantage/inconvenient of selinux comparing to grsecurity.