Improve CSV and JSON output

[silverhack]

It is a common request to have a compliance report separated in CSV or JSON output, rather than exported in single RAW files, for easier consumption by other tools. Actually, CSV, JSON and CLIXML output are a bit redundant and probably not useful, so instead saving metadata into RAW files, it would be nice to be able to export pass/fails compliance results into a well formatted CSV and JSON files.

On the other hand, the output should be consistent across all formats. As an improvement, CSV and JSON outputs should contain the same fields and same field name in both cases. That consolidated output could then be used for further processing and for easier consumption by other tools.

Finally, the Excel output was deprecated in Monkey365 and will be removed two releases later (0.91.4).

[silverhack]

Hi all,

The proposed CSV will have the following headers:

"ASSESSMENT_START_TIME"
"TENANT_ID"
"TENANT_NAME"
"UNIQUE_ID"
"PROVIDER"
"FINDING_ID"
"FINDING_TITLE"
"FINDING_TYPE"
"SERVICE_NAME"
"SEVERITY_ID"
"SEVERITY"
"FINDING_DESCRIPTION"
"FINDING_RATIONALE"
"FINDING_REMEDIATION"
"FINDING_REFERENCE_URL"
"SUBSCRIPTION_ID"
"SUBSCRIPTION_NAME"
"RESOURCE_LOCATION"
"RESOURCE_TYPE"
"RESOURCE_ID"
"RESOURCE_NAME"
"RESOURCE_GROUP"
"RESOURCE_TAGS"
"COMPLIANCE"

It is strongly based on the Open CyberSecurity Schema Framework schema for cloud findings.

For JSON data, property names will be converted to camelCase.

Please, do let me know if you have ideas about how to improve CSV and JSON data output.

Thanks,