Internship Reflection 2
Chris Hopkins
May 27th
CYSE368
Reflection Paper 2
Continuing my internship as an IT Specialist at the City of Richmond City Hall’s Department of Information Technology has provided a unique and invaluable opportunity for professional and personal growth. This reflection paper serves three primary purposes: to offer a deep reflection on my internship experience, encompassing my observations, projects, tasks, and challenges; to highlight my progress towards achieving the learning objectives set at the start of the internship; and to detail the ongoing monitoring, coaching, and assessment provided by my Internship Instructor.
During this internship, one of my key tasks was to manage and move SecurID tokens to their respective system domains using the tool RSA SecurID and SecurID token, “a hardware device or software-based security token that generates a 6-digit or 8-digit pseudorandom number, or tokencode, at regular intervals. When the tokencode is combined with a personal identification number (PIN), the result is called a passcode”. Initially, these user tokens were assigned to a default “system domain” rather than their specific sectors. My role involved referencing a comprehensive Google Sheet maintained by Mr. James Furguson, which contained the correct security domain information for a significant number of Richmond city staff workers. I was responsible for updating each token to the most recently used one and changing its system domain to the respective, accurate domain. This task required not only technical proficiency but also meticulous attention to detail to ensure accuracy and security.
Amidst the myriad tasks, a prominent challenge surfaced in the perpetual need for vigilance to discern rogue computers and thwart unauthorized access attempts. The dynamic nature of this responsibility demanded swift decision-making and an intimate understanding of network intricacies. Guided by Mr. Furguson’s expertise,To ensure accuracy and efficiency in managing SecurID tokens, I documented a comprehensive procedure outlining which tokens should be deleted or altered. Drawing from my observations and discussions with colleagues, I detailed specific criteria for identifying rogue or outdated tokens, emphasizing factors such as recent usage and system domain alignment. This procedural documentation served as a crucial reference point, guiding my decision-making process and ensuring the integrity of the token management system.
Throughout this paper, I reflect on the various aspects of my internship experience, providing insights into the projects I undertook, the skills I developed, and the challenges I overcame. Additionally, I discuss my progress in achieving my learning objectives and the critical role played by my Internship Instructor in guiding and assessing my development. This reflection aims to encapsulate the lessons learned and the professional growth achieved during my tenure at the Department of Information Technology.
Photos of Spreadsheet (DO NOT READ), procedure notes:
Cited Works
“SecurID Tokens” RSA SecurID Documentation. Accessed May 29, 2024.