![Starbase Logo](https://raw.githubusercontent.com/travomic/starbase/main/./img/branding/logo-light-bg.png)
Democratizing graph-based security analysis 🚀
Starbase from JupiterOne, collects assets and relationships from services and systems including cloud infrastructure, SaaS applications, security controls, and more into an intuitive graph view backed by the Neo4j database.
Security is a basic right. Starbase's goal is to democratize graph-based security analysis and overall visibility into external services and systems. Our team believes that in order to secure any system or service, you must have:
- Knowledge of the assets that you have
- Knowledge of the relationships between assets that you have
- Knowledge of what questions to ask about what you have
Why Starbase?
Starbase offers three key advantages:
- Depth and breadth - Deep visibility from a breadth of external services and systems. Thousands of entities (vertices) and relationships (edges) are available out-of-the-box.
- Uniform data model - The data that Starbase collects is automatically classified, making it easy to develop generic queries.
- Easily extensible - Starbase graph integrations can be easily developed!
Available Integrations / Connectors
Starbase supports 70+ open source graph integrations!
Here are some highlights:
❗ Click here to expand a full list of supported graph integrations❗
- 1AWS
- AirWatch
- JFrog Artifactory
- Auth0
- Azure
- Azure DevOps
- BambooHR
- Bugcrowd
- CbDefense
- Cisco Amp
- Cisco Meraki
- Cloudflare
- CrowdStrike
- Detectify
- DigiCert
- Duo
- Fastly
- Feroot
- Gitlab
- Gitleaks Findings
- GoDaddy
- Google Cloud
- HackerOne
- Heroku
- Jamf
- Jira
- JumpCloud
- Knowbe4
- Malwarebytes
- Microsoft 365
- Nmap
- NowSecure
- NPM
- Okta
- OneLogin
- OpenShift
- PagerDuty
- Qualys
- Rapid7
- SentinelOne
- ServiceNow
- Slack
- Snipe It
- Snowflake
- Snyk
- Tenable io
- ThreatStack
- Trend Micro
- Veracode
- Vuls Findings
- Wazuh
- WhiteHat
- Whois
Usage and Development
Prerequisites
- Install Node.js using the installer or a version manager such as nvm or fnm.
- Install
yarn
. - Install dependencies with
yarn install
. - Register an account in the system each integration targets for ingestion and obtain API credentials.
Configuring Starbase
Starbase leverages credentials from external services to authenticate and
collect data. When Starbase is started, it reads configuration data from a
single configuration file named config.yaml
at the root of the project.
- Copy
config.yaml.example
toconfig.yaml
cp config.yaml.example config.yaml
- Supply configuration values in
config.yaml
for each integration
NOTE: The individual graph integration configuration field names can be found in their respective
graph-*
projects.For example: https://github.com/JupiterOne/graph-google-cloud/blob/main/.env.example
The
config.yaml
would resemble the following for Google Cloud:integrations: - name: graph-google-cloud instanceId: testInstanceId directory: ./.integrations/graph-google-cloud gitRemoteUrl: https://github.com/JupiterOne/graph-google-cloud.git config: SERVICE_ACCOUNT_KEY_FILE: {} PROJECT_ID: "..." ORGANIZATION_ID: "..." CONFIGURE_ORGANIZATION_PROJECTS: false storage: engine: neo4j config: username: neo4j password: devpass uri: bolt://localhost:7687
Running Starbase
Starbase exposes a CLI for bootstrapping graph integration development and execution.
❯ yarn starbase --help
Usage: yarn starbase [options] [command]
Starbase graph ingestion orchestrator
Options:
-h, --help display help for command
Commands:
run collect and upload entities and relationships
setup clone repositories listed in config.yaml
help [command] display help for command
- Run
yarn starbase setup
to clone or update all integrations listed in theconfig.yaml
file as well as install all dependencies for each integration. - Run
yarn starbase run
to collect data for each listed integration and then push collected data to the storage endpoint listed inconfig.yaml
.
For additional information on using Neo4j as a storage endpoint, please see the README.md provided.
Contributing
Starbase is composed of three components:
-
Starbase Core
The Starbase core project is an orchestration engine that handles bootstrapping the underlying graph integrations.
-
Graph Integrations
These are the tools that perform data collection from third party systems and services. You can find a full list of supported graph integrations here. If you have a feature request, a bug to report, or you'd like to contribute to one of the supported integrations, please navigate to the specific integration repository.
-
The Graph Integration SDK contains core utilities and the underlying graph integration runtime packages. See the SDK development documentation for a deep dive into the mechanics of how integrations work.
Changelog
The history of this project's development can be viewed at CHANGELOG.md.
Contact
Join us on #starbase
on the JupiterOne Community Slack.
JupiterOne
If this is too much work, you can create a free cloud-hosted account at https://login.us.jupiterone.io/sign-up.
Footnotes
-
JupiterOne Starbase and the Lyft Cartography projects complement each other as both projects push graph data to a Neo4j database instance. As such, users of Starbase can leverage the AWS connector from Cartography to ingest AWS assets and relationships. A more comprehensive AWS integration is used by the cloud hosted JupiterOne platform and we are considering open sourcing the JupiterOne AWS integration in the future.
↩