osquery / osquery/osquery

Table Request: Content Filter Exclusions (maybe)

Open
#6,825 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

macOS Big Sur virtual tables wishlist
Dominant language
C++
Stars
23.6k
Forks
2.6k
Avg merge
6d 7h
Merged PRs (30d)
14

Description

In Big Sur, Apple started shipping exclusions to the firewall tooling. See https://medium.com/tripmode/apple-started-hiding-the-traffic-of-its-own-mac-apps-9dc83c5a9c5b (and countless other sources)

This is represented by the plist /System/Library/Frameworks/NetworkExtension.framework/Versions/A/Resources/Info.plist and may or may not have an API call.

This is the kind of information I might expect in osquery, but it's also a simple plist to read, so I don't really feel a compelling need for a table. Thoughts?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting /System/Library/Frameworks/NetworkExtension.framework/Versions/A/Resources/Info.plist on macOS Big Sur and determine whether a public API exposes the same exclusions. Then establish whether osquery should provide a table and define the expected data and validation before identifying implementation and test locations.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos
Domain
operating-systems, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.