# osquery office hours 2022-06-07
YouTube Link: https://www.youtube.com/watch?v=Lxa8s54jdA8
## Announcements and Highlights since the last meeting
* 5.3.0 wsa cut
* In q3, ToB is likely to work on windows arm support
* Sharvil might be giving a talk on endpointsecurity and osquery at macdevops
* WWDC22 Announced some new ES things. These are some interesting looking events. Might be an Apple tool to explore. TBD!
## Any Questions / Issues / PRs people want to discuss?
The intent of this section is to provide a clear time for community members to bring up _anything_.
Broad questions? Bugs? Deployment questions? Blocked PRs?
Can we mark it as stable?
There's a known issues in the tests, but this is testing only. (https://github.com/osquery/osquery/pull/7621)
Anyone tested it?
* Sharvil on a couple machines
* Zach will try to push to Fleet's Edge channel
* seph will try to push to Kolide's beta channel
## Watcher for disk
Should osquery measure the disk usage in terms of IOPS or write/read throughput? Some queries will do a lot of rocks access, which will, in turn, cause a lot of disk IO.
Alessandro is concerned that this is an odd direction:
* If one is interested in data integrity, than you have to take the diskIO
* If one is interested in performance, than we should explore alternate DBs (Like the PR from packetzero from a couple years ago)
Alessandro thinks that the watchdog is incompatable with rocks DB and integrity.
Some additional questions about whether it's meaningful to blocklist queries, if the issue is coming from an event stream.
And discussion about performance vs integrity tradeoffs around rocksDB and other storage engines.
Discussion about whether there are visible metrics about what is causing disk IO.
* Maybe, but it probably requires a lot of knowledge
* There's the `events` table, but that's very coarse
* translating events to actual diskio requires specialized knowledge
* connecting scheduled queries to to events, also requires local knowlege
* Let alone additional disk load from things like hashing your filesystem
* and distributed queries
## Deprecate the foreign tables concept
Native are tables that have an implementation on the platform you're on. Foriegn tables stubs for the tables that are only there are other platforms.
* Currently, this is broken. (Probably when we moved off `buck`).
* It requires a lot of additional linking
* Probably doesn't work with extended schemas
Might be for some internal Facebook use case? That's sort of the implication from the commit https://github.com/osquery/osquery/commit/e79d0ae5ce5ec13962fb9bef4063e7328e08f953
Given that it's already broken, there's some support for just removing it.
Some discussion about what might be interesting to replace it. Maybe a use case is to make it simpler to write queries to handle tables that might not be present. Say if an extension was missing. This use case isn't really clear yet, nor is an approach.
## New macOS features at WWDC this week for osquery
* New event types for EndpointSecurity: authentication, login sessions, screensharing connections, and XProtect detections
* Noted that the XProtect table in osquery has been "broken" since macOS stopped storing detection events to the filesystem [#6588](https://github.com/osquery/osquery/issues/6588) and collecting XProtect in an evented table would re-enable this osquery use-case
Discussion about notarization and codesignging, and what the non-macOS tools are for this:
* https://github.com/indygreg/PyOxidizer/tree/main/apple-codesign (good blog posts)
* Apple's java transporter
## Code Reviews
* [macOS EndpointSecurity based FIM](https://github.com/osquery/osquery/pull/7594)
* [macOS `password_policy`](https://github.com/osquery/osquery/pull/7579)
* [macOS Unified Access Logging (UAL)](https://github.com/osquery/osquery/pull/7598)
* [macOS kernel_panics table](https://github.com/osquery/osquery/pull/7585) (Not a big PR to review, test files are provided)
* We are not affected by a reported OpenSSL bug https://github.com/osquery/osquery/issues/7616
* Two sqlite reports -- https://github.com/osquery/osquery/issues/7617
* There's a memory access violation in sqlite bad databases. Might be vulnerable in ATC
* Probably not vulnerable to the other
* libarchive, uncompressed function. Probably not affected https://github.com/osquery/osquery/issues/7618
## Look at old PRs
_(If there's time, we've been trying to re-visit old PRs)_
[Reverse Sorted List of PRs](https://github.com/osquery/osquery/pulls?q=is%3Apr+is%3Aopen+sort%3Acreated-asc)