eWEEK content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More.
LAS VEGAS—SCAP, the Security Content Automation Protocol now in beta development at the National Security Agency, could streamline the way civilian organizations enable automated vulnerability management and compliance with regulations, including FISMA.
Discussed at a full-capacity crowd keynote speech at the Black Hat 2007 briefing given by Tony Sager, chief of the Vulnerability Analysis and Operations Group at the NSA, SCAP should be included in proposal requests that security managers send to vendors.
SCAP uses data feeds from the NVD (National Vulnerability Database), which is defined and maintained by the National Institute of Standards and Technology, better known as NIST. SCAP is an open standard, and the NVD is available license-free.
SCAP uses information from six open standards, including CVE (Common Vulnerability and Exposures) and CCE (Common Configuration Enumeration ), both overseen by MITRE, along with data provided by the XCCDF (eXtensible Configuration Checklist Description Format), a standard XML expression for specifying checklists and reporting results from those checklists.
Although it seems like a bottomless pit of alphabet soup, SCAP basically boils down to a way for organizations to specify how systems and applications should be equipped to report their current security configuration and a way for external tools to be used to confirm these configurations to generate reports. Most of the literature around SCAP and Sagers comments focused on FISMA (Federal Information Security Management Act) compliance, which guides how the federal government and contractors secure computers and data networks.
However, security managers can use SCAP reporting tools to issue break-fix reports that actually dispatch technicians to ensure that out-of-compliance machines are remediated. According to Sager at Blackhat, “SCAP is focused on automating compliance. Its an evolving and very exciting development.”
The list of standards that supply data to the NVD that SCAP uses to determine compliance are impressive. Security managers who are faced with vulnerability management will likely benefit from bringing a degree of uniformity to their assessment, remediation and reporting efforts that SCAP and SCAP-enabled tools will offer.
SCAP content is made up of security checklists data in XML format. The checklist data is built using efforts from a variety of U.S. government security and military groups. The data enumerates product names, vulnerabilities associated with those products and standards for reporting a score that indicates the seriousness of the vulnerability.
SCAP scans look not only at the vulnerabilities in specific products, but also at the way in which those products are configured. Configuration issues and software flaws all generate impact scores that are reported.
Labs Technical Director Cameron Sturdevant can be reached at cameron_sturdevant@ziffdavis.com.
Check out eWEEK.coms Security Center for the latest security news, reviews and analysis. And for insights on security coverage around the Web, take a look at eWEEKs Security Watch blog.