fleet

module
v0.0.0-...-98a7958 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Nov 5, 2020 License: MIT

README

Fleet is Retired

This notice is to inform you that on Wednesday, November 4th, 2020 Kolide has officially retired Fleet. This repository will be left up in an archived state for posterity, and to assist existing Fleet users.

Please refer to the FAQ below for additional information including migration options.

FAQ

Q: What was Kolide Fleet?

Kolide Fleet was an open-source Osquery Fleet Manager written in Go and Javascript.

Q: What does retiring entail?

Effective immediately, Kolide will no longer promote, endorse, support, or update Fleet. Any infrastructure outside of Github supporting downloads or packages will also be retired.

Since we will not be updating Fleet with any security patches or accepting bug bounty reports, it is important that you find a suitable alternative right away.

Q: Is Kolide retiring Kolide Launcher?

No. Kolide Launcher is a major component of our SaaS product, and we fervently believe in keeping the endpoint agent technology open-source.

Q: Why is Kolide retiring Fleet?

We are proud and humbled by all of the organizations using Fleet today. We think it’s a great solution to monitor server-based infrastructure using Osquery. We recognize many organizations depend on Fleet so retiring it was not a decision we took lightly.

Since 2019, Kolide has found success building a SaaS endpoint security product around the philosophy of User Focused Security. This philosophy is about building a foundation of trust between the security team and the end-users of a given organization.

When Fleet is used to obtain visibility on end-user devices, it is not software that enables an honest and accountable relationship between the security team and the end-users who are subject to the data collection Fleet enables.

Specifically, Fleet allows administrators to vacuum up large quantities of end-user data without providing those users with any visibility or tools to understand or control that process. Fleet does not hold security practitioners accountable for the data they collect or how it will be ultimately used. In fact, many folks reach out to us asking how to use Fleet and Osquery together to collect things like web browser history, device geolocation, and other personal information from devices. These objectives are antithetical to our company’s values. At Kolide these values are non-negotiable and we no longer want to enable software under our name and branding that enables those use-cases.

While we could change Fleet to meet these ideals and be compatible with our philosophy, we would rather invest that same energy and resources toward improving our SaaS app.

Given the facts above, we have decided it is in our best interest to retire the project and thoroughly explain our rationale.

Q: Why retire Fleet now?

Kolide has not substantially contributed to Fleet for over 2 years. Recently, an active contributor reached out to let us know they were planning on forking it and asked for our blessing. This recent reach-out caused us to re-evaluate if it’s something Kolide wants to continue to directly invest in or endorse.

After going through that exercise, we determined that Fleet was built by a different Kolide; one that embodied different values and had different goals. Due to the mismatch in ideals and the opportunity to distance ourselves from Fleet, we have decided now is the best time to retire the project and let the community decide on a suitable fork to follow.

Q: What should I use instead of Fleet?

Kolide no longer endorses the use of Fleet for monitoring end-user devices.

If you are looking to get additional visibility on end-user devices and want to do it honestly, you should check out Kolide K2. It’s a refreshing take on how to use technologies like Osquery and Slack to achieve the security team’s goals while simultaneously respecting end-users and their privacy.

If you use Fleet to monitor servers and are looking for a direct migration path https://github.com/fleetdm/fleet appears to be the first of many promising forks.

We will update this space with forks that best support that use case.

Also, since Fleet is open source under the permissive MIT license, you are of course free to fork it and build your own version. Our only ask is you do not associate Kolide or our branding as a means of promoting or endorsing any derivative of Fleet you create.


original readme below...

Kolide Fleet CircleCI Go Report Card

Fleet is the most widely used open-source osquery Fleet manager. Deploying osquery with Fleet enables live queries, and effective management of osquery infrastructure.

Documentation for Fleet can be found on GitHub.

Fleet Dashboard Screenshot of dashboard

Live Queries Screenshot of live query interface

Scheduled Query/Pack Editor Screenshot of pack editor

Using Fleet

The CLI

If you're interested in learning about the fleetctl CLI and flexible osquery deployment file format, see the CLI Documentation.

Deploying Osquery and Fleet

Resources for deploying osquery to hosts, deploying the Fleet server, installing Fleet's infrastructure dependencies, etc. can all be found in the Infrastructure Documentation.

Accessing The Fleet API

If you are interested in accessing the Fleet REST API in order to programmatically interact with your osquery installation, please see the API Documentation.

The Web Dashboard

Information about using the Kolide web dashboard can be found in the Dashboard Documentation.

Developing Fleet

Development Documentation

If you're interested in interacting with the Kolide source code, you will find information on modifying and building the code in the Development Documentation.

If you have any questions, please create a GitHub Issue.

Community

Chat

Please join us in the #kolide channel on Osquery Slack.

Community Projects

Below are some projects created by Kolide community members. Please submit a pull request if you'd like your project featured.

Kolide SaaS

Looking for the quickest way to try out osquery on your fleet? Not sure which queries to run? Don't want to manage your own data pipeline?

Try our osquery SaaS platform providing insights, alerting, fleet management and user-driven security tools. We also support advanced aggregation of osquery results for power users. Get started with your 30-day free trial today.

Rube

Directories

Path Synopsis
cmd
server
contexts/host
Package host enables setting and reading the current host from context
Package host enables setting and reading the current host from context
contexts/token
Package token enables setting and reading authentication token contexts
Package token enables setting and reading authentication token contexts
contexts/viewer
Package viewer enables setting and reading the current user contexts
Package viewer enables setting and reading the current user contexts
health
Package health adds methods for checking the health of service dependencies.
Package health adds methods for checking the health of service dependencies.
launcher
Package launcher provides a gRPC server to handle launcher requests.
Package launcher provides a gRPC server to handle launcher requests.
live_query
package live_query implements an interface for storing and retrieving live queries.
package live_query implements an interface for storing and retrieving live queries.
logging
package logging provides logger "plugins" for writing osquery status and result logs to various destinations.
package logging provides logger "plugins" for writing osquery status and result logs to various destinations.
mail
Package mail provides implementations of the Fleet MailService
Package mail provides implementations of the Fleet MailService
pubsub
Package pubsub implements pub/sub interfaces defined in package kolide.
Package pubsub implements pub/sub interfaces defined in package kolide.
service
Package service holds the implementation of the kolide service interface and the HTTP endpoints for the API
Package service holds the implementation of the kolide service interface and the HTTP endpoints for the API
sso
websocket
Package websocket contains helpers and implementation for backend functions that interact with the frontend over websockets.
Package websocket contains helpers and implementation for backend functions that interact with the frontend over websockets.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL