
I think it's a lost cause.
There's a mountain of paperwork on writing in clear language out there, e.g. [link|http://www.dot.gov/ost/ogc/plain.htm|DOT]. But people who write the rule book don't seem to care.
As a rough translation, I'd offer:
Application Information Security Assurance (ISA)
This service's mission is to identifiesy the sensitivity and criticalityimportance of an information resource and the corresponding security requirements in the Business Impact Assessment; design information security protection mechanisms, controls, and processes that will satisfy the requirements; ensure the appropriate protection mechanisms, controls, and processes are implemented and tested; manage the residual risk; and culminatesproduce with a certification (the technical analysis that establishes the extent to which an application meets specified security requirements), accreditation (the management analysis that determines, from a business standpoint, whether implemented security controls satisfy specified security requirements to a level that provides an acceptable level of risk); and approval to deploy the information resource.
But even that is a mish-mash. It's not clear whether ISA is a group of people that does something, or a software process or what.
Is it a paper document or on-line? If it's on-line, I'd suggest hyperlinking definitions of the various jargon (BIA, etc.). If it's not on-line, I'd use footnotes to define
certification, accreditation, etc.
But I'm not an editor, so take my comments with a bunch of salt. :-)
Good luck! I think you'll need it. Unfortunately. :-/
Cheers,
Scott.