Security Content Automation Protocol: Difference between revisions

Revision as of 20:54, 22 March 2011

Revision as of 15:31, 20 July 2011

Line 39:

A vendor seeking validation of a product that implements a SCAP component ([[Common Vulnerabilities and Exposures|CVE]], CCE, CPE, [[CVSS]], [[XCCDF]] or [[Open Vulnerability and Assessment Language|OVAL]]), or capability ([[Federal Desktop Core Configuration]] (FDCC) Scanner, Authenticated Configuration Scanner, Authenticated Vulnerability Scanner, Unauthenticated Vulnerability Scanner, Intrusion Detection and Prevention, Patch Remediation, Mis-configuration Remediation, Asset Management, Asset Database, Vulnerability Database, Mis-configuration Database or Malware Tool), should contact an NVLAP accredited SCAP validation laboratory for assistance in the validation process.

A customer who is subject to the [[Federal Information Security Management Act of 2002|FISMA]] requirements, or wants to use security products that have been tested and validated to the SCAP standard by an [http://nvd.nist.gov/scapproducts.cfm#scap_labs independent third party laboratory] should visit the [http://nvd.nist.gov/scapproducts.cfm SCAP validated products web page] to verify the status of the product(s) being considered.

==External links==