New Features and Improvements
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.
Allowsasset relationships will now appear as green in the graph and
Deniesrelationships will now appear as red.
Users can now “Tag” rules in order to group them together and search for them more easily.
Policy ID, Revision number, and "Powered by J1" footnote are now configurable by the user when downloading a Policy PDF.
COMING SOON: J1QL queries will soon support returned property aliases.
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)
- JupiterOne now supports Auth0 with an initial integration. Please see documentation for more details.
#255 - Now
#243 - JupiterOne now assigns boolean values to
#248 - JupiterOne now always executes steps in org child projects even if the child project has service disabled
New properties added to resources:
Added support for ingesting the following new relationships:
Source _class Target
JupiterOne now uses
name || loginfor
- JupiterOne by default ingests host detections with types
Potential, Confirmed. We recommend avoiding ingesting Info detections until you are ready to process them in a meaningful way.
Fixed bug that caused
jupiterone_user_groupentities in the graph.
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.