attachment-0001
<div dir="ltr"><div><div><div><div>Hi Joe,<br><br></div>Some thoroughly useful definitions from the latest IETF Security<br></div>Automation Configuration Management (SACM) terminology draft.<br><br></div>Cheers,<br></div>
- Ira<br><div><div><div><div><div><div><div dir="ltr"><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div>
<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Adam W. Montville</b> <span dir="ltr"><<a href="mailto:adam.w.montville@gmail.com">adam.w.montville@gmail.com</a>></span><br>
Date: Fri, Aug 15, 2014 at 10:45 AM<br>Subject: [sacm] Fwd: New Version Notification for draft-ietf-sacm-terminology-05.txt<br>To: <a href="mailto:sacm@ietf.org">sacm@ietf.org</a><br><br><br><div style="word-wrap:break-word">
<div>I've submitted an update to our terminology draft today, which reflects the following additions. If these additions have been made in the wrong place, or if you have better definitions, please speak up.</div><div>
<br></div><div>Broker: An entity providing and/or connecting services on the behalf of other architectural components. Within the SACM Architecture, for example, a broker may provide authorization services and find, upon request, entities providing requested services.</div>
<div><br></div><div>Capability: The extent of an architectural component's ability. For example, a Posture Information Provider may only provide endpoint management data, and then only a subset of that data.</div><div>
<br></div><div>Client: An architectural component receiving services from another architectural component.</div><div><br></div><div>Consumer: An architectural component receiving information from another architectrual component.</div>
<div><br></div><div>Function: A behavioral aspect of a particular architectural component, which belies that component's purpose. For example, the Management Plane can provide a brokering function to other SACM architectrual components.</div>
<div><br></div><div>Management Plane (TBD per list; was "Control Plane"): Architectural component providing common functions to all SACM participants, including authentication, authorization, capabilities mappings, and the like.</div>
<div><br></div><div>Provider: An architectural component providing information to another architectrual component.</div><div><br></div><div>Proxy: An architectural component providing functions, information, or services on behalf of another component, which is not directly participating in the architecture.</div>
<div><br></div><div>Repository: An architectural component intended to store information of a particular kind. A single repository may provide the functions of more than one repository type (i.e. configuration baseline repository, assessment results repository, etc.)</div>
<div><br></div><div>Role: A label representing a collection of functions provided by a particular architectural component.</div><div><br></div><div>Supplicant: The entity seeking to be authenticated by the Management Plane for the purpose of participating in the SACM architecture.</div>
<div><br></div><div>Regards,</div><div><br></div><div>Adam</div><div><br><div>Begin forwarded message:</div><br><blockquote type="cite"><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family:'Helvetica';color:rgba(0,0,0,1.0)"><b>From: </b></span><span style="font-family:'Helvetica'"><a href="mailto:internet-drafts@ietf.org" target="_blank">internet-drafts@ietf.org</a><br>
</span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family:'Helvetica';color:rgba(0,0,0,1.0)"><b>Subject: </b></span><span style="font-family:'Helvetica'"><b>New Version Notification for draft-ietf-sacm-terminology-05.txt</b><br>
</span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family:'Helvetica';color:rgba(0,0,0,1.0)"><b>Date: </b></span><span style="font-family:'Helvetica'">August 15, 2014 at 9:00:01 AM CDT<br>
</span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family:'Helvetica';color:rgba(0,0,0,1.0)"><b>To: </b></span><span style="font-family:'Helvetica'">David Waltermire <<a href="mailto:david.waltermire@nist.gov" target="_blank">david.waltermire@nist.gov</a>>, David Harrington <<a href="mailto:ietfdbh@comcast.net" target="_blank">ietfdbh@comcast.net</a>>, Adam W. Montville <<a href="mailto:adam.w.montville@gmail.com" target="_blank">adam.w.montville@gmail.com</a>>, "David Harrington" <<a href="mailto:ietfdbh@comcast.net" target="_blank">ietfdbh@comcast.net</a>>, "David Waltermire" <<a href="mailto:david.waltermire@nist.gov" target="_blank">david.waltermire@nist.gov</a>>, "Adam W. Montville" <<a href="mailto:adam.w.montville@gmail.com" target="_blank">adam.w.montville@gmail.com</a>>, "Nancy Cam-Winget" <<a href="mailto:ncamwing@cisco.com" target="_blank">ncamwing@cisco.com</a>>, Nancy Cam-Winget <<a href="mailto:ncamwing@cisco.com" target="_blank">ncamwing@cisco.com</a>><br>
</span></div><br><div><br>A new version of I-D, draft-ietf-sacm-terminology-05.txt<br>has been successfully submitted by Adam W. Montville and posted to the<br>IETF repository.<br><br>Name:<span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>draft-ietf-sacm-terminology<br>
Revision:<span style="white-space:pre-wrap"> </span>05<br>Title:<span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>Terminology for Security Assessment<br>Document date:<span style="white-space:pre-wrap"> </span>2014-08-15<br>
Group:<span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>sacm<br>Pages:<span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>9<br>URL: <a href="http://www.ietf.org/internet-drafts/draft-ietf-sacm-terminology-05.txt" target="_blank">http://www.ietf.org/internet-drafts/draft-ietf-sacm-terminology-05.txt</a><br>
Status: <a href="https://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/" target="_blank">https://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/</a><br>Htmlized: <a href="http://tools.ietf.org/html/draft-ietf-sacm-terminology-05" target="_blank">http://tools.ietf.org/html/draft-ietf-sacm-terminology-05</a><br>
Diff: <a href="http://www.ietf.org/rfcdiff?url2=draft-ietf-sacm-terminology-05" target="_blank">http://www.ietf.org/rfcdiff?url2=draft-ietf-sacm-terminology-05</a><br><br>Abstract:<br> This memo documents terminology used in the documents produced by<br>
SACM (Security Automation and Continuous Monitoring).<br><br><br><br><br>Please note that it may take a couple of minutes from the time of submission<br>until the htmlized version and diff are available at <a href="http://tools.ietf.org" target="_blank">tools.ietf.org</a>.<br>
<br>The IETF Secretariat<br><br></div></blockquote></div><br></div><br>_______________________________________________<br>
sacm mailing list<br>
<a href="mailto:sacm@ietf.org">sacm@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/sacm" target="_blank">https://www.ietf.org/mailman/listinfo/sacm</a><br>
<br></div><br></div></div></div></div></div></div>