Baton: A toolkit for adding identity governance to any application

The Baton toolkit gives developers the ability to extract, normalize, and interact with workforce identity data such as user accounts, permissions, roles, groups, resources, and more. Through the Baton CLI, developers can audit infrastructure access on-demand, run diffs, and extract access data. This can be used for automating user access reviews, exports into SIEMs, real-time visibility, and many other use cases.

Baton is structured as a toolkit of related command line tools. For each data source there is a "connector", such as baton-github for interacting with GitHub's API. This tool exports data in a format that the baton tool can understand, transform, and use to perform operations on the application

🎉 🎉 Launching Baton as an Open Source Project!

• Announcing Baton, an Open Source Toolkit for Auditing Infrastructure User Access
• Technical Deep Dive: Using Baton to Audit Infrastructure Access
• Baton and the Journey to Identity Security and Unified Access Control

What can you do with Baton?

As a generic toolkit for auditing access, Baton can be used for many use cases, such as:

• Export GitHub access updates to a CSV file using Baton
• Use Baton to get Splunk alerts when a new Github admin is added
• Set up a daily check for GitHub user rights updates using Baton
• Diff access rights from two SaaS systems with Baton
• Finding all AWS IAM Users with a specific IAM Role
• Auditing Github Repo Admins
• Finding users in apps that aren't in your IdP
• Detecting differences or changes in permissions in GitHub or AWS
• Discovering all access for an user or account across all SaaS and IaaS systems
• Calculating the effective access of a user based on group membership

These are just a few of the use cases that Baton can be leveraged for.

Trying it out: Find all GitHub repo admins

Baton can installed via Homebrew:

brew install conductorone/baton/baton conductorone/baton/baton-github

Baton has also a flake available

Add baton as an input and install it:

{
  inputs = {
    nixpkgs.url = "https://flakehub.com/f/NixOS/nixpkgs/*";

    baton.url = "github:conductorOne/baton";
  };

  outputs =
    {
      nixpkgs,
      baton,
    }:
    {
      devShells = {
        x86_64-linux = {
          default = nixpkgs.mkShell {
            packages = [
              baton.packages.x86_64-linux.default
            ];
          };
        };
      };
    };
}

Once installed, you can audit GitHub access with the following:

# Run the baton github connector
baton-github 
# Output the resources discovered
baton resources
# Output the same data to JSON and parse it with jq
baton resources -o json | jq '.resources[].resource.displayName'

We have also recorded a short video exploring some of the data Baton can extract from Github:

What connectors exist in Baton today?

We released five initial connectors with the open source launch of Baton. The ConductorOne team has dozens more connectors written in our precursor proprietary project from before Baton, and is aggressively porting them to the Baton ecosystem.

Additionally, making a new connector is really easy -- we wrap up many complexities in the SDK, letting a connector developer focus on translating to the Baton data model.

• 1Password
• Amazon Web Services
• Asana
• BambooHR
• Bitbucket
• Bitbucket Data Center
• Box
• Broadcom SAC
• Calendly
• Celigo
• CloudAMQP
• Cloudflare
• Cloudflare Zero Trust
• Confluence
• Confluence Data Center
• CrowdStrike
• Databricks
• Datadog
• Discord
• Dockerhub
• Duo
• Elastic
• Expensify
• Fastly
• Formal
• Fullstory
• Galileo Financial Technologies
• GitHub
• Google BigQuery
• Google Identity Platform
• Google Workspace
• Hubspot
• Jamf
• JD Edwards
• Jenkins
• Jira
• Jira Data Center
• JumpCloud
• LDAP
• Linear
• Litmos
• Microsoft 365
• Microsoft SQL Server
• Miro
• MongoDB
• MySQL
• New Relic
• Notion
• Okta
• OneLogin
• Opsgenie
• PagerDuty
• Panorama
• Panther
• PostgreSQL
• Privx
• Retool
• Segment
• SentinelOne
• ServiceNow
• Slack
• Snipe-IT
• Snowflake
• Snyk
• Splunk
• Tableau
• Temporal Cloud
• Torq
• Verkada
• Very Good Security
• XSOAR
• Zendesk
• Zoom

Learn more about Baton

The Baton documentation site contains more documentation and example use cases.

Contributing, support and issues

We started Baton because we were tired of taking screenshots and manually building spreadsheets. We welcome contributions, and ideas, no matter how small -- our goal is to make identity and permissions sprawl less painful for everyone. If you have questions, problems, or ideas: Please open a Github Issue!

See CONTRIBUTING.md for more details.

baton command line usage

baton is a utility for working with the output of a baton-based connector

Usage:
  baton [command]

Available Commands:
  access         List effective access for a user
  completion     Generate the autocompletion script for the specified shell
  diff           Perform a diff between sync runs
  entitlements   List entitlements
  export         Export data from the C1Z for upload
  grants         List grants
  help           Help about any command
  principals     List principals
  resource-types List resource types for the latest (or current) sync
  resources      List resources for the latest sync
  stats          Simple stats about the c1z

Flags:
  -f, --file string            The path to the c1z file to work with. (default "sync.c1z")
  -h, --help                   help for baton
  -o, --output-format string   The format to output results in: (console, json) (default "console")
  -v, --version                version for baton

Use "baton [command] --help" for more information about a command.