Network Admission Control (NAC) for Securing Endpoint Devices - Desklib

The report discusses the implementation procedures of NAC Systems in order to secure the endpoint devices in ABC Company. These systems are able to protect and secure the endpoint devices used within the company. The project discusses the various kind of plans based on the implementation of the systems. The report also discusses the number of resources that would be required within the project. The estimated budget and time of the project have been proposed within the report. The different risks that might affect the project have been discussed. The report also discusses the communication procedures between stakeholders. The process of deployment of the project has been discussed in the report. The recommendations based on the project have also been discussed within the report.

Running head: NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES

1NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
Executive Summary
The report discusses the implementation procedures of NAC Systems in order to secure the endpoint
devices in ABC Company. These systems are able to protect and secure the endpoint devices used within
the company. The project discusses the various kind of plans based on the implementation of the
systems. The report also discusses the number of resources that would be required within the project.
The estimated budget and time of the project have been proposed within the report. The different risks
that might affect the project have been discussed. The report also discusses the communication
procedures between stakeholders. The process of deployment of the project has been discussed in the
report. The recommendations based on the project have also been discussed within the report.

2NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
Table of Contents
1. Outline of Project....................................................................................................................................3
2. Project Requirements (Functional and Non-Functional)..........................................................................3
3. Project Team Members...........................................................................................................................4
4. Project Plan.............................................................................................................................................4
4.1 Determination of Project Scope.........................................................................................................4
4.1.1 Work Breakdown Structure (WBS)..............................................................................................4
4.2 Estimation of Time for Project...........................................................................................................4
4.2 Resource needs for Project................................................................................................................4
4.3 Gantt Chart and Network Diagram for Project..................................................................................6
4.4 Cost Estimation for Project................................................................................................................9
4.5 Plan Quality for Project......................................................................................................................9
4.6 Stakeholder Analysis for Project......................................................................................................10
4.7 Plan Communication for Project......................................................................................................11
4.8 Plan project Risks Management......................................................................................................12
4.9 Plan Project Deployment.....................................................................................................................14
5. Project Sign Off......................................................................................................................................15
6. Post-Project Review and Recommendations.........................................................................................16
References.................................................................................................................................................17

3NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
1. Outline of the Project
The goal of the project is to implement NAC systems for securing the endpoint devices used
within ABC Company. The start of the project is Mon 27-05-19 and the end date of the project is Fri 04-
10-19. The primary goal of the project is to secure the endpoint systems of the company. The objective
of the company is to achieve a high secured networked system within the company.
2. Project Requirements (Functional and Non-Functional)
With the implementation of the Network Admission Control (NAC) within the networked system
of the company that would be responsible for securing the end-point systems, there could be defined
two forms of requirements. This could be defined as functional and non-functional requirements.
The functional requirements of the implementation of NAC are:
1. Use of System Standards – The MANs and LANs should be permitted for complying with the
existing and emerging standards
2. Issues of Regulatory – The networked components should be able to conform to the
necessary requirements based on different licensing providing agencies (Nunes et al., 2014).
3. Safety – The use of MANs and LANs should be specified in a certain manner that it would be
able to allow for the implementation of the requirements based on mechanical, electrical and material
safety purposes.
The different forms of non-functional requirements during the implementation of NAC are:
1. Authentication – The different users who would make use of the networked endpoint devices
should authenticate themselves before they would be granted permission for accessing into the
protected network (Kuliesius & Dangovas, 2016). Based on the authentication measures, the network
would be able to make different forms of policy-based decisions for characteristics based on device and
user identity.
2. Health status of Endpoint Devices – Before providing access to networks, the endpoint
devices should be checked. This would highly be able to ensure the vulnerabilities and parameters based
on security software configuration (Lee et al., 2014). The providing of network access would be
dependent on the results of the examination.

4NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
3. Authorization – The NAC could be configured for limiting a particular device into a specific
network. This process could be further tuned to some specific networks.
3. Project Team Members
The team members involved within the project are project managers, software developers,
software testers, quality assurance team, networking team and subject matter experts.
4. Project Plan
4.1 Determination of Project Scope
4.1.1 Work Breakdown Structure (WBS)
Implementation of NAC
for Endpoint Devices
Start Project Initial Planning and
Initiation
Meeting with the owners
Understanding the
requirements
Proposing the Idea for
NAC System
Implementation
Preparing a project plan
Approval of the project
plan
Preparing the financial
plan
Approval of the financial
plan
Completion of the phase
Technical Equipment
Procurement Phase
Preparing the requirement
plan for the technical
equipments
Contacting the proper
technical service provider
Procuring of the materials
Completion of the phase
Execution of the NAC
Implementation Process
Preparing the technical
plan for the project
Checking the endpoint
devices
Execution of the technical
plan
Testing of the end-point
devices after
implementation
Completion of the phase
Quality Assurance
Processes of the System
Preparing a quality
assurance test plan
Quality Assurance testing
process
Completion of the phase
Project Closure Phase
Documentation of the
project
Sign-off of project
Making of payments
End Project
(Figure 1: The Work Breakdown Structure for the Project)
(Source: Created by author)
4.2 Estimation of Time for the Project
The time taken for the project is 95 days.
4.2 Resource needs for the Project
The different resources required for the implementation project based on NAC includes the
need for human, software libraries and productive tools.
The human resources required for the project are: owners, project sponsors, project managers,
software developers, software testers, quality assurance team, networking team and subject matter
experts.

5NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
The software libraries included within the implementation of NAC are such type of computer
software that would be licensed under open-source licenses and free software licenses (Koh, Oh & Im,
2014).
The different productivity tools that would be used during the implementation of NAC are:
mobile supported productivity applications and tools.

6NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
4.3 Gantt Chart and Network Diagram for the Project
ID Outline
Number
Task
Mode
Task Name Duration Start Finish PredecessorsResource Names
0 0 Implementation of NAC for
Endpoint Devices
95 days Mon
27-05-19
Fri
04-10-19
1 1 Start Project 0 days Mon
27-05-19
Mon
27-05-19
2 2 Initial Planning and
Initiation
21 days Mon
27-05-19
Mon
24-06-19
3 2.1 Meeting with the owners 1 day Mon
27-05-19
Mon
27-05-19
1
4 2.2 Understanding the
requirements
1 day Tue
28-05-19
Tue
28-05-19
3
5 2.3 Proposing the Idea for
NAC System
Implementation
3 days Tue
28-05-19
Thu
30-05-19
3 Project
Manager,Project
Sponsor
6 2.4 Preparing a project plan 10 days Fri 31-05-19 Thu
13-06-19
5 Networking
Team
7 2.5 Approval of the project
plan
0 days Thu
13-06-19
Thu
13-06-19
4,6
8 2.6 Preparing the financial
plan
7 days Fri 14-06-19 Mon
24-06-19
7 Project
Manager,Project
Sponsor9 2.7 Approval of the financial
plan
0 days Mon
24-06-19
Mon
24-06-19
8
10 2.8 Completion of the phase 0 days Mon
24-06-19
Mon
24-06-19
9
11 3 Technical Equipment
Procurement Phase
15 days Tue
25-06-19
Mon
15-07-19
12 3.1 Preparing the
requirement plan for the
technical equipments
10 days Tue
25-06-19
Mon
08-07-19
10 Networking
Team,Project
Manager,Technical
Equipments[1]13 3.2 Contacting the proper
technical service provider
2 days Tue
09-07-19
Wed
10-07-19
12 Project
Manager
14 3.3 Procuring of the materials 3 days Thu
11-07-19
Mon
15-07-19
13 Technical
Equipments[1]
15 3.4 Completion of the phase 0 days Mon
15-07-19
Mon
15-07-19
14
16 4 Execution of the NAC
Implementation Process
31 days Tue
16-07-19
Tue
27-08-19
17 4.1 Preparing the technical
plan for the project
7 days Tue
16-07-19
Wed
24-07-19
15 Networking
Team,Project
Manager,Software18 4.2 Checking the endpoint
devices
10 days Thu
25-07-19
Wed
07-08-19
17 Networking
Team
19 4.3 Execution of the technical
plan
15 days Thu
25-07-19
Wed
14-08-19
17 Networking
Team,Software
Developers20 4.4 Testing of the end-point
devices after
implementation
9 days Thu
15-08-19
Tue
27-08-19
19,18 Networking
Team,Software
Testers
21 4.5 Completion of the phase 0 days Tue
27-08-19
Tue
27-08-19
20
22 5 Quality Assurance Processes
of the System
15 days Wed
28-08-19
Tue
17-09-19
23 5.1 Preparing a quality
assurance test plan
5 days Wed
28-08-19
Tue
03-09-19
21 Quality
Assurance
Team24 5.2 Quality Assurance testing
process
10 days Wed
04-09-19
Tue
17-09-19
23 Quality
Assurance
Team25 5.3 Completion of the phase 0 days Tue
17-09-19
Tue
17-09-19
24
26 6 Project Closure Phase 13 days Wed
18-09-19
Fri 04-10-19
27 6.1 Documentation of the
project
10 days Wed
18-09-19
Tue
01-10-19
24 Subject Matter
Experts
28 6.2 Sign-off of project 1 day Wed
18-09-19
Wed
18-09-19
25
29 6.3 Making of payments 3 days Wed
02-10-19
Fri 04-10-19 27,28 Project
Manager
30 7 End Project 0 days Fri 04-10-19 Fri 04-10-19 29
27-05
Project Manager,Project Sponsor
Networking Team
13-06
Project Manager,Project Sponsor
24-06
24-06
Networking Team,Project Manager,Technical Equipments[1]
Project Manager
Technical Equipments[1]
15-07
Networking Team,Project Manager,Software Developers
Networking Team
Networking Team,Software Developers
Networking Team,Software Testers
27-08
Quality Assurance Team
Quality Assurance Team
17-09
Subject Matter Experts
Project Manager
04-10
F S T T S M W F S T T S M W F S T T S M W F S T T S M W F S T T S M W F S T T S M W F S T T S M W F S T T S M W F S T T S M W F S T T S M W F
20 May '19 27 May '19 03 J un '19 10 Jun '19 17 J un '19 24 J un '19 01 Jul '19 08 J ul '19 15 J ul '19 22 Jul '19 29 J ul '19 05 Aug '19 12 Aug '19 19 Aug '19 26 Aug '19 02 Sep '19 09 Sep '19 16 Sep '19 23 Sep '19 30 Sep '19 07 Oct '19
(Figure 2: The Gantt chart for the Project)
(Source: Created by author)

7NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES

8NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES

9NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
(Figure 3: The Network Diagram for the Project)
(Source: Created by author)
4.4 Cost Estimation for the Project
The estimated costs for the project is AUD $ 346,400.
4.5 Plan Quality for Project
In order to plan quality aspects for the NAC implementation project, some of the certain aspects
should be taken into consideration. These include:
1. Ensuring that the software quality should be based on ISO standards – During this process,
the company owners should ensure that the current process that is being implemented within the
company would be based on the ISO 9000 standard. It can be defined as an international set of certain
standards, which could be used for developing the quality management system within the industry
(Shang et al., 2016). ISO 9000-3 is a kind of supporting documentation that would be able to interpret
ISO 9001 based on developing software and different network components.
2. The quality planning process for checking the proper implementation of the NAC systems for
the endpoint devices includes the introducing of the service. It also discusses the plans based on
defining the specification of the new systems. The process that would be defined within the project
would also be discussed with the internal team (Vukalović & Delija, 2015). Hence, the risks would be
discussed and thus proper plans based on the management of such risks would also be defined. These
kinds of quality assurance process would be highly useful for measuring the quality aspects of the NAC
systems.

10NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
4.6 Stakeholder Analysis for Project
Stakeholder Communication Plan
Stakeholder Power/Interest Key Issues and Interests Communication Medium Frequency
Project Manager High To understand each of the required processes occurring the
implementation of the project.
Face-to-face
communication, email,
progress report
Weekly
Software
developers
Medium To understand the proper techniques based on the
implementation of the NAC systems.
Email, progress report Daily
Software Testers High To test the code implementation of the networked systems Email, progress report Daily
Networking team High To understand the various practices of the NAC systems.
They would also check the endpoint devices to which the
NAC would be implemented (Eskerod & Jepsen, 2016).
Progress report Weekly
Quality Assurance
Team
High The team would be responsible for assuring the quality of
the implementation for the NAC systems.
Email, Progress report Weekly

11NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
4.7 Plan Communication for Project
Purpose Medium Frequency Audience
Project Team Meetings Review the status of the
project
Face-to-face meeting Weekly Project Sponsor
Software Development
team
Networking Team
Kick-off Meeting Introducing the project,
deliverables, goals, time
and budget of the project
A face-to-face meeting,
Video Conferencing
During the start of the
project
Project Team, Project
Sponsor, Owners
Project Status meetings Updating the progress
over the project works
Progress reports, email Weekly Project Manager, Project
Sponsor
Design Review of NAC
Systems
Preparing reports based
on providing feedback
from other stakeholders
Progress reports, email Daily Software Development
team, Networking team
Check-ins or Meeting Updating the interested
parties about the
developmental aspects of
the project
Face-to-face meeting Weekly Project Sponsor

12NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
4.8 Plan project Risks Management
Risk
ID
Risks Category Priority Likelihood Impact Controls Person Responsible
R1 Issues based on providing the
facility of the wiring or cabling
might not be proper and thus
might affect the
implementation process
(Marcelino-Sádaba et al., 2014)
Operational High Medium High The vendors who are
responsible for planning the
wiring and cabling should be
responsible for dealing with
the implantation of the wiring
(Bowers & Khorakian, 2014).
Proper circuitry should be
established.
Project Manager,
Technical Service
Providers
R2 Issues may arise whenever the
processing of orders from
initiation to completion is not
proper (Heldman, 2018).
Unforeseen issues based on
providing facility could be
considered as another risk
during the project.
Operational Medium Medium Low The project manager should
ensure that each of the
processing of orders should
occur in a planned process
(Harrison & Lock, 2017). They
should ensure that each of the
processing of orders should
occur in a planned manner.
Project Manager
R3 The endpoint devices might not
support the NAC facility (Smith,
Rabiti & Szilard, 2017). The
parameters based on the
Technical High High High The technical service provider
and the networking team
should be responsible for
properly checking the
Networking Team,
Technical Service
Provider

13NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
configuration of devices might
have been miscalculated that
might lead to complexities in
the implementation plan
endpoint devices (Liu & Wang,
2014). They should also
ensure that the endpoint
devices would be able to
capture the implementation
of
R4 The financial plan for the
project might get exceeded due
to poor planning of the budget
for the project (Kliem & Ludin,
2019). Different prices of
products may vary and the
project sponsor might not
revise the financial plan of the
project. This might result in
cost overruns.
Financial Low Medium Medium The project sponsor should
continuously update the
progress plan of the project
(Milosevic & Martinelli, 2016).
They should ensure that each
of the costs that are exceeding
the normal planned budget of
the project should be updated
and thus new plans to be
implemented.
Project sponsor

14NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
4.9 Plan Project Deployment
The ABC Company who is planning for the implementation of the NAC systems for the endpoint
devices should have a clear form of understanding of the proper use of NAC. In a real form, the NAC
would be suited for the different needs based on specific business purposes. The use of NAC would be
ideal for limiting the network access to the network jacks and thus putting enforcement for the basic
policies based on security (Mijumbi et al., 2015). The use and implementation of NAC would help in
ensuring that the latest form of AV signatures would be installed on the endpoint devices. Before the
deployment of NAC would be done on the endpoint devices, the risks affecting the company should be
measured. a specific issue should be addressed with the implementation of the NAC systems.

15NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
5. Project Sign Off
Project Name: Implementation of NAC for the
security of Endpoint Devices
Project Manager: Kevin Jane
Start Date: Mon 27-05-19 Completion Date: Fri 04-10-19
Project Duration: 95 days Sponsor: Ronald Atkins
Project Goal: To implement the NAC for the security of the endpoint devices
Project Deliverables: Deliver a NAC system, technical documentation plan, financial plan
I acknowledge that I have completed each task with
proper diligence. I have agreed to each of the
standards that had been defined and have ensured
the proper quality levels.
I acknowledge that I have completed each task with
proper diligence. I have agreed to each of the
standards that had been defined and have ensured
the proper quality levels.
Project Manager Name and Signature: Kevin Jane Project Sponsor Name and Signature: Ronald Atkins
Date: Wed 02-10-19 Date: Wed 02-10-19

16NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
6. Post-Project Review and Recommendations
Based on understanding the detailed aspects of the project, it has been ensured that each of the
stages of the project has been defined and implemented properly. The project plan had been performed
as described. The plans for implementation of the NAC systems have been completed as per proper
guidelines.
The certain recommendations that would be put based on the implementation of the NAC
project are that the project manager should understand the requirements of the company. The
company should be able to maximize the form of investment based on extending the possibility of NAC.
The most important purpose of implementing NAC is based on supporting the needs of controlling
access to networks. The different devices to which the NAC systems would be putting an impact are
PDAs, VoIP phones, Wi-Fi devices and printers. In such kind of devices, the critical kind of networking
occurs due to which there is a high need for the implementation of NAC systems within the
organisation. The project manager and other technical staff within the project should ensure that each
of the necessities of the user would be met properly. This would ensure a proper form of business
growth of the organisation and that the networked components within the organisation would work
properly.

17NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
References
Abbassi, M., Ashrafi, M., & Tashnizi, E. S. (2014). Selecting balanced portfolios of R&D projects with
interdependencies: A Cross-Entropy based methodology. Technovation, 34(1), 54-63.
Bowers, J., & Khorakian, A. (2014). Integrating risk management in the innovation project. European
Journal of innovation management, 17(1), 25-40.
Eskerod, P., & Jepsen, A. L. (2016). Project stakeholder management. Routledge.
Harrison, F., & Lock, D. (2017). Advanced project management: a structured approach. Routledge.
Heldman, K. (2018). PMP: project management professional exam study guide. John Wiley & Sons.
Kliem, R. L., & Ludin, I. S. (2019). Reducing project risk. Routledge.
Koh, E. B., Oh, J., & Im, C. (2014, March). A study on security threats and dynamic access control
technology for BYOD, smart-work environment. In Proceedings of the International
MultiConference of Engineers and Computer Scientists (Vol. 2, pp. 1-6).
Kuliesius, F., & Dangovas, V. (2016, July). SDN enhanced campus network authentication and access
control system. In 2016 Eighth International Conference on Ubiquitous and Future Networks
(ICUFN) (pp. 894-899). IEEE.
Lee, J., Uddin, M., Tourrilhes, J., Sen, S., Banerjee, S., Arndt, M., ... & Nadeem, T. (2014, June). mesdn:
Mobile extension of sdn. In Proceedings of the fifth international workshop on Mobile cloud
computing & services (pp. 7-14). ACM.
Liu, S., & Wang, L. (2014). Understanding the impact of risks on performance in internal and outsourced
information technology projects: The role of strategic importance. International Journal of
Project Management, 32(8), 1494-1510.
Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A. M. E., & Villanueva, P. (2014). Project risk
management methodology for small firms. International journal of project management, 32(2),
327-340.
Mijumbi, R., Serrat, J., Gorricho, J. L., Bouten, N., De Turck, F., & Boutaba, R. (2015). Network function
virtualization: State-of-the-art and research challenges. IEEE Communications surveys &
tutorials, 18(1), 236-262.

18NETWORK ADMISSION CONTROL (NAC) SECURING ENDPOINT DEVICES
Milosevic, D. Z., & Martinelli, R. J. (2016). Project management toolbox: tools and techniques for the
practicing project manager. John Wiley & Sons.
Nunes, B. A., Santos, M. A. S., De Oliveira, B. T., Margi, C. B., Obraczka, K., & Turletti, T. (2014). Software-
Defined Networking Enabled Capacity Sharing in User Centric Networks. IEEE Communications
Magazine, 52(9), 9.
Shang, W., Bannis, A., Liang, T., Wang, Z., Yu, Y., Afanasyev, A., ... & Zhang, L. (2016, April). Named data
networking of things. In 2016 IEEE first international conference on internet-of-things design and
implementation (IoTDI) (pp. 117-128). IEEE.
Smith, C., Rabiti, C., & Szilard, R. (2017). Risk-Informed Safety Margins Characterization (RISMC)
Pathway Technical Program Plan (No. INL/EXT-17-43243-Rev000). Idaho National Lab.(INL),
Idaho Falls, ID (United States).
Vukalović, J., & Delija, D. (2015, May). Advanced persistent threats-detection and defense. In 2015 38th
International Convention on Information and Communication Technology, Electronics and
Microelectronics (MIPRO) (pp. 1324-1330). IEEE.