{"id":413,"date":"2026-04-30T15:40:58","date_gmt":"2026-04-30T15:40:58","guid":{"rendered":"https:\/\/sites.wp.odu.edu\/shauntellgavinocollins\/?page_id=413"},"modified":"2026-04-30T17:25:44","modified_gmt":"2026-04-30T17:25:44","slug":"cyse-368-2","status":"publish","type":"page","link":"https:\/\/sites.wp.odu.edu\/shauntellgavinocollins\/cyse-368-2\/","title":{"rendered":"CYSE 368"},"content":{"rendered":"\n<h2 class=\"wp-block-heading has-text-align-center\">CYSE 368 Internship Final Paper<br><strong>Shauntell Gavino-Collins<br>Cavalier Logistics<br>Mr. Collins, Network Consultant<br>CYSE 368 Internship Fall 2025<br>December 01, 2025<\/strong><\/h2>\n\n\n\n<div class=\"wp-block-buttons is-content-justification-center is-layout-flex wp-container-core-buttons-layout-1 wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link wp-element-button\">Table of Contents<\/a><\/div>\n<\/div>\n\n\n\n<h4 class=\"wp-block-heading has-text-align-left\">1. Introduction<\/h4>\n\n\n\n<h4 class=\"wp-block-heading has-text-align-left\">2. Management Environment<\/h4>\n\n\n\n<h4 class=\"wp-block-heading has-text-align-left\">3. Work Duties &amp; Assignments<\/h4>\n\n\n\n<h4 class=\"wp-block-heading has-text-align-left\">4. Use of Cybersecurity Skills &amp; Knowledge<\/h4>\n\n\n\n<h4 class=\"wp-block-heading has-text-align-left\">5. ODU Curriculum Connection<\/h4>\n\n\n\n<h4 class=\"wp-block-heading has-text-align-left\">6. Learning Outcomes Reflection<\/h4>\n\n\n\n<h4 class=\"wp-block-heading has-text-align-left\">7. Motivating Aspects<\/h4>\n\n\n\n<h4 class=\"wp-block-heading has-text-align-left\">8. Discouraging Aspects<\/h4>\n\n\n\n<h4 class=\"wp-block-heading has-text-align-left\">9. Challenging Aspects<\/h4>\n\n\n\n<h4 class=\"wp-block-heading has-text-align-left\">10. Recommendations for Future Interns<\/h4>\n\n\n\n<h4 class=\"wp-block-heading has-text-align-left\">11. Conclusion<\/h4>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-group is-layout-constrained wp-block-group-is-layout-constrained\"><div class=\"wp-block-group__inner-container\">\n<p><strong>Introduction<\/strong><br>When I started looking for internships, Cavalier Logistics stood out because they had an<br>incredible flexible schedule and let interns work on real network security issues instead of simply<br>shadowing people all day. The company is based in Sterling, Virginia, and they handle<br>transportation and supply chain management, air freight, ocean freight, warehousing, and<br>distribution. With offices across multiple states, they rely heavily on their network infrastructure<br>to keep everything running smoothly between locations. I wanted a hands-on experience in a real<br>business environment, and this seemed like the perfect opportunity.<br>Cavalier Logistics operates in a highly competitive industry where timing is everything. A<br>delayed shipment or compromised client data could mean losing contracts worth millions of<br>dollars. This reality made the cybersecurity work feel urgent and meaningful from day one.<br>Understanding the stakes helped me appreciate why every firewall rule and access control<br>decision mattered so much.<br>My long-term goal is to work in forensic accounting and cybercrime prevention, so I wanted to<br>understand how companies protect their digital infrastructure and sensitive client data. This<br>internship let me see both the technical side of cybersecurity and how it fits into actual business<br>operations in the logistics industry. The logistics sector faces unique cybersecurity challenges<br>that I hadn\u2019t fully appreciated before. Unlike financial institutions or healthcare providers, or<br>other industries, logistics companies must maintain security while coordinating with countless<br>external partners, freight carriers, customs brokers, warehouse operators, and international<br>shipping lines. Each external connection represents a potential vulnerability, which meant I got<br>to see how security professionals balance openness for business efficiency with protection<br>against threats.<br>Before starting, I set three main goals. First, I wanted to get comfortable working with<br>enterprise-level networking equipment and cloud-based management platforms, specifically<br>Cisco Meraki access points, routers, switches, and firewalls. Second, I wanted to understand how<br>network security policies get implemented across multiple locations, including things like<br>network segmentation, VPNs, and traffic monitoring. Third, I hoped to improve my analytical<br>and communication skills by working directly with my supervisor, Mr. Collins, to learn how<br>cybersecurity principles translate into daily decisions.<br>My first day at Cavalier Logistics included the usual orientation activities such as safety<br>briefings, data security training, and tours of the network operations area. My initial impression<br>was quite positive also due to the company having a professional atmosphere, but people were<br>also collaborative and willing to teach. What stood out most was that cybersecurity wasn\u2019t<br>treated like some background IT department; it was clearly important to every part of the<br>business. During the orientation, the HR representative explicitly mentioned that network<br>security incidents had cost the company significant revenue in previous years, which explained<br>why security was taken so seriously across all departments. That made me realize I was joining<br>an organization that had learned hard lessons about the business impact of cybersecurity failures.<\/p>\n\n\n\n<p><strong>Management Environment<\/strong><br>I worked directly under Mr. Collins, the company\u2019s Network Consultant, who served as both my<br>supervisor and mentor. His management style was hands-on but also gave me room to learn<br>independently. He didn\u2019t just tell me what to do either, he encouraged me to observe, ask<br>questions, and actually understand the systems we were working with. We had weekly meetings<br>to review what I was working on, discuss any network issues that came up, and make sure my<br>projects aligned with what the company needed.<br>What impressed me most about Mr. Collins\u2019s approach was his emphasis on understanding the<br>\u201cwhy\u201d behind every technical decision. When we reviewed firewall configurations, he wouldn\u2019t<br>just show me the rules, he would explain the business logic driving each policy. For example,<br>when discussing why certain IP ranges were blocked, he\u2019d trace it back to previous security<br>incidents or compliance requirements from specific clients. This contextual teaching method<br>helped me develop intuition about security architecture rather than just memorizing procedures.<br>He also encourages me to question existing configurations and propose alternatives, which built<br>my confidence in technical decision-making even as an intern.<br>Mr. Collins also modeled professional growth in meaningful ways. He regularly attended<br>industry conferences and vendor training sessions, often sharing insights from these experiences<br>during our meetings. He subscribed to multiple cybersecurity newsletters and threat intelligence<br>feeds, demonstrating that staying current isn\u2019t optional in this field. Watching him dedicate time<br>to continuous learning, despite his busy schedule, reinforced that cybersecurity professionals<br>must commit to lifelong education. He also connected me with other IT professionals in the<br>company, creating networking opportunities that broadened my understanding of how different<br>specializations collaborate.<br>The management structure at Cavalier includes specialized teams across IT, logistics<br>coordination, accounting, and operations. The network security division plays a central role<br>because if the network goes down, pretty much everything else stops working. I got to see how<br>different departments communicated with each other, especially when network changes affected<br>customer-facing systems or warehouse operations. It showed me that cybersecurity can\u2019t exist in<br>a vacuum, it has to support business goals, not just protect systems for the sake of protection.<br>One particularly illuminating experience involved sitting in on a cross-departmental meeting<br>about implementing multi-factor authentication for warehouse management systems. The IT<br>team advocated for strict security controls, while operations managers worried about slowing<br>down time-sensitive shipping processes. Watching Mr. Collins navigate these competing<br>priorities taught me valuable lessons about stakeholder management. He presented data on<br>authentication times, proposed phased implementation, and demonstrated how security could<br>actually improve efficiency by reducing password reset calls. This approach helped me<br>understand that technical expertise alone isn\u2019t enough, successful cybersecurity professionals<br>must also be skilled negotiators who can translate security needs into language that resonates<br>with different audiences.<br>The management culture emphasized accountability and fixing problems before they became<br>bigger issues. Every configuration change, security update, or access modification had to be<br>documented and reviewed. This reminded me of the chain of custody principles we learned in<br>class, maintaining the integrity of data and keeping records is crucial for both security and<br>compliance. Mr. Collins also emphasized ethical responsibility, which reinforced what I\u2019d<br>learned about how even small shortcuts in documentation could create long-term vulnerabilities.<br>I believe the management environment worked really well. The balance between supervision and<br>independence gave me freedom to apply what I\u2019d learned in class while still having professional<br>guidance. I learned that good leadership in cybersecurity isn\u2019t about micromanaging, it\u2019s about<br>creating an environment where people feel comfortable asking questions and taking their work<br>seriously.<\/p>\n\n\n\n<p><strong>Work Duties &amp; Assignments<\/strong><br>As a Network Security Intern, I did a mix of hands-on configuration work and observation of<br>larger enterprise systems. My main responsibilities included helping deploy, monitor, and<br>document Cisco Meraki MR-56 Access Points, which provided cloud-managed wireless<br>networking across multiple Cavalier facilities. I learned to use the Meraki dashboard to configure<br>SSIDs set up network segmentation for staff and guest users and monitor performance metrics<br>across all seven states where Cavalier operates. What impressed me most was how scalable the<br>system was and how we could new sites remotely without taking anything offline.<br>Working with the Meraki system introduced me to the practical side of wireless security that<br>textbooks can\u2019t fully capture. I learned about the delicate balance between signal strength and<br>security, too powerful and you\u2019re broadcasting your network beyond your physical premises,<br>creating opportunities for parking lot attacks; too weak and legitimate users experience<br>connectivity issues. Mr. Collins showed me how to use heat mapping tools to optimize access<br>point placement, ensuring adequate coverage while minimizing signal bleeding into public areas.<br>I also learned to configure rogue access point detection, which automatically alerts<br>administrators when unauthorized wireless devices appear on the network. During one incident,<br>this system detected an employee who had connected a personal router to bypass network<br>restrictions, a seemingly innocent action that could have created a significant security<br>vulnerability.<br>One of the major projects involved working with Cisco FPR1010-NFGW-K9 Next Generation<br>Firewalls. These devices are critical for maintaining secure connections and protecting data as it<br>moves between networks. I worked with Mr. Collins to review firewall configurations, analyze<br>traffic patterns, and verify that access control lists (ACLs) were blocking unauthorized activity.<br>This gave me real insight into how modern firewalls use deep packet inspection and advanced<br>threat detection to defend against breaches.<br>The firewall work particularly fascinated me because it revealed the cat and mouse nature of<br>cybersecurity. During one session, Mr. Collins showed me the logs where the firewall had<br>blocked hundreds of automated attacks originating from international IP addresses. These<br>weren\u2019t sophisticated attacks, just automated scripts scanning for common vulnerabilities, but<br>their volume was staggering. I also learned about false positives and the challenges of tuning<br>firewall rules to minimize traffic disruption. Finding that balance requires understanding both<br>network behavior patterns and business operations.<br>I also spent time working with Cisco routers and switches. Mr. Collins showed me how to<br>configure to VLANs to separate VoIP systems from data networks, which ensures both web<br>applications and phone systems work properly. I got to see how properly configured access lists<br>and routing policies prevent broadcast storms and keep the network reliable. This helped me<br>connect the theoretical networking concepts from class to actual enterprise configurations.<br>Another learning experience was working with VeloCloud SD-WAN devices, which optimize<br>wide-area network performance and provide redundancy across multiple ISP circuits. These<br>systems help ensure that if one internet connection goes down, the network automatically<br>switches to a backup. I shadowed Mr. Collins during ISP circuit installations and saw show<br>coordination with vendors and troubleshooting protocols kept business running during outages.<br>These experiences showed me that technical skill is important, but so is communication, you<br>have to be able to explain issues clearly to service providers and other stakeholders.<br>One particularly memorable project involved documenting the company\u2019s disaster recovery<br>procedures. Mr. Collins assigned me to review existing documentation and identify gaps or<br>outdated information. This task initially seemed tedious, but it taught me how crucial<br>documentation is for business continuity. I discovered procedures referencing equipment that had<br>been replaced years ago and contact information for vendors who no longer provided services.<br>Updating this documentation meant speaking with various team members, verifying current<br>procedures, and creating clear step-by-step guides. This project demonstrated that cybersecurity<br>extends beyond technical implementation to include organizational preparedness, ensuring that<br>when incidents occur, teams can respond quickly and effectively.<br>Looking back, these projects showed me how network security functions as a living system.<br>Every device, from a firewall to a wireless access point, is a layer in the organization\u2019s defense<br>strategy. Getting to participate in this environment gave me a front-row seat to see how all these<br>layers work together to protect the confidentiality, integrity, and availability of business<br>operations.<\/p>\n\n\n\n<p><strong>Use of Cybersecurity Skills and Knowledge<\/strong><br>I came into the internship with a decent foundation from my ODU classes, I understood the<br>basics of encryption, authentication, access control, and network segmentation. Working with<br>these concepts in a real production environment was completely different from taking exams<br>about them. Everything was more connected and complicated than I expected. Working with the<br>Cisco Meraki MR-56 Access Points was a good example. In some of my classes, I learned about<br>how user segmentation and access policies as separate concepts. At Cavalier, I saw how they<br>directly affected both network speed and security at the same time. The Meraki cloud dashboard<br>was honestly fascinating; Mr. Collins could manage wireless access across all seven states from<br>one screen. It made me realize how much cloud-based tools have changed IT work, especially for<br>companies with multiple locations.<br>The practical application of encryption protocols was particularly eye-opening. From my classes,<br>we discussed WPA3 and certificate-based authentication theoretically. At Cavalier, I helped<br>implement these protocols and immediately encountered real-world complications. For instance,<br>legacy devices used by warehouse scanners couldn\u2019t support the latest encryption standards,<br>forcing us to maintain separate network segments with older protocols. This created a security<br>trade-off that required careful risk assessment, do we upgrade expensive equipment prematurely,<br>or do we accept calculated risk while implementing compensating controls? These decisions<br>involved cost-benefit analyses that classroom scenarios rarely capture.<br>Working with the Next Generation Firewalls really deepened my understanding of enterprise-level protection. Firewall rules aren\u2019t just abstract configurations; they reflect the company\u2019s<br>actual operational priorities and balance usability with security. I also learned to read logs,<br>analyze blocked traffic, and identify suspicious activity patterns. Configuring VLANs and access<br>lists on routers and switches also helped me see how network segmentation can minimize the<br>spread of potential breaches.<br>One of the most interesting lessons came from watching how VoIP systems and web applications<br>are integrated securely. Seeing Mr. Collins configure VLANs to support VoIP showed me that<br>cybersecurity goes beyond just protecting devices, it ensures reliable communication for the<br>entire organization. I also got familiar with auditing configurations, documenting changes, and<br>reviewing compliance logs. The on-the-job learning expanded my skill set way beyond the<br>classroom. I got better at troubleshooting connectivity issues, using monitoring tools to interpret<br>system alerts, and recognizing when automation can improve reliability. I also learned that<br>human factors play a huge role in cybersecurity, even the most advanced hardware can fail if<br>users ignore best practices or skip documentation. This changed how I think about the field:<br>cybersecurity isn\u2019t just a technical discipline, it\u2019s an ongoing process of staying on top of threats<br>that are continuously adapting.<\/p>\n\n\n\n<p><strong>ODU Curriculum Connection<\/strong><br>My education at ODU gave me a strong foundation that translated well into my internship at<br>Cavalier Logistics. Courses like CYSE 200T Cybersecurity, IT 205 Introduction to ObjectOriented Programming, IT 201 Introduction to Information Systems, CRJS 310<br>Cybercriminology: Foundations, and CYSE 406 Cyber Law, gave me the framework to<br>understand what I was seeing and contributing to. Theories about layered defense, redundancy,<br>and threat modeling became tangible when I worked with the company\u2019s actual infrastructure. I<br>could see how the discussions in one of my classes about the CIA Triad, which revolved around<br>confidentiality, integrity, and availability, played out through access control configurations,<br>firewall policies, and backup systems. Other ways that my classes helped me was not only<br>preparing me with awareness but gave me information regarding VPN setups, encryption<br>protocols, authentication, lessons on ethical hacking, and vulnerability assessment.<br>However, the internship also exposed areas where academic preparation meets real-world<br>constraints. While ODU taught me to design and analyze secure networks conceptually, Cavalier<br>Logistics taught me how to implement them practically within the limits of cost, business needs,<br>and scalability. In the classroom, cybersecurity is often isolated from other business operations,<br>but this internship showed me how deeply interconnected security is with finance, logistics, and<br>human resources. Network downtime doesn\u2019t just affect data, it disrupts shipments, delays<br>transactions, and impacts the company\u2019s reputation.<br>Through this experience, I also discovered new areas I want to learn more about. I developed a<br>stronger interest in cyber risk auditing and compliance management, which align with my future<br>goals in forensic accounting. The internship made it clear that the most effective cybersecurity<br>professionals understand both the technical infrastructure and the organizational ecosystem that<br>depends on it. ODU\u2019s interdisciplinary approach prepared me well for this but the internship<br>gave me the perspective and confidence to actually apply it.<\/p>\n\n\n\n<p><strong>Learning Outcomes Reflection<\/strong><br>The first goal I set before starting was to gain hands-on experience with enterprise-grade<br>networking tools and systems. I definitely achieved this through daily work with Cisco Meraki<br>MR-56 access points, next-generation firewalls, routers, and switches. Each week brought new<br>technical challenges, from configuring VLANs for traffic segmentation to checking VPN tunnel<br>stability between Cavalier\u2019s regional branches. By shadowing Mr. Collins during configuration<br>reviews and change-control meetings, I learned now just how to do things, but why they\u2019re done<br>that way. For example, firewall rules weren\u2019t just lines of code, they reflected carefully thoughtout business policies that balanced operational access with risk tolerance. Being able to connect<br>these technical decisions to organizational strategy confirmed that I was developing both<br>technical competence and strategic awareness.<br>My second goal was to understand how cybersecurity supports business continuity across<br>different locations. Cavalier Logistics was perfect for this because their operations span multiple<br>time zones, and connectivity problems could, again, delay shipments and hurt client<br>relationships. I saw firsthand how redundancy, through SD-WAN failover paths and cloudmanaged wireless systems ensured that no single outage could shut down communication.<br>During one incident when an ISP circuit briefly failed, I watched Mr. Collins redirect traffic<br>through a backup link within minutes. Seeing that rapid response reinforced that cybersecurity is<br>as much about resilience and recovery as it is about prevention.<br>The third goal was to develop professional communication and problem-solving skills, which I<br>definitely accomplished. Early on, I sometimes hesitated to ask questions during technical<br>discussions because I didn\u2019t want to interrupt. Mr. Collins encouraged me to speak up, reminding<br>me that asking questions is how you actually learn. Over time, I got more comfortable<br>articulating technical observations clearly and concisely, and I learned to translate complex<br>networking issues into language that non-technical staff could understand. That ability to<br>communicate risk and recommend solutions across departments turned out to be one of the most<br>valuable skills I gained.<br>An unexpected but equally important outcomes was developing a stronger sense of ethical<br>responsibility. Handling access credentials, monitoring user activity, and viewing internal traffic<br>data all required discretion and professionalism. The internship reinforced that cybersecurity<br>practitioners are responsible for protecting trust, every log entry or configuration command has<br>ethical implications. Taking this responsibility seriously deepened my respect for the field and<br>confirmed that ethics isn\u2019t just an abstract course topic, it\u2019s a daily practice that defines your<br>credibility.<\/p>\n\n\n\n<p><strong>Motivating or Exciting Aspects<\/strong><br>The best part of the internship was knowing my work actually mattered. When I helped<br>configure something that protected data from moving between warehouses, or when a firewall<br>rule, I worked on blocked a potential threat, it felt real. It wasn\u2019t just practice anymore, it was<br>protecting actual company operations. I\u2019ll admit, every successful deployment felt pretty<br>satisfying because there is something motivating about seeing your preparation pay off,<br>especially when you\u2019re working with a team and know that clients are depending on this on this<br>stuff to work correctly.<br>Working with cutting-edge technology in a real business setting is also exciting. Cisco\u2019s Meraki<br>dashboard fascinated me because it showed how cloud computing can change network<br>administration. Through one interface, our team could monitor wireless devices across seven<br>states, review bandwidth usage, and push firmware updates remotely. I gained new appreciation<br>for how scalable cloud-based systems are and how they let small IT teams manage huge<br>infrastructure efficiently. This experience helped me see the future of enterprise networking,<br>where automation and visibility reduce human error and speed up response times.<br>Another motivating factor was the mentorship culture. Mr. Collins consistently connected<br>technical lessons to bigger professional themes. For example, after trouble shooting a VLAN<br>misconfiguration one day, he explained how similar issues could create serious vulnerabilities if<br>left undocumented. These conversations transformed routine tasks into real learning moments<br>and showed me how experienced professionals think strategically. They also taught me that<br>mastering cybersecurity involves constant curiosity, willingness to adapt, and learning no matter<br>what is new in the field.<br>The internship renewed my enthusiasm for combining cybersecurity with forensic accounting. I<br>started imagining how similar investigative approaches could be applied to financial systems to<br>detect fraud or anomalies. That realization got me genuinely excited about designing a career that<br>combines technology with financial integrity.<\/p>\n\n\n\n<p><strong>Discouraging Aspects<\/strong><br>The internship was great overall, but it definitely had some frustrating parts. The biggest one was<br>not having access to the more critical production systems. I get why, they can\u2019t let interns<br>accidentally break important stuff, but it meant I spent a lot of time watching instead of doing it.<br>During maintenance windows, I basically sat on the sidelines. At first, it was frustrating because<br>I wanted to experience it hands-on and not just observing. Eventually I realized I was still<br>learning a lot by watching Mr. Collins work through problems, and I started taking better notes<br>so I could try things later in a test environment. But yeah, I wish I could\u2019ve done more<br>configuration work.<br>Another thing that took getting used to was the invisible nature of success in cybersecurity. In<br>many cases, a day with no incidents just meant systems were working correctly, but that<br>normalcy could feel anticlimactic. Unlike other fields where you can see your progress, network<br>security often rewards silence and stability. It took time to accept that prevention, not reaction, is<br>the real measure of success. Once I shifted my perspective, I found, in a way, a sense of<br>accomplishment in maintaining security and ensuring calm rather than waiting for crises to be<br>resolved.<br>I also occasionally felt the strain of communication gaps between departments. When technical<br>jargon clashed with logistics terminology, misunderstandings could slow down decision-making.<br>Watching Mr. Collins navigate those situations taught me the importance of empathy and clarity.<br>Security professionals must translate risks into operational language that makes sense to nontechnical people. Although these communication challenges were sometimes frustrating, they<br>provided important lessons in diplomacy and patience, qualities that will help me in any<br>collaborative environment.<\/p>\n\n\n\n<p><strong>Challenging Aspects<\/strong><br>The most demanding part of the internship was learning to balance security, performance, and<br>usability. Every configuration change involves trade-offs. Strengthening encryption could slow<br>things down; tightening access controls might make things less convenient for remote users.<br>Understanding how to strike the right balance requires both technical knowledge and<br>understanding organizational priorities. Through testing and feedback, I learned that effective<br>security design is as much an art as a science, it must protect without making it impossible to get<br>work done.<br>Another major challenge was interpreting network anomalies in real time. When monitoring the<br>Meraki dashboard or firewall logs, spikes in traffic or unusual IP connections could signal<br>potential intrusions, but they required contact to understand. Early on, I found the volume of data<br>overwhelming, but with guidance, I learned to filter alerts, establish baselines, and use data<br>visualization to spot meaningful patterns. This process improved my analytical discipline and<br>reinforced the importance of staying calm and evidence-based under pressure.<br>Time management also turned out to be harder than expected. Balancing multiple small projects,<br>documentation updates, configuration checks, and troubleshooting tickets, required<br>organizational skills beyond the purely technical. I developed a workflow using checklists and<br>version-control notes to make sure nothing fell through the cracks. By the final week, I could<br>handle overlapping tasks more efficiently, which proved to me that technical expertise must be<br>supported by good planning.<br>The learning curve for enterprise-levels tools was steep. Cisco\u2019s interface ecosystem, SD-WAN<br>orchestration, and firewall policy syntax were intimidating at first. That challenge became<br>something I\u2019m proud of. Each time I figured out an unfamiliar log entry or fixed a configuration<br>warning, I felt myself getting better. The process reinforced an important professional truth:<br>competence comes from pushing through discomfort and leaning into complexity rather than<br>avoiding it.<\/p>\n\n\n\n<p><strong>Recommendations for Future Interns<\/strong><br>For students who follow in my footsteps at Cavalier Logistics, my first recommendation is to<br>show up with strong foundational knowledge of networking principles. Understanding subnets,<br>VLANs, routing tables, and OSI layers will make on-the-job learning much smoother. If you can<br>read and interpret network diagrams, you\u2019ll gain credibility. It\u2019s also worth getting familiar with<br>Cisco networking environments beforehand. Exploring free Cisco Networking Academy courses<br>before starting would be really helpful.<br>I\u2019d also recommend developing soft skills alongside technical ones. My most successful<br>moments during the internship happened when I combined technical knowledge with being able<br>to communicate clearly. Learning how to summarize findings for managers, creating accurate<br>reports, and being knowledgeable about cybersecurity concepts is a great way to put yourself<br>ahead of other interns too.<br>Approach every assignment with curiosity and humility. Some tasks, like labeling cables or<br>organizing documentation, might seem trivial, but they\u2019re crucial to maintain system<br>organization. Treating small duties with the same care as high-profile projects show reliability<br>and earns your mentor\u2019s trust. Ask for feedback regularly, and when you hit limitations, use them<br>as opportunities for independent research. Setting up a home lab or simulation environment can<br>help you practice what you observe on site.<br>Future interns should take ethical responsibility seriously. At Cavalier Logistics, even routing<br>network access involves sensitive client information. Understanding confidentiality agreements,<br>documenting changes accurately, and avoiding shortcuts are non-negotiable. Your integrity<br>builds your reputation; one careless action can undo months of clever work. Those who treat<br>cybersecurity not just as technology but as a professional ethic will do well in this environment.<\/p>\n\n\n\n<p><strong>Conclusion<\/strong><br>Looking back on my internship at Cavalier Logistics, I see it as a defining chapter in my<br>academic and professional journey. It transformed classroom lessons into lived experience,<br>showing me how cybersecurity protects what keeps modern businesses running, which is data<br>and connectivity. I came in eager to learn about network security; I left understanding that<br>security is the foundation supporting every organization process. Through exposure to Cisco<br>technologies, SD-WAN architecture, and cloud management, I gained not only technical<br>competence but also strategic awareness of how business and cybersecurity work together.<br>The biggest takeaway is that effective security is holistic. It depends equally on systems, people,<br>and policies. The internship shows me how leadership, documentation, and communication<br>reinforce technical defenses. It also deepened my appreciation for how different departments<br>work together such as logistics specialists, accountants, and IT engineers all rely on one<br>another\u2019s precision. This insight has reshaped how I view my education at Old Dominion<br>University. I now see my courses not as isolated courses or subjects, but as connected pieces of a<br>larger professional picture.<br>As I continue my studies, I plan to focus on courses that combine data analytics, risk<br>management and digital forensics. I am also pursuing certifications such as Certified Fraud<br>Examiner (CFE) and Cisco Certified Network Associate (CCNA) to strengthen both my<br>technical and investigative credentials. The internship confirmed my ambition to build a career<br>that combines cybersecurity with forensic accounting which would be an area where I can help<br>organizations detect, prevent, and analyze digital financial crimes.<br>This experience has reinforced my belief that cybersecurity is more than a career path; it is a<br>commitment to protecting trust and organizational resilience. The lessons that I learned at<br>Cavalier Logistics such as discipline, adaptability, and ethical integrity will continue to guide my<br>academic work and professional conduct. I now see every configuration, audit, or report not as a<br>routine task but as a contribution to a safer and more transparent digital world. The internship did<br>not just teach me how to protect networks, it taught me how to think like someone responsible<br>for protecting information, a perspective that will shape every step of my future career.<\/p>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>CYSE 368 Internship Final PaperShauntell Gavino-CollinsCavalier LogisticsMr. Collins, Network ConsultantCYSE 368 Internship Fall 2025December 01, 2025 1. Introduction 2. Management Environment 3. Work Duties &amp; Assignments 4. Use of Cybersecurity Skills &amp; Knowledge 5. ODU Curriculum Connection 6. Learning Outcomes Reflection 7. Motivating Aspects 8. Discouraging Aspects 9. Challenging Aspects 10. Recommendations for Future Interns&#8230; <\/p>\n<div class=\"link-more\"><a href=\"https:\/\/sites.wp.odu.edu\/shauntellgavinocollins\/cyse-368-2\/\">Read More<\/a><\/div>\n","protected":false},"author":30947,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"_links":{"self":[{"href":"https:\/\/sites.wp.odu.edu\/shauntellgavinocollins\/wp-json\/wp\/v2\/pages\/413"}],"collection":[{"href":"https:\/\/sites.wp.odu.edu\/shauntellgavinocollins\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sites.wp.odu.edu\/shauntellgavinocollins\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/shauntellgavinocollins\/wp-json\/wp\/v2\/users\/30947"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/shauntellgavinocollins\/wp-json\/wp\/v2\/comments?post=413"}],"version-history":[{"count":5,"href":"https:\/\/sites.wp.odu.edu\/shauntellgavinocollins\/wp-json\/wp\/v2\/pages\/413\/revisions"}],"predecessor-version":[{"id":438,"href":"https:\/\/sites.wp.odu.edu\/shauntellgavinocollins\/wp-json\/wp\/v2\/pages\/413\/revisions\/438"}],"wp:attachment":[{"href":"https:\/\/sites.wp.odu.edu\/shauntellgavinocollins\/wp-json\/wp\/v2\/media?parent=413"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}