Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
JupiterOne 14 July 2022 Release - AskJ1 Community
<main> <article class="userContent"> <h2 data-id="new-features-and-improvements">New Features and Improvements</h2> <ul><li><p>Address top problems from the homepage: You can now see and take action on the top alerts that are revelant to your security to-do list. The top problems widget allows you to access alerts directly from the J1 Search homepage, sorted by criticality.</p> <p><img src="https://us.v-cdn.net/6035534/uploads/77F8BEYUWC2F/topproblems.png" alt="" class="embedImage-img importedEmbed-img"></img></p></li> <li><p>J1 Integrations has a new look-and-feel: J1 Integrations is visually updated to offer a refreshed experience, aligning with the rest of JupiterOne UI updates.</p> <p><img src="https://us.v-cdn.net/6035534/uploads/647L06HX8LQ5/integrationsv2.png" alt="" class="embedImage-img importedEmbed-img"></img></p></li> <li><p>Introducing: The new JupiterOne navigation bar. The navigation bar is updated to focus on key actions from the previous tile menu and the settings menu. You can now access J1 Graph and Integrations directly from the navigation bar.</p></li> <li><p>For the audit trail in Policies, the email address of the user related to a set of changes is now included in the file download.</p></li> <li><p>The Mac keyboard shortcut for Search Anywhere <code class="code codeInline" spellcheck="false" tabindex="0">CMD + K</code> is now supported.</p></li> <li><p>Improved query performance by implementing a solution to parallelize the execution of queries.</p></li> <li><p>Added the ability to use lists in query parameters.</p></li> <li><p>Added additional math utility functions. Each function that transforms a decimal into an integer to the nearest whole number.</p> <ul><li><p>Added ROUND function in the query language. This enables you to round a decimal to the nearest whole number in an expression. For example, if the decimal is 0.65, it rounds to 1. If it is 2.33, it will round to 2.</p> <ul><li>```<br> How many gigabytes do I have stored in each of my S3 buckets?</li> </ul><p>FIND aws_s3_bucket as s3<br> RETURN<br> s3.displayName,<br> ROUND(s3.bucketSizeBytes / 1000000000) as "Gigabytes Stored"</p></li> <li><p>Added CEIL function in the query language. This enables you to round decimals up to the nearest whole number.</p> <ul><li>```<br> How many findings were created each day?</li> </ul><p>FIND Finding<br> RETURN <br> CEIL(Finding.createdOn / (1000<em>60</em>60*24)) as "Created Date", <br> COUNT(Finding)</p></li> <li><p>Added FLOOR function in the query language. This enables you to round decimals down to the nearest whole number.</p> <ul><li>```<br> How many gigabytes do I have stored in each of my log groups?</li> </ul><p>FIND aws_cloudwatch_log_group as logGroup <br> RETURN <br> logGroup.displayName,<br> FLOOR(logGroup.storedBytes / 1000000000) as "Gigabytes Stored"</p></li> <li><p>Added SQRT function in the query language. This enables you to use square roots in math expressions.</p></li> </ul></li> <li><p>Added the ability to include positive exponents in expressions.</p> <ul><li><p>```<br> What is the score of each of the risks in my organization?</p> <p>FIND * as anyEntity<br> THAT HAS Risk as r <br> RETURN <br> anyEntity.displayName, <br> anyEntity._class, <br> SQRT((5 - r.impact)^2 + (5 - r.probability)^2)) as score<br> ORDER BY score ASC</p></li> </ul></li> <li><p>Added the ability to include expressions in CONCAT functions.</p> <ul><li><p>```<br> How many megabytes do I have in each of my S3 buckets?</p> <p>FIND aws_s3_bucket as s3 <br> RETURN <br> s3.displayName,<br> CONCAT(s3.bucketSizeBytes / 1000 / 1000, "mb") as "Bucket Size"</p></li> </ul></li> </ul><h2 data-id="integrations">Integrations</h2> <h3 data-id="aws">AWS</h3> <ul><li><p>Added the following 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>AWS CodePipeline Pipeline</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">aws_codepipeline_pipeline</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Workflow</code></td> </tr><tr><td>AWS CodePipeline Service</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">aws_codepipeline</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Service</code></td> </tr></tbody></table></li> <li><p>Added the following 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">aws_codepipeline</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">aws_codepipeline_pipeline</code></td> </tr></tbody></table></li> <li><p>When more than 50 instances are managed by SSM in a region, the step was failing due to API limits. This is now fixed.</p></li> <li>J1 now stops building <code class="code codeInline" spellcheck="false" tabindex="0">aws_network_acl_protects_subnet</code> if <code class="code codeInline" spellcheck="false" tabindex="0">networkAcl.SubnetId</code> is undefined.</li> </ul><h3 data-id="cisco-secure-workload">Cisco Secure Workload</h3> <ul><li>Fixed an issue that was preventing workloads with a null UUID from being ingested.</li> <li>Fixed an issue that was causing the same workload finding relationship to be created multiple times.</li> </ul><h3 data-id="datastax-astra">Datastax Astra</h3> <ul><li>Released a new integration for <a rel="nofollow" href="https://www.datastax.com/">Datastax</a></li> <li><p>The following entities are created:<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>Access List</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_access_list</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Firewall</code></td> </tr><tr><td>Access List Address</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_access_list_address</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Configuration</code></td> </tr><tr><td>Access Role</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_access_role</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">AccessRole</code></td> </tr><tr><td>Database</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_database</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Database</code></td> </tr><tr><td>Organization</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_organization</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">datastax_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">User</code></td> </tr></tbody></table></li> <li><p>The following relationships are created:<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">datastax_access_list</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_access_list_address</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_database</code></td> <td><strong>ASSIGNED</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_access_list</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_organization</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_access_list</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_organization</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_database</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_organization</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_database</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_organization</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_user</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_user</code></td> <td><strong>ASSIGNED</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">datastax_access_role</code></td> </tr></tbody></table></li> </ul><h3 data-id="microsoft-365">Microsoft 365</h3> <ul><li>The integration no longer sets <code class="code codeInline" spellcheck="false" tabindex="0">jailBroken</code> to true when the response from API is "jailBroken": "Unknown". It is now set to <code class="code codeInline" spellcheck="false" tabindex="0">undefined</code>.</li> </ul><h3 data-id="microsoft-teams">Microsoft Teams</h3> <ul><li>Released a new integration for <a rel="nofollow" href="https://www.microsoft.com/en-us/microsoft-teams/group-chat-software">Microsoft Teams</a>.</li> <li><p>The following entities are created:<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>Account</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_teams_account</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Account</code></td> </tr><tr><td>Channel</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_teams_channel</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Channel</code></td> </tr><tr><td>Team</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_teams_team</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Group</code></td> </tr><tr><td>User</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_teams_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">User</code></td> </tr></tbody></table></li> <li><p>The following relationships are created:</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">microsoft_teams_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_teams_team</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_teams_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_teams_user</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_teams_team</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_teams_channel</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_teams_team</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">microsoft_teams_user</code></td> </tr></tbody></table></li> </ul><h2 data-id="bug-fixes">Bug Fixes</h2> <ul><li><p>Resolved an issue where Insight tables were limiting the returns to 50 rows, regardless of the amount of data available in the table.</p></li> <li><p>Fixed a bug related to the last sign-in timestamp on the J1 Search homepage, where dates were not transcribed properly.</p></li> <li><p>Addressed a problem in J1 Compliance with linking policies to requirements where data did not persist when unlinking and relinking items.</p></li> <li><p>Fixed an issue with RBAC privileges for J1 Compliance non-admins.</p></li> <li><p>Resolved a bug where querying for <code class="code codeInline" spellcheck="false" tabindex="0">getprocedure</code> returned duplicates, regardless of the policy.</p></li> <li><p>Resolved an issue in which a timestamp would be displayed instead of a number when using an alias with a COUNT function that evaluates a property that is of the timestamp type.</p></li> <li><p>Resolved an issue that changed the format of an aliased property that is of the timestamp type.</p></li> <li><p>Resolved an issue that was returning incorrect results when using CONCAT with only a value that is of the string type.</p></li> </ul><h2 data-id="coming-soon">Coming Soon</h2> <p>In the coming weeks, look for the following new features and enhancements:</p> <ul><li>Updates to the entity drawer in J1 Assets, including an updated look-and-feel and additional actions.</li> <li>Additional updates to the J1 Search homepage to help you find the information that matters to you, faster.</li> <li>J1 Insights is getting a refresh: this includes an updated look-and-feel, aligning with JupiterOne's visual updates, and will also introduce updated functionality.</li> <li>Job statuses for J1 Integrations: know more about your integration jobs in a single consolidated view so you can see what you need to address and feel confident in the data JupiterOne receives.</li> <li>The <code class="code codeInline" spellcheck="false" tabindex="0">IAM</code> query policy is getting some updates to expand on the ability to use scoped <code class="code codeInline" spellcheck="false" tabindex="0">IAM</code> policies.</li> </ul> </article> </main>
.png)