A couple of things to think about as we move towards the idea of Compliance As Code and a
central CLI/WebUI.
1.
We are moving away from authoring content in XML and towards a YAML
style format which
was shown at Defense in Depth last year.
Many people were smiling and liking the idea.
Even now, playing with
YAML as the authoring language at DevConf has people smiling and
exclaiming how easy it is to use. There is no perfect format, but we have had too much
feedback over the dislike of XML for authoring.
2. One guide
authoring language to many outputs. In essence, the build system would
consume
the YAML guides (migrated from XCCDF), Ansible, BASH, Inspec,
OVAL (possibly migrating
writing this in YAML), etc. to output in DS, XCCDF, Ansible/Bash roles, Inspec, etc. to be
consumed by the engine of your choice. Don't think that the OpenSCAP scanner should