Azul Intelligence Cloud

Monitors code executed by the Java runtime in production to collect data on what code runs versus is simply present. Uses sophisticated techniques to identify code and map to a Java-specific Common Vulnerabilities and Exposures (CVE) database to generate accurate results unattainable by other tools.

Focuses scarce human effort where vulnerable code is or has been used versus simply present, to help reduce issue backlogs. Retains component and code use history, focusing forensic efforts to determine if vulnerable code was actually exploited prior to it being known as vulnerable.

When previously unknown vulnerabilities in Java applications are published, the Azul Vulnerability Detection CVE knowledge base is rapidly updated, so DevOps team can efficiently triage critical vulnerabilities in production during events like Log4J. 

JVM Inventory combined with the Azul Migration Toolkit (AMT) or other ITAM tools provides enterprises with the most accurate, complete view of their Oracle Java footprint.

JVM Inventory uses information that is only available at runtime to map Oracle JVMs to the applications that are using them. Migration teams can quickly notify application owners that these instances are being replaced, which can slash weeks or months off the average 6-9 month timeline of unaided migrations.

Once Oracle Java is eliminated, JVM Inventory immediately detects any new running Oracle JVMs, enabling organizations to remediate regressions and ensure Oracle Java stays out of an enterprise’s application infrastructure, mitigating audit risks.