[BUG] Invalid User Subject in Postman fapolicyd Ruleset

Component:

Security Hardening Baseline / fapolicyd Rules Templates

Severity:

High (Causes fapolicyd.service to crash on startup/reload)

Symptom:

When compiling the master rules database, the parser errors out with an unknown user exception:

    fapolicyd[XXXXX]: [ ERROR ]: user all is unknown
    fapolicyd[XXXXX]: [ ERROR ]: Subject is missing in line 20
    systemd[1]: fapolicyd.service: Control process exited, code=exited, status=1/FAILURE

Root Cause:

The rule attempts to match all users by assigning uid=all. The fapolicyd engine interprets uid= as an explicit lookup for a literal username or ID in /etc/passwd. Because no user named "all" exists, the engine flags it as a fatal missing subject error.

Broken Syntax Example:

    allow perm=any uid=all : dir=/opt/Postman/

Remediation Fix:

To apply a rule globally to all users, remove the uid= prefix entirely and use the native wildcard keyword all. Update the source rule file to:

    allow perm=any all : dir=/opt/Postman/

Find the source fapolicyd rules file for the Postman installation and inspect the rule matching /opt/Postman/. Replace the invalid uid=all form with the native all subject syntax shown in the issue. Compile the master rules database and verify that fapolicyd.service starts or reloads without the unknown-user and missing-subject errors.