Week 7 Blog: Why It's Important to Hunt for Threats Before They Happen

I learned in Week 7 that proactive threat hunting is an important part of modern cybersecurity because it looks for threats before they can do a lot of damage. Threat hunting is when security teams actively look for strange behavior on networks, systems, and endpoints instead of waiting for automated tools to send them alerts. This method assumes that attackers may already be inside the environment and that regular defenses aren't enough to stop advanced or hidden threats. One important thing I learned this week was how threat hunting works as a planned activity. Usually, it starts with making a guess based on threat intelligence, past attacks, or known methods used by attackers. After that, analysts gather and look at logs, authentication records, network traffic, and endpoint activity to find signs of a breach. I learned that this process depends a lot on human thought and experience, not just tools, because automated systems may not always have the right context to see unusual behavior. Another important thing I learned is how threat hunting is very similar to real attack methods, like brute-force attacks, social engineering, and threats that come from the cloud. Brute-force attacks use weak passwords and bad authentication controls, while social engineering uses people's behavior to trick them through phishing, vishing, and impersonation. In cloud environments, attackers can easily get in through misconfigured settings, stolen credentials, and access that is too open. Threat hunting helps find these problems early by spotting strange login attempts, strange access locations, and strange user behavior. I also learned that good threat hunting makes all security operations stronger. You can use the results of threat hunts to make detection rules better, make authentication controls like MFA stronger, cut down on too many permissions, and raise employee security awareness. Threat hunting is not something you do once; it's a cycle that helps companies stay one step ahead of attackers. This week taught me that proactive threat hunting is necessary to lower risk, make things more visible, and make security stronger overall.

Comments

Post a Comment

Popular posts from this blog

Week 1 Posting -

This first week of BSIT380: System Hardening and Network has really changed how I think about cybersecurity. The class started by comparing it to a big sporting event, where both teams study their opponent before the big day. That comparison helped me see why threat data and intelligence are so important: you can't protect a network if you don't know who the attackers are, what they want, and how they work. We talked about today's threat actors, such as nation-states, cybercriminal groups, insiders, and hacktivists. Each one has its own reasons for doing what they do and ways of doing it. I also learned that threat intelligence is more than just reading about attacks in the news. It means getting information from a lot of different places, looking for patterns, and using that information to make the organization's security better. The readings talked about the frameworks and threat research sources that analysts use, as well as different ways to model threats that hel...
Read more

Week 8 Blog: Ideas and Tools for Automating

This week really drove home how important automation is in today's cybersecurity work. One of the most important things I learned is that attackers are already using automation to launch network-speed attacks on a large scale. If defenders only use manual processes, they will automatically fall behind. Security Operations Centers (SOCs) use tools like SIEM and SOAR to find, connect, and respond to threats much faster than a person could do it alone. Automation doesn't take the place of analysts, but it does make them better at responding quickly and effectively. I also learned that playbooks and orchestration are very important for making sure that responses are always the same. Instead of responding to each alert in a different way, businesses can set up structured workflows that automatically collect logs, add information, isolate endpoints, or let the right teams know. This cuts down on alert fatigue and makes responding to incidents more consistent. It's important to t...
Read more

Week 5 Blog — Software and Hardware Assurance Best Practices

This week made me realize that security isn't just about making the operating system stronger; it's also about protecting everything from the code to the firmware and hardware. My biggest lesson about software was that security needs to be built in from the start, not added on later. That's why it's important to have a good SDLC and follow safe coding practices, like checking input, using the least amount of privilege, and testing early. It also made sense why third-party libraries and tight deadlines can be a problem: one weak spot can become a real vulnerability. I learned why firmware is so important on the hardware side: it controls low-level functions and is found in almost every device, such as servers, embedded systems, and IoT. If firmware isn't kept up to date and managed properly, it can break everything else. I also learned how hardware can help with a "root of trust," which is useful for things like secure boot and checking the system's in...
Read more