Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
JupiterOne 2021.76 Release - AskJ1 Community
<main> <article class="userContent"> <p>2021-07-27</p> <h2 data-id="new-features-and-improvements">New Features and Improvements</h2> <ul><li>The Policies app has an updated look and feel.</li> <li>JupiterOne now supports importing different versions of the same compliance framework.</li> <li>JupiterOne has optimizated J1QL query autocomplete. This decreases the latency between typing & showing results.</li> <li>Users can now use the date a policy/procedure was created within a template by using the <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">{{createdOn}}</code> variable.</li> <li>URLs in the status checker widget can now be clicked on in order to navigate to the link.</li> <li>The Asset Inventory App now uses consistent date formats (previously, certain attributes were shown having a timestamp instead of a date/time).</li> <li>JupiterOne has added a "Removed" chip to entity properties that used to have a value but were manually removed, allowing a user to see what data is not present.</li> </ul><h2 data-id="new-integrations">New Integrations</h2> <h3 data-id="kubernetes-beta">Kubernetes Beta</h3> <p>We continue to work on an <a rel="nofollow" href="https://github.com/JupiterOne/graph-kubernetes/blob/master/docs/jupiterone.md">integration for Kubernetes</a> clusters. <br><a rel="nofollow" href="beta-request-form">Please reach out</a> if you're interested in using the integration and help us make it valuable for your operations!</p> <h3 data-id="salesforce-beta">Salesforce Beta</h3> <p>We also continue to enhance our <a rel="nofollow" href="../docs/integrations/salesforce/salesforce.md">integration for Salesforce</a>. <br> The integration currently ingests groups, users, user roles, and permission sets to support user access review and monitoring in JupiterOne. <br><a rel="nofollow" href="beta-request-form">Please reach out</a> if you're interested in using the integration. We'd love to hear your thoughts on what to add to make the integration valuable for you.</p> <h3 data-id="aws">AWS</h3> <ul><li>New relationships added:</li> </ul><table><thead><tr><th>Source Entity <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">_type</code></th> <th>Relationship <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">_class</code></th> <th>Target Entity <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">_type</code></th> </tr></thead><tbody><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">aws_dynamodb</code></td> <td><strong>SENDS</strong></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">aws_cloudtrail</code></td> </tr><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">aws_dynamodb_table</code></td> <td><strong>SENDS</strong></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">aws_cloudtrail</code></td> </tr><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">DataStore</code></td> <td><strong>LOGS (TO)</strong></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">aws_s3_bucket</code></td> </tr></tbody></table><ul><li>New properties added to resources:</li> </ul><table><thead><tr><th>Entity</th> <th>Properties</th> </tr></thead><tbody><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">aws_elasticache_cluster_node</code></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">hostname</code></td> </tr><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">aws_elasticache_memcached_cluster</code></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">hostname</code></td> </tr><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">aws_db_instance</code></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">hostname</code></td> </tr><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">aws_rds_cluster</code></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">loggingEnabled</code>, <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">enabledCloudwatchLogsExports</code></td> </tr><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">aws_db_instance</code></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">loggingEnabled</code>, <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">enabledCloudwatchLogsExports</code></td> </tr></tbody></table><ul><li><p>JupiterOne has added <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">classic</code> to <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">aws_elb.category</code> property (Classic ELB).</p></li> <li><p>JupiterOne has improved the consistency of setting the <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">value</code> property of Route53 records to<br> always remove the ending period. This allows for more consistent mapping for<br> the domain records to the corresponding entity they connect to. The ending<br> period, if present, is preserved in the <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">aliasTarget</code> and <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">resourceRecords</code><br> properties.</p></li> </ul><h3 data-id="crowdstrike">Crowdstrike</h3> <ul><li>JupiterOne has fixed the timeout of <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">synchronize</code> step for large data sets.</li> </ul><h3 data-id="github">GitHub</h3> <ul><li>JuptierOne has migrated to latest integration SDK for improved error handling and reporting.</li> <li>JupiterOne fixed the failure to uploads raw data for <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">github_pull_request</code> entities by removing <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">head</code> and <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">base</code> properties.</li> </ul><h3 data-id="google-cloud">Google Cloud</h3> <ul><li><p>JupiterOne will not fail during the step that fetches App Engine Applications even when<br><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">appengine.apps.get</code> responds with a <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">404</code>.</p></li> <li><p>JuptierOne added support for ingesting the following <strong>new</strong> relationships:</p></li> </ul><table><thead><tr><th>Source</th> <th>class</th> <th>Target</th> </tr></thead><tbody><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">google_iam_binding</code></td> <td><strong>ASSIGNED</strong></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">google_group</code></td> </tr><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">google_iam_binding</code></td> <td><strong>ASSIGNED</strong></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">google_iam_service_account</code></td> </tr><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">google_iam_binding</code></td> <td><strong>ASSIGNED</strong></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">google_user</code></td> </tr><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">google_iam_binding</code></td> <td><strong>USES</strong></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">google_iam_role</code></td> </tr></tbody></table><ul><li><p>JupiterOne now handles cases where global <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">google_compute_image</code> has been removed from Google<br> Cloud and results in a <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">404</code> status code when attempting to fetch.</p></li> <li><p>JupiterOne will not fail in the step that fetches resource manager project when project cannot<br> be fetched.</p></li> </ul><h3 data-id="qualys">Qualys</h3> <ul><li>JupiterOne now provides details from the response body in the case of <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">400</code> <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Bad Request</code> when verifying authentication.</li> <li>JupiterOne now correctly handles response of <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">200</code> where <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">UNAUTHORIZED</code> displays in the body of the mesage. JupiterOne now displays to user as a configuration/authorization issue.</li> </ul><h3 data-id="okta">Okta</h3> <ul><li>JupiterOne has migrated to latest integration SDK for improved error handling and reporting.</li> <li>New properties added to resource:</li> </ul><table><thead><tr><th>Entity</th> <th>Properties</th> </tr></thead><tbody><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">okta_user</code></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">mfaEnabled</code></td> </tr></tbody></table><ul><li>New entity added:</li> </ul><table><thead><tr><th>Resources</th> <th>Entity <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">_type</code></th> <th>Entity <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">_class</code></th> </tr></thead><tbody><tr><td>Okta Rule</td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">okta_rule</code></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Configuration</code></td> </tr></tbody></table><ul><li>New relationships added:</li> </ul><table><thead><tr><th>Source Entity <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">_type</code></th> <th>Relationship <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">_class</code></th> <th>Target Entity <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">_type</code></th> </tr></thead><tbody><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">okta_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">okta_rule</code></td> </tr><tr><td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">okta_rule</code></td> <td><strong>MANAGES</strong></td> <td><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">okta_user_group</code></td> </tr></tbody></table> </article> </main>
.png)