Bug 2038900

Summary:	[RFE] openscap report in json format
Product:	Red Hat Enterprise Linux 9	Reporter:	Markus Schibli <mschibli>
Component:	openscap	Assignee:	Jan Černý <jcerny>
Status:	CLOSED MIGRATED	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9.0	CC:	ekolesni, jcerny, matyc, mhaicman, mmarhefk, vpolasek
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	9.1
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-18 07:27:31 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Markus Schibli 2022-01-10 14:04:23 UTC

Description of problem:
Customer would like to have the output of the openscap scanner in json format

Version-Release number of selected component (if applicable):
Openscap versions for RHEL8.x / RHEL9.x

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
currently the openscap scanner output is only in xml format available

Expected results:
it should be possible to have the choice between json and xml format for the openscap scanner output. 

Additional info:
There are discussion in https://github.com/OpenSCAP/openscap/issues/1555 , but no progress at all.

Comment 4 Evgeny Kolesnikov 2022-01-24 15:16:26 UTC

NIST does not have a standard for SCAP documents in any format other than XML. It is impossible to directly map an XML structure into a JSON, therefore it is unclear how should the end result look.

Comment 8 RHEL Program Management 2023-08-17 14:13:17 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 9 RHEL Program Management 2023-08-18 07:27:31 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.