Concluded WG Security Automation and Continuous Monitoring (sacm)

Changed milestone "Adopt as a WG document at least one Data Model submission instantiating the SACM Information Model", set due date to November 2017 from November 2015

SACM met on Tuesday (2016-11-15) at 9:30 for 2.5 hours, and we discussed our architectural approach, how to get software identifiers collected from endpoints, and open issues with our information model.  We also started considering how we can keep our information model minimized but extendable based on some real-world state collection data. 

Next steps include enumerating the functions/interfaces and data that we need flowing through the SACM environment to support our vulnerability assessment scenario.

SACM met on Wednesday to discuss it’s recently adopted vulnerability assessment draft [1], a couple of individual submissions (software identification [2] and endpoint compliance profile [3]), and the SACM information model [4][5].

SACM will meet again on Friday to discuss it’s terminology draft [6], and the work done this week on solidifying the structure of our information model.

Our requirements draft [7] has made it through WGLC and we intend to prepare this for shepherding through the IESG.

During the Wednesday meeting there was consensus, which will be verified on the list, to adopt the software identification I-D [2] as a WG draft.

The endpoint compliance profile draft will be updated at least once more to make some clarifications before the WG is willing to consider adoption.


[1] https://datatracker.ietf.org/doc/draft-coffin-sacm-vuln-scenario/
[2] https://datatracker.ietf.org/doc/draft-birkholz-sacm-coswid/
[3] https://datatracker.ietf.org/doc/draft-haynes-sacm-ecp/
[4] https://datatracker.ietf.org/doc/draft-ietf-sacm-information-model/
[5] https://tools.ietf.org/html/draft-cam-winget-sacm-information-model-00
[6] https://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/
[7] https://datatracker.ietf.org/doc/draft-ietf-sacm-requirements/

Changed milestone "Submit SACM Information Model Internet-Draft to the IESG for consideration as an Informational RFC", set description to "Submit SACM Information Model Internet-Draft to the IESG for consideration as a Standards-track RFC"

Changed milestone "Adopt as a WG document at least one Data Model submission instantiating the SACM Information Model", set state to active from review, accepting new milestone

Deleted milestone "Submit protocol and data format for retrieving configuration and policy information for driving data collection and analysis Internet-Draft to the IESG for consideration as Proposed Standard"

Deleted milestone "Initial submission of an Internet-Draft for a protocol and data format for retrieving configuration and policy information for driving data collection and analysis", not present in approved charter

Added milestone "Submit protocol and data format for collecting endpoint posture Internet-Draft to the IESG for consideration as Proposed Standard ", due 2014-09-30, from approved charter

Added milestone "Initial submission of protocol and data format for retrieving configuration and policy information for driving data collection and analysis Internet-Draft", due 2014-01-31, from approved charter

Deleted milestone "Submission to the IESG of the Internet-Draft for a protocol and data format for retrieving configuration and policy information for driving data collection and analysis for consideration as standards-track RFC"

Changed milestone "Submission to the IESG of the Internet-Draft on SACM Architecture for consideration as Informational RFC", set description to "Submit protocol and data format for collecting endpoint posture Internet-Draft to the IESG for consideration as Proposed Standard", set due date to September 2014 from April 2014

Changed milestone "Submission to the IESG of the Internet-Draft on Requirements for consideration as Informational RFC", set description to "Submit protocol and data format for retrieving configuration and policy information for driving data collection and analysis Internet-Draft to the IESG for consideration as Proposed Standard", set due date to September 2014 from April 2014

Changed milestone "Submission to the IESG of the Internet-Draft on Use Cases for consideration as Informational RFC", set description to "Submit SACM Architecture Internet-Draft for consideration as Standards-track RFC"

Changed milestone "Initial submission of an Internet-Draft on Requirements", set description to "Initial submission of an Internet-Draft on Requirements taking into consideration RFC5706 and RFC3535"

Added milestone "Submission to the IESG of the Internet-Draft a protocol and data format for collecting actual endpoint posture for consideration as standards-track RFC", due October 2014

Added milestone "Submission to the IESG of the Internet-Draft for a protocol and data format for retrieving configuration and policy information for driving data collection and analysis for consideration as standards-track RFC", due October 2014

Added milestone "Initial submission of an Internet-Draft for a protocol and data format for retrieving configuration and policy information for driving data collection and analysis", due January 2014