Example Scan Result File

Using the --result-file parameter creates a file with evaluation results in the following format.

{
    "applicationId" : "...",
    "scanId" : "...",
    "reportHtmlUrl" : "http://...",
    "reportPdfUrl" : "http://.../pdf",
    "reportDataUrl" : "http://.../raw",
    "policyAction" : "None",
    "policyEvaluationResult" : {
        "alerts" : [...detailed list of components which caused the violation...],
        "affectedComponentCount" : 15,
        "criticalComponentCount" : 4,
        "severeComponentCount" : 65,
        "moderateComponentCount" : 36,
        "criticalPolicyViolationCount" : 4,
        "severePolicyViolationCount" : 85,
        "moderatePolicyViolationCount" : 46,
        "grandfatheredPolicyViolationCount" : 0,
        "legacyViolationCount" : 0
     }
}

applicationId - is the application in IQ Server against which you run policy evaluation

scanId - can be used in some rest api

reportHtmlUrl, reportPdfUrl, reportDataUrl - report with policy evaluation results in different formats

policyAction - policy evaluation outcome (can be None, Warn, Fail)

policyEvaluationResult - contains a summary of the evaluation:

alerts - contains information about components that caused a policy violation

affectedComponentCount - number of components that caused a policy violation

criticalComponentCount - number of critical components that caused a policy violation

severeComponentCount - number of severe components that caused a policy violation

moderateComponentCount - the number of moderate components which caused a policy violation

criticalPolicyViolationCount - number of critical policies that were violated

severePolicyViolationCount - number of severe policies that were violated

moderatePolicyViolationCount - number of moderate policies that were violated

grandfatheredPolicyViolationCount (depracated) - number of policies that were violated, but moved to grandfathered

legacyPolicyViolationCount - number of legacy policy violations