osquery is an operating system instrumentation framework for OS X and Linux.
The tools make low-level operating system analytics and monitoring both performant and intuitive.
| Platform | Build status | |||
|---|---|---|---|---|
| OS X 10.9 | | Homepage: | https://osquery.io | |
| OS X 10.10/11 | | Downloads: | https://osquery.io/downloads | |
| CentOS 6.x | | Tables: | https://osquery.io/tables | |
| CentOS 7.x | | Packs: | https://osquery.io/packs | |
| Ubuntu 12.04 | | Guide: | https://osquery.readthedocs.org | |
| Ubuntu 14.04 | |  | https://osquery-slack.herokuapp.com | |
| Ubuntu 16.04 | | |||
| Windows 10 | |
What is osquery?
osquery exposes an operating system as a high-performance relational database. This allows you to write SQL-based queries to explore operating system data. With osquery, SQL tables represent abstract concepts such as running processes, loaded kernel modules, open network connections, browser plugins, hardware events or file hashes.
SQL tables are implemented via a simple plugin and extensions API. A variety of tables already exist and more are being written: https://osquery.io/tables . To best understand the expressiveness that is afforded to you by osquery, consider the following SQL queries:
List the
users : SELECT * FROM users; processes that have a deleted executable: SELECT * FROM processes WHERE on_disk = 0;SELECT DISTINCT processes.name, listening_ports.port, processes.pid
FROM listening_ports JOIN processes USING (pid)
WHERE listening_ports.address = '0.0.0.0';SELECT name, program || program_arguments AS executable
FROM launchd
WHERE (run_at_load = 1 AND keep_alive = 1)
AND (program != '' OR program_arguments != '');SELECT address, mac, COUNT(mac) AS mac_count
FROM arp_cache GROUP BY mac
HAVING count(mac) > 1;SELECT address, mac, mac_count
FROM
(SELECT address, mac, COUNT(mac) AS mac_count FROM arp_cache GROUP BY mac)
WHERE mac_count > 1;- performed on an ad-hoc basis to explore operating system state using the osqueryi shell
- executed via a scheduler to monitor operating system state across a set of hosts
- launched from custom applications using osquery Thrift APIs
Downloads / Install
For latest stable and nightly builds for OS X and Linux (deb/rpm), as well as yum and apt repository information visit https://osquery.io/downloads . For installation information for FreeBSD, which is supported by the osquery community, see the wiki .
Building from source
Building osquery from source is encouraged! Join our developer community by giving us feedback in Github issues or submitting pull requests!
File Integrity Monitoring (FIM)
osquery provides several FIM features too! Just as OS concepts are represented in tabular form, the daemon can track OS events and later expose them in a table. Tables like
file_events or yara_events can be selected to retrieve buffered events. The configuration allows you to organize files and directories for monitoring. Those sets can be paired with lists of YARA signatures or configured for additional monitoring such as access events.
Process and socket auditing
There are several forms of eventing in osquery along with file modifications and accesses. These range from disk mounts, network reconfigurations, hardware attach and detaching, and process starting. For a complete set review the table documentation and look for names with the
_events suffix. Vulnerabilities
Facebook has a bug bounty program that includes osquery. If you find a security vulnerability in osquery, please submit it via the process outlined on that page and do not file a public issue. For more information on finding vulnerabilities in osquery, see a recent blog post about bug-hunting osquery .
Learn more
Read the launch blog post for background on the project. If you're interested in learning more about osquery, visit the users guide and browse our RFC-labeled Github issues. Development and usage discussion is happing in the osquery Slack, grab an invite automatically: https://osquery-slack.herokuapp.com/ !
