Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
JupiterOne 2021.78 Release - AskJ1 Community
<main> <article class="userContent"> <p>August 24, 2021</p> <h2 data-id="new-features-and-improvements">New Features and Improvements</h2> <ul><li><p>New Parameter feature supports the ability to define parameterized values or secrets via API. These parameters can then be referenced in queries <br> and questions within J1QL. Secrets can also be referenced in alert rules (e.g. for Webhook authentication).</p> <p>Learn more [here] (<a href="https://github.com/JupiterOne/docs/blob/main/docs/parameters.md#jupiterone-parameter-service)" rel="nofollow">https://github.com/JupiterOne/docs/blob/main/docs/parameters.md#jupiterone-parameter-service)</a>.</p></li> <li><p>Improved the query policy editor for user group permissions to clarify that data from ANY permission filter returns results for users within the group.</p></li> <li><p>Improved the login experience so that a user navigates directly to a deep link even after authentication.</p></li> </ul><h2 data-id="bug-fixes">Bug Fixes</h2> <ul><li><p>Resolved erroneous <code class="code codeInline" spellcheck="false" tabindex="0">accessRule</code> permission errors when querying under certain circumstances.</p></li> <li><p>Resolved unexpected results when paginating query results in a compliance requirement.</p></li> <li><p>Updated the Policies & Procedures app to no longer display the <em>No procedure found</em> image while loading.</p></li> <li><p>Updated the Account Usage graph to remove the Relationship Count label from the legend as this data is unsupported.</p></li> <li><p>Resolved deleting a policy or procedure that has an invalid template.</p></li> <li><p>Resolved pagination for questions with multiple queries.</p></li> </ul><h2 data-id="integrations">Integrations</h2> <h3 data-id="aws">AWS</h3> <ul><li>Fixed error processing for GuardDuty findings.</li> </ul><h3 data-id="github">GitHub</h3> <ul><li>Added support for ingesting the following <strong>new</strong> entities:</li> </ul><table><thead><tr><th>Entity</th> </tr></thead><tbody><tr><td>github_app*</td> </tr><tr><td>github_user (role: OUTSIDE)</td> </tr></tbody></table><p>* This usage requires that an GitHub organization admin allows the <code class="code codeInline" spellcheck="false" tabindex="0">organization_administration: read</code> scope for the JupiterOne GitHub app. Github notifies admins by email.</p> <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>github_account</td> <td>INSTALLED</td> <td>github_app</td> </tr><tr><td>github_repo</td> <td>ALLOWS</td> <td>github_user (role: OUTSIDE)</td> </tr></tbody></table><h3 data-id="google-cloud">Google Cloud</h3> <ul><li><p>Added managed question:<br> "Which Google Cloud API services are disabled for my project?"</p></li> <li><p>Changed <code class="code codeInline" spellcheck="false" tabindex="0">google_iam_bindings.permissions: string[]</code> to<br><code class="code codeInline" spellcheck="false" tabindex="0">google_iam_bindings.permissions: string</code> due to limitations on<br><code class="code codeInline" spellcheck="false" tabindex="0">string[]</code>property lengths in JupiterOne. Queries need to change from <code class="code codeInline" spellcheck="false" tabindex="0">permissionmks={{string}}</code> to <code class="code codeInline" spellcheck="false" tabindex="0">permissions~={{string}}</code> to maintain expected query results.</p></li> <li><p>Managed <code class="code codeInline" spellcheck="false" tabindex="0">google_iam_roles</code> now have a <code class="code codeInline" spellcheck="false" tabindex="0">permissions</code> property, similar to<br> custom <code class="code codeInline" spellcheck="false" tabindex="0">google_iam_roles</code>.</p></li> <li><p>Allowed BigQuery data to be ingested independently of KMS key data.</p></li> </ul><h3 data-id="jira">Jira</h3> <ul><li><p>Loosened hostname validation to allow <code class="code codeInline" spellcheck="false" tabindex="0">example.atlassian.net/jira</code>.</p></li> <li><p>Fixed the error that occurs when a issue creator or reporter user is no longer in the Jira instance.</p></li> <li><p>Migrated to the latest SDK. Let us know if you observe any problems by emailing <a rel="nofollow" href="mailto:support@jupiterone.com">support@jupiterone.com</a>.</p></li> </ul><h3 data-id="knowbe4">KnowBe4</h3> <ul><li><p>Fixed handling of repeated entries for training modules.</p></li> <li><p>Fixed handling of invalid users or modules listed in enrollments.</p></li> <li><p>Fixed logging to correctly report fetch errors.</p></li> <li><p>Fixed handling of non-rate-limiting errors to avoid invoking backoff-retry function.</p></li> </ul><h2 data-id="coming-soon">Coming Soon!</h2> <h3 data-id="final-reminder-update-to-query-language-to-follow-de-morgan-s-law">Final Reminder: Update to Query Language to follow De Morgan's Law</h3> <p>To maintain language correctness, J1QL will fulfill shorthand filters in accordance <br> with De Morgan's Law. This improvement only impacts queries that use the <br> operators <code class="code codeInline" spellcheck="false" tabindex="0">!=</code>, <code class="code codeInline" spellcheck="false" tabindex="0">!~=</code>, <code class="code codeInline" spellcheck="false" tabindex="0">!^=</code>, <code class="code codeInline" spellcheck="false" tabindex="0">!$=</code> when operating on a group of values.</p> <p>For example,</p> <pre class="code codeBlock" spellcheck="false" tabindex="0">FIND jira_user WITH accountType != ('atlassian' OR 'app' OR 'customer') </pre> <p>is the equivalent of</p> <pre class="code codeBlock" spellcheck="false" tabindex="0">FIND jira_user WITH accountType != 'atlassian' AND accountType != 'app' AND accountType != 'customer' </pre> <p>In short, J1QL interprets the above query to return all <code class="code codeInline" spellcheck="false" tabindex="0">jira_user</code> entities, <br> excluding those that have an <code class="code codeInline" spellcheck="false" tabindex="0">accountType</code> value of <code class="code codeInline" spellcheck="false" tabindex="0">atlassian</code> or <code class="code codeInline" spellcheck="false" tabindex="0">app</code> or <code class="code codeInline" spellcheck="false" tabindex="0">customer</code>.</p> <p>!!! warning<br><strong>This is a breaking change!</strong> We are taking precautions to ensure saved questions <br> and queries are not inadvertently affected.</p> <pre class="code codeBlock" spellcheck="false" tabindex="0">We are running maintenance jobs to update all saved queries in questions, alerts, and Insights dashboard widgets during the rollout of this change. You do NOT have to make those changes manually. However, if you have stored queries outside of your JupiterOne account (such as in a custom script), please update those queries accordingly. </pre> <p>!!! note<br> This change is planned to release on <strong>Tuesday, Aug 31, 2021</strong>.</p> </article> </main>
.png)