FIPS Standard

Software: the programs and data components within the cryptographic boundary, usually stored on erasable
media (e.g., disk), that can be dynamically written and modified during execution.
Split knowledge: a process by which a cryptographic key is split into multiple key components, individually
sharing no knowledge of the original key, that can be subsequently input into, or output from, a
cryptographic module by separate entities and combined to recreate the original cryptographic key.
Status information: information that is output from a cryptographic module for the purposes of indicating
certain operational characteristics or states of the module.
System software: the special software within the cryptographic boundary (e.g., operating system, compilers
or utility programs) designed for a specific computer system or family of computer systems to facilitate the
operation and maintenance of the computer system, and associated programs, and data.
Tamper detection: the automatic determination by a cryptographic module that an attempt has been made to
compromise the physical security of the module.
Tamper evidence: the external indication that an attempt has been made to compromise the physical
security of a cryptographic module. (The evidence of the tamper attempt should be observable by an
operator subsequent to the attempt.)
Tamper response: the automatic action taken by a cryptographic module when a tamper detection has
occurred (the minimum response action is the zeroization of plaintext keys and CSPs).
Target of Evaluation (TOE): an information technology product or system and associated administrator and
user guidance documentation that is the subject of an evaluation.
TEMPEST: a name referring to the investigation, study, and control of unintentional compromising
emanations from telecommunications and automated information systems equipment.
TOE Security Functions (TSF): used in the Common Criteria, a set of the TOE consisting of all hardware,
software, and firmware that must be relied upon for the correct enforcement of the TOE Security Policy.
TOE Security Policy (TSP): used in the Common Criteria, a set of rules that regulate how assets are
managed, protected, and distributed within a Target of Evaluation.
Trusted path: a means by which an operator and a TOE Security Function can communicate with the
necessary confidence to support the TOE Security Policy.
User: an individual or a process (subject) acting on behalf of the individual that accesses a cryptographic
module in order to obtain cryptographic services.
Validation authorities: NIST and CSE.
Zeroization: a method of erasing electronically stored data, cryptographic keys, and CSPs by altering or
deleting the contents of the data storage to prevent recovery of the data.
2.2 Acronyms
The following acronyms and abbreviations are used throughout this standard:
ANSI American National Standards Institute
API Application Program Interface
8