Standard

Available (1835)

Showing 1777 - 1788 per page



Web Authentication: An API for accessing Public Key Credentials Level 1

This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to Relying Parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality.

Web Authentication: An API for accessing Public Key Credentials Level 2

This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to Relying Parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality

LTFS Bulk Transfer Version 1.0

The LTFS Bulk Transfer standard defines a method by which a set of files, directories and objects from a source system can be transferred to a destination system.  The bulk transfer of large quantities of data is well suited for LTFS due to the economic and environmental characteristics of tape. Building on top of the LTFS format, a standardized method for transferring data is defined that provides many advantages.

LTFS Bulk Transfer v1.0

Akoma Ntoso Version 1.0

The Akoma Ntoso standard distinguishes between concepts regarding the description and identification of legal documents, their content, and the context in which they areused.  Names are used to associate the document representations to concepts so that documents can be “read/understood” by a machine, thus allowing sophisticated services that are impossible to attain with documents containing only typographical information, such as documents created in word-processing applications.To make documents machine-readable, every part with a relevant meaning and role must have a “name” (or “tag”) that machines can read. The content is marked up as precisely as possible according to the legal analysis of the text. This requires precisely identifying the boundaries of the different text segments, providing an element name that best describes the text in each situation, and also providing a correct identifier to each labelled fragment.

Advanced Message Queueing Protocol (AMQP) v1.0

The OASIS AMQP TC advances a vendor-neutral and platform-agnostic protocol that offers organizations an easier, more secure approach to passing real-time data streams and business transactions. The goal of AMQP is to ensure information is safely and efficiently transported between applications, among organizations, across distributed cloud computing environments, and within mobile infrastructures. AMQP avoids proprietary technologies, offering the potential to lower the cost of enterprise middleware software integrations through open interoperability. By enabling a commoditized, multi-vendor ecosystem, AMQP seeks to create opportunities for transforming the way business is done in the Cloud and over the Internet.

KMIP Asymmetric Key Lifecycle Profile v1.0

The OASIS KMIP TC works to define a single, comprehensive protocol for communication between encryption systems and a broad range of new and legacy enterprise applications, including email, databases, and storage devices. By removing redundant, incompatible key management processes, KMIP will provide better data security while at the same time reducing expenditures on multiple products.

Cloud Computing - End-to-end fault and performance management framework of virtual network services in inter-cloud

This recommendation provides end-to-end fault and performance management framework of virtual network services (VNSs) in inter-cloud computing and relevant use cases. In particular, the aspects of faults detection and localization of affected area in inter-cloud environments is presented.

Y.e2efapm

KMIP Storage Array with Self-Encrypting Drives Profile v1.0

The OASIS KMIP TC works to define a single, comprehensive protocol for communication between encryption systems and a broad range of new and legacy enterprise applications, including email, databases, and storage devices. By removing redundant, incompatible key management processes, KMIP will provide better data security while at the same time reducing expenditures on multiple products.

KMIP Additional Message Encodings v1.0

The OASIS KMIP TC works to define a single, comprehensive protocol for communication between encryption systems and a broad range of new and legacy enterprise applications, including email, databases, and storage devices. By removing redundant, incompatible key management processes, KMIP will provide better data security while at the same time reducing expenditures on multiple products.

PKCS #11 Cryptographic Token Interface Base Specification Version 2.40

The OASIS PKCS 11 Technical Committee develops enhancements to improve the PKCS #11 standard for ease of use in code libraries, open source applications, wrappers, and enterprise/COTS products: implementation guidelines, usage tutorials, test scenarios and test suites, interoperability testing, coordination of functional testing, development of conformance profiles, and providing reference implementations.

PKCS #11 Cryptographic Token Interface Profiles Version 2.40

The OASIS PKCS 11 Technical Committee develops enhancements to improve the PKCS #11 standard for ease of use in code libraries, open source applications, wrappers, and enterprise/COTS products: implementation guidelines, usage tutorials, test scenarios and test suites, interoperability testing, coordination of functional testing, development of conformance profiles, and providing reference implementations.