Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
openSUSE Leap Documentation › Security Guide › Confining Privileges with AppArmor › Managing Profiled Applications
ContentsContents
Security Guide
  1. About This Guide
  2. 1 Security and Confidentiality
  3. I Authentication
    1. 2 Authentication with PAM
    2. 3 Using NIS
    3. 4 Setting Up Authentication Servers and Clients Using YaST
    4. 5 LDAP—A Directory Service
    5. 6 Network Authentication with Kerberos
    6. 7 Active Directory Support
  4. II Local Security
    1. 8 Configuring Security Settings with YaST
    2. 9 Authorization with PolKit
    3. 10 Access Control Lists in Linux
    4. 11 Encrypting Partitions and Files
    5. 12 Certificate Store
    6. 13 Intrusion Detection with AIDE
  5. III Network Security
    1. 14 X Window System and X Authentication
    2. 15 SSH: Secure Network Operations
    3. 16 Masquerading and Firewalls
    4. 17 Configuring a VPN Server
    5. 18 Managing X.509 Certification
  6. IV Confining Privileges with AppArmor
    1. 19 Introducing AppArmor
    2. 20 Getting Started
    3. 21 Immunizing Programs
    4. 22 Profile Components and Syntax
    5. 23 AppArmor Profile Repositories
    6. 24 Building and Managing Profiles with YaST
    7. 25 Building Profiles from the Command Line
    8. 26 Profiling Your Web Applications Using ChangeHat
    9. 27 Confining Users with pam_apparmor
    10. 28 Managing Profiled Applications
    11. 29 Support
    12. 30 AppArmor Glossary
  7. V SELinux
    1. 31 Configuring SELinux
  8. VI The Linux Audit Framework
    1. 32 Understanding Linux Audit
    2. 33 Setting Up the Linux Audit Framework
    3. 34 Introducing an Audit Rule Set
    4. 35 Useful Resources
  9. A GNU Licenses
Navigation←→
openSUSE Leap Documentation › Security Guide › Confining Privileges with AppArmor › Managing Profiled Applications
Top
←→
Applies to openSUSE Leap 15.0

28 Managing Profiled Applications

28.1 Reacting to Security Event Rejections
28.2 Maintaining Your Security Profiles

After creating profiles and immunizing your applications, openSUSE® Leap becomes more efficient and better protected as long as you perform AppArmor® profile maintenance (which involves analyzing log files, refining your profiles, backing up your set of profiles and keeping it up-to-date). You can deal with these issues before they become a problem by setting up event notification by e-mail, updating profiles from system log entries by running the aa-logprof tool, and dealing with maintenance issues.

28.1 Reacting to Security Event Rejections

When you receive a security event rejection, examine the access violation and determine if that event indicated a threat or was part of normal application behavior. Application-specific knowledge is required to make the determination. If the rejected action is part of normal application behavior, run aa-logprof at the command line.

If the rejected action is not part of normal application behavior, this access should be considered a possible intrusion attempt (that was prevented) and this notification should be passed to the person responsible for security within your organization.

28.2 Maintaining Your Security Profiles

In a production environment, you should plan on maintaining profiles for all of the deployed applications. The security policies are an integral part of your deployment. You should plan on taking steps to back up and restore security policy files, plan for software changes, and allow any needed modification of security policies that your environment dictates.

28.2.1 Backing Up Your Security Profiles

Backing up profiles might save you from having to re-profile all your programs after a disk crash. Also, if profiles are changed, you can easily restore previous settings by using the backed up files.

Back up profiles by copying the profile files to a specified directory.

  1. You should first archive the files into one file. To do this, open a terminal window and enter the following as root: 

    tux > sudo tar zclpf profiles.tgz /etc/apparmor.d

    The simplest method to ensure that your security policy files are regularly backed up is to include the directory /etc/apparmor.d in the list of directories that your backup system archives.

  2. You can also use scp or a file manager like Nautilus to store the files on some kind of storage media, the network, or another computer.

28.2.2 Changing Your Security Profiles

Maintenance of security profiles includes changing them if you decide that your system requires more or less security for its applications. To change your profiles in AppArmor, refer to Section 24.2, “Editing Profiles”.

28.2.3 Introducing New Software into Your Environment

When you add a new application version or patch to your system, you should always update the profile to fit your needs. You have several options, depending on your company's software deployment strategy. You can deploy your patches and upgrades into a test or production environment. The following explains how to do this with each method.

If you intend to deploy a patch or upgrade in a test environment, the best method for updating your profiles is to run aa-logprof in a terminal as root. For detailed instructions, refer to Section 25.7.3.9, “aa-logprof—Scanning the System Log”.

If you intend to deploy a patch or upgrade directly into a production environment, the best method for updating your profiles is to monitor the system frequently to determine if any new rejections should be added to the profile and update as needed using aa-logprof. For detailed instructions, refer to Section 25.7.3.9, “aa-logprof—Scanning the System Log”.

→Chapter 29 Support←Chapter 27 Confining Users with pam_apparmor
Print this page

© 2018 SUSE