De Morgan’s Law in JupiterOne
If you recently read about the breaking fix JupiterOne introduced to maintain J1QL language correctness as defined by De Morgan's Law you may have found yourself in need of a refresher of the operations available in J1QL queries. The JupiterOne platform has several methods available to leverage operators to filter your query results.
Selecting multiple entities or relationships:
( class/type_1 | class/type_2 )
Comparing properties:
AND OR
Why did JupiterOne introduce this change?
JupiterOne strives to align with standard mathematical theory in our query language. J1 has updated J1QL to adhere to De Morgan’s Law, which explains that the complement of the product of all the terms is equal to the sum of the complement of each term. The laws are named after Augustus De Morgan who formally defined the law.
How does this change impact J1QL?
This update to J1QL means customers may notice a difference in their query results when using a != followed by a set of arguments offset by parenthesis.
Prior behavior:
`!= (A and B and C)` is equivalent to `!= A and !=B and != C`
Updated behavior following De Morgan's Law
`!= (A and B and C)` is equivalent to the expression`!= A or != B or != C’
Read the full article by by Tony Ramirez and Jayson Jensen, including code snippets, on the JupiterOne blog.
This Month's Leaders
Categories
- 336 All Categories
- Featured Categories
- 7 About the AskJ1 Community
- 11 Product Announcements
- From Mission Control
- 1 Rapid Response
- 3 How J1 Uses J1
- Topics
- 131 Asset Management
- 56 Compliance & Reporting
- 65 Security Operations
- 40 Security Engineering
- 5 Open Source
- 18 News, Careers and More