SQL powered operating system instrumentation, monitoring, and analytics.
Go to file
2014-10-07 16:00:28 -07:00
.idea Support for CLion C/C++ IDE 2014-09-09 00:10:20 -07:00
CMake checking for libraries 2014-09-23 19:44:58 -07:00
doxygen updating docs header 2014-09-21 14:30:28 -07:00
include/osquery [events] Use pub/sub diction for events 2014-10-03 11:30:51 -07:00
osquery [events] OSX SCNetwork Publisher 2014-10-07 16:00:28 -07:00
third-party@414ab7df32 updating third-party commit hash 2014-09-23 23:21:16 -07:00
tools working osx package maker 2014-10-03 18:09:37 -07:00
.clang-format update the formatting in .clang-format 2014-08-15 12:41:47 -07:00
.gitignore Remove old generated table dir from gitignore 2014-09-27 19:15:27 +00:00
.gitmodules removing lib submodule 2014-09-23 18:50:10 -07:00
.travis.yml Fixed Mac broken build and added building capabilities for Linux 2014-10-02 16:30:29 -07:00
CMakeLists.txt moving make format to cmake 2014-09-23 23:38:23 -07:00
Doxyfile update include paths 2014-09-15 23:52:31 -07:00
Makefile improving the makefile output 2014-09-24 01:28:34 -07:00
osquery.supp Close #79 2014-09-02 12:45:50 -07:00
README.md Update README.md 2014-09-24 21:50:48 -07:00
requirements.txt Initial commit 2014-07-30 17:35:19 -07:00
Vagrantfile Deb package creation for Ubuntu 2014-09-23 17:03:30 -07:00

osquery

osquery is an operating system instrumentation toolchain for *nix based hosts. osquery makes low-level operating system analytics and monitoring both performant and intuitive.

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

SQL tables are implemented via an easily extendable API. A bunch of tables already exist and more are constantly being written. To best understand the expressiveness that is afforded to you by osquery, consider the following SQL queries:

--------------------------------------------------------
-- get the name, pid and attached port of all processes 
-- which are listening on all interfaces
--------------------------------------------------------
SELECT DISTINCT 
  process.name, 
  listening.port, 
  process.pid
FROM processes AS process
JOIN listening_ports AS listening
ON process.pid = listening.pid
WHERE listening.address = '0.0.0.0';
--------------------------------------------------------
-- find every launchdaemon on an OS X host which 
--   * launches an executable when the operating 
--     system starts
--   * keeps the executable running 
-- return the name of the launchdaemon and the full 
-- path (with arguments) of the executable to be ran.
--------------------------------------------------------
SELECT 
  name, 
  program || program_arguments AS executable 
FROM launchd 
WHERE 
  (run_at_load = 'true' AND keep_alive = 'true') 
AND 
  (program != '' OR program_arguments != '');

These queries can be:

  • performed on an ad-hoc basis to explore operating system state
  • executed via a scheduler to monitor operating system state across a distributed set of hosts over time
  • launched from custom applications using osquery APIs

Learn more

If you're interested in learning more about osquery, visit the wiki.