BUS-FPX3012 Fundamentals of Leadership Leadership Experience

As a Network Specialist for the Granite School District in Salt Lake City, Utah, my team and I were tasked with implementing a secure wireless solution. This involved deploying Cisco’s Identity Services Engine (ISE), a system designed to enhance network security by profiling devices that attempt to connect and granting access based on their credentials. A previous penetration test revealed vulnerabilities in our wireless network, and ISE was chosen to address these gaps. The solution provided visibility into device connections, allowing us to manage who accesses the network based on policies such as operating system versions and security requirements. Devices or users not meeting the criteria were restricted from accessing the network, with a guest network option for limited access.

We collaborated with stakeholders, including Jeff Darling (Security Manager), Dale Roberts (Information Systems Director), and Trent Labrum (Senior Network Specialist). Weekly meetings ensured that progress was tracked, and any project changes or issues were addressed promptly. The project was initially tested in a controlled environment to ensure proper device authentication across various models before moving into live deployment. This phased rollout allowed us to resolve issues efficiently. As the team leader, I was responsible for reporting weekly progress to stakeholders, ensuring alignment with the project’s scope, and making necessary adjustments.

Leadership Approach

The shared vision for the ISE project was to improve network security by controlling and filtering device and user access. Following an audit, I was selected by my manager to lead the project due to my understanding of the network’s security needs. We aimed to deploy ISE in the Granite School District’s (GSD) wireless environment to facilitate user and device authentication and enforce security policies. I presented the ISE system as the optimal solution, outlining key features to the stakeholders, who agreed to move forward.

The project was divided into several stages to ensure thorough testing and successful implementation. Regular communication with stakeholders and team members was crucial to keeping the project on track. We encountered challenges, including the need to inventory devices and adapt the system to accommodate new hardware. One significant change involved the guest network, initially planned with a simple password-based system. After testing revealed security concerns, we decided to implement an email-based registration with a verification code. Although this change delayed the project, it ultimately improved security. If we had followed this strategy from the beginning, time could have been saved.

Fostering Collaboration and Motivation

Since the ISE project required a custom approach, the team’s collaboration was essential. Each team member was encouraged to contribute ideas, and every suggestion was considered seriously. For example, one team member proposed using device and user-based certificates for authentication. We tested this approach, but due to certain device limitations, it was not feasible. However, the willingness to test ideas fostered a positive team environment, leading to other solutions that were successfully implemented.

As a leader, maintaining team morale was a priority. Providing time off, offering snacks, and ensuring constant communication kept the team motivated. Clear explanations for any project changes helped team members understand the benefits of the new solution, which aimed to prevent malware and unauthorized access. This collaborative environment not only facilitated the project’s success but also encouraged innovative thinking.

Table: Leadership Project Overview

Table: Leadership Approach Breakdown