Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
JupiterOne 11 February 2022 Release - AskJ1 Community
<main> <article class="userContent"> <h2 data-id="february-11-2022">February 11, 2022</h2> <h2 data-id="new-features-and-improvements">New Features and Improvements</h2> <ul><li><p>There is a new homepage dashboard, providing quick insights into what has changed in your environment and what actions you need to take. Key areas of interest include compliance gaps, problems with assets, and updates on critical assets.</p> <p><img src="https://us.v-cdn.net/6035534/uploads/G4ZRZ1BUS1XL/home-kpis.png" alt="" class="embedImage-img importedEmbed-img"></img></p> <p></p></li> <li><p>The Graph Viewer app has a new look-and-feel.</p></li> <li>In Compliance, you can now re-evaluate a control in a framework on an individual basis to update its status.</li> <li>Also in Compliance, the review frequency for requirements in a framework now defaults to a quarterly cadence.</li> </ul><h2 data-id="integrations">Integrations</h2> <h3 data-id="aws">AWS</h3> <ul><li>Added the <code class="code codeInline" spellcheck="false" tabindex="0">rootUserPasswordLastChanged</code> and <code class="code codeInline" spellcheck="false" tabindex="0">rootUserPasswordNextRotation</code> properties on the <code class="code codeInline" spellcheck="false" tabindex="0">aws_account</code> entity.</li> </ul><h3 data-id="azure">Azure</h3> <ul><li>Added a new property on virtual machines for <code class="code codeInline" spellcheck="false" tabindex="0">state</code>, indicating whether the machine is running or stopped.</li> <li>A property previously named <code class="code codeInline" spellcheck="false" tabindex="0">state</code> has been renamed to <code class="code codeInline" spellcheck="false" tabindex="0">provisioningState</code> as it reflects the virual machine's provision state.</li> <li>The <code class="code codeInline" spellcheck="false" tabindex="0">active</code> field also reflects the virtual machine's state. It's values can be: <code class="code codeInline" spellcheck="false" tabindex="0">true</code> when the state is running, <code class="code codeInline" spellcheck="false" tabindex="0">false</code> when the state is stopped, or <code class="code codeInline" spellcheck="false" tabindex="0">undefined</code> if the state is not known.</li> </ul><h3 data-id="bamboohr">BambooHR</h3> <ul><li>New properties added</li> </ul><table><thead><tr><th>Entity</th> <th>Property</th> </tr></thead><tbody><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">bamboohr_employee</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">active: boolean</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">bamboohr_employee</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">status: "Active", "Inactive"</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">bamboohr_employee</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">employmentHistoryStatus: "Contractor", "Full-Time"</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">bamboohr_employee</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">employeeNumber</code></td> </tr></tbody></table><h3 data-id="google-cloud">Google Cloud</h3> <ul><li>Added a new optional parameter, <code class="code codeInline" spellcheck="false" tabindex="0">FOLDER_ID</code>, which allows ingestion to be restricted to a single folder and its children. If omitted, ingestion will still occur at the organizational level.</li> </ul><h3 data-id="onelogin">OneLogin</h3> <ul><li>Raw data for the <code class="code codeInline" spellcheck="false" tabindex="0">onelogin_user</code> entity was removed due to the large size.</li> </ul><h3 data-id="signal-sciences">Signal Sciences</h3> <ul><li>A new integration for Signal Sciences was released.</li> <li>The following entities are created:</li> </ul><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>Organization</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sigsci_corp</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Organization</code></td> </tr><tr><td>User</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sigsci_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">User</code></td> </tr></tbody></table><ul><li>The following relationships are created</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">sigsci_corp</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sigsci_user</code></td> </tr></tbody></table><h2 data-id="bug-fixes">Bug Fixes</h2> <ul><li>If you are using Azure SAML Group Assignment, you can now add users to multiple groups instead of just one.</li> <li>Questions linked as evidence for frameworks in the Compliance app are editable.</li> <li>Resolved issues related to sync jobs not unlocking following an unrecoverable error.</li> <li>Resolved issues related to deduplication of data in the Qualys integration.</li> </ul> </article> </main>
.png)