Configuring the allow list
From the Security page, you can configure File Access Policy Daemon (fapolicyd) for a specific Red Hat Enterprise Linux® Server or SUSE Linux Enterprise Server endpoint.
fapolicyd is a user-space daemon that determines access rights for files based on a
trust database and file or process attributes. It can be used to either allow list or deny
list file access and execution.
fapolicyd is not included with PowerSC. You must first install it before you can use it with PowerSC GUI.
The three possible installation scenarios are described in
Table 1.
| fapolicyd status | Procedure |
|---|---|
| fapolicyd is not already installed on the PowerSC GUI agent | Install fapolicyd as described in this section. |
| fapolicyd is already running on the PowerSC GUI agent. | You must configure fapolicyd to allow the PowerSC GUI agent
to execute. To do this:
|
| fapolicyd is already running, and the system is both an PowerSC GUI agent and the PowerSC GUI server. This is a limited use case most often found in test environments. | You must configure fapolicyd to allow the PowerSC GUI agent
and PowerSC GUI server to execute. To do this:
|
You can use the PowerSC GUI to configure fapolicyd on PowerSC GUI agents that are running Red Hat Enterprise Linux Server or SUSE Linux Enterprise Server.
When fapolicyd is configured, applications that are unknown by the reputation source are not
allowed to execute.
Important: Keep the following points in
mind if you use the PowerSC GUI to configure fapolicyd:
- PowerSC GUI is not a replacement configuration tool for fapolicyd. See File Access Policy Daemon (fapolicyd) and the fapolicyd man page for complete information about fapolicyd.
- fapolicyd is a powerful application. Although fapolicyd does not prevent root access to the system, it is possible to miss-configure fapolicyd in such a way as to leave the system inaccessible or unusable by other users. Therefore, it is recommended that you first implement and test fapolicyd on an PowerSC GUI agent that is not in production use.
- By default, executable files that are included in the distribution are trusted through a rpmdb backend that generates a list of trusted files from the RPM databases.
To configure the allow list, perform the following steps:
Important: If you receive unexpected fapolicyd events for executable files that
should be allowed, edit the allowed file list as described in Editing the file list.
As an alternative, you can also use the
fapolicyd-cli -f add file command to add the
executable file to the trusted list, and run the fapolicyd-cli -u command
to perform an update of the trust database.