16.3. Build a Cross-Functional Team
You absolutely must build this kind of team if you want a successful NAC implementation, and you absolutely must perform this step early in the process, rather than later. We have seen many NAC implementations stall because of internal politics or differences of opinion between the various groups involved. Identify everyone whom the NAC implementation will impact, and get them involved throughout the planning process. For example, if you're in the Security group and don't involve the Desktop team, you might choose a vendor's solution and only later realize that it doesn't integrate well with the software distribution solution that the Desktop team is rolling out. Avoid any bad blood or delays by getting everyone involved from the beginning. Chapter 7, about corporate cooperation, describes whom to get involved and when.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access