Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
JupiterOne 2021.74 Release - AskJ1 Community
<main> <article class="userContent"> <p>2021-06-30</p> <h2 data-id="new-features-and-improvements">New Features and Improvements</h2> <ul><li><p>JupiterOne now provides an updated Compliance experience including a new total compliance status which aggregates adherence to selected individual compliance standards into a snapshot view as well as highlighting open risks, controls, people, and vendors.</p></li> <li><p><code class="code codeInline" spellcheck="false" tabindex="0">Allows</code> asset relationships will now appear as green in the graph and <code class="code codeInline" spellcheck="false" tabindex="0">Denies</code> relationships will now appear as red.</p></li> <li><p>Users can now “Tag” rules in order to group them together and search for them more easily.</p></li> <li><p>Policy ID, Revision number, and "Powered by J1" footnote are now configurable by the user when downloading a Policy PDF.</p></li> <li><p>COMING SOON: J1QL queries will soon support returned property aliases.</p></li> </ul><p>e.g.</p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> Find Person as p that is User as u Return p.name as Name, p.acceptedSecurityPolicyOn as "Accepted Security Policy", p.backgroundCheck as "Completed Background Check" (edited) </pre> <p><img src="https://us.v-cdn.net/6035534/uploads/175K990QVRVZ/review-n-accept.png" alt="" class="embedImage-img importedEmbed-img"></img></p> <p><img src="https://us.v-cdn.net/6035534/uploads/6IHSPDDM2PUG/review-accept-variable.png" alt="" class="embedImage-img importedEmbed-img"></img></p> <h2 data-id="integrations">Integrations</h2> <h3 data-id="auth0">Auth0</h3> <ul><li>JupiterOne now supports Auth0 with an initial integration. Please see <a rel="nofollow" href="https://github.com/JupiterOne/graph-auth0/blob/master/docs/jupiterone.md">documentation</a><br> for more details.</li> </ul><h3 data-id="google-cloud">Google Cloud</h3> <ul><li><p><a rel="nofollow" href="https://github.com/JupiterOne/graph-google-cloud/issues/255">#255</a> - Now <code class="code codeInline" spellcheck="false" tabindex="0">google_redis_instance</code> and <code class="code codeInline" spellcheck="false" tabindex="0">google_memcache_instance</code> use unique <code class="code codeInline" spellcheck="false" tabindex="0">_key</code> values</p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/graph-google-cloud/issues/243">#243</a> - JupiterOne now assigns boolean values to <code class="code codeInline" spellcheck="false" tabindex="0">public</code> property on <code class="code codeInline" spellcheck="false" tabindex="0">google_storage_bucket</code></p></li> <li><p><a rel="nofollow" href="https://github.com/JupiterOne/graph-google-cloud/issues/248">#248</a> - JupiterOne now always executes steps in org child projects even if the child project has service disabled</p></li> <li><p>New properties added to resources:</p></li> </ul><table><thead><tr><th>Entity</th> <th>Properties</th> </tr></thead><tbody><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">google_compute_instance</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">serviceAccountEmails</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">google_cloud_function</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">serviceAccountEmail</code></td> </tr></tbody></table><ul><li>Added support for ingesting the following <strong>new</strong> relationships:</li> </ul><table><thead><tr><th>Source</th> <th>_class</th> <th>Target</th> </tr></thead><tbody><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">google_compute_network</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">CONNECTS</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">google_compute_network</code></td> </tr></tbody></table><h3 data-id="github">GitHub</h3> <ul><li><a rel="nofollow" href="https://github.com/JupiterOne/integrations/issues/5">JupiterOne/integrations#5</a><br> JupiterOne now uses <code class="code codeInline" spellcheck="false" tabindex="0">name || login</code> for <code class="code codeInline" spellcheck="false" tabindex="0">displayName</code> of <code class="code codeInline" spellcheck="false" tabindex="0">Account</code> and <code class="code codeInline" spellcheck="false" tabindex="0">User</code> entities.</li> </ul><h3 data-id="qualys">Qualys</h3> <ul><li>JupiterOne by default ingests host detections with types <code class="code codeInline" spellcheck="false" tabindex="0">Potential, Confirmed</code>. We recommend avoiding ingesting Info detections until you are ready to process them in a meaningful way.</li> </ul><h2 data-id="bug-fixes">Bug Fixes</h2> <ul><li><p>Fixed bug that caused <code class="code codeInline" spellcheck="false" tabindex="0">jupiterone_user</code> and <code class="code codeInline" spellcheck="false" tabindex="0">jupiterone_user_group</code> entities in the graph.</p></li> <li><p>Fixed bug that caused query policies to be combined improperly when users belong to multiple groups with different query policies. Query policies are now combined to expand scope if multiple query policies apply to user.</p></li> </ul> </article> </main>
.png)