OVAL is the Open Vulnerability Assessment Language, an open standard for not just conveying checklist information but also how to gather and test for compliance, for example, check a registry key for specified values and compare to the required settings for compliance.
In short, it means our menu of Compliance Checklists is now huge and more readily caters for the differing requirements of commercial, federal and military organizations. The industry’s quest for a unified standard that caters for the similar but separate requirements for
- compliance auditing
- vulnerability management
- inventory and configuration management
- remediation and mitigation
has taken several evolutionary steps, all with a range of acronyms at every step. Likewise, NNT have needed to sequentially expand and refine our own technological capabilities.
The first important step along this path was to ensure CIS checklist content could be utilized and, as a result, NNT Change Tracker is now a Certified Vendor for CIS Benchmarks.
The Center For Internet Security is recognized as one of the most valuable and useable sources of vulnerability and hardening intelligence. Significantly, CIS content is drawn from a consensus of Manufacturers, OEMs, security product vendors and researchers of exploits and vulnerabilities.
CIS Checklists are provided in a wide range of formats and include a detailed background to the vulnerability, how to audit for its existence, and how to remediate if found.
Checklists are provided in both the CIS’s own Embedded Check Language rulesets (for use in their CIS-CAT tool) and the more standardized, Extensible Configuration Checklist Description Format (XCCDF). NNT Change Tracker can now utilize both CIS checklist ruleset formats.
OVAL and XCCDF, STIGs and SCAP
Adoption of OVAL however opens up a much wider range of checklists including those provided in the National Vulnerability Database repository here
and also the checklists provided for the US Military known as STIGs (Security Technical Implementation Guides)
Of course, SCAP (Security Content Automation Protocol) has now been positioned as an all-encompassing standard and is a superset of OVAL and XCCDF.
While SCAP leverages OVAL and XCCDF, using the same checklist ruleset content, this is combined with vulnerability scoring metrics (CVSS) and other standardized platform, vulnerability and configuration enumeration/naming conventions to provide a more comprehensive standard (respectfully CPE, CVE and CCE – see www.mitre.org for more details).
It is important to note however, that the ‘meat’ of SCAP is still the OVAL content and NNT can just as easily use SCAP’s OVAL content.
Share this blog post