Your IT infrastructure is ready to make the big move—from on-premises to the public cloud. Or perhaps you’re already in the cloud, but it’s time for a change to a new platform provider.
Wouldn’t it be great if you could get an automatic alert every time something in your house or car broke, like when a spark plug or fuse failed, or when a light bulb went out? That way you could fix those problems before they caused you any trouble… If only. For most of us, the prospect of such a smart home is still a distant glimmer in the future, but for IT teams (and others) working in a modern enterprise, you can get automatic notifications when parts of your infrastructure fail, and you can fix those failures before they cause problems. How? With the IT swiss army knife/ticketing system known as ServiceNow.
In many jurisdictions, there is a legislative or accounting requirement to store data for a minimum of five years. Easier said than done. That’s why multiple data backups are necessary.
Scanning ports is very popular among cybercriminals. It’s often their first step of reconnaissance to discover services they can exploit and systems they can break into as they try to steal or destroy sensitive data. Two recent examples of major breaches illustrate just how handy port scanning is to threat actors:
In 2019, cloud computing hasn’t just hit the mainstream, it is the mainstream. In fact, some experts are predicting that upwards of 80% of enterprise workloads will live in the cloud by 2020.
If you are reading this, you are likely interested in or already utilize cloud solutions. Both Azure and AWS (Amazon Web Services) offer a variety of infrastructure as a service (IaaS), platform as a service (PaaS) and software as a service (SaaS) offerings. Selection between the two, with AWS the dominant market leader, is typically based on business requirements and online research or direct referrals (some of your contacts recommend a solution based on pricing, uptime or other). I could rehash vendor websites, favorable reviews, and other somewhat biased materials to prove the headline but, as always, I prefer to go my own route, bringing my own biases to the fore.
DevOps as a practice and philosophy includes the communication and teamwork between developers and IT operations. Traditionally, developers and operations are two very different teams who would point fingers when issues would arise with software. DevOps is an attempt to abolish this and has both teams work together. The business result of this is a more stable and reliable software to provide to customers.
Over the past week, news broke about a rogue device that had gone unnoticed on NASA’s Jet Propulsion Lab (JPL) IT network. The fact that a Raspberry Pi went unnoticed for almost 10 months is a clear signal of network management issues and lackluster security policies in place within NASA, and other government agencies for that matter.
When troubleshooting problems or investigating potential security breaches, the Windows event log is a great place to start. Windows provides an extensive list of various event logs grouped by a provider with a sometimes staggering number of events recorded within. With all of these events being recorded, it’s hard to figure out what’s going on. One way to search event logs across not one but hundreds of servers at once is with PowerShell.
As a previous sufferer of imposter syndrome, I understand what it’s like to feel like you’re living someone else’s remarkable life doing what someone else should be doing; but not me.