Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
Starter Configurations for Insights Dashboards - AskJ1 Community
<main> <article class="userContent"> <p>J1 provides prebuilt starter configurations for you to use if you did not want to <a rel="nofollow" href="https://jupiterone.vanillacommunities.com/kb/articles/812-getting-started-with-insights-dashboards">import the JSON file</a> for the dashboard of your choice. The following prebuilt dashboards available are:</p> <ul><li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/aws-accounts">AWS Accounts</a></p> <p>Shows AWS master accounts, sub-accounts, as well as validated/unvalidated external accounts discovered by JupiterOne via analysis of IAM policies and trusts.</p> <p><strong>Prerequisite:</strong> This dashboard requires the J1 AWS integration and works best with multiple AWS accounts configured using AWS Organizations.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/aws-cost-analysis">AWS Cost Analysis</a></p> <p>Uses helpful queries for identifying resources that can result in increasing costs and attack surface within your AWS environment.</p> <p><strong>Prerequisite:</strong> This dashboard requires the J1 AWS integration and works best with multiple AWS accounts configured using AWS Organizations.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/aws-iam">AWS IAM</a></p> <p>Shows AWS IAM Groups, Users, Roles, and important access policy assignments.</p> <p><strong>Prerequisite:</strong> This dashboard requires the J1 AWS integration.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/aws-resources">AWS Resources</a></p> <p>Shows key AWS resources and related metrics across accounts.</p> <p><strong>Prerequisite:</strong> This dashboard requires the J1 AWS integration with one or more AWS accounts.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/aws-s3-security">AWS S3 Security</a></p> <p>Show several key configurations, metrics, and graphs related to AWS S3 security.</p> <p><strong>Prerequisite:</strong> This dashboard requires the J1 AWS integration.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/azure-datastore-security">Azure DataStore Resources</a></p> <p>Shows Azure container resources and encryption settings as well as logging options set on containers.</p> <p><strong>Prerequisite:</strong> This dashboard requires the J1 Azure integration.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/azure-resources">Azure Resources</a></p> <p>Shows Azure resources covering encryption settings, guest access, and resource access to key vaults.</p> <p><strong>Prerequisite:</strong> This dashboard requires the J1 Azure integration.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/critical-attack-surface">Critical Asset Attack Surface</a></p> <p>Critical assets are those that are business-critical, defined by contextual attributes in J1 Assets. The assets that are directly exposed to the internet or directly allowing access to everyone should be immediately mitigated. The number should remain zero. There is a Critical Assets alert rule pack that can be imported to continuously monitor and alert on it. Additionally, there are widgets to show the attack surface associated with critical assets that are indirectly connected to the internet or allowing access to everyone. These attack surface assets are the immediate first contact point which, if compromised, could lead to the compromise of critical assets a few points away. These attack surface entities should be closely monitored for any configuration changes or any alerts/problems.</p> <p>At the bottom of this dashboard are a few widgets showing critical assets connected to user endpoints 1-2 degrees away that are not monitored or protected by an agent, and accessible by users without MFA. User endpoints and users are inherently risky, especially with a remote workforce. If any of those ae found, they should be remediated by installing a security agent on the user endpoint and enabling MFA on the user account.</p> <p><strong>Prerequisite:</strong> This dashboard requires critical assets to be configured and defined in J1 Assets.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/data-breach-cost">Data Breach Cost</a></p> <p>Shows sensitive data discovery findings from publicly accessible or unencrypted data stores, and use a formula to calculate the potential cost if based on the number of sensitive data records that could be exposed.</p> <p><strong>Prerequisite:</strong> This dashboard requires a DLP service to be enabled and integrated, such as Amazon Macie.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/data-protection">Data Protection</a></p> <p>Shows secure development related metrics, including repo counts by project, open pull requests by developer, pull requests with self-approved/unapproved commits, and pull requests with commits made by unknown/unvalidated developers.</p> <p><strong>Prerequisite:</strong> This dashboard requires integrations with GitHub or GitLab or Bitbucket. Additionally, to correctly identify known developers, an IdP/SSO integration such as Okta, Google, or Azure AD is needed.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/development">Development</a></p> <p>Shows secure development related metrics, including repo counts by project, open pull requests by developer, pull requests with self-approved/unapproved commits, and pull requests with commits made by unknown/unvalidated developers.</p> <p><strong>Prerequisite:</strong> This dashboard requires integrations with GitHub or GitLab or Bitbucket. Additionally, to correctly identify known developers, an IdP/SSO integration such as Okta, Google, or Azure AD is needed.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/gcp-compute">GCP Compute Projects and Instances</a></p> <p>Shows important configurations related to GCP Compute Projects and Instances.</p> <p><strong>Prerequisite:</strong> This dashboard requires the J1 Google Cloud integration.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/gcp-iam">GCP IAM</a></p> <p>Shows GCP IAM users, roles, service accounts, and important access privilege information.</p> <p><strong>Prerequisite:</strong> This dashboard requires the J1 Google Cloud integration.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/gdpr-data-locations">GDPR Data Locations</a></p> <p>Shows data stores in the EU, US, and elsewhere.</p> <p><strong>Prerequisite:</strong> This dashboard requires J1 cloud infrastructure integrations such as AWS, Azure, and Google Cloud.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/google-workspace">Google Workspace</a></p> <p>Shows various counts of both admin and non-admin users, third-party OAuth tokens and non-active super-admins. Additional widgets allow for Chrome version insight as well as notification of outdated/vulnerable versions of Chrome (adjust query as-needed).</p> <p><strong>Prerequisite:</strong> This dashboard requires the J1 Google Workspace integration.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/github-insights">GitHub Insights</a></p> <p>Shows detailed information on GitHub accounts, reporting on user access, developer activity, collaborator details, insights on pull requests, and issue summaries by repo.</p> <p><strong>Prerequisite:</strong> This dashboard requires the J1 GitHub integration.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/high-risk-assets">High Risk Assets </a></p> <p>Shows vulnerability findings associated with production and internet-facing systems, non-public data stores with public access, and public data stores containing sensitive data.</p> <p><strong>Prerequisite:</strong> This dashboard requires J1 cloud infrastructure integrations such as AWS, Azure, and Google Cloud.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/cloud-instance-workload-analysis">IR - Cloud Instance & Workload Analysis </a></p> <p>This is an interactive dashboard that prompts you to enter the hostname or IP address or instance ID of a cloud workload/instance.</p> <p>It answers these key questions for any given virtual instance or workload across all three major CSPs in seconds:</p> <ul><li>Is the workload/instance still active or online? What are its configurations?</li> <li>What resources are connected to it?</li> <li>What else are in the same blast radius?</li> <li>How is it connected to the Internet (external attack path)?</li> <li>Who has admin/privileged access to it?</li> <li>What data stores does it have access to?</li> </ul><p><strong>Prerequisite:</strong> This dashboard requires J1 cloud infrastructure integrations such as AWS, Azure, and Google Cloud.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/user-endpoint-blast-radius">IR - User Endpoint Blast Radius</a></p> <p>This is an interactive dashboard that prompts you to enter a macAddress of a device and visualize the device owner's access, full inventory of digital identities, and the resources they have access to.</p> <p><strong>Prerequisite:</strong> This dashboard works best when integrations related to user endpoint agents and SaaS applications is as complete as possible.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/jamf-crowdstrike">Jamf & CrowdStrike Sensor Activity</a></p> <p>Shows CrowdStrike sensor counts and non-responsive sensors. It compares JAMF enrolled devices to those both protected and not-protected by CrowdStrike, and reports missing JAMF-managed device encryption.</p> <p><strong>Prerequisite:</strong> This dashboard requires the following J1 integrations: CrowdStrike and JAMF. Some potential edits may be needed for the widget queries to accommodate integration names and the method and jamf_computer_group naming conventions you are using to distribute CrowdStrike sensor code. Select <strong>Edit</strong> for each widget and make the appropriate changes to match your system.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/jira-insights">Jira Insights</a></p> <p>Shows detailed information on Jira accounts, reporting on users, issues, and remediations.</p> <p><strong>Prerequisite:</strong> This dashboard requires the J1 Jira integration.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/network-security">Network Security</a></p> <p>This board contains several widgets:</p> <ul><li>A list of firewalls (e.g. network ACLs, security groups) allowing Internet access</li> <li>A matrix table showing the ingress/egress access and allowed ports from/to an external network, including the internet</li> <li>A matrix table showing the ingress/egress access and allowed ports between internal networks</li> <li>A list of expired certificates</li> <li>A list of DNS records not pointing to an internal resource</li> <li>A list of domains/subdomains</li> </ul></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/okta-user-management">Okta User Management</a></p> <p>Shows Okta users by current status, inactive users, and deprovisioned/inactive users with access to other accounts.</p> <p><strong>Prerequisite:</strong> This dashboard requires Okta and other user account services.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/resource-classification">Resource Classification</a></p> <p>Shows counts of documented risks from risk assessments based on their current status, and a listing of currently open risks.</p> <p><strong>Prerequisite:</strong> The risk records are ingested from either a specific Jira project, or can be entered directly into JupiterOne via the UI, API, or JSON upload.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/risk-register">Risk Register</a></p> <p>Shows a dynamically updating report of package dependencies in the software code repos and their corresponding licenses, which helpful to produce an open-source report for auditing.</p> <p>The dashboard can be shared with an auditor/customer/partner by generating a unique shareable link (similar to sharing a Google Doc).</p> <p><strong>Prerequisite:</strong> This dashboard requires integration with GitHub, GitLab, or Bitbucket. Additionally, because JupiterOne does not have access to code, a script to scan the dependencies is needed to capture the dependencies and licenses. An example script can be found <a rel="nofollow" href="https://github.com/JupiterOne/secops-automation-examples/tree/master/npm-inventory">here</a>.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/code-deps-licenses">Software Package Dependencies and Licenses</a></p> <p>Shows a dynamically updating report of package dependencies in the software code repos and their corresponding licenses, which is helpful to produce an open-source report for auditing.</p> <p>The dashboard can be shared with an auditor/customer/partner by generating a unique shareable link (similar to sharing a Google Doc).</p> <p><strong>Prerequisite:</strong> This dashboard requires integration with GitHub, GitLab, or Bitbucket. Additionally, because JupiterOne does not have access to code, a script to scan the dependencies is needed to capture the dependencies and licenses. An example script can be found <a rel="nofollow" href="https://github.com/JupiterOne/secops-automation-examples/tree/master/npm-inventory">here</a>.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/team-growth">Team Growth</a></p> <p>Shows total number of employees and the number of new team members added in the last 30/60/90 days.</p> <p><strong>Prerequisite:</strong> An integration to an identity provider or directory service, such as Okta, Azure AD, JumpCloud.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/team-manager-direct-reports">Team, Manager and Direct Reports</a></p> <p>This is an interactive dashboard that prompts you to enter an individual's email to get the person's peers/team members, manager, and direct reports.</p> <p><strong>Prerequisite:</strong> A J1 integration to an identity provider that is configured with a directory service with data related to people management. Integrations such as Google Workspace, Okta, Azure AD, JumpCloud, and HRIS integrations such as BambooHR.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/user-access">User Access</a></p> <p>Shows users across different environments/accounts, admin users, and shared/system user accounts.</p> <p>Within the Admin Users widget an additional query to find users that are assigned to roles which are tied to administrative IAM access policies is included. This is in addition to the first query that is finding users who are deemed to be administrators based on the type/role attribute directly on the user.</p> <p><strong>Prerequisite:</strong> This dashboard works best when integrations to different providers and accounts are as complete as possible.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/user-endpoints">User Endpoints</a></p> <p>Shows key metrics and status associated with user endpoints/devices and endpoint security agents.</p> <p><strong>Prerequisite:</strong> This dashboard requires J1 integration with endpoint protection agents such as Carbon Black, SentinelOne, CrowdStrike, Malwarebytes, Cisco AMP. Using the JupiterOne endpoint agents (powered by Stethoscope-app) can improve the richness of this dashboard as well.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/user-training">User Training</a></p> <p>Shows metrics and status related to security awareness training for endusers.</p> <p><strong>Prerequisite:</strong> This dashboard requires a J1 integration with a security awareness training provider, such as KnowBe4.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/vendor-mgmt">Vendor Management</a></p> <p>Shows metrics related to current vendors, and their validation state. This can be helpful to maintain a registry of vendors your company interacts with, and alert on newly discovered, unvalidated vendors.</p> <p><strong>Prerequisite:</strong> This dashboard requires one or more configured integrations, which create vendor assets. It also assumes you are using an IdP or SSO service (such as Google GSuite) that issues OAuth tokens against third-party vendor apps.</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/insights-dashboards/blob/main/src/boards/vuln-reporting">Vulnerability Reporting</a></p> <p>This dashboard presents multiple operational and reporting metrics to help with vulnerability management. It aggregates findings and risks across both infrastructure and application development, identifies the highest risk items by context, such as findings impacting production workloads and applications deployed to production.</p> <p>This dashboard also reports on vulnerability analytics and patterns -- Top 10 CVEs, Top 10 CWEs -- as well as workflow items such as Jira issues or records from other ticketing systems.</p> <p><strong>Prerequisite:</strong> This dashboard requires multiple configured J1 integrations to provide the following coverage as needed:</p> <ul><li>cloud infrastructure (AWS / Azure / GCP)</li> <li>application code repos (GitHub / GitLab / Bitbucket)</li> <li>infrastructure vulnerability scanners (AWS Inspector / Qualys / Tenable / etc.)</li> <li>code scanners (Snyk / Veracode / Rapid7 / etc.)</li> </ul></li> </ul> </article> </main>
.png)