3 ms·
Thank you for the reply; however, I am still having a hard time understanding how exactly Osquery works under the hood. How does it communicate with other hosts
by usrme 9y ago
Thank you for the reply; however, I am still having a hard time understanding how exactly Osquery works under the hood. How does it communicate with other hosts? With what does it query for information once it reaches a remote node? What kind of overhead does it have in terms of network transfer when querying? Maybe I am completely off base and am mistaking how this works... Is Osquery set up on every individual host and I query for that information remotely using whatever tools I have at my disposal?
- fiorix 9y agoYou can configure osquery to execute periodic queries (scheduled queries) of all kinds: computing md5 of your binaries and other files, taking a snapshot of sockets/connections per process, and so on. By default, osquery uses glog, which means it'll output the results to a local file that you can ship anywhere you want. There's also logging plugins to help you push the results of scheduled queries to other systems. Once you have that data flowing through your pipelines you can start doing security/anomaly detection on things.
- anonymousDan 9y agoBut do you need an installation of osquery on the remote machines too? Or some kind of remote agent? Or does it just try to login to each remote machine over e.g. SSH?
- coredog64 9y agoIt's a remote agent. If you want the scheduled execution, you install the program and configure it internally to run on a schedule. I haven't finished the work yet, but my employer will be feeding the log results into our ELK stack. There are other frontends like 'doorman' which allow for ad hoc queries. That is a little more work to stand up.