From: Murdock, Joe (jmurdock@sharplabs.com)
Date: Wed Apr 16 2008 - 20:23:55 EDT
Here is another link to the SOH protocol specification:
http://download.microsoft.com/download/9/5/E/95EF66AF-9026-4BB0-A41D-A4F
81802D92C/Windows_Communication_Protocols.zip
This link will download a zip file containing all the publically
available Microsoft communications protocol specifications. If you're
going to read the SOH spec, it's helpful to have the entire collection
as the SOH spec contains relative links to other documents in the
collection, such as the MS-PEAP and MS-HCEP protocols used as transports
by SOH.
Joe
-----Original Message-----
From: owner-ids@pwg.org [mailto:owner-ids@pwg.org] On Behalf Of
thrasher@lexmark.com
Sent: Wednesday, April 16, 2008 8:29 AM
To: ids@pwg.org
Subject: IDS> NAP Statement of Health (SOH) link
It is advised that devices who want to become interoperable with NAP
implement the Statement of Health (SOH) for NAP. The protocol is
documented
here: http://msdn2.microsoft.com/en-us/library/cc246924.aspx
Microsoft NAP provides a means for third parties to define, measure and
cause action based on the health of the device. Third party services
that
implement the SOH need to define what it means for a device to be
healthy,
based on what they feel is important to secure and what is possible to
measure.
Administrators have the ability to allow non-SOH capable devices to
participate in a NAP controlled environment by placing such devices on
exception lists. Exceptions may introduce increased security risks to a
given network.
I can go into (slightly) more detail on Thursday.
Thanks,
Erhan
This archive was generated by hypermail 2.1.4 : Wed Apr 16 2008 - 20:24:06 EDT