Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
JupiterOne 20 January 2023 Release - AskJ1 Community
<main> <article class="userContent"> <h2 data-id="new-features-and-improvements">New Features and Improvements</h2> <ul><li><p>The J1 Homepage is refreshed and streamlined, allowing you to easily find answers to your important questions.</p> <ul><li>You can navigate between queries using your broswer buttons</li> <li>You can share the query by copying the broswer <code class="code codeInline" spellcheck="false" tabindex="0">url</code>, which is now a unique <code class="code codeInline" spellcheck="false" tabindex="0">url</code></li> <li>J1 now provides syntax correction for queries</li> </ul></li> <li><p>Use the updated Questions Libray to find answers to tough security questions by leveraging the knowledge of JupiterOne. <br><img src="https://user-images.githubusercontent.com/112508192/213535414-75056bf0-8f0c-443f-900f-339c3fb27521.gif" alt="questions" class="embedImage-img importedEmbed-img"></img></p></li> <li><p>Your J1 Insights dashboards now have access controls in the share functionality to allow you to control who can access specified dashboards.</p></li> <li>In-app notifications are now available in J1 to keep you up-to-date on key events.</li> <li>A beta release of Query Builder is now available upon request. This feature helps you explore your assets with highly specified queries without needing to learn the syntax specifics of J1QL.<br><img src="https://user-images.githubusercontent.com/112508192/213540898-12c5e1b5-5c96-40e3-922c-c2c206b0ed9b.gif" alt="2023-01-19 12 39 29" class="embedImage-img importedEmbed-img"></img></li> </ul><h2 data-id="integrations">Integrations</h2> <h3 data-id="jamf">Jamf</h3> <ul><li>Email addresses properties are now set to all lower case on user and device entities to ensure they are consistent with other integrations.</li> </ul><h3 data-id="kandji">Kandji</h3> <ul><li>Refactored the integration so that the <code class="code codeInline" spellcheck="false" tabindex="0">kandji_app</code> entity is only created once and then referenced instead of being created once for each device that Kandji manages. This update reduces the number of Kandji entities that are created.</li> </ul><h3 data-id="microsoft-365">Microsoft 365</h3> <ul><li><p>Added additional properties <br></p><table><thead><tr><th>Entity _type</th> <th>Property</th> </tr></thead><tbody><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">azure_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">active</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">azure_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">accountEnabled</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">azure_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">userType</code></td> </tr></tbody></table></li> <li><p>This enhancement allows you to include these properties in your\r queries, so that you can now search or configure alerts based on whether the user is active, their account is enabled or disabled, or the type of (regular, admin, system, etc).</p></li> </ul><h3 data-id="sentinelone">SentinelOne</h3> <ul><li>Removed the <code class="code codeInline" spellcheck="false" tabindex="0">licensekey</code> property from the <code class="code codeInline" spellcheck="false" tabindex="0">sentinelone_agents</code> entity to prevent exposure of the license key.</li> </ul><h3 data-id="snyk">Snyk</h3> <ul><li><code class="code codeInline" spellcheck="false" tabindex="0">snyk_finding</code> now uses <code class="code codeInline" spellcheck="false" tabindex="0">originalSeverity</code> for <code class="code codeInline" spellcheck="false" tabindex="0">severity</code> to match what is displayed in the UI.</li> <li><code class="code codeInline" spellcheck="false" tabindex="0">snyk_finding</code> display name was changed to use the package name.</li> <li><p>Added 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>Snyk Group</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_group</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Group</code></td> </tr><tr><td>Snyk Organization</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_organization</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Organization</code></td> </tr><tr><td>Snyk Service</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_service</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Service</code></td> </tr><tr><td>Snyk Role</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_role</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">AccessRole</code></td> </tr></tbody></table></li> <li><p>Added 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">snyk_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_group</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_service</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_group</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_organization</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_group</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_role</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_organization</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_project</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_organization</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_user</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_service</code></td> <td><strong>IDENTIFIED</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_finding</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_service</code></td> <td><strong>SCANS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_project</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_user</code></td> <td><strong>ASSIGNED</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">snyk_role</code></td> </tr></tbody></table></li> </ul><h3 data-id="tenable">Tenable</h3> <ul><li>Fixed a bug that caused the <code class="code codeInline" spellcheck="false" tabindex="0">severity</code> property for the <code class="code codeInline" spellcheck="false" tabindex="0">tenable_vulnerability_finding</code> to be populated with <code class="code codeInline" spellcheck="false" tabindex="0">riskFactor</code>. It has been corrected to populate with the severity. The corrected values include "info", "low", "medium", "high", and "critical".</li> </ul><h2 data-id="bug-fixes">Bug Fixes</h2> <ul><li>Problems with searching case-sensitive letters in J1 Alerts is resolved.</li> <li>PDF download issues in J1 Policies is resolved.</li> <li>Resolved a known issue with incorrect relationships being shown in the Vulnerabilities & Findings tab.</li> <li>J1 Insights issues with widget timeouts have been resolved.</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>Alert trend lines will soon be updated to included rule errors, as well as each instance of the rule being evaluated. These updates allow you to see a holistic view of rules, evaulations, and the outcomes of actions (alerts).</li> <li>Introducing: Asset Categories! J1 is reworking how assets are categorized, based on industry standards. These categorizes will persist throughout J1 to make searching, and finding, the right information easier.</li> <li>The home experience will become more flexible for your user groups by allowing you as an admin to publish J1 Insights dashboards to you and your user groups landing experience.</li> <li><code class="code codeInline" spellcheck="false" tabindex="0">csv</code> exports from query results and assets will soon be pushed to the notification panel to allow for larger exports and a single repository of your downloads.</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)