Skip to content

Writing OVAL Content

Jump to bottom Edit New page
Greg Elin edited this page Jul 20, 2015 · 20 revisions

SCAP-Security-Guide Authoring Conventions

Understanding the following conventions will make it easier for you to navigate the SCAP-Security-Guide repository and author content.

  • All OVAL definitions are written as source OVAL XML files expressed in a shorthand syntax
  • Each source OVAL XML definition defines exactly one vulnerability assessment definition
  • Each source OVAL XML files is named for the vulnerability assessed using underscores (example: accounts_password_pam_decredit.xml)
Add a custom footer
Add a custom sidebar
Clone this wiki locally