Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
JupiterOne 4 November 2022 Release - AskJ1 Community
<main> <article class="userContent"> <h2 data-id="new-features-and-improvements">New Features and Improvements</h2> <ul><li>J1 Query results can now visualize multiple relationships between two nodes in the graph viewer to help drive context and declutter your views.</li> <li>Graph widgets in Insights will now size up or size down depending on your widget size to declutter your views to keep you focused on what matters.</li> <li>The Graph Widget navigational UI can now be toggled on/off directly from the widget more actions button.</li> <li>Dive into your complex Table Widgets with the expansion of our drill down capabilities for Insights.</li> </ul><h2 data-id="integrations">Integrations</h2> <h3 data-id="azure-devops">Azure DevOps</h3> <ul><li>Added new entity <code class="code codeInline" spellcheck="false" tabindex="0">azure_devops_repo</code>.</li> <li>Added new mapped relationship <code class="code codeInline" spellcheck="false" tabindex="0">azure_devops_project_uses_repo</code>.</li> <li>Added new relationship <code class="code codeInline" spellcheck="false" tabindex="0">azure_devops_project_uses_repo</code> if the repo isn't github or bitbucket.</li> </ul><h3 data-id="github">GitHub</h3> <ul><li>Updated permissions for branch protection rules to include <code class="code codeInline" spellcheck="false" tabindex="0">repo dicussions: read-only</code> which will allow private repo rules to be ingested.</li> </ul><h3 data-id="jira">Jira</h3> <ul><li>Improved the retry logic.</li> <li>Basic authentication is no longer supported. API tokens are required for authentication.</li> </ul><h3 data-id="tenable">Tenable</h3> <ul><li>Added <code class="code codeInline" spellcheck="false" tabindex="0">last_fixed</code> property to <code class="code codeInline" spellcheck="false" tabindex="0">tenable_vulnerability_finding</code> entities</li> <li>Added the following properties to the <code class="code codeInline" spellcheck="false" tabindex="0">tenable_vulnerability_finding</code>: <code class="code codeInline" spellcheck="false" tabindex="0">cve</code>, <code class="code codeInline" spellcheck="false" tabindex="0">cpe</code>, <code class="code codeInline" spellcheck="false" tabindex="0">description</code>, <code class="code codeInline" spellcheck="false" tabindex="0">recommendation</code>, <code class="code codeInline" spellcheck="false" tabindex="0">impact</code>.</li> <li>Refactor Container Security to v2 as v1 has been deprecated.</li> <li><p>The following <strong>new</strong> entities have been added:</p> <table><thead><tr><th>Resources</th> <th>Entity <code class="code codeInline" spellcheck="false" tabindex="0">_type</code></th> <th>Entity <code class="code codeInline" spellcheck="false" tabindex="0">_class</code></th> </tr></thead><tbody><tr><td>Container Image</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_image</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Image</code></td> </tr><tr><td>Container Repository</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_repository</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Repository</code></td> </tr><tr><td>Service</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_scanner</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Service</code></td> </tr></tbody></table></li> <li><p>The following <strong>new</strong> relationships have been added:</p> <table><thead><tr><th>Source Entity <code class="code codeInline" spellcheck="false" tabindex="0">_type</code></th> <th>Relationship <code class="code codeInline" spellcheck="false" tabindex="0">_class</code></th> <th>Target Entity <code class="code codeInline" spellcheck="false" tabindex="0">_type</code></th> </tr></thead><tbody><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_account</code></td> <td><strong>PROVIDES</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_scanner</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_image</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_repository</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_scanner</code></td> <td><strong>SCANS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_image</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_image</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_report</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_image</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_finding</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_image</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_malware</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_image</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_unwanted_program</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_repository</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">tenable_container_image</code></td> </tr></tbody></table></li> </ul><h3 data-id="vmware-vsphere">VMware vSphere</h3> <ul><li>Published the intitial beta integration as a Docker image on DockerHub for customers that want to test the integration.</li> </ul><h2 data-id="bug-fixes">Bug Fixes</h2> <ul><li>Small issues in the datatable were resolved.</li> <li>Unnecessary refresh on the J1 Query results Entity Drawer was resolved.</li> <li>Small SSO issues for those based outside of the US were resolved.</li> <li>Unexpected behavior related to toggling the query sidebar on/off was resolved.</li> <li>Resolved issues with syncing resources via the J1 AWS integration.</li> <li>Small fix to resolve regions being incorrectly targeted by AWS polling intervals.</li> <li>Enhancement made to AWS GovCloud IAM logic to resolve permissions-based errors.</li> </ul><h2 data-id="coming-soon">Coming Soon</h2> <ul><li>J1 Alerts is getting a design refresh! We are continuing our look-and-feel updates over J1 Alerts.</li> <li>Leverage JupiterOne's knowledge in Insights with the J1 managed dashboards for security use cases that help you solve real problems. We are putting our knowledge front and center in the J1 Library.</li> <li>Your J1 Query results will become more effective with upgrades to the table visualization and a new expandable entity drawer to help you dive into entities without leaving your J1 Query results tables or your graph view. The expanded entity drawer will provide J1 curated graph visualizations.</li> <li>Insights will be upgraded with the ability download J1 dashboards as well as individual widgets to help you share your visualizations with ease.</li> <li>No more silent failures for your alert rules: get notified when rules are not working, including an error log to help you triage and manage.</li> <li>In the coming months, we will be updating the Questions Library, Homepage, and KPIs to make finding the right information and questions even easier.</li> <li>If you are a Google BigQuery user, you will soon be able leverage your J1 data bi-directionally to trigger and route alerts right from your J1 account to your internal BigQuery instances!</li> <li>AWS Config. Recorder will soon be a fully supported & generally available service to all J1 users via the Integrations section of the platform.</li> </ul> </article> </main>
.png)