Skip to main content

JupiterOne Release Notes - August 2025

Executive Summary​

Key strategic initiatives include the implementation of caching mechanisms in the application layer, optimization of backend services, and introduction of new integrations to facilitate seamless data flow. Enhancements to user interfaces, API response times, and compliance tracking capabilities are also prominent in this release. Collectively, these changes are designed to empower users with quicker access to insights and more robust tools for compliance and security management, fostering a more efficient operational environment. As we continue to innovate, user feedback remains pivotal to our development roadmap, ensuring that we meet the evolving needs of our enterprise customers.

Application​

Bug Fixes​

  • Fixed Timeout Error in Long-Running Queries: An issue that previously caused timeout errors during the execution of long-running queries has been effectively resolved. This bug manifested in scenarios involving large datasets, leading to frustration and inefficiencies for users attempting to analyze extensive data. The query execution engine has undergone significant adjustments, allowing for better resource management and optimized processing times. As a result, users can now confidently execute complex queries without encountering timeout interruptions, thus enhancing reliability and usability across the query feature.

Integrations​

New Integrations​

  • Ingest AWS CloudWatch Log Metric Filters: The integration now includes functionality to ingest AWS CloudWatch log metric filters directly into the JupiterOne graph, enhancing users' compliance tracking capabilities. This integration has been augmented to pull and transform log data into actionable insights that can be leveraged for compliance assessments. Users will gain improved visibility into their cloud operations, enabling more effective oversight of compliance metrics and enhancing operational accountability. It is essential to configure AWS access appropriately to ensure successful ingestion of CloudWatch logs.

Security Updates​

  • GitLab Integration Updated to Use Vulnerability_Findings REST Endpoint: The GitLab integration has been significantly improved by transitioning to the new vulnerability_findings REST endpoint, which enhances vulnerability tracking accuracy. This update involved a thorough refactor of the integration to replace outdated endpoints, resulting in a more efficient data retrieval process. Users will benefit from increased accuracy in vulnerability data, which will now reflect real-time insights and faster response times to potential security threats. No additional configuration is needed following this update, ensuring a seamless transition for users.

Content​

Bug Fixes​

  • Corrected Article Display Issues in Knowledge Base: The Knowledge Base has undergone a fix for display issues affecting certain articles on mobile devices. Problems with rendering due to CSS and responsiveness have been rectified to ensure a consistent and professional appearance across all platforms. Users accessing the Knowledge Base on mobile devices will now experience a seamless experience, which is critical for those needing to access essential information while on-the-go.

Breaking Changes​

This release includes a significant change in the authentication process, now requiring the adoption of multi-factor authentication (MFA) for all users. To facilitate this migration, users are urged to review their authentication settings and set up preferred MFA options. Detailed instructions on configuring MFA can be found in the updated user documentation. The transition is necessary to enhance security and protect user accounts from unauthorized access.

Known Issues​

Currently, there are no additional known issues reported in this release. Users are encouraged to report any new issues they encounter to the support team for prompt resolution.

Additional Notes​

  • Performance metrics indicate a substantial improvement in query execution times following the implementation of prompt caching, with a noted decrease in average response times by up to 50%.
  • Upcoming deprecations include older API endpoints that will be phased out in the next release cycle, allowing users to prepare for migration to newly established endpoints.
  • Detailed documentation regarding all new features, enhancements, and configuration notes is available on the JupiterOne documentation site. Users are encouraged to review this material to fully utilize the platform's capabilities.

These release notes provide an exhaustive overview of the August 2025 updates to JupiterOne, ensuring that enterprise customers have the necessary information to navigate the changes effectively and leverage new features to their fullest potential.

Contents