{"id":121,"date":"2026-04-26T19:16:11","date_gmt":"2026-04-26T19:16:11","guid":{"rendered":"https:\/\/student.wp.odu.edu\/atrev004\/?p=121"},"modified":"2026-04-26T19:18:01","modified_gmt":"2026-04-26T19:18:01","slug":"internship-final-paper","status":"publish","type":"post","link":"https:\/\/student.wp.odu.edu\/atrev004\/2026\/04\/26\/internship-final-paper\/","title":{"rendered":"\u00a0CYSE 368 Internship Final Paper"},"content":{"rendered":"\n

Internship Final Paper
CYSE 368 Internships in Cybersecurity
Alexander L. Trevino
Commander, Navy Reserve Forces Command
US Navy
Professor Teresa Duvall
TA Joshua Russell
Spring 2026
April 19, 2026
Table of Contents<\/p>\n\n\n\n

    \n
  1. Introduction \u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026.. 3-4<\/li>\n\n\n\n
  2. Management Environment at the Internship \u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026 4-5<\/li>\n\n\n\n
  3. Major Work Duties, Assignments, and Projects \u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026 5-7<\/li>\n\n\n\n
  4. Specific Use of Cybersecurity Skills and Knowledge \u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026 8<\/li>\n\n\n\n
  5. How the ODU Curriculum Prepared Me \u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026.. 9<\/li>\n\n\n\n
  6. Internship Outcomes and Objectives \u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026 9-10<\/li>\n\n\n\n
  7. Most Motivating and Exciting Aspects of the Internship \u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026 10-11<\/li>\n\n\n\n
  8. Most Discouraging Aspects of the Internship \u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026.. 11<\/li>\n\n\n\n
  9. Most Challenging Aspects of the Internship \u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026.. 11-12<\/li>\n\n\n\n
  10. Recommendations for Future Interns\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026. 12<\/li>\n\n\n\n
  11. Conclusion \u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026 12-13<\/li>\n\n\n\n
  12. Introduction

    I decided to complete my internship at Commander, Navy Reserve Forces Command because it gave me the chance to see how IT supports the Navy mission from inside a major operational command. I was already assigned to the command in my regular duties, but this internship placed me on temporary assigned duty in the Information System Technology (IT) department so I could work directly in the N6 environment. That opportunity mattered to me because I did not want an internship that stayed at the surface level. I wanted one that would show me how support, security, accountability, and mission readiness connect in a real command setting. I also wanted to better understand whether Navy IT and cyber work was the right long term professional path for me. By the end of the internship, I had a much clearer answer.
    Commander, Navy Reserve Forces Command sits near the top of the Navy Reserve structure and supports a broad enterprise mission that reaches far beyond a single office. The command provides oversight and support that affects Navy Reserve Centers and Reserve Component Commands across the force. Because of that larger role, the IT shop does more than solve isolated computer issues. It supports operations, communications, secure systems, user access, accountability requirements, and the technical backbone that helps the command stay ready to execute its mission. During this internship I learned that work done in the N6 shop can have consequences for multiple commands and users, which gave even routine tasks more meaning. Something as simple as accurate documentation, proper escalation, or timely troubleshooting could make a difference for people and processes outside of the immediate workspace.
    At the beginning of my internship, I had several specific objectives that I wanted to achieve. The first objective was to gain hands on experience with Navy Reserve IT policy and departmental operations so I could better understand the standards and governing principles within the N6 environment. The second objective was to analyze how the command\u2019s technology strategy and innovation efforts support operational and cybersecurity capabilities. The third objective was to apply cybersecurity principles to practical situations encountered during the internship instead of only understanding them in theory. A fourth personal objective, which grew out of my professional goals, was to use this experience to sharpen my view of a future officer path in Navy IT and cyber related leadership.
    My orientation to the internship was practical from the start. LT Christopher Gregory did not keep me in one narrow lane. Instead, he introduced me to the shop in a structured way and pushed me through different departments so I could understand how the organization worked as a whole. That approach set the tone for the rest of the internship. Rather than learning only one process, I was expected to observe, ask questions, understand why procedures mattered, and connect technical work to the larger mission. My first exposure centered on the Customer Support Center (CSC), where I saw how issues were documented, prioritized, and tracked. From there I moved into more security focused and accountability driven work in Key Management Infrastructure (KMI) and the Local Registration Authority (LRA) area. This rotation model gave me a wider view of the department and made the internship much more valuable than passive observation would have been.
    My initial impression of the command\u2019s IT environment was that it was professional, fast moving, and deeply tied to mission support. I quickly noticed that users often came to the shop when something important was already being affected, whether that involved email access, printer connectivity, certificate problems, or network issues. I also saw that the work required
    more than technical knowledge. It required patience, clear communication, complete documentation, and the judgment to know when an issue needed to be elevated. From the beginning, I understood that this was not a space where careless work could be excused as a learning mistake. The shop expected a serious attitude, attention to detail, and a willingness to learn from every task.
    Overall, the introduction to this internship showed me that I was stepping into an environment where IT and mission readiness are directly connected. That was exactly the type of experience I wanted. I wanted to see how cybersecurity, user support, and command operations meet in the real world. This internship gave me that opportunity, and it provided the foundation for the learning and reflection that shaped the rest of this paper.

    Management Environment at the Internship<\/strong>
    The management environment during my internship was structured, supportive, and effective. LT Christopher Gregory supervised my work and helped shape the overall experience, but his approach was not limited to assigning tasks and expecting results with no guidance. We synced up every day, which gave me a clear sense of direction and helped me stay grounded in the purpose behind each assignment. Those daily check ins also created a useful balance between independence and oversight. I was given room to learn, observe, and contribute, but I also had regular opportunities to ask questions, clarify expectations, and receive feedback on both technical and professional performance.
    One of the strongest features of the management environment was exposure to multiple sections of the shop. LT Gregory intentionally moved me through different departments instead of leaving me in a single support role for the entire internship. That decision made the experience more demanding, but it also made it more complete. I was able to see how the CSC, KMI, and LRA functions each support the command in different ways. As I transitioned through those areas, I also saw how leadership, documentation, technical procedures, and accountability standards carried across the entire shop. This helped me understand that IT support is most effective when every section operates with the same commitment to reliability, professionalism, and mission awareness.
    The supervision style in the shop also emphasized learning through direct exposure rather than through passive instruction alone. I shadowed technicians, observed how experienced personnel approached issues, and then took on responsibilities that matched my growing level of understanding. That model worked well for me because it showed not only what to do, but why the process mattered. I was not simply told to complete steps in a checklist. I was expected to understand how documentation, escalation, communication, and technical accuracy all fit together. This made the internship feel more like real professional development and less like a temporary student requirement.
    Another important part of the management environment was that I was brought into officer meetings that focused on policy, planning, and strategy for the Navy IT department. Being included in those discussions helped me see that the internship was not limited to technical troubleshooting alone. I was able to observe how officers think about priorities, manpower, process improvement, and the larger mission of the command. Through the guidance of the officers involved, I began to understand the Navy from a broader perspective instead of only viewing work as one task after another. That exposure was valuable because it showed me the managerial side of IT leadership and helped me better understand the type of role I may want to grow into in the future.
    Another important part of the management environment was the example set in communication and professionalism. Through both observation and interview discussion, I saw that LT Gregory placed strong value on intellectual curiosity, clear communication, and humility in technical work. He made it clear that technical ability alone is not enough in an IT environment. A person also needs to explain issues in a way that customers can understand, treat others professionally, and stay willing to do the less visible work that keeps the mission moving. That leadership mindset had a real effect on how I viewed my own role during the internship. It reminded me that growth in this field requires both technical competence and professional maturity.
    In my view, the management environment was effective because it challenged me without making me feel unsupported. I was pushed to move across departments, learn different functions, and think more broadly about how the N6 shop supports the command. At the same time, the daily communication and the structured rotation through the shop gave me enough support to stay on track. That combination made the internship meaningful and helped me develop a better understanding of what strong technical leadership looks like in a Navy environment.

    Major Work Duties, Assignments, and Projects<\/strong>
    My internship involved a wide range of duties that gave me practical experience in customer support, accountability procedures, secure systems support, monitoring, and incident related processes. One of the most valuable aspects of the experience was that I was not limited to one type of work. Instead, I was able to see how several different IT functions work together to support the command. Each section had its own responsibilities, but all of them contributed to mission readiness, continuity, and security.
    I began in the Customer Support Center, which serves as the front line for many user issues. Working in that section introduced me to the process of receiving, documenting, categorizing, and resolving support tickets. I learned how issues are tracked from the time a user reports a problem until the time the matter is closed or elevated. The shop used a Power App created by LT Gregory to support the ticketing process, and that tool reinforced the importance of documenting each step accurately. I saw how clear notes support continuity when an issue needs to be handed off and how organized ticketing can reveal patterns in recurring problems across the command. This work mattered because the CSC is often the first point of contact between users and the technical team. If issues are not documented correctly at that stage, the entire resolution process can become slower, less effective, and more frustrating for the people who need help.
    A major portion of my work in the CSC involved Outlook and email related issues. Many users depended on email access for daily operations, so problems with sending, receiving, synchronization, or account setup could quickly interfere with their ability to work. I assisted with troubleshooting those problems by checking account settings, verifying the correct profiles, and confirming connectivity and authentication. I also worked through Common Access Card related issues, including certificate problems that prevented access to email, websites, and required systems. These tasks may appear routine on the surface, but they are necessary to the
    business of the command because communication failures can slow work, delay responses, and affect coordination across offices and commands. Restoring user access quickly and accurately helps maintain workflow and reduces avoidable downtime.
    In addition to account and email issues, I assisted with printer and scanner troubleshooting. This included reconnecting and mapping devices, verifying that the correct printer was selected, confirming connectivity, and making sure the right drivers were installed. I also supported general workstation troubleshooting by checking connections, resolving access problems, and helping determine whether an issue was user related, device related, or network related. These duties taught me that even smaller support tasks are important because they directly affect the ability of personnel to complete daily responsibilities. A printer that will not connect or a workstation that will not function properly may not sound dramatic, but in an operational environment those issues still interrupt productivity and require timely attention.
    After building a foundation in the CSC, I transitioned into Key Management Infrastructure (KMI). This section introduced a stronger emphasis on accountability and security procedures because the equipment involved supports classified communications. In this area I learned how Secret Internet Protocol Router Network (SIPR) related equipment is issued and inventoried for different commands within the Navy Reserve. SIPR systems are used to transmit classified information and support secure communications, so the equipment associated with that environment must be handled with a very high level of care. My duties included recording serial numbers and asset tags, verifying entries for accuracy, performing basic functionality checks, and preparing equipment for delivery by packaging and sealing it correctly. This work required careful attention to detail because mistakes in documentation or handling could create accountability issues or affect support for secure systems. The importance of this work was clear. Classified network capable equipment cannot be treated casually. Proper inventory, verification, and chain of custody support both operational continuity and security.
    One of the most memorable assignments during my time around KMI involved an urgent SIPR connectivity problem inside the building. Right before an Admiral level meeting with senior Navy leadership, the SIPR connection went down. Because the timeline was short and the event was important, the response had to be immediate and precise. I assisted with rewiring and restoring connectivity by helping repatch physical connections and move the line to the correct network ports, then verifying that the connection was stable before the meeting began. What made this situation especially valuable for me as an intern was that one of the senior IT personnel was able to explain what she was doing while she was doing it. Even in a rushed moment, she broke down the problem, the purpose of each step, and how the physical network path affected the connection. That allowed me to learn in real time instead of only watching from the side. This was a strong example of how technical problems can become mission critical without warning. It also showed me why calm problem solving, teamwork, and adherence to process matter so much in real time situations.
    Later in the internship I moved into work related to the Local Registration Authority (LRA) area. This portion of the internship focused more heavily on monitoring, log review, and basic incident response related procedures. I learned how to use Event Viewer to review device and system logs, paying attention to event identifiers that could indicate system health issues, abnormal behavior, or possible security concerns. I also ran scripts to review information more efficiently, including system and security logs, disk space, group membership, registry changes, and software changes that might point to unauthorized installations or configuration issues. I learned that security applications cannot simply be installed and ignored. They have to be monitored to confirm that they are running correctly, reporting properly, and staying current.
    The work in the LRA area also gave me a better understanding of what happens when suspicious or abnormal activity is found. I learned that if an issue is confirmed or strongly suspected, the affected device may need to be removed from the network to prevent additional compromise. I also learned that incidents must be documented and reported through the proper chain, including command leadership and Naval Network Warfare Command when required. This part of the internship made it clear that technical action and reporting responsibility go together. A person cannot simply identify a problem and move on. In a command environment, the response has to be documented, communicated, and handled in a way that protects both the system and the mission.
    Another major project during my internship developed into a capstone style effort. LT Gregory thought it would be a good idea for me to take on a problem that had both technical and operational value, so he directed me to speak with ENS Scanlon about an issue in his area and see how it could be improved. After meeting with ENS Scanlon, who works in a subdivision of manpower, I learned about a major issue involving the Inactive Duty Training Travel Reimbursement (IDTR) process used to support reimbursement for reservists. He explained that the system often involves a delay of about two weeks even in situations where much of the review could potentially be automated. That delay creates extra work for both applicants and approvers and slows down a process that affects many people.
    From that discussion, I began working on an application concept that could automate much of the review process. The idea was for a Sailor to enter a Department of Defense identification number into the application and allow the system to automatically check key requirements before routing the request. If the information clearly met the standards, the request could be marked approved. If the information showed a definite disqualifying issue, it could be marked denied. If something was close to the requirement or needed a human judgment call, such as mileage that fell near a threshold, it could be marked pending review. This concept showed me how automation can improve both accuracy and efficiency when it is built around an existing administrative process.
    By the end of the internship, the application was in the final stages of being refined and adjusted. It has the potential to be presented to the Admiral for possible implementation because of the time and labor it could save across the command. This single capstone project has the ability to save tens of millions of dollars for the military and taxpayers. Even having the potential to be used in other branches not just the Navy. A process that can take more than two weeks could potentially be reduced to minutes in clear cut cases, while still preserving human review when needed. Beyond the technical side, this project taught me how innovation, leadership guidance, and practical problem solving can come together to improve quality of life for both the person submitting a request and the person reviewing it. It also gave me experience thinking about technology not just as a tool for fixing problems, but as a way to redesign processes at a broader organizational level.
    Taken together, these duties showed me that every part of the shop supports the business of the command. The Customer Support Center restores functionality and keeps personnel productive. Key Management Infrastructure protects accountability and supports secure communications. The Local Registration Authority area strengthens monitoring and response. Even though the tasks were different, they all contributed to readiness, continuity, and security. That broad exposure was one of the most valuable parts of the internship because it showed me how technical support functions as an integrated mission enabler rather than a collection of disconnected tasks.

    Specific Use of Cybersecurity Skills and Knowledge<\/strong>
    This internship gave me the opportunity to use cybersecurity knowledge in a practical setting instead of only understanding it as a classroom subject. Before the internship, I already had a foundation in cybersecurity concepts from my coursework and previous exposure to technical work. I understood the general importance of access control, system security, authentication, documentation, and troubleshooting. However, the internship moved those ideas out of theory and into an environment where the impact of each decision was more immediate and operational.
    One of the clearest ways I used cybersecurity related knowledge was in access and certificate troubleshooting. Common Access Card issues, authentication problems, and access failures all involve basic security principles because they deal with identity verification, trust relationships, and controlled access to systems. Helping users regain access required more than simply fixing an inconvenience. It required attention to the security process that protects those systems in the first place. I also used cybersecurity thinking in documentation and escalation because not every issue should be handled casually or closed too quickly. Knowing when a problem may reflect a larger security or configuration concern is part of acting responsibly in a command environment.
    My work in Key Management Infrastructure strengthened my understanding of security through accountability and chain of custody. Before this internship, I understood in a general sense that secure systems require controlled handling of equipment. During the internship, I saw how that principle works in practice. Recording serial numbers, confirming asset tags, verifying equipment functionality, and sealing hardware for delivery are not just administrative steps. They are part of maintaining trust, accountability, and secure support for classified communications. That experience helped me understand cybersecurity as something broader than software or network defense alone. It also includes disciplined control over physical assets that support secure systems.
    The Local Registration Authority portion of the internship expanded my understanding of monitoring and incident awareness. Reviewing logs, checking system status, watching for abnormal changes, and learning how incidents are reported all required a more analytical approach to security. I saw that cybersecurity in a real organization involves constant attention to system behavior and a readiness to act when something appears wrong. It is not enough to know that incidents can happen. A technical team has to monitor for signs of trouble, document findings accurately, and follow reporting procedures that protect the organization. That part of the internship changed my understanding of cybersecurity because it showed me how closely technical detail, operational discipline, and leadership communication are connected.
    Overall, the internship deepened my view of cybersecurity by showing me that it is both technical and organizational. It includes access control, secure equipment handling, monitoring, documentation, escalation, and incident response. It also depends on professionalism and judgment. The experience helped me move from seeing cybersecurity mainly as an academic subject to seeing it as a set of practices that directly support mission readiness in the Navy environment.

    How the ODU Curriculum Prepared Me<\/strong>
    The ODU curriculum gave me an important academic foundation for this internship, especially in how I think about systems, security, and problem solving. My classes helped me understand that cybersecurity is not only about technology itself, but also about risk, policy, process, and human behavior. Because of that preparation, I was able to enter the internship with a stronger understanding of why documentation matters, why access control matters, and why careful analysis is necessary when dealing with technical issues. The coursework gave me useful vocabulary, conceptual knowledge, and a more disciplined way of approaching problems.
    At the same time, the internship showed me the difference between understanding a concept and applying it in a live command environment. School prepared me to think about cybersecurity and IT in a structured way, but the internship forced me to operate inside real workflows, real accountability requirements, and real time consequences. In class, a student may analyze a scenario, discuss best practices, or complete a lab in a controlled environment. In the internship, I had to think about users who needed immediate support, secure equipment that had to be documented correctly, and system information that might require escalation if something looked abnormal. That difference was important because it made the academic material feel more real.
    There were several points where the internship reinforced what I have learned at ODU. The importance of security principles, the value of organized documentation, and the need to approach problems methodically all carried over from the classroom into the workplace. I also made connections between my coursework and the practical use of log review, system awareness, authentication related issues, and structured troubleshooting. Those links helped me see that the curriculum does provide a meaningful foundation for work in this field.
    However, there were also parts of the internship that revealed concepts and skills not fully developed in the classroom. The pace of support in a command environment, the importance of chain of accountability for secure equipment, the realities of escalation procedures, and the challenge of communicating technical issues to a wide range of users are all areas that become clearer through real experience. The internship also exposed me to the broader organizational side of the work, including how technical actions connect to leadership decisions and operational readiness. In that sense, ODU prepared me conceptually, but the internship gave me the practical and professional context that the classroom alone cannot fully provide.
    For me, the relationship between ODU and the internship was complementary. The curriculum gave me the foundation to understand what I was seeing, and the internship gave me the opportunity to apply, test, and expand that understanding. Together, they strengthened my preparation for future work in cybersecurity and information technology.

    Internship Outcomes and Objectives<\/strong>
    The internship fulfilled my objectives in meaningful ways. My first objective was to gain hands on experience with Navy Reserve IT policy and departmental operations. This objective was met strongly. By working in the Customer Support Center, Key Management Infrastructure, and Local Registration Authority areas, I gained direct exposure to how the N6 shop functions. I saw how issues are documented, how work is assigned and escalated, how secure equipment is handled, and how monitoring and reporting processes support the command. These were not abstract descriptions. They were daily practices that I had the chance to observe and support.
    My second objective was to analyze how the command\u2019s technology strategy and innovation efforts support operational and cybersecurity capabilities. This objective was also fulfilled. I saw examples of innovation and process improvement in the way the shop used a Power App to track tickets and improve continuity. I also saw that strategy is not just expressed in high level policy language. It is reflected in the design of systems, the structure of workflows, and the way technical support is organized to protect readiness. Working under LT Gregory gave me a better understanding of how leadership can improve support processes while still maintaining accountability and security.
    My third objective was to apply cybersecurity principles to practical situations during the internship. This objective was fulfilled throughout the experience. I applied security related thinking when dealing with access and authentication issues, certificate problems, secure equipment accountability, log review, and incident related procedures. More importantly, the internship showed me that cybersecurity principles have to be carried out through real habits such as careful documentation, disciplined handling of hardware, proper escalation, and awareness of abnormal system behavior. This made the objective more meaningful because I was able to move beyond theory and see how those principles function in real work.
    A fourth personal objective was to use the internship to shape my professional path in Navy IT and cyber work. In this area, the internship may have had the strongest impact of all. It confirmed that this is a field where I can see myself growing. The experience showed me that I find the work rewarding and meaningful because it supports real mission requirements and challenges me to keep improving. It also helped me see that a future in Navy IT leadership is not just about technical ability. It requires communication, accountability, intellectual curiosity, and the willingness to learn continuously. That realization gave the internship value well beyond the course requirement.
    In summary, the internship did not just partially fulfill my goals. It met them in ways that were practical, clarifying, and professionally useful. The experience gave me direct exposure to departmental operations, showed me how support and innovation contribute to the mission, allowed me to apply cybersecurity principles in a real setting, and strengthened my commitment to growing in this field.

    Most Motivating and Exciting Aspects of the Internship<\/strong>
    The most motivating aspect of the internship was seeing how technical work directly supports mission readiness. I found it rewarding to know that the work of the N6 shop was not separate from the mission, but part of what allows the command to operate effectively. Even tasks that might seem routine in another setting had real importance because they affected communication, access, accountability, and continuity across the command. That sense of purpose made the work more meaningful.
    Another exciting part of the internship was the chance to move through different sections and learn from each one. I was able to see the support side of the mission in the Customer Support Center, the accountability and secure systems side in Key Management Infrastructure, and the monitoring and incident awareness side in the Local Registration Authority area. That variety kept the internship engaging and helped me build a broader view of IT work in the Navy. It also gave me more confidence because I could see how each experience added to my understanding.
    A particularly motivating moment came when I assisted with the urgent SIPR connectivity issue before an Admiral level meeting. That situation showed me how quickly a technical problem can become mission critical and how important it is to respond calmly and effectively under pressure. Being part of that response reinforced the value of the work and showed me that this field offers both challenge and purpose. Overall, the internship was motivating because it showed me that technical skill, when combined with discipline and professionalism, can make a real difference in mission success.

    Most Discouraging Aspects of the Internship<\/strong>
    The most discouraging aspects of the internship were tied less to the work itself and more to the realities of operating in a demanding military environment. Navy IT work can be complex because even simple issues may involve multiple layers of policy, accountability, and operational impact. At times, that meant that progress could feel slower than expected. A problem that appeared straightforward on the surface sometimes required more checking, more documentation, or more coordination than I first assumed.
    Another discouraging aspect was realizing how little room there is for careless error when dealing with secure systems, asset accountability, or possible incident related concerns. That level of responsibility is necessary, but it can also make the learning process feel more intense because every detail matters. Repeated verification and careful handling are essential, yet they can be mentally tiring over time.
    Even so, these discouraging moments were still valuable. They taught me patience, discipline, and respect for the standards required in the environment. Instead of making me lose interest, they helped me understand the seriousness of the field and the level of professionalism expected from people who want to succeed in it.

    Most Challenging Aspects of the Internship<\/strong>
    The most challenging aspect of the internship was adapting to the breadth of the mission while continuing to learn new systems and responsibilities. Because I moved through multiple sections, I had to adjust quickly from user support work to secure equipment accountability and then to monitoring and incident awareness tasks. Each area had its own procedures, terminology, and priorities. That required me to stay flexible and pay close attention so I could understand both the technical work and the reason it mattered.
    Another major challenge was developing the level of detail expected in documentation and reporting. In an academic setting, students often focus on whether they understand a concept. In this internship, understanding was only part of the requirement. I also had to communicate clearly, record information accurately, and follow procedures carefully enough that someone else could rely on the documentation if the issue needed to be handed off or reviewed later. That standard made the work more demanding, but it also helped me grow.
    A final challenge was balancing the role of learner with the responsibility to contribute professionally. I had to be honest about what I did not know while still carrying myself like someone who could be trusted in a serious environment. That balance pushed me to ask better
    questions, observe more closely, and treat every task as part of my professional development. In the end, those challenges made the internship more valuable because they forced growth rather than comfort.

    Recommendations for Future Interns<\/strong>
    I would recommend that future interns begin this internship with a strong willingness to learn and a serious attitude toward both technical and professional expectations. Basic familiarity with computer systems, troubleshooting, and cybersecurity concepts will help, but technical skill alone is not enough. A future intern should also understand the importance of communication, documentation, accountability, and respect for procedure. Those qualities affect daily performance just as much as technical ability.
    Future interns should prepare by reviewing common support concepts before they begin. This includes email troubleshooting, printer and scanner connectivity, account and authentication issues, and general workstation support. They should also understand that in a Navy environment, these tasks are not only about convenience. They support the mission by restoring functionality and allowing personnel to do their jobs. Having that mindset early will help an intern take even routine duties seriously.
    I would also advise future interns to arrive with curiosity and humility. One of the strongest lessons I took from observing and interviewing LT Gregory was that intellectual curiosity matters. A person should not stop at the first answer that appears to solve a problem. They should keep asking why, look deeper, and try to understand how the full system works. At the same time, they should stay humble enough to learn from others, accept correction, and handle less visible tasks with the same effort they would give to more impressive ones. In a good technical environment, no task is beneath a person who is serious about learning.
    Finally, future interns should be ready for the reality that military IT work can be more complex and demanding than many people expect. There are layers of accountability, policy, and mission impact that make the environment different from a casual support setting. The more prepared an intern is to work carefully, communicate professionally, and stay adaptable, the more they will gain from the experience.

    Conclusion<\/strong>
    My main take away from this internship is that IT and cybersecurity work in the Navy is about far more than fixing devices or solving isolated technical issues. It is about supporting readiness, protecting secure systems, communicating clearly, and operating with accountability in an environment where the mission matters. This internship helped me see that every technical action has a wider context. Documentation affects continuity. Access support affects productivity. Secure equipment handling affects trust and accountability. Monitoring and reporting affect security and command awareness. That broader understanding is one of the most important things I gained from the experience.
    This internship will influence the remainder of my time at ODU by giving me a clearer picture of the skills I still want to strengthen. I want to continue developing both technical
    knowledge and professional communication because I now understand how closely those two areas work together. The internship also helped me connect classroom learning to real operational settings, which gives more meaning to the rest of my coursework. Instead of seeing classes only as graduation requirements, I can now see them more clearly as tools that support the type of work I want to do in the future.
    The experience will also influence my future professional path. It confirmed that I see myself growing in this field and that I find the work rewarding and meaningful. It showed me that Navy IT leadership requires more than technical competence. It requires discipline, patience, communication, curiosity, and a mission focused mindset. Those are qualities I want to continue building. This internship also helped shape my long term interest in becoming an Information Professional Officer by showing me how IT supports Navy operations in direct and practical ways.
    In the end, this internship was valuable not only because it fulfilled a course requirement, but because it gave me a realistic and motivating look at the kind of work I may want to pursue long term. I completed the required 100 internship hours and interview, but more importantly, I left with a stronger professional direction, a deeper respect for the work of the N6 shop, and greater confidence in my ability to grow within this field.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

    Internship Final PaperCYSE 368 Internships in CybersecurityAlexander L. TrevinoCommander, Navy Reserve Forces CommandUS NavyProfessor Teresa DuvallTA Joshua RussellSpring 2026April 19, 2026Table of Contents<\/p>\n","protected":false},"author":26774,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","wds_primary_category":0},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/student.wp.odu.edu\/atrev004\/wp-json\/wp\/v2\/posts\/121"}],"collection":[{"href":"https:\/\/student.wp.odu.edu\/atrev004\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/student.wp.odu.edu\/atrev004\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/student.wp.odu.edu\/atrev004\/wp-json\/wp\/v2\/users\/26774"}],"replies":[{"embeddable":true,"href":"https:\/\/student.wp.odu.edu\/atrev004\/wp-json\/wp\/v2\/comments?post=121"}],"version-history":[{"count":2,"href":"https:\/\/student.wp.odu.edu\/atrev004\/wp-json\/wp\/v2\/posts\/121\/revisions"}],"predecessor-version":[{"id":123,"href":"https:\/\/student.wp.odu.edu\/atrev004\/wp-json\/wp\/v2\/posts\/121\/revisions\/123"}],"wp:attachment":[{"href":"https:\/\/student.wp.odu.edu\/atrev004\/wp-json\/wp\/v2\/media?parent=121"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/student.wp.odu.edu\/atrev004\/wp-json\/wp\/v2\/categories?post=121"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/student.wp.odu.edu\/atrev004\/wp-json\/wp\/v2\/tags?post=121"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}