EMA Research Blog: Navigating IT and Security Horizons

When people think of IT mobility, the images most immediately conjured regard smartphones and tablets. In truth, however the mobile device landscape could be considered broader than this. The basic definition of a mobile device is simply “any computing device designed principally for portability.” By that definition, laptops should clearly be included in that scope. However, some definitions state that a mobile device must be “handheld” indicating size is a factor without actually specifying how small a device must be to achieve that designation. Regardless of size limitations, those definitions still favor inclusion of laptops since many are available with a form facture that is smaller than some of the larger tablets. Therefore, the defining descriptor for a mobile device must fall to its portability, which also happens to be the key differentiator between a laptop and a desktop PC. Logically, therefor, a laptop is, in fact, a mobile device.

As a follow-up to my previous columns on change management, I’d like to step back a little and shine a light on an even broader landscape. Here I’ll touch briefly on process, dialog, and workflow as a triad that can help IT organizations move forward toward a more efficient and potentially more business-aligned way of [...]

Most network managers are still many years away from turning on Internet Protocol version 6 (IPv6) in their enterprise local area networks (LANs). Private non-routable IPv4 address ranges can happily exist behind a network address translation (NAT) gateway for the foreseeable future. However, things could change. At any time, someone above your pay grade might [...]

Many small and midsized IT organizations rely on a mix of freeware and open source software to manage their infrastructure. These free tools can be effective and economical choices for smaller networks. But how do you know when it’s time to upgrade to a commercial product? Scale is one of the first indicators that you [...]

You may not have noticed, but log analytics has become table stakes for network management toolsets. Last year, Enterprise Management Associates® (EMA™) surveyed network managers about the data sources that have become important to engineering and operations tasks. Log files consistently scored higher than anything else, including flow data, packet analysis, and SNMP metrics. Fifty-nine [...]

IT administrators love to write scripts – at least, the most talented ones do. Scripting provides a powerful platform to automate simple and repeatable tasks. However, like with most powerful tools, there is an overwhelming temptation for scripting to be overused. When faced with a project deadline, a high-pressure failure event, or even just the need to simplify day-to-day events, administrators can unintentionally create scripts that are so complex they actually put the business at risk. I must confess that during my 2 decades-long tenure as an IT administrator and engineer, I’ve written a lot of scripts…a LOT of scripts…and learned a lot of important lessons. Scripting was never intended to replace application programming. Its purpose is to provide a quick and easy resource for performing simple and repeatable tasks. It is not uncommon, however, for scripts to start simple but balloon over time into complex code that is virtually unintelligible even to its author.

In preparation for my new ‘Achieving Hi-Fidelity Security’ research project, I thought I would post a relevant blog I wrote for InformationSecurityBuzz.com.

Consumers of IT services want speed and dependability above all else. When they envision a new service, they want it built and deployed in record time. While there has always been time pressure, it has become more pressing with the consumerization of IT. Consumerization describes the emergence of IT in the consumer market which then spread to business and government organizations. Users carry their devices and expectations to the workplace and want the same instant gratification, self-service mobile access, and constant stream of new apps they experience in their personal use of technology. Combine this with business intelligence capabilities advancing big data and analytics, and you end up with digital transformation: using data, pervasive connectivity, and easy to use devices to change the way businesses interact with their customers and conduct their core activities. These trends have raised the bar on the expectations of IT to innovate as quickly as possible.

This is the third blog in my series on change management. In the first, I examined both the processes and the use cases associated with managing change. In the second, I looked at metrics, best practices, and pitfalls. In this third blog, I’ll look at how the technologies for service modeling, automation, visualization, and self-service [...]

There is a reason orchestras have a single conductor. Can you imagine the cacophony that would result if a horn section performed out of sync with a string section? Or if the percussions played a faster beat then the woodwinds?  But in IT management, it’s all too common for organizations to have separate automation platforms conducting individual software elements. In fact, this is often the cause of an increased IT complexity that results in degraded performance and reliability. For instance, SAP’s popular customer relationship management (CRM) software includes a built-in job scheduler – the Computing Center Management System (CCMS) – with some limited capabilities specifically designed to support its unique platform (such as to analyze and distribute client workloads). But this is an independent tool requiring administration and monitoring tasks separate from any other automated solutions. An average IT organization will need to manage dozens of similar management platforms, each with its own unique interface and operating parameters.