Network Access Protection (NAP) : MSDN

Looking to integrate your product with NAP?

MS NAP Team — Fri, 15 Feb 2008 00:42:00 GMT

If so, you have probably already taken a look at our MSDN area, and probably even our sample code in the Platform SDK (…\Microsoft SDKs\Windows\v6.0\Samples\NetDs\NAP). Well, I have some good news for you. We worked with an awesome guy by the name of Dan Griffin (JWSecure, Inc.) to build a better example of how to integrate with NAP.

Dan really put something cool together that is closer to a real world implementation. I welcome you to sample his nicely done “Registry” System Health Agent (SHA) / System Health Validator (SHV).

We always welcome new NAP Partners! To find out how to become a NAP partner, drop us a line.

Cheers and NAP the WORLD!

Jeff Sigman
Senior Program Manager
Network Access Protection (NAP)

Please check out the NAP Blog, FAQ, Forum, MSDN and Site.

NAP SDK updates for SHA/V developers

MS NAP Team — Wed, 18 Oct 2006 01:35:00 GMT

For those who are developing SHA/SHV components, please take a moment to read the following changes in the document. The sample code will be modified in the future version of the SDK.

If you need further clarification, please use the public forum http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=576&SiteID=17 to post your question.

Thanks.

Calvin Choe
NAP Ninja
Microsoft Corporation

The documentation for the SoHAttributeValue union is incomplete. The description of the vendorId member of SoHAttributeValue should read as follows:

The ID value for the SHA/SHV pair. This is a 4-byte code; the first 3 bytes are the IETF-assigned SMI code of the vendor and the last byte identifies the component itself. See NapMicrosoftVendorIds.h for IDs used to identify internal Microsoft enforcers and system health components.

When implementing a SHA or SHV, do not use the ID values assigned to internal Microsoft enforcers.

In the future, the SoHAttributeValue documentation on MSDN will be updated with this new description.

Before you can use the sample shipping with the SDK, you must change the vendorId value used by the sample SHA and SHV. You must also remove an unnecessary line of code. Here are the required changes:

Open Callback.cpp. If you installed the SDK to the default location, this file will be found in C:\Program Files\Microsoft SDKs\Windows\v6.0\Samples\NetDs\NAP\SHA\EXE.
Find the line value.vendorSpecificVal.vendorId = MicrosoftVendorId;
Change this line to value.vendorSpecificVal.vendorId = QuarSampleSystemHealthId;
Save your changes.
Open SampleShv.cpp. If you installed the SDK to the default location, this file will be found in C:\Program Files\Microsoft SDKs\Windows\v6.0\Samples\NetDs\NAP\SHV.
Delete line 348, which reads goto Cleanup;
Replace all instances of the line (pAttrValue->vendorSpecificVal.vendorId == MicrosoftVendorId) with (pAttrValue->vendorSpecificVal.vendorId == QuarSampleSystemHealthId). In the original version of SampleShv.cpp, there are two instances of this conditional statement, one at line 514 and one at line 524.
Save your changes and build the sample.

Cathy Dumas

Programming Writer

NAP API reference documentation updated on MSDN

MS NAP Team — Thu, 10 Aug 2006 17:00:00 GMT

SHA and QEC developers take note: the NAP API reference documentation has been updated on MSDN with information about API support on NAP for Windows XP with Service Pack 2. All client APIs are supported on this platform. The topic About NAP for Windows XP with Service Pack 2 provides information about differences in NAP functionality for XP and Vista. The topic also has information about joining the beta program.

More MSDN updates for NAP:

We’ve made the following changes to the NAP API documentation:

· The topic InitializeNapAgentNotifier was added.

· The topic UninitializeNapAgentNotifier was added.

· The topic NapNotifyType was added.

· The methods of the INapClientManagement interface were updated. The methods are now declared in the napmanagement.h file.

Cathy Dumas

Programming Writer

NAP API reference material updated on MSDN

MS NAP Team — Thu, 15 Jun 2006 23:16:00 GMT

The NAP API documentation has been updated on MSDN. Here’s a list of changes for the beta 2 docs:

There are two new topics describing the NAP constants, entitled INapEnforcementClientConnection Constants and NAP Type Constants.
The description of the hintTimeOutInMsec parameter in the topic INapSystemHealthValidator::Validate was updated.
The configClsid member was added to the topic NapComponentRegistrationInfo.
The syntax block of the SoHAttribute structure was updated.
The description of the machineName parameter in the topic INapSystemHealthValidationRequest::GetMachineName was updated. The method description was also updated.
The description of the percentage member in the topic FixupInfo was updated.
The Remarks section of the topic INapEnforcementClientCallback::NotifySoHChange was updated.
A description of the E_PENDING return value was added to the topic INapSystemHealthAgentCallback::ProcessSoHResponse.

Some other minor changes were made to fix typos and add links to pages.

If you are looking for sample code, download and install the Vista Beta 2 SDK (available here). If you install the SDK to the default location, you will find the NAP sample application in C:\Program Files\Microsoft SDKs\Windows\v1.0\Samples\NetDS\NAP.

To send feedback on the documentation, click the “Send comments about this topic to Microsoft” link at the bottom of any API reference page. A programming writer will email you with a response. The majority of these updates were in response to feedback from customers. Thanks for all the great comments we have received so far on the docs. Your input is important!

Cathy Dumas

Programming Writer