Informationsteknik, kontorsutrustning

This document provides a standardized framework for specifying objective, repeatable and reproducible evaluation methods and evaluation activities.This document does not specify how to evaluate, adopt, or maintain evaluation methods and evaluation activities. These aspects are a matter for those originating the evaluation methods and evaluation activities in their particular area of interest.

This document defines the required structure and content of security functional components for the purpose of security evaluation. It includes a catalogue of functional components that meets the common security functionality requirements of many IT products.

This document provides packages of security assurance and security functional requirements that have been identified as useful in support of common usage by stakeholders.
EXAMPLE Examples of provided packages include the evaluation assurance levels (EAL) and the composed assurance packages (CAPs).
This document presents:
— evaluation assurance level (EAL) family of packages that specify pre-defined sets of security assurance components that may be referenced in PPs and STs and which specify appropriate security assurances to be provided during an evaluation of a target of evaluation (TOE);
— composition assurance (CAP) family of packages that specify sets of security assurance components used for specifying appropriate security assurances to be provided during an evaluation of composed TOEs;
— composite product (COMP) package that specifies a set of security assurance components used for specifying appropriate security assurances to be provided during an evaluation of a composite product TOEs;
— protection profile assurance (PPA) family of packages that specify sets of security assurance components used for specifying appropriate security assurances to be provided during a protection profile evaluation;
— security target assurance (STA) family of packages that specify sets of security assurance components used for specifying appropriate security assurances to be provided during a security target evaluation.
The users of this document can include consumers, developers, and evaluators of secure IT products.

This document establishes the general concepts and principles of IT security evaluation and specifies the general model of evaluation given by various parts of the standard which in its entirety is meant to be used as the basis for evaluation of security properties of IT products.
This document provides an overview of all parts of the ISO/IEC 15408 series. It describes the various parts of the ISO/IEC 15408 series; defines the terms and abbreviations to be used in all parts of the standard; establishes the core concept of a Target of Evaluation (TOE); describes the evaluation context and describes the audience to which the evaluation criteria is addressed. An introduction to the basic security concepts necessary for evaluation of IT products is given.
This document introduces:
— the key concepts of Protection Profiles (PP), PP-Modules, PP-Configurations, packages, Security Targets (ST), and conformance types;
— a description of the organization of security components throughout the model;
— the various operations by which the functional and assurance components given in ISO/IEC 15408-2 and ISO/IEC 15408-3 can be tailored through the use of permitted operations;
— general information about the evaluation methods given in ISO/IEC 18045;
— guidance for the application of ISO/IEC 15408-4 in order to develop evaluation methods (EM) and evaluation activities (EA) derived from ISO/IEC 18045;
— general information about the pre-defined Evaluation Assurance Levels (EALs) defined in ISO/IEC 15408-5;
— information in regard to the scope of evaluation schemes.

This document defines the assurance requirements of the ISO/IEC 15408 series. It includes the individual assurance components from which the evaluation assurance levels and other packages contained in ISO/IEC 15408-5 are composed, and the criteria for evaluation of Protection Profiles (PPs), PP-Configurations, PP-Modules, and Security Targets (STs).

1.1 Field of application
This document is applicable to a VSE and defines the terms common to the ISO/IEC 29110 series.
1.2 Target audience
This document is targeted both at the general audience wishing to understand the ISO/IEC 29110 series of documents, and more specifically, at users of the ISO/IEC 29110 series. It should be read first when initially exploring VSE profile documents. While there is no specific prerequisite to read this document, it will be helpful to the user in understanding the terms used in the other parts.

This International Standard provides a description of the primary services that have been internationally defined to promote consistency among implementations; implementations can provide any of these services in combination with any other services that are appropriate. This document
organizes ITS services by defining service groups, which are placed into one of several service domains.
Each service group contains one or more individual services, each of which is described.
This International Standard is intended for use by at least two groups of people involved in the ITS sector. The first group is those looking for ideas about the services that ITS implementations can provide and the second is those who are developing standards.
For the first group, this International Standard provides service descriptions that can act as the catalyst for more detailed descriptions. The level of detail can differ from one ITS implementation to another, depending on whether or not a national ITS architecture is involved, and whether this architecture
is based directly on services, or on groups of functions. The service descriptions in this standard are pitched at a high-level as too much detail can be prescriptive and reduces flexibility.
For standards developers, this International Standard is applicable to the working groups of ISO TC204 and other Technical Committees who are developing standards for the ITS sector. This International Standard is designed to provide information and explanation of services that can form the basis and reason for developing standards.
Due to its nature, this document is largely advisory and informative with minimal requirements. It is designed to assist the integration of services into a cohesive reference architecture, thereby promoting interoperability and the use of common data definitions. Specifically, services defined within the
service groups can be the basis for definition of 'use cases', 'user needs' or "user service requirements' depending on the methodology being used to develop the resultant ITS architecture functionality, along with definition of applicable data within data dictionaries, as well as applicable communications and data exchange standards.

I detta dokument:
— beskrivs det svenska adressystemet för belägenhetsadresser,
— anges krav och rekommendationer för den geografiska indelning som svenska kommuner utgår ifrån vid adressättning av platser,
— beskrivs hur en adress är uppbyggd och regler för adresskomponenter i belägenhetsadresser för gatuadresser, byadresser, gårdsadresser och metertalsadresser.
Detta dokument omfattar inte interna hänvisningar i en byggnad eller inom en anläggning

This document specifies the behavior of Web APIs that provide access to features in a dataset in a manner independent of the underlying data store. This standard defines discovery and query operations.
Discovery operations enable clients to interrogate the API, including the API definition and metadata about the feature collections provided by the API, to determine the capabilities of the API and retrieve information about available distributions of the dataset.
Query operations enable clients to retrieve features from the underlying data store based upon simple selection criteria, defined by the client.

This document specifies the behavior of Web APIs that provide access to features in a dataset in a manner independent of the underlying data store. This standard defines discovery and query operations.
Discovery operations enable clients to interrogate the API, including the API definition and metadata about the feature collections provided by the API, to determine the capabilities of the API and retrieve information about available distributions of the dataset.
Query operations enable clients to retrieve features from the underlying data store based upon simple selection criteria, defined by the client.

This document specifies the security characteristics for secure cryptographic devices (SCDs) based on the cryptographic processes defined in ISO 9564, ISO 16609, and ISO 11568.
This document:
— states the security characteristics concerning both the operational characteristics of SCDs and the management of such devices throughout all stages of their life cycle;
— provides guidance for methodologies to verify compliance with those requirements. This information is contained in Annex A.
Annex A provides an informative illustration of the concepts of security levels described in this document as being applicable to SCDs.
This document does not address issues arising from the denial of service of an SCD.
This document does not address software services that use Multi-Party Computation (MPC) to achieve some security objectives and relying on these, offer cryptographic services. These are sometimes called
‘soft’ or software HSMs in common language, which is misleading and is not correct according to this document, which defines an HSM as a physical device with the properties and security measures noted in this document.
NOTE ISO 13491-2 specifies checklists to be used to evaluate secure cryptographic devices (SCDs) incorporating cryptographic processes as specified in ISO 9564-1, ISO 9564-2, ISO 16609, ISO 11568 in the financial services environment. The checklists in ISO 13491-2 specify requirements for the security characteristics and management of specific types of SCD functionality and the environments into which SCDs may be deployed.

The ISO 15638 series (Parts 1 to 24) define the framework for online fleet management of regulated/ unregulated commercial freight vehicles utilizing data communication between in-vehicle systems and an application service provider via an on-board communication unit interfacing with road monitoring
infrastructure and roadside sensors. This document defines an unregulated service architecture framework for freight vehicle safety information provision architecture. This statement does not preclude the regulated service where jurisdiction requires such a function.
The objective of this document is to provide a freight vehicle safety information provision service function/application for non-enforcement applications [and sometimes for regulated application service (RAS)]. This is for the road transport safety management purposes of regulated commercial
freight vehicle movements.
This document intends to reinforce vehicle safety for non-enforcement and other purposes by providing safety advisory information of overhead clearance provisions to the freight vehicle drivers/operators transporting heavy goods on the freight vehicles.
This document defines the framework for remote vehicle safety information provision for nonenforcement and other management purpose applications conceptual operation.
This document is complementary to, and does not replace, any other documents in the ISO 15638 series.
This document is beneficial to vehicle safety management purpose entities, and it provides additional use cases for TARV service applications.
This document is specifically oriented towards the realization of safer road transport of freight vehicles by providing safety advisory information to the vehicle from the service provider. It utilizes the ISO 15638 series basic architecture framework defined in ISO 15638-21. The service provider provides users with safety information of overhead clearance for that vehicle and gives adequate safety advice messages, as necessary. The various V2X communication paths can be used according to the various use cases.

This document forms Part 1 of the 23793 series addressing the minimum requirements for minimal risk manoeuvres (MRM), which are the response of an ADS to perform automated fallback to reach a minimal risk condition (MRC).
This document contains the classification framework for all type of MRMs. The classification framework establishes the concept of MRM operation, classification of different MRM types, and basic principles of the decision-making process to decide which MRM type may be performed based on the situation.
This document also contains the minimum requirements of the control strategy and test procedures for the two simplest types: Straight Stop for type1 and In-lane Stop for type2.
The scope of the MRM described in this document covers minimum requirements for ADS performance during MRM action, from initiation to termination, which aims to achieve an MRC. MRM action-specific
safety requirements for robust system design, such as what is specified in ISO 26262[4] and ISO 21448,[5] are not within the scope of this standard.
The MRM described in this standard are intended to be used on light-duty vehicles equipped with Level 3-5 ADS.
The scope does not include methods for detecting ADS failures and the decision-making process to initiate an MRM. This is because there are numerous cases that can initiate MRMs, and there is no general agreement on classification of those cases in the industry.

This document provides guidance on aspects of the design of human-system interaction, including: conceptual design, user-system interaction design, user interface design, and navigation design for interactive systems.
This document applies to all design and development approaches and methodologies (including: human-centred design, object-oriented, waterfall, HFI (human factors integration), agile and rapid development).
This document refers to applicable international standards, where available, rather than duplicating  their content. It also provides guidance that is not available in other international standards.

This standard defines the identification, data, information services, application guidance aspects, and applicable requirements of AIDC technology for different items and their hierarchy in Industrial
Construction during their whole life-cycle. It:
— provides unique identification for items in Industrial construction.
— specifies the semantics and data syntax to be used.
— specifies the data carriers to be used on items of various categories, substitutes, and sizes.
— makes recommendations about the metadata of the items.
— specifies the application test method and parameters based on the large scale test and scientific sampling rules.
— define the information services protocol to be used as interface between business applications and the AIDC system.
— makes guidance for designers, workers, engineers, managers, end users and maintainers about the AIDC application in their daily work.

This document defines a set of core practices and concepts that have wide acceptance in organizations and industries using agile approaches. This document defines a set of core practices that are present in agile methodologies.
The practices and concepts defined in this document are applicable to a single agile team, as well as for multiple agile teams. These practices and concepts are applicable throughout the lifecycle of software systems, products and services.

This document specifies common security requirements for internet-connected radio equipment. This document provides technical specifications for radio equipment, which concerns electrical or electronic products that are capable to communicate over the internet, regardless of whether these products  communicate directly or via any other equipment.

Common security requirements for internet connected radio equipment that equipment enables the holder or user to transfer money, monetary value or virtual currency. This document provides technical specifications for radio equipment processing virtual money or monetary value, which apply to electrical or electronic products that are capable to communicate over the internet, regardless of whether these products communicate directly or via any other equipment.

Common security requirements for radio equipment processing personal data or traffic data or location  data being either internet connected radio equipment, radio equipment designed or intended exclusively  for childcare; toys and wearable radio equipment. The standard provides technical specifications for  radio equipment processing personal data, traffic data or location data, which concerns electrical or  electronic products that are capable to communicate over the internet, regardless of whether these products communicate directly or via any other equipment, childcare, toys or wearable radio equipment. 
The scope does not apply to 5G network equipment used by providers of public electronic communications networks and publicly available electronic communications services within the meaning  of in Directive (EU) 2018/1972 of the European Parliament and of the Council as defined in that Regulation.