Week 6 Reflection: Analyzing Data for Security Monitoring

This week, we learned how data analysis can help us keep an eye on security by not only finding threats but also predicting them. It really showed that modern security isn't just about firewalls; it's also about looking through a lot of data to find the signal in the noise. Here are some important things to remember from the readings and discussion: Sentiment Analysis as Intelligence: Using Natural Language Processing (NLP) for threat intelligence was one of the most interesting ideas. It's crazy to think that we can figure out when hackers will attack by looking at the "tone" of their forums. Since I'm interested in AI, it was cool to see it used to track emotional trends on the dark web. The Whitelisting Problem: We also talked about whitelisting. A "deny-all" approach is the safest way to go, but it makes things very difficult to run in environments that change all the time. It's hard to find a balance between strict security and the need for speed and new ideas. I also learned the difference between historical and trend analysis. Historical analysis is good for figuring out what went wrong after something bad happened, while trend analysis helps us figure out what is normal so we can spot future problems. This week's main theme was balance. The goal is to stay safe without slowing down productivity, whether it's using machine learning to find domain generation algorithms or deciding how strict to make a whitelist.

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