ETSI
ETSI
-
Technical committeeTypeAcronymETSI ES 202 382CommitteePublished year2005Description
To specify the method and a proforma for definition of Protection Profiles in ETSI standards. This is derived in part from the work defined in 33wgTD054 and is directly related to the actual protection profile to be developed by the STF identified in 33wgTD042.
-
Technical committeeTypeAcronymETSI ES 202 336-11 V1.1.1CommitteePublished year2014Description
The present document applies to Battery Systems with integral control and monitoring for telecommunication and datacom (ICT) equipment. It applies to battery system with a dedicated monitoring and control unit. The present document defines: - Monitored and controlled battery system architectures. - The minimum set of exchanged information required at the interface, described in "natural language" in text tables. - The XML files with tags and variables corresponding to the data in the tables of the annexes.
Technology -
Technical committeeTypeAcronymETSI EG 202 549CommitteePublished year2006Description
The present document gives guidance on the application of security countermeasures to service capabilities. It covers
the construction of services from service capabilities and how a security evaluation of a service capability should be
performed. The present document examines and gives guidance on the use of the Composition assurance class defined
by the Common Criteria working group in order to be able to answer the question: "if components A and B are
evaluated as having security ratings X and Y what is the security rating that can be assigned to the combination of A
and B?"
The present document builds on the guidance to the Common Criteria for Information Technology Security Evaluation
given in EG 202 387 [3] with a particular view to assessing the security of the NGN. In the NGN context, where
services are not explicitly defined but are made from combining service capabilities, the present document gives
guidance on the means to apply effective security to both service capabilities in isolation, and to service capabilities in
combination.
The guidance reviews the service capability model in clause 4 and examines the requirements for security arising from
the service capability requirements defined for NGN-R1 in clause 5. The analysed security requirements are presented
in the form of ISO/IEC 15408-2 [17] functional models. Clause 6 presents a review of the Common Criteria
Composition assurance class and describes its impact on the ETSI standardization process. Annex A reviews the use of
cryptographic techniques in the NGN.
A number of assumptions of the design of NGN for security analysis to take place are made on the NGN development
process. The assumption in the present document is that the NGN has been developed using top-down decomposition of
the specification, using techniques of planned validation of the specification, with careful recording of design decisions
and validation results. -
Technical committeeTypeAcronymETSI EG 202 387CommitteePublished year2005Description
The purpose of the document is to provide developers of security standards with a summary of the requirements of ISO/IEC-15408 in the context of standardization and to give guidance on how formal methods and other engineering techniques can be used to ensure that standards meet, as far as is possible, the requirements of ISO/IEC 15408 and do not prevent an implementation from achieving an appropriate EAL.
-
Technical committeeTypeAcronymCEN/CLC/ETSI TR 101 551CommitteePublished year2014Description
This Technical Report (TR) provides many of the technical underpinnings on which the interactive Toolkit content (linked to in this subsection of the G3ict Accessible Procurement Portal) is based. This TR was authored jointly by the agencies that produced the European Standard, namely the European Committee for Standardization (CEN), the European Committee for Electrotechnical Standardization.(CENELEC), and the European Telecommunications Standards Institute (ETSI).
This TR can be used as a linear read-through of similar guidance to that found in the Toolkit. This TR can also be used as a reference to the various clauses of the European Standard’s related directives, references, and subsections.
The interactive Toolkit should be consulted first. This TR can support the activities of procurement personnel who are already knowledgeable about the Standard, and who are already well versed in the concepts and resources contained in the Toolkit(s) and other resources available elsewhere in this G3ict Accessible Procurement Portal. -
Technical committeeTypeAcronymCEN/CLC/ETSI TR 101 550CommitteePublished year2014Description
The present document specifies the functional accessibility requirements applicable to ICT products and services, together with a description of the test procedures and evaluation methodology for each accessibility requirement in a form that is suitable for use in public procurement within Europe. The present document might be useful for other purposes such as procurement in the private sector. The present document is intended to be used as the basis for an accessible ICT procurement toolkit. The present document will primarily be useful for public procurers to identify the requirements for their purchases, and also for manufacturers to employ it within their design, build and quality control procedures. The present document contains the necessary functional requirements and provides a reference document such that if procedures are followed by different actors, the results of testing are similar and the interpretation of those results is clear. The test descriptions and evaluation methodology included in the present document are elaborated to a level of detail compliant with ISO/IEC 17007:2009 [i.14], so that conformance testing can give conclusive results. The inherent nature of certain situations makes it impossible to make reliable and definitive statements that accessibility requirements have been met. In those situations therefore, the requirements in the present document are not applicable: - when the product is in a failure, repair or maintenance state where the ordinary set of input or output functions are not available; - during those parts of start-up, shutdown, and other state transitions that can be completed without user interaction. NOTE 1: Even in the above situations, it is best practice to apply requirements in the present document wherever it is feasible and safe to do so. NOTE 2: Compliance issues are covered in normative clause C.1.
-
AcronymETSI TS 187 016CommitteePublished year2010Description
To provide countermeasure to assure that users of the NGN have protection from abuse of identity. This to cover Identity protection, authentication and integrity countermeasures and to define credential management. The document will extend from TR 187010 and will identify the functional objectives from ISO 15408-2 (particularly those in class Privacy and related to subject-user binding).
-
AcronymETSI TS 187 003CommitteePublished year2011Description
This work item aims to define a stage 2, NGN release 3 security architecture. This Work Item shall set forth the specific security architecture for NGN Release 3 using the Release 2 document as a baseline with additions to support the Release 3 functionality as described in the Release 3 definition.
-
AcronymETSI TS 187 001CommitteePublished year2014Description
This new work item aims to capture the NGN release 1 specific security objectives and requirements in a stage 1 type deliverable.
-
AcronymETSI TS 141 101CommitteePublished year2014Description
ETSI TS 141 101 / 3GPP TS 41.101; Overview of Technical Specifications and Technical Reports for a GERAN-based 3GPP system