This repo contains a set of sample dashboards in JSON format can be easily imported into JupiterOne Insights app.
List of dashboards:
- AWS Accounts
- AWS Cost Analysis
- AWS IAM
- AWS Resources
- AWS S3 Security
- Azure DataStore Resources
- Azure Resources
- Critical Asset Attack Surface
- Data Breach Cost
- Data Protection
- Device Management
- Device Anomaly Detection (Beta)
- GCP Compute Projects and Instances
- GCP IAM
- GDPR Data Locations
- Google Workspace
- GitHub Insights
- High Risk Assets
- IR - Cloud Instance & Workload Analysis
- IR - User Endpoint Blast Radius
- Jamf & CrowdStrike Sensor Activity
- Jira Insights
- MongoDB Insights
- Network Security
- Okta User Management
- Resource Classification
- Risk Register
- Software Package Dependencies and Licenses
- Team Growth
- Team, Manager and Direct Reports
- Toxic Combinations
- User Access
- User Endpoints
- User Training
- Vendor Management
- Vulnerability Reporting
- PoV Insights
To import a dashboard template to your own JupiterOne account, simply
add a new dashboard in your Insights app, and upload (or drag-n-drop)
the desired board.json file to your new board.
We welcome and appreciate your contribution to this repository of
dashboard templates. You can download the dashboard JSON using the
download button near the top right of your selected Insights board
in the JupiterOne web app, and make a pull request to this repo.
Alternatively, feel free to share that JSON directly to our support
team or in the jupiterone-community Slack.
The JSON download only contains the widget definitions and layout. It does NOT contain any of your actual data.
Boards added to the mapping in src/index.ts MANAGED_BOARDS will be added to every account as "J1 Managed Boards".
This mapping allows specifying the name for the boards title and a category for the default category this board will appear in. This category can be overriden by admin users of an account.
Managed boards will be static and match the board/widget config defined in this repo exactly for each account.
When changes are ready to be deployed to the frontend insights page the package.json version
of this repo needs to be manually bumped. This triggers a Jenkins action once merged that publishes a new
@jupiterone/insights-dashboard package version.
Note - Only boards exported from src/index.ts will be available in the frontend application.
Finally, the applications team will need to bump the dependency version in the insights SPA.