Eh? What’s that mean? Developer Days is a weeklong conference where they get down into the weeds about the various SCAP schemas and how they fit into the overall program of security automation.
Highlights and new ideas:
Remedial Markup Language: Fledgeling schema to describe how to remediate a vulnerability. A fully automated security system would scan and then use the RML content to automagically fix the finding… say, changing a configuration setting or installing a patch. this would be much awesome if combined with the CVE/CWE so you have a vulnerability scanner that scans and fixes the problem. Also needs to be kept in a bottle because the operations guys will have a heartattack if we are doing this without any human intervention.
Computer Network Defense: There is a pretty good scenario slide deck on using SCAP to automate hardening, auditing, monitoring, and defense. The key from this deck is how the information flows using automation.
Common Control Identifier: This schema is basically a catalog of controls (800-53, 8500.2, PCI, SoX, etc) in XML. The awesomeness with this is that one control can contain a reference implementation for each technology and the checklist to validate it in XCCDF. At this point, I get all misty…
Open Checklist Interactive Language: This schema is to capture questionaires. Think managerial controls, operational controls, policy, and procedure captured in electronic format and fed into the regular mitigation and workflow tools that you use so that you can view “security of the enterprise at a glance” across technical and non-technical security.
Network Event Content Automation Protocol: This is just a concept floating around right now on using XML to describe and automate responses to attacks. If you’re familiar with ArcSight’s Common Event Format, this would be something similar but on steroids with workflow and a pony!
Attendance at developer days is limited, but thanks to all the “Powar of teh Intarwebs, you can go here and read the slides!
Similar Posts: