858915e195
The previous PR (osquery/osquery#6832) was not enough to cover all type of changes to the inputs of the generation of the amalgamation file. The previous PR was only fixing the case where a spec file would change (it's mtime would be newer than the output, to be specific), but not if the dependency list itself would change. So if a new spec file was added or one was removed, it would not rerun. Moreover, with build systems that are not Ninja, any generated artifact that due to a config change is not generated anymore, will remain in the build folder, affecting the amalgamation file generation. Specifically if a table is disabled and its .cpp is not generated anymore, but previously it was generated, the amalgamate script will still pick it up because it doesn't receive a list of files to use, but uses the content of a folder. Finally, better express the dependency of the amalgamation file, so that it depends on the output of the targets/commands that generate the table source code, not the spec files (which are already input/dependency of the custom commands generating the tables source code) and not the tables source code generating target names (which would only express the need to run those targets before the amalgamation file generation, not the need to rerun the generation). |
||
---|---|---|
.github | ||
cmake | ||
docs | ||
external | ||
libraries | ||
osquery | ||
packs | ||
plugins | ||
specs | ||
tests | ||
tools | ||
.artifactignore | ||
.clang-format | ||
.gitignore | ||
.gitmodules | ||
.readthedocs.yml | ||
.watchmanconfig | ||
azure-pipelines.yml | ||
CHANGELOG.md | ||
CMakeLists.txt | ||
CODE_OF_CONDUCT.md | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
Doxyfile | ||
LICENSE | ||
LICENSE-Apache-2.0 | ||
LICENSE-GPL-2.0 | ||
mkdocs.yml | ||
README.md | ||
SECURITY.md | ||
SUPPORT.md | ||
Vagrantfile |
osquery
osquery is a SQL powered operating system instrumentation, monitoring, and analytics framework.
Available for Linux, macOS, Windows, and FreeBSD.
Information and resources
- Homepage: https://osquery.io
- Downloads: https://osquery.io/downloads
- Documentation: https://osquery.readthedocs.org
- Stack Overflow: https://stackoverflow.com/questions/tagged/osquery
- Table Schema: https://osquery.io/schema
- Query Packs: https://osquery.io/packs
- Slack: Request an auto-invite!
- Build Status:
- CII Best Practices:
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.
Learn more
The osquery documentation is available online. Documentation for older releases can be found by version number, as well.
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 here!