Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
JupiterOne 13 January 2022 Release - AskJ1 Community
<main> <article class="userContent"> <p>January 13, 2022</p> <h2 data-id="new-features-and-improvements">New Features and Improvements</h2> <ul><li><p>There is a new login experience and new look-and-feel for the search page.<br><img src="../assets/new-login.png" alt="" class="embedImage-img importedEmbed-img"></img></p></li> <li><p>For previously created account API tokens, the details for those APIs are now viewable.</p></li> </ul><h2 data-id="fixes-and-resolutions">Fixes and Resolutions</h2> <ul><li>Release notes have moved to a new naming convention. Instead of aligning with our internal sprint numbers, we are now using the actual date.</li> </ul><h2 data-id="integrations">Integrations</h2> <h3 data-id="addigy">Addigy</h3> <ul><li>Added a new integration for Addigy</li> <li>Ingests the following entities:</li> </ul><table><thead><tr><th>Resource</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>Addigy Device</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">addigy_hostagent</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">HostAgent</code></td> </tr><tr><td>Addigy Policy</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">addigy_policy</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Policy</code></td> </tr><tr><td>Addigy User</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">addigy_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">User</code></td> </tr></tbody></table><ul><li>Creates the following relationships:</li> </ul><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">addigy_hostagent</code></td> <td>HAS</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">addigy_policy</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">addigy_policy</code></td> <td>CONTAINS</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">addigy_policy</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">addigy_user</code></td> <td>HAS</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">addigy_policy</code></td> </tr></tbody></table><ul><li>Creates the following mapped relationship:</li> </ul><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">addigy_hostagent</code></td> <td>PROTECTS</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">*user_endpoint*</code></td> <td>FORWARD</td> </tr></tbody></table><h3 data-id="google-workspace">Google Workspace</h3> <ul><li>Fixed an issue that was causing duplicate <code class="code codeInline" spellcheck="false" tabindex="0">_key</code> values for <code class="code codeInline" spellcheck="false" tabindex="0">google_mobile_device</code> assets.</li> </ul><h3 data-id="okta">Okta</h3> <ul><li>Improved the retry logic to ensure successful completion when 500 errors are occasionally returned.</li> <li>Improved error messaging so that you know when a 403 error has resulted from a permissions issue that you can resolve yourself.</li> </ul><h3 data-id="jamf">Jamf</h3> <ul><li>Improved how firewall assets are populated.</li> </ul><h3 data-id="github">GitHub</h3> <ul><li>Added a new <code class="code codeInline" spellcheck="false" tabindex="0">active</code> Boolean property to the <code class="code codeInline" spellcheck="false" tabindex="0">github_user</code> asset.</li> </ul><h3 data-id="qualys">Qualys</h3> <ul><li>Changed the <code class="code codeInline" spellcheck="false" tabindex="0">qualysAssetId</code> asset to use the <code class="code codeInline" spellcheck="false" tabindex="0">Asset ID</code> class,</li> <li>Added the <code class="code codeInline" spellcheck="false" tabindex="0">qualysQWebHostId</code> property to the <code class="code codeInline" spellcheck="false" tabindex="0">discovered_host</code> asset.</li> </ul><h2 data-id="coming-soon">Coming Soon</h2> <ul><li>Compliance Version 2.0: Major updates to the J1 Compliance app are in progress, and are planned for release in the coming weeks. This new version includes the centralization and reusability of controls, a new look-and-feel, and improved navigation within the app.</li> </ul> </article> </main>
.png)