top of page

My Internship Experience: Exploring System Security and Compliance

                                                     (Part 2)

In this stage, I focused on improving system security and compliance. I took responsibility for applying STIG measures to various software components and successfully resolved a recurring issue with a virtual machine (VM) scan issue by configuring the remote registry service and updating policies.

          In the second stage of my internship, I delved deeper into system security and compliance, specifically on STIG (Security Technical Implementation Guide) and SCAP (Security Content Automation Protocol) scans. After shadowing the cybersecurity experts within my team and closely observing their detailed approach to STIG implementation, I was tasked with applying these measures to various software components, including Microsoft Defender, Microsoft Edge, PowerPoint, Office, Excel, and Word. Each software had unique security requirements, highlighting the importance of attention to detail. I began the process by reviewing the STIG guidelines for each software component, focusing on capturing essential security requirements, including access control, data protection, and network security. This phase enabled me to identify and prioritize the critical security measures needed for each software component, considering their unique attributes and complexity. It provided a strong base for all the tasks that followed, making sure that our STIG compliance efforts were carefully adjusted to meet the exact security needs and weaknesses of each software part.

          One of my team members encountered difficulties while attempting to scan a virtual machine (VM) and sought my assistance in identifying and resolving the issue. After thorough research, I resolved the recurring error through a structured troubleshooting process with three key steps, and some detailed subtasks. First, I tackled the issue by enabling the remote registry service by setting it to "Automatic", recognizing that the problem stemmed from this service not being active. Then, I referenced a comprehensive help guide available in the company's shared folder to ensure that all necessary configurations were accurately configured for the SCAP scanning process. Lastly, to solidify these changes, I initiated a 'gpupdate /force' command to guarantee the prompt application of updated policies. After a system restart, I reattempted the SCAP scan, and it was completed successfully without encountering any errors.

                This experience has given me valuable insights into the complexities of maintaining systems that adhere to rigorous security standards. It has also emphasized the need to stay informed about the latest security standards and best practices to effectively safeguard systems against potential threats and vulnerabilities.

bottom of page