W7-3/3 Reflection On A Future In Cyber Security (8/12)

          I am glad I had this opportunity and experience. I now have an interest to work in this field. I could see myself working in vulnerability management or perhaps red team operations. I also still have a big interest in programming, but I feel as if I am not limited to programming and that my future could go either way. What I find so appealing about cyber security is the strategy within it. The balancing acts that I have mentioned in previous posts is an aspect that I really like about cyber security. I like the thought of working within the ebb and flow of a constantly evolving environment. To me tactical choices are very interesting.


     Once I graduate, I will be turning in resumes/CVs to both programming and cyber security jobs. While some might argue that I should specialize, I never like to pigeon hole or limit myself. I certainly wouldn’t like to do it so early in my computer science journey. Regardless of where I end up, I think they will always remain to be interests of mine. I plan on working on some personal programming projects in the future and there are several writings on cyber security and related topics that I want to read. I certainly want to read more of Kevin Mitnick’s books. I may even write my capstone on cyber security or information warfare. Timothy L. Thomas has a very interesting series on Chinese information warfare that I would like to read through in the future. I hope that in the future that I can procure a job in either field, while it is interesting to read about programming and cyber security it is even better to apply those skills. 

Comments

Post a Comment

Popular posts from this blog

W7-2/3 On Being Prepared & Further Recommendations (8/11)

   One can never be fully prepared. There is always more that a person can do to prepare themselves. I wish that before starting this internship that I would have had a better understanding of the basic concepts of cyber security (e.g. passive and active defense, vulnerability factors, etc.). I also wish that I had prior experience with all the tools and software I used. If you can find out the tools used at an internship, then it’s a good idea to try and learn some of those tools. Your internship will require less training and more application which will make the experience more productive for you. If you cannot find out what tools your internship will use, then it isn’t a bad idea to browse freeware related to that field (e.g. Maltego and Zed Attack Proxy for digital forensics and pen testing respectively). Most places are trying to save money, so they probably use freeware to some capacity. The most popular freeware is your best bet and even if they don’t use it, the...
Read more

W2-2/3 Network Mapping (7/5)

On Thursday we covered network mapping. The process of network mapping usually consists of four phases: identify the space of IP addresses you are monitoring and partition the space into different categories (1). Examine the IP space (2), identify blind and confusing traffic (3), and identify clients and servers (4).    During phase one the mapping of the inventory is undetermined and remains to be IP space. A security inventory should monitor every resource's address (that it is able to) on the network (i.e. anything within or on the network an attacker can access), what resources a service is running on, at the very minimum. During phase two cyber security personal should also consider enumerating roles to make searching easier; identifying VPNs, NATs, DHCP, and proxies; keep centrality or volume metrics (e.g. monthly ephemeral summaries); per-host white lists; and monitoring the versions of all services on a particular resource. Ask what addresses make up the network?...
Read more

W1-2/3 Prioritization (6/27)

   On Wednesday we covered prioritization. What is the most important thing to respond to first? How do we determine what is and what isn't more important? How do we assess the risk being taken? How much risk is too much risk? While some matters may be more general, a lot of prioritization will be based upon what the establishment is doing, who would target them, what resources does the establishment have for defense, etc. The effectiveness of cyber response teams is determined by how appropriate the prioritization of incidents is. Randomly responding and less formalized response protocols/orders (e.g. stacks/LIFO or queues/FIFO) will hinder the potential security capabilities of an establishment. One cannot prioritize for random or abstract orders and expect any type of long-term success. It is best to make decision making and risk taking as formalized as possible. What you do is just as important as what you do first. Basically, some things are more important to attend to ri...
Read more