Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
JupiterOne 6 October 2022 Release - AskJ1 Community
<main> <article class="userContent"> <h2 data-id="new-features-and-improvements">New Features and Improvements</h2> <ul><li>J1 Insights can now pass a variable directly to a shared dashboard URL.</li> <li>The Insights navigation has a new modern style to help you get to your boards easier.</li> <li>Scrolling in Insights is now easier with enhancements to J1 Graph and pie charts.</li> <li>A class filter is now available in J1 Graph to help you specify your query results in the Graph.</li> <li>Shortcut keys are now available in the Graph to enhance the undo and redo experience while exploring your query results.</li> <li>You can now set a default in the Graph Insights widget to group or expand nodes upon loading.</li> </ul><h2 data-id="integrations">Integrations</h2> <h3 data-id="general">General</h3> <ul><li>It is now possible to add custom tags to an integration configuration directly from the UI.</li> </ul><h3 data-id="azure">Azure</h3> <ul><li>Fixed an issue that could occur during the fetch-batch-application step.</li> <li>Fixed an issue with the relationship being created between <code class="code codeInline" spellcheck="false" tabindex="0">azure_kubernetes_service</code> and <code class="code codeInline" spellcheck="false" tabindex="0">azure_resource_group</code>.</li> </ul><h3 data-id="cisco-secure-workload">Cisco Secure Workload</h3> <ul><li><p>Added new entities:</p> <table><thead><tr><th>Entity</th> <th>Resource</th> </tr></thead><tbody><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">csw_policy</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Policy</code></td> </tr></tbody></table></li> <li><p>Added new relationships:</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">csw_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">csw_policy</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">csw_policy</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">csw_scope</code></td> </tr></tbody></table></li> </ul><h3 data-id="github">GitHub</h3> <ul><li>Added a relationship between two pull requests that share the same merge commit. This feature allows for the discovery of pull-request merges without approval given the following scenario:</li> </ul><blockquote class="UserQuote blockquote"><div class="QuoteText blockquote-content"> <p class="blockquote-line">PR1 - Branch A -> main with commit {A}<br> PR2 - Branch B -> main with commits {A, B}<br> PR3 - Branch C -> main with commits {A, B, C}</p> </div></blockquote> <pre class="code codeBlock" spellcheck="false" tabindex="0">If PR3 is merged first, PR1 and PR2 are flagged as MERGED and potentially without approval in some circumstances. This new CONTAINS relationship indicates that PR3 ->CONTAINS-> (PR1 | PR2). | Source Entity `_type` | Relationship `_class` | Target Entity `_type` | | --------------------- | --------------------- | --------------------- | | `github_pullrequest` | **CONTAINS** | `github_pullrequest` | </pre> <ul><li>Fixed the <code class="code codeInline" spellcheck="false" tabindex="0">github_pullrequest</code> entity property <code class="code codeInline" spellcheck="false" tabindex="0">allCommitsApproved</code> so that it is only set if commits are available on a given pull request. If a repo is private, permissions do not allow J1 to pull the commit history.</li> </ul><h3 data-id="hashicorp-vault">Hashicorp Vault</h3> <ul><li><p>Released a new integration for Hashicorp Vault.</p></li> <li><p>The following entities are created:</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>Account</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_account</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Account</code></td> </tr><tr><td>Authentication Backend</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_auth_backend</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Service</code></td> </tr><tr><td>Secret</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_secret</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Secret</code></td> </tr><tr><td>Secret Engine</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_engine</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Service</code></td> </tr><tr><td>User</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">User</code></td> </tr></tbody></table></li> <li><p>The following relationships are created:</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">hashicorp_vault_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_auth_backend</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_engine</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_user</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_auth_backend</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_user</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_engine</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">hashicorp_vault_secret</code></td> </tr></tbody></table></li> </ul><h3 data-id="jira">Jira</h3> <ul><li>Added a new configuration option that allows you to exclude the issue description field from being ingested to JupiterOne.</li> </ul><h3 data-id="kandji">Kandji</h3> <ul><li><p>Released a new integration for Kandji.</p></li> <li><p>The following entities are created:</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>Account</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">kandji_account</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Account</code></td> </tr><tr><td>App</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">kandji_app</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Application</code></td> </tr><tr><td>Device</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">kandji_device</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Device</code></td> </tr><tr><td>User</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">kandji_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">User</code></td> </tr></tbody></table></li> <li><p>The following relationships are created:</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">kandji_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">kandji_device</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">kandji_device</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">kandji_app</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">kandji_device</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">kandji_user</code></td> </tr></tbody></table></li> </ul><h3 data-id="microsoft-defender-for-endpoint">Microsoft Defender for Endpoint</h3> <ul><li><p>Released a new integration for Microsoft Defender for Endpoint.</p></li> <li><p>The following entities are created:</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>Account</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_account</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Account</code></td> </tr><tr><td>Device/Machine/Host</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">user_endpoint</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Device</code></td> </tr><tr><td>Logon User</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_logon_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">User</code></td> </tr><tr><td>Machine</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_machine</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">HostAgent</code></td> </tr><tr><td>User</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">User</code></td> </tr><tr><td>Vulnerability</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_vulnerability</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Finding</code></td> </tr></tbody></table></li> <li><p>The following relationships are created:</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">microsoft_defender_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_machine</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_user</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_machine</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_logon_user</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_machine</code></td> <td><strong>IDENTIFIED</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_vulnerability</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_machine</code></td> <td><strong>MANAGES</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">user_endpoint</code></td> </tr></tbody></table></li> <li><p>The following mapped relationships are created:</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> <th>Direction</th> </tr></thead><tbody><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_defender_vulnerability</code></td> <td><strong>IS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">*cve*</code></td> <td>FORWARD</td> </tr></tbody></table></li> </ul><h2 data-id="bug-fixes">Bug Fixes</h2> <ul><li>Insights dashboards with variables have received a few fixes that resolve drill down issues and the run query function of a widget.</li> <li>Two bugs in widgets were resolved to enable you to toggle between multiple queries within a widget and delete a widget from the modal view.</li> <li>Resolved a bug related to J1 Policies where deleted procedures were still returning in query results.</li> <li>Downloading evidence from a control is updated due to a few issues with inconsistent downloads.</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>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> </ul> </article> </main>
.png)