Coronavirus (COVID-19) is greatly impacting the lives of organizations, employees and stakeholders. With the outbreak’s rising impact, more employees are migrating to remote, work-from-home practices as means of achieving “social distancing.” However, inevitable challenges are emerging with remote workdays. Obstacles include, but aren’t limited to, employee isolation, diminished productivity and poor team communication or collaboration.
SOLID is one of the most popular sets of design principles in object-oriented software development. All of them are broadly used and worth knowing. But in this first post of my series about the SOLID principles, I will focus on the first one: the Single Responsibility Principle.
Choosing the right OpenStack distribution is essential to the success of an OpenStack project at every organisation. When selecting one, organisations should always follow certain criteria. Is it possible to operate the considered OpenStack distributions economically? How easy is it to deploy them? Can the organisation upgrade its production OpenStack cloud without affecting the workloads? Everyone planning to deploy OpenStack should ask themselves these questions.
FIPS 140-2 is a set of publicly announced cryptographic standards developed by the National Institute of Standards and Technology. It is an essential part of FEDRamp requirements for many governmental agencies in the US and Canada, as well as their business partners from all around the world. Furthermore, as a well established and verified security standard, an increasing number of large companies and financial institutions are asking for FIPS compliance.
The Robot Operating System (ROS) is a popular open-source platform for advanced robotics. Its flexibility and ease-of-use make it well-suited to a wide array of robotics applications – however, these robots are not always sufficiently protected against security threats. Opportunistic attacks are by far the most prevalent, and robots with inadequate ROS security make tempting targets for bad actors.
There are things in life that one can expect to become outdated. Most clothes, some cars, and there have certainly been a lot of hairstyles that have lost their luster over time. ServiceNow has added a new trend to that list – the controller’s checklist. Using one to keep track of the thousands of tasks that needed to be completed each month as part of the financial close process must go the way of the mullet, and here’s why.
Welcome to the new world, my friends. Now that working from home is our new reality, we've found that many of our customers are taking a much closer look at the technology that binds us all together and allows us to access corporate resources: the humble VPN. In the spirit of enablement, I’ve put together a quick list of dashboards that can help add that extra bit of visibility for our faithful Splunk Enterprise Security customers.
For those of us already using Microsoft Teams, the benefits couldn’t be clearer: Microsoft Teams provides everyone with one place to chat, meet, call, and collaborate, no matter where you are. IT professionals who support modern workplace tools like Office 365, and remote meeting platforms like Zoom and WebEx, can greatly benefit from connecting critical applications like Exoprise, directly into the Teams Channels they are already using.
When monitoring highly distributed applications, which might rely on hundreds of services and infrastructure components across multiple cloud-based and on-premise environments, identifying problems and pinpointing the origin of an issue can be challenging. Even if you already have robust monitoring and alerts, your infrastructure and applications will likely change over time, which may make it difficult to reliably detect irregular behavior.
