|
|
|
Cryptologic Management Philosophy Why the way that we manage cryptography affects our abstraction. by Roy D. Follendore III Copyright (c) 2006 by RDFollendoreIII March 16, 2006 Let us assume that the principle purpose of security is not secrecy. Therefore it is to be assumed that the principle purpose of cryptography is not secrecy. We shall assume that cryptologic functions can and should be used to improve the performance of communication and not just to restrict communications. Such logical aspects as randomizations, XOR and NOR, authentication techniques, and cryptologic algorithm processes are simply tricks in the security designers toolbox that are there to be used or not used with respect to the philosophical objectives. These tools constantly change and depending on the application become subroutines that are increasingly complex and abstract. The way that we choose to abstract the problem of cryptography in designing systems is a real modern problem that we must face. A typical technical expert who spends his/her day coding could easily spend a career on a single aspect of cryptography but would not be able to explain how his techniques should be deployed. There is evidence that organizations have not been interested in the design and development of the potential benefits of security as much as it has been interested in the power that goes into exploiting the authority of security. From a scientific perspective, the patterns in which we choose to design and deploy these techniques may be regarded in terms of a forensic problem. (By choosing to do this, we expect that… or by ignoring this, we do not consider that important.) In this way it becomes possible to build up a self understanding of what we have and have not been objectively been willing to deal with within our security philosophy. Cryptography is in itself a symbolic abstraction for it is in this self analysis that we need to pay particular attention to the True reasons why these systems that exist. Self realization is the starting point. To be designers of cryptographic security systems we must first consider ourselves as communications analysts. Installing cryptography without regard to the performance objectives of communications is the same as randomly closing down access to satellite telecommunications in order to improve the bit error rate. Why does this happen? Consider the implications of the various ways that we can abstract the applications of cryptography. The bias that is put on each of these directly affects the qualities and capabilities of the resulting cryptologic design.
The essence of sociology, uniqueness, levels, independence, modeling, reasoning, logic, rationality, mathematics, events and convergence are all part of the process of cryptologic abstraction. Cryptographic abstraction is ultimately a process of reductionism but the problem is that reductionistic engineering management can not manage reductionistic cryptologic design. Each of these definitions represents remarkably different aspects of thinking and they each imply the potential of different resulting problems in their outcomes. Once again, within the explicit technical design is therefore important to understand the ‘intellectual chemistry’ of the cryptologic design process. A random group of security cryptologic designers who walk into a room to produce a security product change the way in which decisions are made. |
|
Copyright (c) 2001-2007 RDFollendoreIII All Rights Reserved
|