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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...