Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
JupiterOne 15 December 2022 Release - AskJ1 Community
<main> <article class="userContent"> <h2 data-id="new-features-and-improvements">New Features and Improvements</h2> <ul><li>J1 Insights now honors your defined query permission for your users as defined in your account settings.</li> <li>The matrix charts in J1 Insights are now equipped with a sticky header for easier contextual scrolling.</li> <li><p>You are now able to view the query that powers the J1 Insights managed dashboard widgets under the more actions area.</p> <p><img src="https://us.v-cdn.net/6035534/uploads/IRVII9410X6E/how-to-view-the-j1-managed-dashboard-queries.gif" alt="" class="embedImage-img importedEmbed-img"></img></p></li> <li><p>Rule actions now include Tines triggers, allowing you to push data from a J1 query to a Tines action workflow.</p></li> </ul><h2 data-id="integrations">Integrations</h2> <h3 data-id="jamf">Jamf</h3> <ul><li>Added <code class="code codeInline" spellcheck="false" tabindex="0">realName</code> property to the <code class="code codeInline" spellcheck="false" tabindex="0">user_endpoint</code> entity.</li> </ul><h3 data-id="malwarebytes">MalwareBytes</h3> <ul><li>Added <code class="code codeInline" spellcheck="false" tabindex="0">osVersion</code> property to <code class="code codeInline" spellcheck="false" tabindex="0">malwarebytes_agent</code> entity.</li> </ul><h3 data-id="rapid7">Rapid7</h3> <ul><li>Added new properties to the following entities:<br> | Entity | Property |<br> | --------------- | ------------------------- |<br> | insightvm_user | active |<br> | insightvm_asset | name |<br> | insightvm_asset | osName |<br> | insightvm_asset | osVersion |<br> | insightvm_asset | osDetails |<br> | insightvm_asset | platform |<br> | insightvm_asset | ipAddress |<br> | insightvm_asset | category |<br> | insightvm_asset | webLink |<br> | insightvm_asset | numCriticalVulnerabilties |<br> | insightvm_asset | lastScanDate |</li> </ul><h3 data-id="snyk">Snyk</h3> <ul><li><code class="code codeInline" spellcheck="false" tabindex="0">snyk_finding</code> now includes the target property from a <code class="code codeInline" spellcheck="false" tabindex="0">snyk_project</code> repoName. This update fixes an issue that was preventing relationships from being created between the <code class="code codeInline" spellcheck="false" tabindex="0">snyk_finding</code> and the <code class="code codeInline" spellcheck="false" tabindex="0">gitlab_project</code>.</li> </ul><h3 data-id="sysdig">Sysdig</h3> <ul><li><p>Added support for ingesting the following new entities:<br></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>Agent</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sysdig_agent</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Scanner</code></td> </tr><tr><td>Cluster</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sysdig_cluster</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Cluster</code></td> </tr></tbody></table></li> <li><p>Added support for ingesting the following new relationships:<br></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">sysdig_agent</code></td> <td><strong>SCANS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sysdig_cluster</code></td> </tr></tbody></table></li> </ul><h3 data-id="terraform-provider">Terraform Provider</h3> <ul><li>Fixed an issue that was causing questions that were updated in J1 to not update in the Terraform Provider.</li> </ul><h3 data-id="trend-micro">Trend Micro</h3> <ul><li>Assigned <code class="code codeInline" spellcheck="false" tabindex="0">Device</code> class to the <code class="code codeInline" spellcheck="false" tabindex="0">trend_micro_computer</code> entity. Now, the <code class="code codeInline" spellcheck="false" tabindex="0">trend_micro_computer</code> is classified as both <code class="code codeInline" spellcheck="false" tabindex="0">Host</code> and <code class="code codeInline" spellcheck="false" tabindex="0">Device</code>.</li> </ul><h3 data-id="veracode">Veracode</h3> <ul><li>Ingest <code class="code codeInline" spellcheck="false" tabindex="0">Dynamic</code> and <code class="code codeInline" spellcheck="false" tabindex="0">SCA</code> scans in addition to the existing <code class="code codeInline" spellcheck="false" tabindex="0">Static</code> scan type.</li> </ul><h3 data-id="vmware-vsphere">VMware vSphere</h3> <ul><li>The config value <code class="code codeInline" spellcheck="false" tabindex="0">domain</code> must now include the full domain. Previously, <code class="code codeInline" spellcheck="false" tabindex="0">.vmwarevmc.com</code> was appended to the supplied domain.</li> </ul><h2 data-id="bug-fixes">Bug Fixes</h2> <ul><li>J1 Insights received some bug fixes for rearranging widgets and removing widgets.</li> </ul><h2 data-id="coming-soon">Coming Soon</h2> <ul><li>Your J1 Insights dashboard will soon be downloadable as a PDF to help facilitate the sharing of your dashboards offline.</li> <li>Access Controls are being introduced into J1 Insights. These controls will allow you to control which of your groups and users have access to each J1 Insights dashboards.</li> <li>Upcoming releases for in-app notifications will keep you informed on the latest notifications from J1 Rapid Response, Policies, Compliance, and Integrations.</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, home page, 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 directly from your J1 account to your internal BigQuery instances.</li> <li>AWS Config Recorder will soon be a fully supported and generally available service to all J1 users via the J1 Integrations section of the platform.</li> </ul> </article> </main>
.png)