ISO/IEC 2382-8:1998
Information technology – Vocabulary – Part 8: Security (Second Edition)
This HTML version of ISO/IEC 2382-8:1998 is based on an Estonian–English version of the document on Imprimaatur’s Web site. I’ve removed cross-referential links to terms – such as “data”, “resources” – defined in other ISO/IEC 2382 documents. I hope to restore these (in some form) in a future version.
Caveat lector!
- I do not have access to an official ISO copy, so I cannot attest to its accuracy. However, spot checking definitions cited in other documents suggests that it is a reliable version. Except… figure 1 is missing… at least for the moment.
- Imprimaatur’s version carries no copyright notice.
- You can get a print or an Adobe PDF version from ISO – but you’ll have to stump up 122 Swiss francs for this.
ISO/IEC 2382-8:1998
08.01 – General concepts
- 08.01.01 – computer security, COMPUSEC (abbreviation) /US/
- The protection of data and resources from accidental or malicious acts, usually by taking appropriate actions.
- NOTE – Those acts may be modification, destruction, access, disclosure, or acquisition, if not authorized.
- 08.01.02 – administrative security, procedural security
- Administrative measures for computer security.
- NOTE – These measures may be operational and accountability procedures, procedures of investigating breaches in security, and reviewing audit trails.
- 08.01.03 – communications security, COMSEC (abbreviation)
- Computer security applied to data communication.
- 08.01.04 – data security
- Computer security applied to data.
- 08.01.05 – security audit
- An independent review and examination of data processing system records and activities to test for adequacy of system controls, to ensure compliance with established security policy and operational procedures, to detect breaches in security, and to recommend any indicated changes in control, security policy, and procedures.
- 08.01.06 – security policy
- A plan or course of action adopted for providing computer security.
- 08.01.07 – data integrity
- The property of data whose accuracy and consistency are preserved regardless of changes made.
- 08.01.08 – file protection
- The implementation of appropriate administrative, technical, or physical means to guard against the unauthorized access to, modification of, or deletion of a filefile.
- 08.01.09 – confidentiality
- The property of data that indicates the extent to which these data have not been made available or disclosed to unauthorized individuals, processes, or other entities.
- 08.01.10 – accountability
- The property that ensures that the actions of an entity may be traced uniquely to that entity.
- 08.01.11 – authentication
- The act of verifying the claimed identity of an entity.
- 08.01.12 – message authentication
- Verification that a message was sent by the purported originator to the intended recipient and that the message was not changed in transit.
- 08.01.13 – authentication information
- Information used to establish the validity of the claimed identity of an entity.
- 08.01.14 – credentials
- Data that are transferred to establish the claimed identity of an entity.
- 08.01.15 – authentication exchange
- A mechanism intended to ensure the identity of an entity by means of an information exchange.
- 08.01.16 – authorization
- The granting of rights, which includes the granting of access based on access rights.
- 08.01.17 – availability (in computer security)
- The property of data or of resources being accessible and usable on demand by an authorized entity.
- 08.01.18 – certification (in computer security)
- Procedure by which a third party gives assurance that all or part of a data processing system conforms to security requirements.
- 08.01.19 – security clearance, clearance
- Permission granted to an individual to access data or information at or below a particular security level.
- 08.01.20 – security level
- The combination of a hierarchical security classification and a security category that represents the sensitivity of an object or the security clearance of an individual.
- 08.01.21 – closed-security environment
- An environment in which special attention is paid (in the form of authorizations, security clearances, configuration controls, etc.) to protect data and resources from accidental or malicious acts.
- 08.01.22 – open-security environment
- An environment in which protection of data and resources from accidental or malicious acts is achieved through normal operational procedures.
- 08.01.23 – privacy
- Freedom from intrusion into the private life or affairs of an individual, when that intrusion results from undue or illegal gathering and use of data about that individual.
- 08.01.24 – risk analysis, risk assessment
- A systematic method of identifying the assets of a data processing system, the threats to those assets, and the vulnerability of the system to those threats.
- 08.01.25 – risk acceptance
- A managerial decision to accept a certain degree of risk, usually for technical or cost reasons.
- 08.01.26 – sensitivity
- A measure of importance assigned to information by the information owner to denote its need for protection.
- 08.01.27 – system integrity
- The quality of a data processing system fulfilling its operational purpose while both preventing unauthorized users from making modifications to or use of resources and preventing authorized users from making improper modifications to or improper use of resources.
- 08.01.28 – threat analysis
- An examination of actions and events that might adversely affect a data processing system.
- 08.01.29 – trusted computer system
- A data processing system that provides sufficient computer security to allow for concurrent access to data by users with different access rights and to data with different security classification and security categories.
- 08.01.30 – subject (in computer security)
- An active entity that can access objects.
- Example: A process that involves execution of a program.
- NOTE – A subject may cause information to flow among objects or may change the state of the data processing system.
- 08.01.31 – object (in computer security)
- An entity to which access is controlled.
- Examples: A file, a program, an area of main storage; data collected and maintained about a person.
08.02 – Classification of information
- 08.02.01 – security classification
- The determination of which specific degree of protection against access the data or information requires, together with a designation of that degree of protection.
- Examples.“Top secret”, “secret”, “confidential”.
- 08.02.02 – sensitive information
- Information that, as determined by a competent authority, must be protected because its disclosure, modification, destruction, or loss will cause perceivable damage to someone or something.
- 08.02.03 – security category
- A nonhierarchical grouping of sensitive information used to control access to data more finely than with hierarchical security classification alone.
- 08.02.04 – compartmentalization
- A division of data into isolated blocks with separate security controls for the purpose of reducing risk.
- Example: The division of data relative to a major project into blocks corresponding to subprojects, each with its own security protection, in order to limit exposure of the overall project.
- 08.02.05 – multilevel device
- A functional unit that can simultaneously process data of two or more security levels without risking to compromise computer security.
- 08.02.06 – single-level device
- A functional unit that can only process data of a single security level at a particular time.
08.03 – Cryptographic techniques
- 08.03.01 – cryptography
- The discipline that embodies the principles, means, and methods for the transformation of data in order to hide their semantic content, prevent their unauthorized use, or prevent their undetected modification.
- 08.03.02 – encryption, encipherment
- The cryptographic transformation of data.
- NOTES – 1. The result of encryption is ciphertext. 2. The reverse process is called decryption. 3. See also public-key cryptography, symmetric cryptography, irreversible encryption.
- 08.03.03 – irreversible encryption, irreversible encipherment, one-way encryption
- Encryption that produces ciphertext from which the original data cannot be reproduced.
- NOTE – Irreversible encryption is useful in authentication. For example, a password might be irreversibly encrypted and the resulting ciphertext stored. A password presented later would be irreversibly encrypted identically and the two strings of ciphertext compared. If they are identical, the presented password is correct.
- 08.03.04 – decryption, decipherment
- The process of obtaining, from a ciphertext, the original corresponding data.
- NOTE – A ciphertext may be encrypted a second time, in which case a single decryption does not produce the original plaintext.
- 08.03.05 – cryptographic system, ciphersystem, cryptosystem
- The documents, devices, equipment, and associated techniques that are used together to provide a means of encryption or decryption.
- 08.03.06 – cryptanalysis
- The analysis of a cryptographic system, its inputs or outputs, or both, to derive sensitive information, such as plaintext.
- 08.03.07 – plaintext, cleartext
- Data, the semantic content of which is available without using cryptographic techniques.
- 08.03.08 – ciphertext
- Data produced through the use of encryption, the semantic content of which is not available without the use of cryptographic techniques.
- 08.03.09 – key (in computer security)
- A bit string that controls the operations of encryption or decryption.
- 08.03.10 – private key
- A key that is intended for decryption for the exclusive use by its owner.
- 08.03.11 – public key
- A key that is intended for use by any entity for encrypted communication with the owner of the corresponding private key.
- 08.03.12 – public-key cryptography, asymmetric cryptography
- Cryptography in which a public key and a corresponding private key are used for encryption and decryption.
- NOTE – If a public key is used for encryption, the corresponding private key must be used for decryption, and vice versa.
- 08.03.13 – symmetric cryptography
- Cryptography in which the same key is used for encryption and decryption.
- 08.03.14 – secret key
- A key that is intended for use by a limited number of correspondents for encryption and decryption.
- 08.03.15 – transposition
- Encryption that rearranges bits or characters according to some scheme.
- NOTE – The resulting ciphertext is called transposition cipher.
- 08.03.16 – substitution
- Encryption that replaces bit strings or character strings with other bit strings or character strings.
- NOTE – The resulting ciphertext is called substitution cipher.
08.04 – Access control
- 08.04.01 – access control
- A means of ensuring that the resources of a data processing system can be accessed only by authorized entities in authorized ways.
- 08.04.02 – access control list, access list
- A list of entities, together with their access rights, that are authorized to access a resource.
- 08.04.03 – access category
- A category to which entities may be assigned, based on the resources that the entity is authorized to use.
- 08.04.04 – access level
- The level of authority required from an entity to access a protected resource.
- Example: The authority to access information at a particular security level.
- 08.04.05 – access right
- Permission for a subject to access a particular object for a specific type of operation.
- Example: Permission for a process to read a file but not write to it.
- 08.04.06 – access permission
- All of a subject's access rights with respect to some object.
- 08.04.07 – access period
- A period of time during which specified access rights prevail.
- 08.04.08 – access type (in computer security)
- A type of operation specified by an access right.
- Examples: Read, write, execute, append, modify, delete, create.
- 08.04.09 – ticket (in computer security)
- A representation of one or more access rights that possessor has to an object.
- NOTE – The ticket represents an access permission.
- 08.04.10 – capability (in computer security)
- A representation of the identifications of an object, or of a class of objects, and of a set of authorized access types for these objects.
- NOTE – A capability can be implemented in the form of a ticket.
- 08.04.11 – capability list
- A list associated with a subject that identifies all of the subject's access types for all objects.
- Example: A list associated with a process that identifies all of its access types for all files and other protected resources.
- 08.04.12 – identity authentication, identity validation
- The performance of tests to enable a data processing system to recognize entities.
- Example: The checking of a password or of an identity token.
- 08.04.13 – identity token
- A device used for identity authentication.
- Examples: Smart card, metal key.
- 08.04.14 – password
- A character string that is used as authentication information.
- 08.04.15 – minimum privilege
- Restriction of the access rights of a subject to only those rights that are necessary for the execution of authorized tasks.
- 08.04.16 – need-to-know
- A legitimate requirement of a prospective recipient of data to know, to access, or to possess any sensitive information represented by these data.
- 08.04.17 – logical access control
- The use of mechanisms related to data or information to provide access control.
- Example: The use of a password.
- 08.04.18 – physical access control
- The use of physical mechanisms to provide access control.
- Example: Keeping a computer in a locked room.
- 08.04.19 – controlled access system, CAS (abbreviation)
- A means of automating physical access control.
- Examples: The use of magnetic striped badges, smart cards, biometric readers.
- 08.04.20 – read access
- An access right that gives permission to read data.
- 08.04.21 – write access
- An access right that gives permission to write data.
- NOTE – Write access may grant permission to append, modify, delete or create data.
- 08.04.22 – user ID, user identification
- A character string or pattern that is used by a data processing system to identify a user.
- 08.04.23 – user profile (1)
- A description of a user, typically used for access control.
- NOTE – A user profile may include data such as user ID, user name, password, access rights, and other attributes.
- 08.04.24 – user profile (2)
- A pattern of a user's activity that can be used to detect changes in the activity.
08.05 – Security violations
- 08.05.01 – computer abuse
- A willful or negligent unauthorized activity that affects the computer security of a data processing system.
- 08.05.02 – computer crime
- A crime committed with the aid of, or directly involving, a data processing system or computer network.
- NOTE – This a revised version of the definition in ISO/IEC 2382-1:1993.
- 08.05.03 – computer fraud
- A fraud committed with the aid of, or directly involving, a data processing system or computer network.
- 08.05.04 – threat
- A potential violation of computer security.
- NOTE – See figure 1. [Missing.]
- 08.05.05 – active threat
- A threat a deliberate unauthorized change to the state of a data processing system.
- Example: A threat that would result in modification of messages, insertion of spurious messages, masquerade, or denial of service.
- 08.05.06 – passive threat
- A threat of disclosure of information without changing the state of a data processing system.
- Example: A threat that would result in the recovery of sensitive information through the interception of data transmitted.
- 08.05.07 – flaw (in computer security), loophole
- An error of commission, an omission, or an oversight that allows protection mechanisms to be bypassed or disabled.
- 08.05.08 – vulnerability
- Any weakness or flaw in a data processing system.
- NOTES – 1. If a vulnerability corresponds to a threat, a risk exists. 2. See figure 1. [Missing.]
- 08.05.09 – risk
- The possibility that a particular threat will exploit a particular vulnerability of a data processing system.
- NOTE – See figure 1. [Missing.]
- 08.05.10 – denial of service
- The prevention of authorized access to resources or the delaying of time-critical operations.
- 08.05.11 – compromise
- A violation of computer security whereby programs or data may have been modified, destroyed, or made available to unauthorized entities.
- NOTE – See figure 1. [Missing.]
- 08.05.12 – loss
- A quantitative measure of harm or deprivation resulting from a compromise.
- NOTE – See figure 1. [Missing.]
- 08.05.13 – exposure
- The possibility that a particular attack will exploit a particular vulnerability of a data processing system.
- NOTE – See figure 1. [Missing.]
- 08.05.14 – compromising emanation
- Signals that are unintentionally emitted and that, if intercepted and analyzed, may reveal sensitive information being processed or transmitted.
- Examples: Acoustic emanation, electromagnetic emanation.
- 08.05.15 – disclosure
- A violation of computer security whereby data have been made available to unauthorized entities.
- 08.05.16 – penetration
- Unauthorized access to a data processing system.
- NOTE – See figure 1. [Missing.]
- 08.05.17 – breach
- The circumvention or disablement of some element of computer security, with or without detection, which could result in a penetration of the data processing system.
- NOTE – See figure 1. [Missing.]
- 08.05.18 – network weaving
- A penetration technique in which different communication networks are used to gain access to a data processing system to avoid detection and trace-back.
- 08.05.19 – attack
- An attempt to violate computer security.
- Examples: Malicious logic, wiretapping.
- NOTE – See figure 1. [Missing.]
- 08.05.20 – analytical attack, cryptanalytical attack
- An attempt to break a code or to find a key using analytical methods.
- Examples: A statistical analysis of patterns; a search for flaws in an encryption algorithm.
- NOTE – Contrast with exhaustive attack.
- 08.05.21 – ciphertext-only attack
- An analytical attack in which a cryptanalyst possesses only ciphertext.
- 08.05.22 – known-plaintext attack
- An analytical attack in which a cryptanalyst possesses a substantial quantity of corresponding plaintext and ciphertext.
- 08.05.23 – chosen-plaintext attack
- An analytical attack in which a cryptanalyst can submit an unlimited number of plaintext messages and examine the corresponding ciphertext.
- 08.05.24 – exhaustive attack, brute-force attack
- A trial-and-error attempt to violate computer security by trying possible values of passwords or keys.
- NOTE – Contrast with analytical attack.
- 08.05.25 – eavesdropping
- The unauthorized interception of information-bearing emanations.
- 08.05.26 – wiretapping
- Surreptitious access to a some part of a data circuit to obtain, modify, or insert data.
- 08.05.27 – active wiretapping
- Wiretapping with the purpose to modify or insert data.
- 08.05.28 – passive wiretapping
- Wiretapping limited to obtaining data.
- 08.05.29 – masquerade
- The pretence by an entity to be a different entity in order to gain unauthorized access.
- 08.05.30 – piggyback entry
- Unauthorized access to a data processing system via an authorized user's legitimate connection.
- 08.05.31 – (to) tailgate
- To gain unauthorized physical access by following an authorized person through a controlled door.
- 08.05.32 – (to) scavenge
- To search, without authorization, through residual data to acquire sensitive information.
- 08.05.33 – (to) spoof
- To take action intended to deceive a user, an observer (such as an eavesdropper) or a resource.
- 08.05.34 – aborted connection
- A disconnection that does not follow established procedures.
- NOTE – An aborted connection may enable other entities to gain unauthorized access.
- 08.05.35 – failure access
- An unauthorized and usually inadvertent access to data in a data processing system, resulting from a failure of hardware or software.
- 08.05.36 – between-the-lines entry
- Access obtained through active wiretapping by an unauthorized user to a momentarily inactive transmission channel connected to a legitimate user resource.
- 08.05.37 – trapdoor
- A hidden software or hardware mechanism, usually created for testing and troubleshooting, that may be used to circumvent computer security.
- 08.05.38 – maintenance hook
- A trapdoor in software that allows easy maintenance and development of additional features and that may allow entry into the program at unusual points or without the usual checks.
- 08.05.39 – aggregation
- Acquisition of sensitive information by collecting and correlating information of lesser sensitivity.
- 08.05.40 – linkage (in computer security), fusion
- The purposeful combination of data or information from one data processing system with data or information from another system to derive protected information.
- 08.05.41 – traffic analysis
- The inference of information from observation of traffic flow.
- Example: Analysis of presence, absence, amount, direction, and frequency of traffic.
- 08.05.42 – data corruption
- An accidental or intentional violation of data integrity.
- 08.05.43 – flooding
- Accidental or intentional insertion of a large volume of data resulting in denial of service.
- 08.05.44 – contamination
- The introduction of data of one security classification or security category into data of a lower security classification or different security category.
- 08.05.45 – covert channel
- A transmission channel that may be used to transfer data in a manner that violates security policy.
- 08.05.46 – malicious logic
- A program implemented in hardware, firmware, or software, and whose purpose is to perform some unauthorized or harmful action.
- Examples: A logic bomb, a Trojan horse, a virus, a worm.
- 08.05.47 – virus
- A program that propagates itself by modifying other programs to include a possibly changed copy of itself and that is executed when the infected program is invoked.
- NOTE – A virus often causes damage or annoyance and may be triggered by some event such as the occurrence of a predetermined date.
- 08.05.48 – worm
- A self-contained program that can propagate itself through data processing systems or computer networks.
- NOTE – Worms are often designed to use up available resources such as storage space or processing time.
- 08.05.49 – Trojan horse
- An apparently harmless program containing malicious logic that allows the unauthorized collection, falsification, or destruction of data.
- 08.05.50 – bacterium, chain letter
- A program that propagates itself by electronic mail to everyone in each recipient's distribution list.
- 08.05.51 – logic bomb
- Malicious logic that causes damage to a data processing system when triggered by some specific system condition.
- 08.05.52 – time bomb
- A logic bomb to be activated at a predetermined time.
08.06 – Protection of sensitive information
- 08.06.01 – verification
- Comparing an activity, a process, or product with the corresponding requirements or specifications.
- Example: Comparing of a specification with a security policy model or comparing object code with source code.
- 08.06.02 – data protection
- The implementation of administrative, technical, or physical measures to guard against the unauthorized access to data.
- NOTE – This is a revised version of the definition in ISO/IEC 2382-1:1993.
- 08.06.03 – countermeasure
- An action, device, procedure, technique, or other measure that is designed to minimize vulnerability.
- 08.06.04 – failsafe (in computer security)
- Pertaining to avoidance of compromise in the event of a failure.
- 08.06.05 – data validation
- A process used to determine if data are accurate, complete, or meet specified criteria.
- NOTE – Data validation may include format checks, completeness checks, check key tests, reasonableness checks, and limit checks.
- 08.06.06 – keystroke verification
- The determination of the accuracy of data entry by the re-entry of the same data through a keyboard.
- 08.06.07 – audit trail (in computer security)
- Data collected for the potential use in a security audit.
- 08.06.08 – privacy protection
- The measures taken to ensure privacy.
- NOTE – The measures include data protection and limitations on the gathering, combining and processing of data about individuals.
- 08.06.09 – digital signature
- Data appended to a message, that allow the recipient of the message to verify the source and integrity of the message.
- 08.06.10 – digital envelope
- Data appended to a message, that allow the intended recipient to verify the content of the message.
- 08.06.11 – biometric
- Pertaining to the use of specific attributes that reflect unique personal characteristics, such as a fingerprint, an eye blood-vessel print, or a voice print, to validate the identity of a person.
- 08.06.12 – call-back, dial-back
- A procedure in which a data processing system identifies a calling terminal, disconnects the call, and dials the calling terminal to authenticate the calling terminal.
- 08.06.13 – clearing (in computer security)
- Overwriting classified data on a data medium that has a particular security classification and security category, so that this data medium may be reused for writing at the same security classification and security category.
- 08.06.14 – sanitizing
- Removing sensitive information from a document to reduce its sensitivity.
- 08.06.15 – residual data
- Data left in a data medium after deletion of a file or a portion of a file.
- NOTE – Residual data remain recoverable until clearing of the data medium has taken place.
- 08.06.16 – separation of duties
- Dividing responsibility for sensitive information so that an individual acting alone can compromise the security of only a limited portion of a data processing system.
- 08.06.17 – entrapment
- The deliberate planting of apparent flaws in a data processing system for the purpose of detecting attempted penetrations or for confusing an intruder about which flaws to exploit.
- 08.06.18 – penetration testing
- Examining the functions of a data processing system to find a means of circumventing computer security.
- 08.06.19 – computer-system audit
- A examination of the procedures used in a data processing system to evaluate their effectiveness and correctness, and to recommend improvements.
- 08.06.20 – contingency procedure
- A procedure that is an alternative to the normal path of a process if an unusual but anticipated situation occurs.
- 08.06.21 – data authentication
- A process used to verify data integrity.
- Examples: Verification that data received are identical to data sent, verification that a program is not infected by a virus.
- NOTE – Not to be confused with authentication.
- 08.06.22 – message authentication code
- A bit string that is a function of both data (either plaintext or ciphertext) and a secret key, and that is attached to the data in order to allow data authentication.
- NOTE – The function used to generate the message authentication code is typically a one-way function.
- 08.06.23 – manipulation detection, modification detection
- A procedure that is used to detect whether data have been modified, either accidentally or intentionally.
- 08.06.24 – manipulation detection code, modification detection code, MDC (abbreviation)
- A bit string that is a function of data to which it is attached to allow manipulation detection.
- NOTES – 1. The resulting message (data plus MDC) may then be encrypted in order to achieve secrecy or data authentication. 2. The function used to generate the MDC must be public.
- 08.06.25 – repudiation
- The denial by one of the entities involved in a communication of having participated in all or part of the communication.
- NOTE – In the description of techniques and mechanisms the term“non-repudiation” is often used to mean that none of the entities involved in a communication can deny its participation in the communication.
- 08.06.26 – security filter
- A trusted computer system that enforces a security policy on the data that pass through the system.
- 08.06.27 – guard (in computer security)
- A functional unit that provides a security filter between two data processing systems operating at different security levels or between a user terminal and a database to filter out data that the user is not authorized to access.
- 08.06.28 – mutual suspicion
- The relationship between interacting entities in which neither entity relies upon the other entity to function correctly or securely with respect to some property.
- 08.06.29 – notarization
- The registration of data with a trusted third party that allows the later assurance of the accuracy of the data's characteristics such as content, origin, time, and delivery.
- 08.06.30 – traffic padding
- A countermeasure that generates spurious data in transmission media to make traffic analysis or decryption more difficult.
- 08.06.31 – virus signature
- A unique bit string that is common to each copy of a particular virus and that may be used by a scanning program to detect the presence of the virus.
- 08.06.32 – anti-virus program, vaccine program
- A program designed to detect viruses and possibly to suggest or take corrective action.
08.07 – Recovery of data
- 08.07.01 – data restoration
- The act of regenerating data that have been lost or contaminated.
- NOTE – Methods include copying data from archive, data reconstruction from source data, or data reconstitution from alternative sources.
- 08.07.02 – data reconstruction
- A method of data restoration by analyzing original sources.
- 08.07.03 – data reconstitution
- A method of data restoration by assembling data from components available in alternative sources.
- 08.07.04 – backup procedure
- A procedure to provide for data restoration in case of a failure or a disaster.
- Example: Making backup files.
- 08.07.05 – backup file
- A file made for possible later data restoration.
- Example: Copy of a file preserved at an alternate site.
- 08.07.06 – backward recovery
- The data reconstitution of an earlier version of data by using a later version and data recorded in a journal.
- 08.07.07 – forward recovery
- The data reconstitution of a later version of data by using an earlier version and data recorded in a journal.
- 08.07.08 – (to) archive
- To store backup files and any associated journals, usually for a given period of time.
- 08.07.09 – archive file
- A file set aside for later research or verification, for security, or for any other purpose.
- 08.07.10 – archived file
- A file for which an archive file exists.
- 08.07.11 – cold site, shell site
- A facility with at least the equipment necessary to support the installation and operation of an alternative data processing system.
- 08.07.12 – hot site
- A fully equipped computer center that provides an immediate alternative data processing capability.
- 08.07.13 – contingency plan, disaster recovery plan
- A plan for backup procedures, emergency response, and post-disaster recovery.
08.08 – Copy protection
- 08.08.01 – copy protection
- The use of special techniques to detect or prevent the unauthorized copying of data, software, or firmware.
- 08.08.02 – software piracy
- The unauthorized use, copying, or distribution of software products.
- NOTE – This is an revised version of the definition in ISO/IEC 2382-1:1993.
- 08.08.03 – padlocking
- The use of special techniques to protect data or software against unauthorized copying.
- 08.08.04 – bad sectoring
- A technique for copy protection in which bad sectors are intentionally written on a disk.
- 08.08.05 – checking code
- Machine instructions that read part of a disk to determine whether it is an unauthorized copy.
- 08.08.06 – extra sector
- A sector that is written on a track in excess of the standard number of sectors, as part of a method of copy protection.
- 08.08.07 – extra track
- A track that is written on a disk in excess of the standard number of tracks, as part of a method of copy protection.
- 08.08.08 – fake sector
- A sector consisting of a header but no data, used in large numbers on a disk to cause an unauthorized copying program to fail to copy the disk.
- 08.08.09 – offset track
- A track written at a nonstandard position on a disk, as part of a method of copy protection.
- 08.08.10 – sector alignment
- A technique for copy protection that determines whether a disk is an unauthorized copy by checking whether sectors are positioned properly from track to track.
- 08.08.11 – spiral track
- A track with a spiral shape on a disk, as part of a method of copy protection.
- 08.08.12 – supersector
- An oversized sector written on a disk, as part of a method of copy protection.
- 08.08.13 – weak bit
- A bit intentionally written on a disk with a weak magnetic field strength that may be interpreted as zero or one and that is written as part of a method of copy protection.
- 08.08.14 – wide track
- A set of two or more adjacent tracks on a disk onto which the same data are written, as part of a method of copy protection.
This HTML encoding and antnotations:
Last updated Friday 15 July 2005 – Copyleft & Creative Commons (cc) 2000–2005 Ant – Disclaimer
URL: http://homepage.mac.com/antallan/i2382p8.html
|
|
|
|
