<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Grace Jaman on Medium]]></title>
        <description><![CDATA[Stories by Grace Jaman on Medium]]></description>
        <link>https://medium.com/@graccie?source=rss-ff0ddc9cba21------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MJDkTCZfHk22Ns0bAnjZ6g.jpeg</url>
            <title>Stories by Grace Jaman on Medium</title>
            <link>https://medium.com/@graccie?source=rss-ff0ddc9cba21------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:00:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@graccie/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Cybersecurity Isn’t Just About Technology: It’s About People Too.]]></title>
            <link>https://medium.com/@graccie/cybersecurity-isnt-just-about-technology-it-s-about-people-too-ee5183138b67?source=rss-ff0ddc9cba21------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee5183138b67</guid>
            <dc:creator><![CDATA[Grace Jaman]]></dc:creator>
            <pubDate>Fri, 06 Nov 2026 19:21:01 GMT</pubDate>
            <atom:updated>2026-11-06T19:21:01.753Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Exploring human-factor threats, social engineering, and the role of security awareness in building resilient organizations.</blockquote><p>Cybersecurity is often associated with firewalls, encryption, threat detection, and sophisticated technical controls. But behind many successful cyberattacks is something much more human: trust, urgency, routine and the ability to influence people’s decisions.</p><p>As part of my cybersecurity learning journey, I worked on a project exploring human factors in cybersecurity, with a focus on how human behaviour, social engineering and gaps in security awareness can expose organizations to cyber threats.</p><h3>When Human Behaviour Becomes a Security Risk</h3><p>During the project, I explored how cybercriminals take advantage of everyday human interactions, trust, and communication to manipulate employees and gain unauthorized access to organizational systems and sensitive information.</p><p>Some of the key threats include:</p><ul><li><strong>Social engineering:</strong> Manipulating individuals into revealing sensitive information or granting unauthorized access.</li><li><strong>Phishing and impersonation:</strong> Using convincing messages or trusted identities to influence employees into taking unsafe actions.</li><li><strong>Help-desk exploitation:</strong> Taking advantage of weaknesses in identity verification and account recovery processes.</li><li><strong>Security fatigue:</strong> When repeated security requirements become overwhelming, people may begin to bypass controls or ignore warnings.</li></ul><p>These threats demonstrate that security incidents are not always the result of technical vulnerabilities. In some cases, they begin with an ordinary interaction that appears completely legitimate.</p><h3>A Real-World Case: The MGM Resorts Cyberattack</h3><p>One incident that stood out during our research was the 2023 MGM Resorts cyberattack.</p><p>The incident was widely associated with social engineering and the exploitation of IT help-desk processes. Attackers reportedly used impersonation and identity-related weaknesses to gain access, contributing to significant operational disruption.</p><p>The consequences extended beyond technology. MGM experienced business interruptions, financial losses, and exposure of customer information.</p><p>What makes this incident particularly relevant is how it demonstrates the interconnectedness of human behaviour, identity verification, security processes, and organizational resilience.</p><p>It reinforces an important point: <strong>a weakness in one human-facing process can create consequences across an entire organization.</strong></p><h3>From Awareness to Behaviour Change</h3><p>Beyond the case study, I also contributed to developing a cybersecurity awareness campaign, with a focus on creating practical, engaging, and accessible content that encourages employees to recognize security risks and adopt safer practices in their daily work.</p><p>The objective is not simply to tell employees what they should avoid. It is to help them recognize suspicious situations, make informed decisions, challenge unusual requests, and report potential incidents confidently.</p><p>Accessibility is also an important consideration. Security awareness is only effective when information can be understood and used by people with different needs and abilities.</p><h3>My Key Takeaway</h3><p><strong>Human factors should not be treated as a secondary consideration in cybersecurity.</strong></p><p><strong>Organizations need technical controls, but they also need effective processes, meaningful awareness programs, and a culture where security-conscious behaviour is supported.</strong></p><p><strong>Ultimately, building a resilient security environment requires more than protecting systems. It requires understanding the people who interact with them.</strong></p><p><strong>This project brought together three important aspects of cybersecurity for me: understanding human behavior, strengthening security controls, and recognizing how both contribute to an organization’s overall security and resilience</strong></p><h4>References</h4><ol><li><em>MGM Resorts — Official Cybersecurity Incident Statement (September 12, 2023) </em><a href="https://investors.mgmresorts.com/2023-09-12-MGM-RESORTS-INTERNATIONAL-STATEMENT-ON-CYBERSECURITY-ISSUE?utm_source=chatgpt.com"><em>https://investors.mgmresorts.com/2023-09-12-MGM-RESORTS-INTERNATIONAL-STATEMENT-ON-CYBERSECURITY-ISSUE</em></a></li><li><a href="https://investors.mgmresorts.com/2023-10-05-MGM-RESORTS-UPDATE-ON-RECENT-CYBERSECURITY-ISSUE?utm"><em>https://investors.mgmresorts.com/2023-10-05-MGM-RESORTS-UPDATE-ON-RECENT-CYBERSECURITY-ISSUE?utm</em></a></li><li><a href="https://www.sec.gov/Archives/edgar/data/789570/000119312523251667/d461062d8k.htm"><em>https://www.sec.gov/Archives/edgar/data/789570/000119312523251667/d461062d8k.htm</em></a></li><li><a href="https://www.cybersecuritydive.com/news/mgm-resorts-caesars-attacks-hospitality/693689/?utm"><em>https://www.cybersecuritydive.com/news/mgm-resorts-caesars-attacks-hospitality/693689/?utm</em></a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee5183138b67" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Taking my understanding of security controls beyond documentation and into practice]]></title>
            <link>https://medium.com/@graccie/taking-my-understanding-of-security-controls-beyond-documentation-and-into-practice-0997817ce676?source=rss-ff0ddc9cba21------2</link>
            <guid isPermaLink="false">https://medium.com/p/0997817ce676</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[grc]]></category>
            <category><![CDATA[microsoft-azure]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Grace Jaman]]></dc:creator>
            <pubDate>Mon, 12 Oct 2026 18:41:16 GMT</pubDate>
            <atom:updated>2026-10-12T18:41:16.021Z</atom:updated>
            <content:encoded><![CDATA[<p>Coming from a Risk and Compliance background, I’m interested in understanding how technical security controls work in practice and how they support areas such as risk monitoring, audit evidence, and security oversight.</p><p>This project gave me an opportunity to explore that connection.</p><h3>What I Worked On</h3><p>I deployed an Ubuntu Linux virtual machine in Azure and created a Log Analytics workspace and a storage account as part of the requirements.</p><p>I then configured the Azure Monitor Linux Agent and created a Data Collection Rule (DCR) called <em>Lab6-DCR</em>, which I associated with my virtual machine.</p><p>The rule was configured to collect:</p><ul><li><strong>Linux Syslog:</strong> System and authentication-related events.</li><li><strong>Performance data:</strong> CPU, memory, disk, and network metrics.</li></ul><p>I configured the collected data to be sent to my Log Analytics workspace, where I could query and review it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/1*7vmwJROJ2smIVow4ddQEwQ.png" /><figcaption>Data Collection Rule configured to collect Linux Syslog and performance data</figcaption></figure><h3>Challenges and Troubleshooting</h3><p>One challenge I encountered was during VM deployment, when some VM sizes appeared unavailable in the Azure Portal. After reviewing the available options, I selected <em>Standard D2als_v7</em> and continued with the deployment.</p><p>I also had to revisit my Data Collection Rule after realising that my initial configuration covered Syslog but not performance monitoring. I updated the rule to include the required performance counters.</p><p>During validation, I noticed some Syslog entries reporting that no DCR was associated with the VM. I checked the resource association and ran queries in Log Analytics to investigate further.</p><p>The DCR was associated with the VM, and the Heartbeat and Performance queries confirmed that monitoring data was being collected. This reinforced the importance of validating configurations rather than relying on a single warning message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JUPaEEhCmPI-rcGayoA2qw.png" /><figcaption>Log Analytics results used to verify monitoring data collection from the virtual machine.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6hcD1yLzYLRUW0PCsmODbA.png" /><figcaption>erformance telemetry collected from the Azure VM, including disk, network, processor, and memory metrics.</figcaption></figure><h3>How This Connects to GRC</h3><p>Although this was a technical project, I could see its relevance to Governance, Risk, and Compliance.</p><p><strong>From a risk management perspective</strong>, collecting system and authentication logs can help organisations identify unusual activity and investigate potential security incidents.</p><p><strong>From a compliance perspective</strong>, centralised logging can support audit readiness by providing records that may be needed to demonstrate monitoring activities and investigate events. The usefulness of that evidence depends on appropriate retention, access controls, and monitoring procedures.</p><p><strong>From a governance perspective</strong>, monitoring helps teams gain better visibility into their cloud environments and supports informed decisions about security risks and control effectiveness.</p><p>This project also reminded me that having a security control configured is not the same as proving that it works. Validation is an important part of understanding whether a control is operating as intended.</p><p><strong>Looking Beyond the Technical Side</strong></p><p>One thing I learned from this project is how Azure monitoring tools work together to give teams better visibility into system activity and performance.</p><p>As I continue building my technical knowledge, I’m also learning how these tools connect to GRC, from identifying risks and monitoring security controls to supporting audits and investigating potential incidents.</p><p>This experience has helped me see more clearly how technical security measures support risk management and compliance in real-world environments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0997817ce676" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From a Blank Dashboard to Real Threat Intelligence: My Hands-On OpenCTI Experience]]></title>
            <link>https://medium.com/@graccie/from-a-blank-dashboard-to-real-threat-intelligence-my-hands-on-opencti-experience-1ef659a73012?source=rss-ff0ddc9cba21------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ef659a73012</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <dc:creator><![CDATA[Grace Jaman]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 19:44:22 GMT</pubDate>
            <atom:updated>2026-10-08T19:44:22.500Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of my cybersecurity internship, I recently worked on a hands-on <strong>Threat Intelligence project</strong>.</p><p>For the exercise, we created <strong>Virelia Tech Int’l Ltd</strong>, a fictional organization whose operations were aligned with the <strong>financial and payment services sector</strong>. Using a fictional organization allowed us to work through a realistic cybersecurity scenario without making claims about a real company.</p><p>My assigned task was to conduct threat intelligence and threat landscape analysis for the sector using <strong>OpenCTI</strong>. This included identifying relevant threats, threat actors and campaigns, commonly observed malware and tools, attack techniques, targeting patterns, and relevant industry alerts or historical incidents.</p><p>I was responsible for carrying out the task, including setting up OpenCTI, connecting <strong>AlienVault OTX</strong>, and working through the challenges that came up along the way.</p><h3>Getting Hands-On with OpenCTI</h3><p>OpenCTI was one of the main platforms I used to collect, organize, and analyze cyber threat intelligence.</p><p>I connected <strong>AlienVault OTX</strong> as an external threat intelligence source so that relevant information could be brought into the OpenCTI environment.</p><p>The process seemed straightforward:</p><p><strong>Connect the source → collect the intelligence → process the data → analyze the threats.</strong></p><p>But things didn’t go exactly as planned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KOaVFKdm7gbkNW7lbnesjg.png" /><figcaption><em>Screenshot 1: OpenCTI dashboard showing empty</em></figcaption></figure><h3>When the Dashboard Was Empty</h3><p>After connecting the OTX source, I noticed that the information I expected wasn’t appearing in OpenCTI.</p><p>The first step was to investigate whether the connector itself was the problem.</p><p>After checking the setup, I confirmed that the OTX connector was working and successfully retrieving threat intelligence.</p><p>The data was also reaching the message queue.</p><p>So the question became: <strong>where was the data getting stuck?</strong></p><p>This meant I had to look beyond the dashboard and follow the data through the different components of the environment.</p><h3>Following the Data</h3><p>The environment uses <strong>RabbitMQ</strong> to handle messages between different components.</p><p>I found that the threat intelligence was reaching the queue, but the OpenCTI worker services responsible for processing the information were not running.</p><p>A simple way to think about it is a warehouse: the deliveries were arriving, but there weren’t enough workers to unpack and organize the packages.</p><p>After starting the required worker services, I monitored the queue to confirm that the backlog was actually being processed.</p><p>One check showed the queue dropping from approximately <strong>121,602 messages to 109,469</strong> after around 15 minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1X8nNhreki-OVqIRSEb7CQ.png" /><figcaption><em>Screenshot 2: RabbitMQ queue showing the message count decreasing</em></figcaption></figure><p>That was a good confirmation that the data pipeline was working and the information was being processed. I then checked OpenCTI again, and the dashboard was no longer empty. Threat intelligence information was beginning to populate the platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yXLVapboAYrdm8iPyAbMfQ.png" /><figcaption><em>Screenshot 3: Populated OpenCTI dashboard/entities</em></figcaption></figure><h3>Analyzing the Threat Landscape</h3><p>With the data flowing correctly, I could focus on the actual threat intelligence analysis.</p><p>For the financial and payment services sector, I looked at areas such as:</p><ul><li>Common threats, threat actors, and campaigns</li><li>Malware and tools associated with attacks</li><li>Common attack techniques and MITRE ATT&amp;CK mappings</li><li>Initial access methods such as phishing and stolen credentials</li><li>Patterns in how organizations and users are targeted</li><li>Relevant industry warnings and historical incidents</li></ul><p>The goal wasn’t simply to collect information.</p><p>It was to understand <strong>which threats could be relevant to an organization operating in this sector and why they matter</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e8PjKf8zz90tE2McDXFjSg.png" /><figcaption><em>Screenshot 4: Relevant threat intelligence, entities, or relationships in OpenCTI.</em></figcaption></figure><h3>Where This Connects to GRC</h3><p>This project also helped me see the connection between technical cybersecurity and <strong>Governance, Risk and Compliance (GRC)</strong> more clearly.</p><p>Threat intelligence on its own doesn’t reduce risk. The value comes from understanding what the intelligence means for the organization and using it to ask better questions.</p><p>For example, if phishing and stolen credentials are common attack methods, we can ask:</p><p><strong>Do we have strong MFA controls?</strong></p><p><strong>Are access privileges properly managed?</strong></p><p><strong>Are employees receiving appropriate security awareness training?</strong></p><p><strong>Are suspicious login activities being monitored?</strong></p><p><strong>Would our incident response process be effective if this happened?</strong></p><p>This is where I see the connection:</p><p><strong>Threat Intelligence → Risk → Controls → Business Decisions</strong></p><p>The technical information provides evidence about potential threats, while GRC helps translate that information into conversations around risk, controls, compliance, and business impact.</p><h3>What I Took Away</h3><p>One of my biggest takeaways from this project was the importance of <strong>investigating problems instead of simply assuming something isn’t working</strong>.</p><p>The OpenCTI dashboard was initially empty, but the data wasn’t actually lost. By following the flow of information, I was able to identify where the process was getting stuck, resolve the issue, and confirm that the data was being processed.</p><p>It was a good reminder that cybersecurity isn’t only about knowing the tools. It’s also about being curious, troubleshooting problems, understanding how different components connect, and knowing how to turn technical findings into something meaningful for the business.</p><p>For me, this project strengthened the connection between <strong>threat intelligence, technical security, risk management, and GRC</strong>.</p><p>I’m continuing to build my technical skills, and hands-on projects like this are helping me understand not just <strong>how</strong> security tools work, but also <strong>why the information they provide matters to an organization</strong>.</p><p><strong>One task, One challenge, One investigation, One solution — and one more practical cybersecurity lesson.</strong></p><p><em>Note: Virelia Tech Int’l Ltd is a fictional organization created for this internship exercise.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ef659a73012" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Completing the CyberOps program has been a meaningful step in strengthening my understanding of…]]></title>
            <link>https://medium.com/@graccie/completing-the-cyberops-program-has-been-a-meaningful-step-in-strengthening-my-understanding-of-5b593f056143?source=rss-ff0ddc9cba21------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b593f056143</guid>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Grace Jaman]]></dc:creator>
            <pubDate>Tue, 26 May 2026 09:41:00 GMT</pubDate>
            <atom:updated>2026-05-26T09:41:00.526Z</atom:updated>
            <content:encoded><![CDATA[<h3>Completing the CyberOps program has been a meaningful step in strengthening my understanding of cybersecurity operations and how they connect to Governance, Risk, and Compliance (GRC)</h3><p>Over the past few months, I dedicated time to completing the Cisco CyberOps program, covering areas such as networking fundamentals, network security, endpoint protection, threat analysis, monitoring tools, incident response, vulnerability assessment, and digital forensics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qqjg2pAawPtLou_FcyaLhw.png" /><figcaption>From CyberOps foundations to GRC-focused thinking (building technical awareness to support governance and risk understanding)</figcaption></figure><p>What made the experience particularly valuable was not only the technical exposure, but also the broader understanding it provided around how organizations manage security operations, identify risk, and respond to evolving threats.</p><p>Coming from a background in Fraud, Risk, and Compliance, one of the biggest takeaways for me was recognizing how closely technical security operations align with Governance, Risk, and Compliance (GRC). Understanding how threats are detected, how controls are implemented, and how incidents are managed adds important context to risk evaluation, compliance efforts, and security governance.</p><p>This journey has strengthened my interest in the GRC space and the role it plays in supporting organizational resilience, accountability, and informed decision-making. Moving forward, I’ll be focusing more intentionally on documenting my learning and perspectives around governance, risk management, compliance, security operations, and cybersecurity strategy here and on Medium.</p><p>Looking forward to continuing the journey and contributing thoughtfully to the conversation around security and risk management.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b593f056143" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Trust the Name (Verify the Service)]]></title>
            <link>https://medium.com/@graccie/dont-trust-the-name-verify-the-service-e1156463aa5f?source=rss-ff0ddc9cba21------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1156463aa5f</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[linux-tutorial]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Grace Jaman]]></dc:creator>
            <pubDate>Wed, 04 Mar 2026 11:59:30 GMT</pubDate>
            <atom:updated>2026-03-04T11:59:30.206Z</atom:updated>
            <content:encoded><![CDATA[<p>In my latest Linux lab, I learned something important: Just because a process is named “<strong>nginx</strong>” doesn’t mean it’s actually nginx. As cybersecurity analysts, we don’t trust labels, <strong><em>we verify</em></strong>.</p><p>First, i use <strong>ps</strong> to inspect running processes and understand the hierarchy, then i use <strong><em>sudo netstat -tunap </em></strong>and this allowed me to:</p><ul><li>Identify listening ports</li><li>See which services were bound to which ports</li><li>Match PIDs to active network services</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hMV5gPssZHBxXJO6bbRb_A.png" /><figcaption>Screenshot 1 : output from sudo netstat -tunap cpmmand</figcaption></figure><p>I found a process listening on TCP port 80 commonly used for web servers.</p><p>But here’s the real lesson:</p><p>What if malware renamed itself to “<strong>nginx</strong>” to look legitimate?</p><p>So instead of assuming, I tested it. Using Telnet, I connected directly to port 80: <em>telnet 127.0.0.1 80</em></p><p>When I sent random characters, the server responded with:</p><p><strong><em>HTTP/1.1 400 Bad Request<br> Server: nginx/1.16.1</em></strong></p><p>That confirmed:</p><ul><li>It was actually an HTTP server</li><li>The version number was exposed</li><li>The network stack was fully functional</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/561/1*d5J8uhS9-O6rXlAsC_3U0g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/753/1*7dEbxprM2_OefnAfxvl0sQ.png" /><figcaption>screenshot 2 &amp; 3 : netstat output, after telnet port 80 test, port 22 test and port 68 test</figcaption></figure><p>Then I tested port 22 (SSH) and observed its protocol banner.</p><p>This lab reinforced something critical:</p><p>Security isn’t about guessing, it’s about validating.</p><p>Every port tells a story.<br>Every process has context.</p><p>And every service should be verified.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1156463aa5f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One Wrong Dash Broke My Command (Lessons from Learning the Linux Shell)]]></title>
            <link>https://medium.com/@graccie/one-wrong-dash-broke-my-command-lessons-from-learning-the-linux-shell-6c92108ddb4e?source=rss-ff0ddc9cba21------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c92108ddb4e</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Grace Jaman]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 16:43:20 GMT</pubDate>
            <atom:updated>2026-03-02T16:43:20.230Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of my cybersecurity learning journey, I completed a lab on getting familiar with the Linux shell inside the <strong>CyberOps VM</strong>.</p><p>At first, it felt simple just creating folders and moving files, but it quickly became deeper than that. Using commands like <strong><em>pwd, ls -l, mkdir, cp, mv, and rm</em></strong>, I learned how Linux handles:</p><ul><li>Absolute vs relative paths</li><li>File vs directory permissions</li><li>Redirection (&gt; vs &gt;&gt;)</li><li>Hidden files (ls -la)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*h_-6wh-2CCQjr_59tXZhoA.png" /><figcaption>screenshot 1: verifying file creation and permissions using ls -l</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*63Xe33inDMywRiOOveipLA.png" /><figcaption>screenshot 2: Copying and moving files</figcaption></figure><p>Also learnt how small syntax mistakes can completely change results e.g a wrong dash (– instead of -) caused commands to fail. Linux didn’t break, it did exactly what I told it to do.</p><p>That’s when it clicked, the command line isn’t just typing commands.<br> It’s precision, its logic, it’s understanding how the system interprets instructions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/937/1*7b954YfAc1DZz4SQPx6SkQ.png" /><figcaption>screenshot 3: the error message and a successful command</figcaption></figure><p>As a future security professional this matters. The <strong>attackers</strong> use the command line and <strong>defenders</strong> investigate using the command line.</p><p>This lab wasn’t just about moving files, it was about learning to think like the system.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c92108ddb4e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Least Privilege Through a Windows User Account]]></title>
            <link>https://medium.com/@graccie/understanding-least-privilege-through-a-windows-user-account-d6d04618df3d?source=rss-ff0ddc9cba21------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6d04618df3d</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[windows]]></category>
            <dc:creator><![CDATA[Grace Jaman]]></dc:creator>
            <pubDate>Thu, 26 Feb 2026 20:34:48 GMT</pubDate>
            <atom:updated>2026-02-26T20:34:48.689Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of my cybersecurity lab practice, I worked on a simple task: creating and modifying local user accounts in Windows.</p><p>It sounded basic, but it reinforced one of the most important security principles: <strong>access control matters.</strong></p><p><strong>Part 1: Creating a Standard User</strong></p><p>I created a local account called <strong>User1</strong> and logged into it immediately, I noticed something important:</p><ul><li>The new account could access its own folder.</li><li>It could NOT access another user’s folder.</li><li>It did NOT have administrative privileges.</li></ul><p>This is the <strong>Principle of Least Privilege</strong> in action (users should only have access to what they need).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*u6tr1Seb94bkYM4gQ1TAuA.png" /><figcaption>Screenshot 1: A<em>ccount Creation</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/1*EOVAFxoKuHgU1tFzXOJ8MQ.png" /><figcaption>Screenshot 2: F<em>older Permissions View</em></figcaption></figure><p><strong>Part 2: Reviewing Group Membership</strong></p><p>Using Computer Management (Local Users and Groups), I checked which group User1 belonged to. It was part of the <strong>Users</strong> group (standard privileges), while my main account belonged to the <strong>Administrators</strong> group.</p><p>That difference determines:</p><ul><li>Who can install software</li><li>Who can modify system settings</li><li>Who can control other accounts</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/471/1*aE8Z3spRCw5_850dRRQnUA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/1*Y6zpQ2KdGtpNn6Vbf0zMeA.png" /><figcaption>Screenshot 3 &amp; 4: from Member Group to Administrator and Account Type Change</figcaption></figure><p><strong>Part 3: Privilege Escalation</strong></p><p>I temporarily changed User1 to an Administrator.</p><p>Immediately, it gained elevated privileges, Then I removed it from the Administrators group and deleted the account.</p><p>This exercise showed me how easily permissions can change and why monitoring account privileges is critical in real environments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*EcSjHG33fdCDVTvaslye_Q.png" /><figcaption>Screenshot 5: Account / Group Removal</figcaption></figure><p>In conclusion,</p><p><em>i. Strong passwords protect against unauthorized access</em></p><p><em>ii. Standard accounts reduce risk</em></p><p><em>iii. Admin rights should be tightly controlled</em></p><p><em>iv. Access mismanagement is a real security vulnerability</em></p><p>What looked like a <em>“Basic Windows Task</em>” is actually foundational cybersecurity knowledge.</p><p>Every breach starts somewhere and sometimes it starts with <strong>excessive permissions.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6d04618df3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Behind a Simple Click There is a Danger]]></title>
            <link>https://medium.com/@graccie/behind-a-simple-click-there-is-a-danger-09feaf129e39?source=rss-ff0ddc9cba21------2</link>
            <guid isPermaLink="false">https://medium.com/p/09feaf129e39</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[public-learning]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <dc:creator><![CDATA[Grace Jaman]]></dc:creator>
            <pubDate>Sat, 21 Feb 2026 18:41:38 GMT</pubDate>
            <atom:updated>2026-02-21T18:41:38.911Z</atom:updated>
            <content:encoded><![CDATA[<p>Today’s lab came from a module titled <strong>“The Danger.”</strong><br> And honestly? The title makes sense.</p><p>In this session, I worked with a pre-built OVA file, imported it into VirtualBox, powered up the virtual machine, and successfully logged in. From there, I confirmed the IP address and even used Firefox inside the VM to access Wikipedia (proving that the machine had proper network connectivity).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SqGQZdxmVDxgxmtmXqkJAA.png" /><figcaption>a screenshot to confirm the IP address</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zZK2MsNHy9jIHbsb4-t5NQ.png" /><figcaption>a screenshot to show connectivity</figcaption></figure><p>Sounds simple, right?</p><p>But here’s where the <em>danger</em> comes in.</p><p>When you boot up a virtual machine and connect it to a network, you’re essentially creating another device that could be vulnerable if not configured properly. If misconfigured:</p><ul><li><em>It could expose services.</em></li><li><em>It could leak data.</em></li><li><em>It could become an entry point for attackers.</em></li></ul><p>This lab reminded me that cybersecurity isn’t just about <em>hacking,</em> it’s about understanding systems deeply enough to secure them.</p><p>Every IP address.<br> Every configuration.<br> Every open port.<br> Every connection.</p><p>There’s always a risk behind convenience.</p><p>Day by day, I’m learning that security starts with <strong>awareness</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=09feaf129e39" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Danger: How Stuxnet Changed Cybersecurity Forever]]></title>
            <link>https://medium.com/@graccie/the-danger-how-stuxnet-changed-cybersecurity-forever-50a6dfd281d6?source=rss-ff0ddc9cba21------2</link>
            <guid isPermaLink="false">https://medium.com/p/50a6dfd281d6</guid>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyberwarfare-labs]]></category>
            <dc:creator><![CDATA[Grace Jaman]]></dc:creator>
            <pubDate>Tue, 17 Feb 2026 15:18:28 GMT</pubDate>
            <atom:updated>2026-02-17T15:35:58.499Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hOnmQGz8Bj4r_I-4pTZ7lQ.png" /><figcaption>Image generated for illustrative purposes.</figcaption></figure><p>In today’s digital world, cyberattacks are no longer just about stolen passwords or leaked emails. Some attacks can cause real-world physical destruction. One of the most dangerous examples of this is the <strong>Stuxnet attack</strong> a cyberweapon that changed the history of cybersecurity</p><p><strong>What Was Stuxnet?</strong></p><p>Stuxnet was a highly sophisticated computer worm discovered in 2010. Unlike traditional malware, it was not created to steal data or demand ransom. Instead, it was designed to sabotage industrial systems.</p><p>The primary target was <strong>Iran’s Natanz nuclear facility</strong>, specifically the systems controlling uranium enrichment centrifuges.</p><p><strong>Who Was Affected?</strong></p><p>The direct victim was Iran’s nuclear infrastructure. However, the impact went far beyond one country. Stuxnet demonstrated that critical infrastructure like power plants, factories, water systems could be attacked digitally.</p><p>This realization changed global cybersecurity policies.</p><p><strong>How Did the Attack Work?</strong></p><p>Stuxnet exploited multiple zero-day vulnerabilities in Microsoft Windows systems. It spread through infected USB drives and internal networks.</p><p>Once inside the network, it targeted Siemens Programmable Logic Controllers (PLCs), which controlled industrial machinery. The malware manipulated centrifuge speeds while feeding false data back to monitoring systems. Operators saw normal readings, while equipment was being physically destroyed.</p><p><strong>Why Was It So Dangerous?</strong></p><p>Stuxnet was one of the first known cyberattacks to cause physical destruction. It blurred the line between cybercrime and cyberwarfare.</p><p>The attack proved that:</p><ul><li>Cyber tools can be used as weapons</li><li>Critical infrastructure is vulnerable</li><li>Nation-states can launch silent digital attacks</li></ul><p><strong>The Outcome</strong></p><p>The attack reportedly destroyed hundreds of centrifuges and delayed Iran’s nuclear program.</p><p>More importantly, it changed how governments view cybersecurity. Protection of industrial control systems became a global priority.</p><p>In conclusion, the real danger is not just the malware itself. It is the realization that invisible code can cause real-world destruction. Stuxnet showed the world that cyberattacks are no longer theoretical threats they are strategic weapons. As cybersecurity professionals, understanding these case studies helps us prepare for the next generation of digital threats.</p><p>As I continue my cybersecurity journey, studying cases like <strong>Stuxnet</strong> reminds me that security is not just about technology, it’s about protecting infrastructure, economies, and human lives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50a6dfd281d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hands-On Networking: Switch Configuration and IP Addressing in Action]]></title>
            <link>https://medium.com/@graccie/hands-on-networking-switch-configuration-and-ip-addressing-in-action-9f4a0f1b490e?source=rss-ff0ddc9cba21------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f4a0f1b490e</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[network-configuration]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud-security]]></category>
            <dc:creator><![CDATA[Grace Jaman]]></dc:creator>
            <pubDate>Fri, 13 Feb 2026 13:31:01 GMT</pubDate>
            <atom:updated>2026-02-13T13:31:01.185Z</atom:updated>
            <content:encoded><![CDATA[<p>Practical labs are essential for understanding how real networks work. In this Cisco lab activity, I configured network switches, assigned IP addresses to devices, verified configurations using CLI commands and tested connectivity between devices. This exercise helped me translate theoretical networking concepts into practical skills which i summarized in 4 steps below:</p><h4>1. Basic Switch Configuration</h4><p>I started by performing basic switch configurations through the command-line interface<em> (CLI)</em>. This included setting device identifiers and preparing the switch for network communication. Understanding switch configuration is important because switches form the foundation of local area networks <em>(LANs)</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hf7kVE04NXWntvxTarxrig.png" /><figcaption>Screenshot 1: Switch CLI configuration</figcaption></figure><h4>2. IP Address Configuration on Switches and PCs</h4><p>Next, I configured IP addressing on both switches and PCs. IP addresses allow devices to identify each other and communicate within a network. I ensured that all devices were assigned appropriate IP addresses within the same network segment to enable connectivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*O2FvwXrpeo9kfUFf-X2Wwg.png" /><figcaption>Screenshot 2: IP configuration on PCs</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MmNb1GYIPCAr--e7heA7fA.png" /><figcaption>Screenshot 3: IP configuration on switches</figcaption></figure><p><strong>3. Verification Using Show Commands</strong></p><p>To confirm that configurations were correctly applied, I used Cisco verification commands such as: <em>show running-config, show Ip interface</em> <em>brief</em>, <em>show vlan brief.</em> These commands helped me validate device settings and network interfaces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ImaapESHgZLWzYPCwQFV0w.png" /><figcaption>Screenshot 4: Output of show commands</figcaption></figure><h4>4. Connectivity Testing with Ping</h4><p>After completing the configuration, I tested network connectivity using the <em>Ping</em> command. Successful ping responses confirmed that devices could communicate across the network and that the IP configuration was correct.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4PtCYNo9p_kp5-eoIBALYw.png" /><figcaption>Screenshot 5: Ping test results</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2wKsxD88XPO_wWFKQtGGhw.png" /><figcaption>Screenshot 6: Successful Connectivity Results</figcaption></figure><p>This hands-on exercise strengthened my understanding of how networks are configured and validated in real-world environments. It also showed me the importance of verification when configuring networks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f4a0f1b490e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>