Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

2/8/2012
02:41 PM
Commentary
Commentary
Commentary
50%
50%

I'm Sorry I Called Your Baby Ugly ... But It Is

Your product's user interface may not be as appealing as you might think -- and it might just be jeopardizing its adoption

I like to use technology that is intuitive, solves a problem, and is a "fit" for me. On the other hand, I also like technology that is aesthetically pleasing. Some vendors have managed to deliver on my requirements, which is why I own several Apple products, buy the same brand of suit, and rarely drink domestic beer. But when it comes to security products -- namely the user interface (UI) of security monitoring products -- I am often disappointed and left wanting.

I speak to numerous vendors across different product sectors on a daily basis, so sometimes my disappointment in their UIs squeaks past my gritted teeth. I do my best to provide constructive criticism based on what I hear from customers, friends, and similar vendors, but the receiving vendor often takes offense. I understand. I called its "baby" ugly. Unlike an ugly baby whose appearance is usually beyond the control of its parents, security UIs can be made better.

Why make a UI more aesthetically pleasing? Well, for one thing, if a user can form a connection with the product, then he'll likely learn it quicker. We, as humans, tend to gravitate toward things we like and distance ourselves from those we don’t. If a provided interface is off-putting, how do you think that might impact the user’s learning curve and subsequent adoption?

Another reason is that many security monitoring products have become indistinguishable. I often say that you could take any SIEM vendor’s product marketing materials, strip any mention of its company or product name, and customers would have an extremely hard time assigning the correct company name to the associated materials. Since security monitoring vendors have done little to differentiate themselves, choosing instead to battle for competitive parity, why not innovate the often touted "single pane of glass?" Perhaps it's time to change the way we force users to interact with products.

I mentioned in my previous blog post -- "Where's My 'Minority Report' Dashboard?" -- that ever since I first saw the movie Minority Report, I’ve been waiting on the edge of my seat for a SIEM vendor to emulate the UI employed by Tom Cruise to solve crimes. I’m not saying that a UI of this nature would make a SIEM product more technologically capable than its closest competitor, but it would almost certainly add a bit of shine and differentiation in a product sector that’s quickly approaching commoditization.

Revamping a UI is not only an expensive undertaking, what with customer requirements gathering, design, development, and testing cycles, but it may also be considered a distraction from a vendor’s technical road map. So how do we balance some "UI bodywork beautification" without drastically impacting other core deliverables? Nearly every security product vendor leverages computer and, sometimes, electrical or mechanical engineering students in a work placement or cooperative education capacity. Not only does this provide inexpensive labor for menial tasks within the organization, but it may also serve to entice the student to come back to the company upon graduation -- providing a semi-trained resource already indoctrinated in the company's culture and processes. What I have yet to see, however, is a company bringing in design students to help overhaul, or even iteratively update, its UI. Sure, you could likely go to Starbucks, throw a rock, and hit five people capable of redesigning your product’s UI, but why not use students who are hungry to prove themselves in the real world? I assure you that the cost savings would likely be dramatic.

A balance between utility and aesthetics can be found, but vendors need to take a step back from their babies and objectively ask the question, “Is my baby ugly?” They also need to ask their customers, partners, friends, family (especially school-aged children), and strangers they meet at airports or in elevators what they might do to improve the UI of their product. They might be surprised to learn that they do, in fact, have an ugly baby.

Andrew Hay is senior analyst with The 451 Group's Enterprise Security Practice and is an author of three network security books. Follow him on Twitter: http://twitter.com/andrewsmhay.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...