Revision Summary Date Revision History Revision Class Comments 3/30/2012 1.0 New Released new document. 7/12/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 2.0 Updated and revised the technical content. 11/14/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 2.0 None No changes to the meaning, language, or formatting of the technical content.
5/15/2014 2.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 2.0 None No changes to the meaning, language, or formatting of the technical content. 10/16/2015 2.0 None No changes to the meaning, language, or formatting of the technical content. 9/26/2016 2.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 2.0 None No changes to the meaning, language, or formatting of the technical content.
Goal: To gain network access for a Client computer. Actors Client computer A Client computer is used to access and manipulate protected network resources. Client computers use the NAP protocols to communicate with the network to gain generic access to the network. NEP A NEP controls a Client computer's network access. A NEP uses the NAP services from a Network policy server to determine whether or not the client is sufficiently healthy to have network access. Stakeholders: None. Preconditions The identities of the user and the Client computer are configured in the account databases, such as . The Client computer and the NEP can communicate with each other. The NAP-related policies are expressed in a policy database used by the NPS. The NEP is configured to use NAP and supports the NAP extensions to data link protocols. The NEP and the NPS can communicate with each other by using . The NPS can communicate with Authentication Services and Active Directory. The NEP maintains a state that grants the Client computer network access. Success Guarantee: The NEP provides network access to the Client computer. Main Success Scenario Trigger: The Client computer attempts to access a resource on a network protected by a NEP. The NEP permits the Client computer's network access. The Client computer can access network resources over the network interface Post-Condition: The NEP allows network access to the Client computer. Extensions: None. Remediation Figure 17: Remediation use case Context of Use: This use case is employed when the client is noncompliant with the network policy and it is directed by on the to remediate its' configuration. Goal: To remediate the client based on the health evaluation response. The exact method of remediation depends on the specifics of the /. However, this document uses the / as described in , as an example. Actors
Index A 31 24 18 26 C 30 40 31 25 26 25 26 18 Considerations 31 31 D Dependencies 26 25 Design intent 27 26 29 28 E 25 30 Examples 32 35 Extensibility 39 30 30 25 F 18 Functional requirements - overview ( 4, 18) G 12 H 30 Health validation 27 I 39 31 15 26 4 M 39 O Overview 24 18 4 P 26 39 R 15 Remediation 29 Request network access 28 Requirements 31 30 18 26 S 31 18 25 26 25 30 4 24 System requirements - overview ( 4, 18) System use cases 27 26 29 28 T 24 40 U 26 27 29