Google recently joined Facebook, Apple, Amazon, LinkedIn, Twitter and HPE in recommending its North American employees work from home to help slow down the spread of Coronavirus COVID-19. Workers can communicate in real-time on message systems like Slack and videoconferencing like Zoom. However, with >200k tech workers now at home needing robust and secure connection to the internet for these high bandwidth collaboration tools, the virus is not the only thing these workers are slowing down.

A service desk is the nerve center for all activities related to IT service delivery. It’s at the forefront of all interactions an organization has with its requesters. Implementing a service desk involves processes, workflows, and domain knowledge. That’s why most people stick to a framework when setting up a service desk. Learn more about the most popular ITSM framework. A service desk comes with numerous challenges that can be overcome if you are aware of the best practices.

Simple Network Management Protocols, SNMP, refers to protocols family used to probe and control various network devices. It includes three protocol versions (v1, v2c, v3), all of those supported by IPHost Network Monitor. SNMP is a popular means of watching network devices of any kind (nowadays literally every device with an IP address can support SNMP); however, there are typical problems users can encounter when using SNMP-enabled devices in local or global network.

First things first, why would you want to collect logs from Palo Alto and send them to a Cloud SIEM? There are many reasons. At its core, having a centralized location with a consistent user experience for managing alerts, notifications, and information coming from the technologies securing your environment can provide value in a lot of ways. In this blog, we’ll discuss how to collect, parse, and analyze Palo Alto logs in Logz.io Cloud SIEM, and how it can help secure your cloud workloads.

Security monitoring is a constantly changing area; the threats can appear at any moment; when there are so called 0-day threats, there are quite few techniques available to efficiently prevent an unknown yet type of problem. However, there are typical behavior patterns that can be detected using well-known pieces of software and monitor types. Most techniques mentioned below are related to Unix-like systems; however, exactly the same approaches can be used for every operating system.

Network management is undoubtedly crucial as there is a constant need to pin-point as well as fix the issues quickly whether it’s on premise or on cloud. The more complex and distributed a network becomes, the more alarms or alerts the system generates. Just knowing that something has gone wrong in your network is not enough, you should know the details like why it happened, when it happened, where it started, and what triggered it.

Monitoring is typically viewed as informative service: when a problem arises, messages are being sent, to alert people in charge to detected problems. However, IPHost Network Monitor allows creating composite alerts, including several so-called simple actions (such as “send mail”, “display pop-up” and so on). These simple actions can be used to proactively react to certain failure conditions – not only to inform of them, but also take measures to handle the actual issues.

In a previous article, we examined service meshes in detail. Briefly, a service mesh takes care of network functionality for the applications running on your platform. As Kubernetes has matured as a technology, service meshes have become a hot topic, with various products being developed to solve the challenges associated with areas like traffic management, security, and observability. This article will compare three service meshes.

Service desk or IT teams are critical to organisations for ensuring business continuity and service delivery. Hence, it becomes important for IT organizations to use a slew of metrics to measure how efficient their service desk is. With the recent advancement in IT Service Management (ITSM), the reporting capabilities offer multiple KPI metrics that can be measured and monitored. So, with the increase in service desk metrics, it becomes even more difficult to zero down on which metrics to measure.

Security issues can be a challenge; preventing them via properly set up monitoring can save many resources. However, as network grows, the list of resources subject to monitoring may grow much faster. A typical situation is a data center: when new hosts (servers) are added, multiple monitors of the same type can be added (depending on server type: Web server, mail server and so on). In such a situation, it is required to reduce possible amount of monitors to as small number as possible.