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: