
Addendum to the ProCurve Access Control Security Design Guide
Updating the Access Control Design Process
Table
Factor | Weight | Selection |
Existing network |
| NAC 800 |
infrastructure |
|
|
|
|
|
Vulnerability to risks and |
| NAC 800 |
risk tolerance |
|
|
|
|
|
Management resources |
| NAC 800 |
|
|
|
Interoperability |
| NAC 800 |
requirements |
|
|
|
|
|
Total |
| NAC 800 |
|
|
|
For PCU, the NAC 800 (managed by IDM) is the better choice.
Table
Factor | Weight | Selection |
Existing network |
| NAP |
infrastructure |
|
|
|
|
|
Vulnerability to risks and |
| NAP |
risk tolerance |
|
|
|
|
|
Management resources |
| NAP |
|
|
|
Interoperability |
| NAP |
requirements |
|
|
|
|
|
Total |
| NAP |
|
|
|
For ProCurve, Inc., NAP (managed by IDM) is the better choice.
Choose the Endpoint Integrity Deployment Method
After you select the endpoint integrity solution, you must determine how you will deploy the solution you select. This addendum and the ProCurve Access Control Security Solution Design Guide focus on the deployment methods for the NAC 800. If you select Microsoft NAP, consult the related documenta- tion to understand the available deployment methods and select the best option for your organization.