SQL powered operating system instrumentation, monitoring, and analytics.
Go to file
Teddy Reed c964db2a49
logging: Change logNumericsAsNumbers to numerics and add docs (#6002)
This is an API change for the format of logged events.
The top-level log field "logNumericsAsNumbers" was introduced to help
migrate from string-encoded numerics to JSON numbers.

This change updates the field to be "numerics", updates the flag to
conform to flag naming conventions, and documents the expectation.
2019-11-09 13:29:14 -05:00
.github Add New_Release GitHub issue template (#5979) 2019-11-01 14:36:05 -04:00
cmake formatting functions py2->3 (PR #6011) 2019-11-09 01:26:45 +01:00
docs logging: Change logNumericsAsNumbers to numerics and add docs (#6002) 2019-11-09 13:29:14 -05:00
external CMake: Improvements to extensions support (#5970) 2019-10-31 19:17:28 +01:00
libraries Migrate glog and gflags to source build on macOS and Windows (#5902) 2019-11-08 23:06:09 -05:00
mode Upgrade Python tools to Python3 (#5846) 2019-10-05 10:30:10 -04:00
osquery logging: Change logNumericsAsNumbers to numerics and add docs (#6002) 2019-11-09 13:29:14 -05:00
packs Adding OSX Malware SearchAwesome to osx-attacks (#5713) 2019-08-22 08:55:14 -04:00
plugins logging: Change logNumericsAsNumbers to numerics and add docs (#6002) 2019-11-09 13:29:14 -05:00
specs process_open_sockets/windows: add state column (#5927) 2019-11-01 01:17:24 +01:00
tests Improve deb_packages test (#5980) 2019-11-01 10:36:42 -04:00
third-party tests: Add test for JSON exponent parsing (#5941) 2019-10-29 02:16:15 +01:00
tools formatting functions py2->3 (PR #6011) 2019-11-09 01:26:45 +01:00
.buckconfig Move build system to BUCK 2018-12-07 16:12:35 +00:00
.clang-format format: Remove Cpp restriction (#3521) 2017-08-02 10:32:12 -07:00
.gitignore Restore extension SDK support to osquery 4.x (#5851) 2019-10-18 18:45:20 -04:00
.gitmodules Refactor third-party libraries to build from source on Linux (#5706) 2019-08-30 16:25:19 +02:00
.watchmanconfig watcher: Do not initialize the config in watcher (#3403) 2017-06-13 17:26:34 -07:00
azure-pipelines.yml formatting functions py2->3 (PR #6011) 2019-11-09 01:26:45 +01:00
CHANGELOG.md Typo fixes in v4.1.0 CHANGELOG (#5998) 2019-11-05 08:15:34 -05:00
CMakeLists.txt Migrate glibc from "facebook" dependencies (#5900) 2019-10-31 19:08:09 -04:00
CODE_OF_CONDUCT.md Point CODE_OF_CONDUCT at osquery/foundation (#5721) 2019-08-27 10:25:44 -04:00
CODEOWNERS Initial codeowners (#5603) 2019-06-26 09:14:13 -04:00
CONTRIBUTING.md docs: Nitpicks to improve new-user experience (#5912) 2019-10-21 22:41:04 -04:00
Doxyfile Add clang-format rules from 3.6 (#2360) 2016-08-15 01:33:17 -07:00
LICENSE Clarify licensing (#4792) 2018-08-02 19:26:40 +01:00
LICENSE-Apache-2.0 Clarify licensing (#4792) 2018-08-02 19:26:40 +01:00
LICENSE-GPL-2.0 Clarify licensing (#4792) 2018-08-02 19:26:40 +01:00
mkdocs.yml docs: Update ReadTheDocs with new build docs (#5708) 2019-08-21 21:27:00 -04:00
README.md docs: Add the Coverity scan build status (#5783) 2019-09-09 22:18:59 +02:00
SECURITY.md security: Update SECURITY.md with recent merges (#3787) 2017-10-04 17:28:06 -07:00
SUPPORT.md Improve SUPPORT.md (#4835) 2018-08-08 12:18:57 +01:00
Vagrantfile Prune Vagrant boxes and fix AWS support (#5819) 2019-09-21 21:02:12 -04:00

osquery

osquery logo

osquery is a SQL powered operating system instrumentation, monitoring, and analytics framework.
Available for Linux, macOS, Windows, and FreeBSD.

Information and resources

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/schema. To best understand the expressiveness that is afforded to you by osquery, consider the following SQL queries:

List the users:

SELECT * FROM users;

Check the processes that have a deleted executable:

SELECT * FROM processes WHERE on_disk = 0;

Get the process name, port, and PID, for processes listening on all interfaces:

SELECT DISTINCT processes.name, listening_ports.port, processes.pid
  FROM listening_ports JOIN processes USING (pid)
  WHERE listening_ports.address = '0.0.0.0';

Find every macOS LaunchDaemon that launches an executable and keeps it running:

SELECT name, program || program_arguments AS executable
  FROM launchd
  WHERE (run_at_load = 1 AND keep_alive = 1)
  AND (program != '' OR program_arguments != '');

Check for ARP anomalies from the host's perspective:

SELECT address, mac, COUNT(mac) AS mac_count
  FROM arp_cache GROUP BY mac
  HAVING count(mac) > 1;

Alternatively, you could also use a SQL sub-query to accomplish the same result:

SELECT address, mac, mac_count
  FROM
    (SELECT address, mac, COUNT(mac) AS mac_count FROM arp_cache GROUP BY mac)
  WHERE mac_count > 1;

These queries can be:

  • 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

Download & Install

To download the latest stable builds and for repository information and installation instructions visit https://osquery.io/downloads.

Build from source

Building osquery from source is encouraged! Check out our build guide. Also check out our contributing guide and join the community on Slack.

License

By contributing to osquery you agree that your contributions will be licensed as defined on the LICENSE file.

Vulnerabilities

We keep track of security announcements in our tagged version release notes on GitHub. We aggregate these into SECURITY.md too.

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 our blog post Bug Hunting osquery.

Learn more

If you're interested in learning more about osquery read the launch blog post for background on the project, visit the users guide.

Development and usage discussion is happening in the osquery Slack, grab an invite automatically here!