AppArmor
Upcoming SlideShare
Loading in...5
×
 

AppArmor

on

  • 935 views

 

Statistics

Views

Total Views
935
Views on SlideShare
935
Embed Views
0

Actions

Likes
0
Downloads
6
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

AppArmor AppArmor Presentation Transcript

  • Code 10 First Class - Install and Use AppArmor Luis González Linux Impact Team [email_address]
  • AppArmor
    • AppArmor Concepts
      • AppArmor Overview
      • Lab: Installation of AppArmor
      • Lab: Activate AppArmor
    • Working with AppArmor
      • AppArmor Profiles
      • Profile States
      • Creation of Profiles
      • Lab: Create a Profile with YaST GUI
      • Lab: Create a Profile on the Command Line
  • AppArmor Overview
  • AppArmor Overview
    • AppArmor uses the Linux Security Modules Framework (LSM) to grant or deny access to system resources.
    • Access-control decisions are made in kernel space, so they are mandatory and cannot be bypassed by any user or application
  • AppArmor Overview
  • Benefits of AppArmor
    • AppArmor is an access control system for network services. Using AppArmor you can specify which files each program is allowed to read, write or execute
    • AppArmor is a host intrusion prevention system which protects SUSE Linux applications
    • AppArmor sets up a predefined collection of applications profiles to protect all the standard Linux services (Postfix, OpenSSH, Apache, ...)
    • Easy creation of new profiles for other programs or services
  • Benefits of AppArmor
    • Which Programs can be Protected?
      • General recommendation: Protect every program that mediates privileges.
      • Network services: Every program (server and client) with open network ports should be protected.
      • Cron jobs: Some cron jobs run with privileges (e.g. root) and can be protected.
      • Web applications: CGI scripts, PHP scripts, Java applets, ....
    • The main advantage of AppArmor is the simple configuration. The configuration of SELinux, which has similar goals, is far more time-consuming
  • AppArmor Profiles
      • AppArmor Profiles
    • At the heart of AppArmor are the application profiles. For each application you want to protect you can create a separate profile. A profile defines security rules for applications.
    • A profile contains:
      • The full path to the program that is confined.
      • With the #include directive you can pull in components of other profiles
      • Add POSIX capabilities with the capability statement. You can get more information on linux capabilities with: man 7 capabilities
      • A path entry, specifying which part of the filesystem the program can access. The standard Linux permissions r, w and x can be used here. See man 5 subdomain.d
      • AppArmor Profiles
  • Profile States
      • Profile States
    • An AppArmor profile can be in one of two states:
      • 1. complain (learning mode) The profile exists but rule violations are only reported and logged. This mode is especially useful in the developmental phase of new profiles. You can check whether your program is running without producing warnings in the logfile.
      • 2. enforce Rules are enforced. Violations of rules are not permitted.
      • Profile States
    • There is an easy way to see all loaded profiles and their corresponding state.
    • AppArmor creates a pseudo filesystem in /sys/kernel/security/apparmor where you can get information about the profile states:
    • cat /sys/kernel/security/apparmor/profiles
  • Creation of Profiles
      • Creation of Profiles
    • YaST GUI:
      • Add a profile using the Wizard
      • Or manually add a profile
      • Creation of Profiles
    • Command Line Tools:
      • complain Sets a profile into complain mode. Only Violations of rules will be reported
      • enforce Sets a profile to enforce mode . Violations of rules are no longer permitted
      • unconfined Find processes that are listening for network connections and reports whether they are protected by AppArmor
      • genprof Generates a AppArmor profile
      • autodep Generates a profile skeleton for a program. It will be set to complain mode
  • Labs
  • Lab: Installation of AppArmor
    • Know which software packages are needed by AppArmor
    • Learn how to install all AppArmor packages
  • Lab: Activate AppArmor
    • After all AppArmor components have been installed you need to activate AppArmor on your SUSE server
    • After a default installation, AppArmor should already be activated, but you should know how to activate or deactivate it
      • Lab: Create a Profile With YaST GUI
    • Learn how to create an AppArmor Profile with YaST
      • Lab: Create a Profile on the Command Line
    • Know the most important command line tools of AppArmor
  •  
    • Unpublished Work of Novell, Inc. All Rights Reserved.
    • This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.
    • General Disclaimer
    • This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. Novell, Inc., makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.