Byte-Size Beginner

  Automation can have many benefits and uses, especially when it comes to repetitive and mundane tasks. This week we learned more in-depth about automation when working with cloud environments. However, something that stood out to me the most was automation and orchestration. Interestingly, it connected me back to learning about SOAR in a previous class. While SOAR (Security, Orchestration, Automation, and Response) tools are more for cybersecurity purposes, it incorporates automation and orchestration within the framework. Automation: one task  Orchestration: a collective of single tasks brought together to complete a larger task Seeing the concepts of automation and orchestration pop up again not only shows how they are used in practice and in slightly different contexts, but it also highlights how important they can be across the board. It is one thing to run a single automated task, but orchestrating those tasks can help keep operations more consistent and reliable.

There is so much to learn about cloud environments, more specifically the backend of it. As a consumer it’s pretty straight forward… upload your data to save on physical device storage space, or for accessing your files across different devices. However, the behind the scenes that organizations deal with has a little more too it. Throughout this current term, the more I learn the more I realize it requires similar management in comparison to on site infrastructure. For instance, typically it’s easier to scale a cloud environment in comparison to expanding physical infrastructure, as you don’t need to buy more hardware, or need extra physical space. But did you know that scaling issues can still be a problem? For instance, is you use auto scaling one of the issues you could run into is low performance if you have conflicting policies in place. From an organizational standpoint, using cloud environments doesn’t replace or decrease the oversight and management needed to keep everythin...

  Data back-ups are a simple concept, at least on the surface level. The average user probably uses the cloud as a quick way to back up some personal data, but what happens when that back up fails? While some may think of it as a ‘set it and forget it’ type thing, but in reality, it should be looked at as ‘what if?’. Especially when that data includes private or sensitive information. With that said, what if the data you stored in the cloud was compromised, corrupted, or even disappeared? Even when you use a cloud environment as a back-up, it should never be the only method, as anything can happen. As a best practice, and one of the things highlighted in my Cloud Computing & Governance class this week is the necessity of having multiple back-ups. Following the 3-2-1 rule. What does that mean? It means that a user should have 3 backups, the one that is being used in current time, and 2 on different storage types. For example, storing one on a USB and one on a disk. But, 1 of...

  We all know that security is crucial in today’s digital world; especially when we rely on it for just about everything. Phone numbers? You don’t need to look through a phonebook anymore. Banking? Most of it can be done on apps or online. Mostly it’s all about the convenience of having everything at the tips of our fingers. The problem with this… is security.   But now, we have even more to look out for…. Clouds. A lot of people or organizations store personal information or private data in a cloud environment. That is exactly why having a strong password is important. However, when it comes to organizations or working with sensitive data, one thing I found interesting this week is how password policies should exist. Not only to protect company data but personal data. Enforcing a policy that includes multiple different facets can be the difference in secure and not secure. A good policy should include rules regarding complexity (numbers, upper and lowercase letters, symbo...

 What is Micro-segmentation? I will tell you it’s not the same as network segmentation. Which in theory it sounds like it could be similar…. Right?! Or was it just me. My first thought was that it carried the same characteristics. Network segmentation is the process of breaking a network down into more manageable chunks but also adds a layer of security by isolating different sections of a network. It serves as a dual purpose This week, I learned that micro-segmentation takes it a step further and applies to the cloud. Rather than breaking down networks into sections, it takes security rules and applies them at a workload and application level. Essentially, it applies and takes the same security rules with your workload as it moves to different cloud environments. Does that make micro-segmentation a bodyguard that follows your workload?

  Let’s talk about IoT devices! This is more of a reflection of sorts, and what I consider the relationship of IoT and Cloud computing. I would describe IoT as a device that collects the data and the cloud is what processes/analyzes it. Interestingly, I briefly read an article from Network World ( https://www.networkworld.com/article/964415/how-will-the-cloud-be-able-to-handle-the-emergence-of-iot.html ). Now, I vaguely remember earlier in my college journey hearing about fog computing. I use the word ‘vaguely’ primarily because college students ingest a LOT of information. Or is it ‘you learn a little about a lot’ a more accurate representation? Anyway, that aside, the concept of IoT and the cloud stays the same. However, what   intrigued me was that fog computing is what sits between the two, and it processes an IoTs raw data in real time. Naturally, I questioned: does that mean IoT would longer need cloud computing? On the contrary, it’s still needed. The cloud still ...