CST 499 - Week 1

 Hey everyone,

    This week, I completed three modules: Tools of the Trade: Linux and SQL, Assets, Threats, and Vulnerabilities, and Sound the Alarm: Detection and Response. Each module built on the last and helped me better understand both the technical and analytical sides of cybersecurity.

    In Tools of the Trade: Linux and SQL, I strengthened my understanding of how operating systems and databases are used in security work. I learned how Linux is widely used in cybersecurity for system administration, log analysis, and security operations. Practicing basic Linux commands helped me see how security analysts navigate file systems, manage permissions, and investigate system activity. I also learned how SQL is used to query databases, filter information, and analyze large sets of data. Understanding how to retrieve specific information from logs and datasets showed me how powerful SQL can be in identifying suspicious patterns or investigating incidents.

    In Assets, Threats, and Vulnerabilities, I gained a clearer understanding of what organizations are actually protecting. I learned that assets include anything valuable to a business—such as data, hardware, software, and even reputation. From there, I explored how threats exploit vulnerabilities, and how risk is evaluated based on the likelihood and impact of those threats. This module helped me think more critically about how security is not just technical but strategic. Identifying weaknesses before they are exploited is a key part of reducing risk.

    Finally, in Sound the Alarm: Detection and Response, I learned about the processes used to detect, analyze, and respond to security incidents. I explored the importance of monitoring systems, analyzing alerts, and following structured incident response plans. I also learned how documentation and communication play a major role during incidents. This module helped me understand that cybersecurity is not just about prevention—it’s also about being prepared to act quickly and effectively when something goes wrong.

Overall, this week deepened my understanding of both the technical tools (Linux and SQL) and the broader security concepts (risk, threats, and response). I feel more confident in my ability to analyze systems, understand potential risks, and appreciate the structured approach organizations use to protect their assets.

    Next week, I plan to continue progressing through the next course modules while reviewing key concepts from Linux, SQL, and incident response. I want to spend additional time practicing Linux commands in a lab environment to become more comfortable navigating directories, managing permissions, and analyzing logs. I also plan to strengthen my SQL skills by practicing more complex queries, especially those involving filtering, sorting, and combining data. Additionally, I aim to review the incident response lifecycle to better understand each phase and how they connect in real-world scenarios.

    One challenge I am currently facing is fully understanding more advanced SQL queries, particularly when working with multiple conditions or organizing large datasets. I also sometimes need more practice interpreting security logs efficiently. At this time, I do not urgently need instructor assistance, but I may reach out for clarification or additional resources if I encounter difficulties with more complex query structures or real-world case scenarios.

Comments

Post a Comment

Popular posts from this blog

CST 489 - Week 4

 Hey everyone, Since I have chosen to take part in the Certificate Track of the capstone project, I have faced some challenges during this week's assignments. This week, I spent time developing my certificate track capstone proposal, which helped me clarify my learning goals and better understand how each certification connects to my long-term career plans. Writing the proposal forced me to think beyond just completing courses and instead focus on the skills, artifacts, and outcomes I want to gain from each certificate. I also spent a significant amount of time trying to figure out how to enroll in the AWS Cloud Practitioner course. Navigating AWS’s training site was more complicated than I expected, and it took some trial and error to understand the different learning paths and options available. Although it was a bit frustrating, the experience helped me become more comfortable with AWS’s ecosystem and reminded me that problem-solving and persistence are essential parts of learni...
Read more

CST 370 - Week 1

 Hey everyone, This week, we learned several important topics that form the foundation of computer science and programming. We started with GitHub and practiced using manual commands like git init, git add, git commit, and git push to manage our code. This helped us understand version control and how to keep track of changes when working on projects, especially when collaborating with others. We were also introduced to algorithms and learned what they are—step-by-step methods for solving problems. One example we focused on was Euclid’s Algorithm for finding the greatest common divisor (GCD) of two numbers. It uses a simple but powerful idea: repeatedly replace the numbers with GCD(b, a % b) until the second number becomes zero. We also practiced writing pseudocode, which helped us plan out algorithms in plain language before coding. We also had a homework assignment to help us further understand GitHub commands. Later in the week, we learned about graphs, both weighted and unweight...
Read more

CST 370 - Week 5

 Hey everyone! This week, I explored several important algorithm design techniques and deepened my understanding of how they are applied in solving complex problems efficiently. One of the key highlights was learning about Quick Sort , a widely used sorting algorithm that relies on the Divide-and-Conquer strategy. I now understand how Quick Sort works by dividing the array into smaller parts around a pivot, sorting those parts recursively, and then combining the results. I also learned about its efficiency and how its performance depends on the choice of the pivot. I also studied Binary Tree traversal methods, such as inorder, preorder, and postorder, and how each serves a specific purpose when working with hierarchical data. Alongside traversal, I learned how to calculate the height of a binary tree , which is a foundational concept for evaluating the balance and efficiency of tree-based data structures. I even added my insights on the class Discord group, explaining an easy calc...
Read more