Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Reusable process config for FAA #246

Open
ltk opened this issue Feb 10, 2025 · 1 comment
Open

Feature Request: Reusable process config for FAA #246

ltk opened this issue Feb 10, 2025 · 1 comment
Labels
enhancement New feature or request file access authorization Issues related to file access authorization

Comments

@ltk
Copy link

ltk commented Feb 10, 2025

When configuring FAA, I often find that each Processes config ends up being a list of 1) the same handful of signing-ids for specific Apple binaries, 2) the same handful of signing-ids for some internal tool binaries, and 3) and one or more rules that are actually specific to the files being protected (e.g. Google's team ID for Chrome data). This makes managing a large number of watch items laborious and error-prone.

It'd be quite nice to be able to centralize the definition of 1 and 2 and allow their use in any watch item with config like:

[
  ProcessGroups: [
    [
      Name: "PlatformAllowlist",
      Processes: [
        [
          PlatformBinary: true,
          SigningID: "com.apple.apfsd",
        ],
        [
          PlatformBinary: true,
          SigningID: "com.apple.whatever",
        ],
      ]
    ],
    [
      Name: "InternalAllowlist",
      Processes: [
        [
          TeamID: "<our team id>",
          SigningID: "com.something.somewhere",
        ],
        [
          TeamID: "<our team id>",
          SigningID: "com.something.elsewhere",
        ],
      ]
    ]
  ],
  WatchItems: [
    [
      Path: "/Users/*/Library/Application Support/Google/*/*/Cookies",
      Processes: [
        [ProcessGroup: "PlatformAllowlist"],
        [ProcessGroup: "InternalAllowlist"],
        [TeamID: "<google's team id>"]
      ]
    ]
  ]
]
@mlw mlw added enhancement New feature or request file access authorization Issues related to file access authorization labels Feb 10, 2025
@pmarkowsky
Copy link
Contributor

It's definitely an interesting idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request file access authorization Issues related to file access authorization
Projects
None yet
Development

No branches or pull requests

3 participants