Week 10 Blog: Security Frameworks, Data Privacy, and Risk Mitigation

This week really helped me see how hard it is to protect people's privacy and lower the risk of an organization. Before this module, I mostly thought of security as firewalls, antivirus software, and tools for keeping an eye on things. But I learned that protecting a business goes far beyond just technical controls. It includes rules, guidelines, frameworks, and a planned way to deal with risk. One of the most important things I learned was how important it is to keep your data private in today's world. Companies are always gathering, storing, and processing private information. If that data isn't protected properly, the results can be very bad, both financially and legally. I learned that organizations need to do more than just protect their systems; they also need to follow privacy rules and make sure that data is handled properly. This means restricting access, encrypting private data, and checking for weaknesses on a regular basis. Another important idea I learned was how to reduce risk in an organization. Companies shouldn't wait until after a security breach happens to do something about it. This means doing risk assessments, finding possible threats, figuring out how those threats will affect things, and putting controls in place to lower risk. I now have a better understanding of how standards like NIST and ISO help people manage security in a structured way. These frameworks help businesses make sure that things are done the same way, that people are held accountable, and that security improvements can be measured. This week, I also thought a lot about policies, procedures, and controls. Technical tools are useful, but even the best ones can fail if there aren't clear rules and written procedures. Policies set standards, procedures show how to do things, and controls make sure those standards are met. Together, they make a strong base for a safe place to be. In general, Week 10 taught me that cybersecurity is not just about technology; it is also about planning, governance, and making strategic decisions. To keep data safe, you need a mix of technical tools, clear documentation, risk analysis, and support from leaders. This module helped me understand security from a broader organizational point of view, not just a technical one.

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