Bug 2038900 - [RFE] openscap report in json format
Summary: [RFE] openscap report in json format
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: openscap
Version: 9.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 9.1
Assignee: Jan Černý
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-10 14:04 UTC by Markus Schibli
Modified: 2023-08-17 14:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Story
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-1480 0 None Migrated None 2023-08-17 14:17:01 UTC
Red Hat Issue Tracker RHELPLAN-107294 0 None None None 2022-01-10 14:11:37 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.