The Section 4.6.3, Summary of Profiling Tools.
is designed to set up Novell AppArmor profiles using the Novell AppArmor profiling tools, aa-genprof (Generate Profile) and aa-logprof (Update Profiles from Learning Mode Log File). For more information about these tools, refer toStop the application before profiling it to ensure that the application start-up is included in the profile. To do this, make sure that the application or daemon is not running.
For example, enter /etc/init.d/PROGRAM stop in a terminal window while logged in as root, replacing PROGRAM with the name of the program to profile.
Start YaST and select
.Enter the name of the application or browse to the location of the program.
Click aa-autodep—Creating Approximate Profiles.
. This runs a Novell AppArmor tool named aa-autodep, which performs a static analysis of the program to profile and loads an approximate profile into Novell AppArmor module. For more information about aa-autodep, refer toThe
window opens.In the background, Novell AppArmor also sets the profile to learning mode. For more information about learning mode, refer to aa-complain—Entering Complain or Learning Mode.
Run the application to profile.
Perform as many of the application functions as possible so learning mode can log the files and directories to which the program requires access to function properly. Be sure to include restarting and stopping the program in the exercised functions. AppArmor needs to handle these events as well as any other program function.
Click
to parse the learning mode log files. This generates a series of questions that you must answer to guide the wizard in generating the security profile.If requests to add hats appear, proceed to Section 5.0, Profiling Your Web Applications Using ChangeHat.
The questions fall into two categories:
A resource is requested by a profiled program that is not in the profile (see Figure 3-1). Allow or deny access to a specific resource.
A program is executed by the profiled program and the security domain transition has not been defined (see Figure 3-2). Define execute permissions for an entry.
Each of these cases results in a series of questions that you must answer to add the resource to the profile or to add the program into the profile. The following two figures show an example of each case. Subsequent steps describe your options in answering these questions.
NOTE: Varying Processing Options
Not all of the options introduced below are always present. The options displayed depend on the type of entry processed.
Figure 3-1 Learning Mode Exception: Controlling Access to Specific Resources
Figure 3-2 Learning Mode Exception: Defining Execute Permissions for an Entry
The Figure 3-1) or requires you to define execute permissions for entries (as seen in Figure 3-2).
begins suggesting directory path entries that have been accessed by the application you are profiling (as seen inFor Learning Mode Exception: Controlling Access to Specific Resources: From the following options, select the one that satisfies the request for access, which could be a suggested include, a particular globbed version of the path, or the actual pathname. Note that all of these options are not always available.
The section of a Novell AppArmor profile that refers to an include file. Include files give access permissions for programs. By using an include, you can give the program access to directory paths or files that are also required by other programs. Using includes can reduce the size of a profile. It is good practice to select includes when suggested.
Accessed by clicking Section 4.7, Pathnames and Globbing.
. For information about globbing syntax, refer toLiteral path that the program needs to access to run properly.
After you select a directory path, process it as an entry into the Novell AppArmor profile by clicking
or . If you are not satisfied with the directory path entry as it is displayed, you can also or it.The following options are available to process the learning mode entries and build the profile:
Grant the program access to the specified directory path entries. The Section 4.8, File Permission Access Modes.
suggests file permission access. For more information about this, refer toClick
to prevent the program from accessing the specified paths.Clicking this modifies the directory path (by using wild cards) to include all files in the suggested directory. Double-clicking it grants access to all files and subdirectories beneath the one shown.
For more information about globbing syntax, refer to Section 4.7, Pathnames and Globbing.
Modify the original directory path while retaining the filename extension. A single click causes /etc/apache2/file.ext to become /etc/apache2/*.ext, adding the wild card (asterisk) in place of the filename. This allows the program to access all files in the suggested directories that end with the .ext extension. When you double-click it, access is granted to all files (with the particular extension) and subdirectories beneath the one shown.
Edit the highlighted line. The new (edited) line appears at the bottom of the list.
Abort aa-logprof, losing all rule changes entered so far and leaving all profiles unmodified.
Close aa-logprof, saving all rule changes entered so far and modifying all profiles.
Click
or for each learning mode entry. These help build the Novell AppArmor profile.NOTE: The number of learning mode entries corresponds to the complexity of the application.
For Learning Mode Exception: Defining Execute Permissions for an Entry: From the following options, select the one that satisfies the request for access. For detailed information about the options available, refer to Section 4.8, File Permission Access Modes.
Stay in the same security profile (parent's profile).
Require a separate profile to exist for the executed program. When selecting this option, also select whether AppArmor should sanitize the environment when switching profiles by removing certain environment variables that can modify the execution behavior of the child process. Unless these variables are absolutely required to properly execute the child process, always choose the more secure, sanitized option.
Execute the program without a security profile. When prompted, let AppArmor sanitize the environment to avoid adding security risks by inheriting certain environment variables from the parent process.
WARNING:Unless absolutely necessary, do not run unconfined. Choosing the
option executes the new program without any protection from AppArmor.Click
to prevent the program from accessing the specified paths.Abort aa-logprof, losing all rule changes entered so far and leaving all profiles unmodified.
Close aa-logprof, saving all rule changes entered so far and modifying all profiles.
Repeat the previous steps if you need to execute more functionality of the application.
When you are done, click
. In the following pop-up, click to exit the . The profile is saved and loaded into the Novell AppArmor module.