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

5/24/2012
09:28 AM
50%
50%

Don't Be The Nerdiest Person In The Room

Technical language has its place, but overuse hampers compliance

In the interest of full disclosure, I am fluent in "nerd." I have an engineering degree and years of experience working on technical projects. I know the purpose of a processor reset pin, why "i" is the most common loop counter for software developers, and the purpose of a debounce function in a keyboard driver. Only recently did I give away my EPROM programmer.

In any specialized field, a corresponding technical language is almost always very important. It allows for greater precision, accuracy, and efficiency. We don't want our surgeon to ask for "that long, sharp, curved knife" when we're on the operating table. Surgery requires a number of highly specialized instruments, and accurate, efficient communication between a surgeon and his team is a matter of life and death.

Likewise, designing and managing secure and compliant data systems requires language and terminology a home PC user would never need. For your business, however, precise technical language is not only helpful, it can be a matter of life and death.

Technical documentation designed for other technical professionals must include such precise, technical language to ensure that the systems are secure and verifiable. Such technical documents are a required part of every compliance process.

It is important to recognize that even though highly technical documentation is critical for proper system operation and for passing compliance audits, this level of documentation alone is insufficient. The processes and procedures of people must also be documented and done so in a way that makes sense to the people performing these tasks.

Using jargon and complex technical terms may create important-looking documentation. Unfortunately, this type of documentation can not only be inappropriate for your nontechnical employees and end users, but also absolutely useless. If the documentation governing "people processes" is unusable by your people, then probably the correct people processes necessary for compliance are not happening.

For instance, which of these statements will a nontechnical employee mostly likely remember and follow daily:

1. "Duplication, replication, or any other reproduction of system data files to any media, device, or network by unauthorized employees or other individuals is strictly prohibited in all instances."

Or

2. "Staff should never copy system data."

Compliant systems include people operating in compliant ways. Highly technical language not only hinders nontechnical staff, but also increases the likelihood it will be ignored. Furthermore, nontechnical senior management who cannot understand certain documents cannot honestly vouch for them or help integrate them into a companywide compliant culture.

Excessive and ill-applied use of technical language is, at best, inappropriate and disrespectful. At worst, it is arrogant and dangerous.

Compliant systems need documentation and training that all applicable staff can understand and easily follow. Remember, there is no value in confusing or overly complicated language. The goal should always be to communicate in the most efficient manner that will help create successful and complaint business operations.

Glenn S. Phillips, the president of Forte' Incorporated, works with business leaders who want to leverage technology and understand risks within. He is the author of the book Nerd-to-English and you can find him on twitter at @NerdToEnglish.

Glenn works with business leaders who want to leverage technology and understand the often hidden risks awaiting them. The Founder and Sr. Consultant of Forte' Incorporated, Glenn and his team work with business leaders to support growth, increase profits, and address ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Browsers to Enforce Shorter Certificate Life Spans: What Businesses Should Know
Kelly Sheridan, Staff Editor, Dark Reading,  7/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17366
PUBLISHED: 2020-08-05
An issue was discovered in NLnet Labs Routinator 0.1.0 through 0.7.1. It allows remote attackers to bypass intended access restrictions or to cause a denial of service on dependent routing systems by strategically withholding RPKI Route Origin Authorisation ".roa" files or X509 Certificate...
CVE-2020-9036
PUBLISHED: 2020-08-05
Jeedom through 4.0.38 allows XSS.
CVE-2020-15127
PUBLISHED: 2020-08-05
In Contour ( Ingress controller for Kubernetes) before version 1.7.0, a bad actor can shut down all instances of Envoy, essentially killing the entire ingress data plane. GET requests to /shutdown on port 8090 of the Envoy pod initiate Envoy's shutdown procedure. The shutdown procedure includes flip...
CVE-2020-15132
PUBLISHED: 2020-08-05
In Sulu before versions 1.6.35, 2.0.10, and 2.1.1, when the "Forget password" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a `400` error code is returned, along with a error message saying that th...
CVE-2020-7298
PUBLISHED: 2020-08-05
Unexpected behavior violation in McAfee Total Protection (MTP) prior to 16.0.R26 allows local users to turn off real time scanning via a specially crafted object making a specific function call.