Two major enterprise computing platforms are reaching their end of life this week. Tomorrow (January 14th), in fact. While this may seem like a last-minute blog entry, we know there are plenty of you out there still running Windows 7 on corporate desktops and Windows Server 2008 or 2008 R2 in your data centers.
Microsoft itself estimated that 60% of its Windows Server install base was still running 2008 back in August. Some of those instances may have been upgraded or migrated to cloud VMs, but we’re betting many of them remain. Unofficial estimates peg the number of Windows 7 machines worldwide at around 200 million.
Change can be hard, especially when your systems seem to be working properly and upgrading appears to be a complex and time-consuming endeavor. But operating systems that have reached End of Support open the door for vulnerabilities, bugs, and incompatibility with newer infrastructure. They also make it more difficult to deploy and support newer software that can improve employee efficiency and empower the business to drive revenue in new areas and to compete with others in the industry. With Windows 7 and Windows Server 2008 End of Support upon us, what are your options?
Beekeeper, our proprietary patching automation tool, can be integrated with Powershell scripts for customized patching validation and recovery options. Read on to learn how to insert mneuomics into your script to accomplish this as well as how to recover from failed patching when detected.
This past week Green House Data employees found an invitation to connect in their LinkedIn inboxes from one Coleman Anglin, who claimed to be a Marketing Specialist at the company (unsurprisingly, no one in the marketing department received this invitation).
Of course the humorous last name of “Anglin” belies the true nature of this connection: phishing. While our security team was swift to send out a notice not to connect to this individual, the attempt highlights a growing trend of phishing attacks reaching beyond e-mail to the social media realm.
But why bother posing as a fellow employee or a friend on social media? Several employees asked what the threat could be from this seemingly innocuous connection, even if it was made in bad faith.
As you dig into DevOps methodology, you’re likely to encounter the term “shift left” and the slightly less common “shift right.” What exactly are we shifting here?
The two terms are sides of the same coin. They refer to when you will test your application or piece of technology – is it during development or once your solution has already entered production? Of course, for true DevOps success, the answer is both! Continuous improvement involves testing at all phases of the application lifecycle.
Let’s take a closer look at the ideology behind “shift left” and its counterpart as well as how they affect the development cycle (which can also be applied beyond app development itself and used when designing and deploying most IT systems).
As we approach year-end and look forward to future tech trends, we also reflect on the lessons learned over the past year. In the information security realm, things seem to stay the same even as they change.
Pervasive and persistent threats that are hardly new to the scene have made their way past small fry to take down some of the biggest service providers around. In many ways, 2019 proved the most effective threat vectors remain the most difficult to protect against, with the crucial attack point coming in the form of people – the hardest thing to control for within your organization.
There are some newer threats to consider as well, of course. Hackers never sleep!
Here’s our lineup for the nastiest InfoSec baddies of 2019.