BS ISO/IEC 10181-4:1997

1 Scope
2 Normative references
    2.1 Identical Recommendations/International
          Standards
    2.2 Paired Recommendations/International Standards
          equivalent in technical content
3 Definitions
    3.1 Basic Reference Model definitions
    3.2 Security Architecture definitions
    3.3 Security Frameworks Overview definitions
    3.4 Additional definitions
4 Abbreviations
5 General discussion of Non-repudiation
    5.1 Basic concepts of Non-repudiation
    5.2 Roles of a Trusted Third Party
    5.3 Phases of Non-repudiation
    5.4 Some forms of non-repudiation services
    5.5 Examples of OSI Non-repudiation evidence
6 Non-repudiation policies
7 Information and facilities
    7.1 Information
    7.2 Non-repudiation facilities
8 Non-repudiation mechanisms
    8.1 Non-repudiation using a TTP security token
          (secure envelope)
    8.2 Non-repudiation using security tokens and tamper-
          resistant modules
    8.3 Non-repudiation using a digital signature
    8.4 Non-repudiation using Time Stamping
    8.5 Non-repudiation using an in-line Trusted Third
          Party
    8.6 Non-repudiation using a Notary
    8.7 Threats to Non-repudiation
9 Interaction with other security services and mechanisms
    9.1 Authentication
    9.2 Access Control
    9.3 Confidentiality
    9.4 Integrity
    9.5 Audit
Annex A - Non-repudiation in OSI Basic Reference Model
Annex B - Non-repudiation Facilities Outline
Annex C - Non-repudiation in store and forward systems
Annex D - Recovery in a Non-repudiation service
Annex E - Interaction with the Directory
Annex F - Bibliography

Applies to security service in an Open System environment including Database, Distributed Applications, Open Distributed Processing and OSI. Defines means of provision of protection for systems and objects within systems, with interaction between systems. Does not address the methodology for construction of systems or mechanisms.

This Recommendation | International Standard addresses the application of security services in an Open Systems environment, where the term \'Open Systems\' is taken to include areas such as Database, Distributed Applications, Open Distributed Processing and OSI. The Security Frameworks are concerned with defining the means of providing protection for systems and objects within systems, and with the interactions between systems. The Security Frameworks are not concerned with the methodology for constructing systems or mechanisms. The Security Frameworks address both data elements and sequences of operations (but not protocol elements) which are used to obtain specific security services. These security services may apply to the communicating entities of systems as well as to data exchanged between systems, and to data managed by systems. This Recommendation | International Standard: defines the basic concepts of Non-repudiation; defines general Non-repudiation services; identifies possible mechanisms to provide the Non-repudiation services; identifies general management requirements for Non-repudiation services and mechanisms. As with other security services, Non-repudiation can only be provided within the context of a defined security policy for a particular application. The definitions of security policies are outside the scope of this Recommendation | International Standard. The scope of this Recommendation | International Standard does not include specification of details of the protocol exchanges which need to be performed in order to achieve Non-repudiation. This Recommendation | International Standard does not describe in detail the particular mechanisms that can be used to support the Non-repudiation services nor does it give details of the supporting security management services and protocols. Some of the procedures described in this framework achieve security by the application of cryptographic techniques. This framework is not dependent on the use of a particular cryptographic or other algorithm or on particular cryptographic techniques (i.e. symmetric or asymmetric) although certain classes of Non-repudiation mechanisms may depend on particular algorithm properties. Indeed it is likely, in practice, that a number of different algorithms will be used. Two entities wishing to use cryptographically-protected data must support the same cryptographic algorithm. [ | NOTE — Although ISO does not standardize cryptographic algorithms, it does standardize the procedures used to register them in ISO/IEC 9979.] A number of different types of standard can use this framework including: standards that incorporate the concept of Non-repudiation; standards that specify abstract services that include Non-repudiation; standards that specify uses of a Non-repudiation service; standards that specify the means of providing Non-repudiation within an open system architecture; and standards that specify Non-repudiation mechanisms. Such standards can use this framework as follows: standards of type 1), 2), 3), 4) or 5) can use the terminology of this framework; standards of type 2), 3), 4) or 5) can use the facilities defined in clause 7; and standards of type 5) can be based upon the classes of mechanism defined in clause 8.