iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
ISO

ISO/IEC 18045:2005

(Main)

Information technology — Security techniques — Methodology for IT security evaluation

Information technology — Security techniques — Methodology for IT security evaluation

ISO/IEC 18045:2005 is a companion document to ISO/IEC 15408, Information technology --Security techniques -- Evaluation criteria for IT security. ISO/IEC 18045 specifies the minimum actions to be performed by an evaluator in order to conduct an ISO/IEC 15408 evaluation, using the criteria and evaluation evidence defined in ISO/IEC 15408.

Technologies de l'information — Techniques de sécurité — Méthodologie pour l'évaluation de sécurité TI

General Information

Status
Withdrawn
Publication Date
06-Oct-2005
Withdrawal Date
06-Oct-2005
ICS
35.030 - IT Security
35.040 - Information coding
Technical Committee
ISO/IEC JTC 1/SC 27 - Information security, cybersecurity and privacy protection
Drafting Committee
ISO/IEC JTC 1/SC 27 - Information security, cybersecurity and privacy protection
Current Stage
9599 - Withdrawal of International Standard
Completion Date
19-Aug-2008
Ref Project

Relations

Revised
ISO/IEC 18045:2008 - Information technology — Security techniques — Methodology for IT security evaluation
Effective Date
15-Apr-2008

Buy Standard

ISO/IEC 18045:2005 - Information technology -- Security techniques -- Methodology for IT security evaluationISO/IEC 18045:2005 - Information technology -- Security techniques -- Methodology for IT security evaluation
PreviousNext
Standard
ISO/IEC 18045:2005 - Information technology -- Security techniques -- Methodology for IT security evaluation
English language
276 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 18045
First edition
2005-10-01

Information technology — Security
techniques — Methodology for IT security
evaluation
Technologies de l'information — Techniques de sécurité —
Méthodologie pour l'évaluation de sécurité TI




Reference number
ISO/IEC 18045:2005(E)
©
ISO/IEC 2005

---------------------- Page: 1 ----------------------
ISO/IEC 18045:2005(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.


©  ISO/IEC 2005
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2005 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 18045:2005(E)
Contents Page
Foreword .vii
Introduction .viii
1 Scope.1
2 Normative references.1
3 Terms and definitions.1
4 Symbols and abbreviated terms .3
5 Overview.3
5.1 Organisation of this International Standard .3
6 Document Conventions.3
6.1 Terminology.3
6.2 Verb usage.4
6.3 General evaluation guidance.4
6.4 Relationship between ISO/IEC 15408 and ISO/IEC 18045 structures.4
6.5 Evaluator verdicts.4
7 General evaluation tasks.5
7.1 Introduction.5
7.2 Evaluation input task.6
7.2.1 Objectives.6
7.2.2 Application notes.6
7.2.3 Management of evaluation evidence sub-task.7
7.3 Evaluation output task.7
7.3.1 Objectives.7
7.3.2 Application notes.8
7.3.3 Write OR sub-task.8
7.3.4 Write ETR sub-task.8
7.3.5 Evaluation sub-activities.13
8 Protection Profile evaluation.14
8.1 Introduction.14
8.2 PP evaluation relationships.14
8.3 Protection Profile evaluation activity.15
8.3.1 Evaluation of TOE description (APE_DES.1).15
8.3.2 Evaluation of Security environment (APE_ENV.1).16
8.3.3 Evaluation of PP introduction (APE_INT.1) .19
8.3.4 Evaluation of Security objectives (APE_OBJ.1).20
8.3.5 Evaluation of IT security requirements (APE_REQ.1) .23
8.3.6 Evaluation of Explicitly stated IT security requirements (APE_SRE.1).32
9 Security Target evaluation.35
9.1 Introduction.35
9.2 ST evaluation relationships.35
9.3 Security Target evaluation activity.36
9.3.1 Evaluation of TOE description (ASE_DES.1).36
9.3.2 Evaluation of Security environment (ASE_ENV.1).37
9.3.3 Evaluation of ST introduction (ASE_INT.1).40
9.3.4 Evaluation of Security objectives (ASE_OBJ.1).42
9.3.5 Evaluation of PP claims (ASE_PPC.1).45
9.3.6 Evaluation of IT security requirements (ASE_REQ.1) .46
9.3.7 Evaluation of Explicitly stated IT security requirements (ASE_SRE.1).56
© ISO/IEC 2005 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 18045:2005(E)
9.3.8 Evaluation of TOE summary specification (ASE_TSS.1). 58
10 EAL1 evaluation. 62
10.1 Introduction. 62
10.2 Objectives. 62
10.3 EAL1 evaluation relationships. 62
10.4 Configuration management activity. 63
10.4.1 Evaluation of CM capabilities (ACM_CAP.1). 63
10.5 Delivery and operation activity. 64
10.5.1 Evaluation of Installation, generation and start-up (ADO_IGS.1). 64
10.6 Development activity. 65
10.6.1 Application notes. 65
10.6.2 Evaluation of Functional specification (ADV_FSP.1). 66
10.6.3 Evaluation of Representation correspondence (ADV_RCR.1). 69
10.7 Guidance documents activity. 72
10.7.1 Application notes. 72
10.7.2 Evaluation of Administrator guidance (AGD_ADM.1). 72
10.7.3 Evaluation of User guidance (AGD_USR.1) . 75
10.8 Tests activity. 77
10.8.1 Application notes. 77
10.8.2 Evaluation of Independent testing (ATE_IND.1). 78
11 EAL2 evaluation. 81
11.1 Introduction. 81
11.2 Objectives. 82
11.3 EAL2 evaluation relationships. 82
11.4 Configuration management activity. 82
11.4.1 Evaluation of CM capabilities (ACM_CAP.2). 82
11.5 Delivery and operation activity. 85
11.5.1 Evaluation of Delivery (ADO_DEL.1). 85
11.5.2 Evaluation of Installation, generation and start-up (ADO_IGS.1). 86
11.6 Development activity. 87
11.6.1 Application notes. 87
11.6.2 Evaluation of Functional specification (ADV_FSP.1). 88
11.6.3 Evaluation of High-level design (ADV_HLD.1). 91
11.6.4 Evaluation of Representation correspondence (ADV_RCR.1). 94
11.7 Guidance documents activity. 97
11.7.1 Application notes. 97
11.7.2 Evaluation of Administrator guidance (AGD_ADM.1). 97
11.7.3 Evaluation of User guidance (AGD_USR.1) . 100
11.8 Tests activity. 102
11.8.1 Application notes. 102
11.8.2 Evaluation of Coverage (ATE_COV.1) . 103
11.8.3 Evaluation of Functional tests (ATE_FUN.1) . 104
11.8.4 Evaluation of Independent testing (ATE_IND.2). 108
11.9 Vulnerability assessment activity. 114
11.9.1 Evaluation of Strength of TOE security functions (AVA_SOF.1). 114
11.9.2 Evaluation of Vulnerability analysis (AVA_VLA.1). 116
12 EAL3 evaluation. 121
12.1 Introduction. 121
12.2 Objectives. 122
12.3 EAL3 evaluation relationships. 122
12.4 Configuration management activity. 122
12.4.1 Evaluation of CM capabilities (ACM_CAP.3). 122
12.4.2 Evaluation of CM scope (ACM_SCP.1) . 126
12.5 Delivery and operation activity. 127
12.5.1 Evaluation of Delivery (ADO_DEL.1). 127
12.5.2 Evaluation of Installation, generation and start-up (ADO_IGS.1). 128
12.6 Development activity. 129
12.6.1 Application notes. 130
iv © ISO/IEC 2005 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 18045:2005(E)
12.6.2 Evaluation of Functional specification (ADV_FSP.1) .130
12.6.3 Evaluation of High-level design (ADV_HLD.2) .134
12.6.4 Evaluation of Representation correspondence (ADV_RCR.1).138
12.7 Guidance documents activity .140
12.7.1 Application notes.140
12.7.2 Evaluation of Administrator guidance (AGD_ADM.1).140
12.7.3 Evaluation of User guidance (AGD_USR.1).143
12.8 Life cycle support activity.146
12.8.1 Evaluation of Development security (ALC_DVS.1) .146
12.9 Tests activity.148
12.9.1 Application notes.148
12.9.2 Evaluation of Coverage (ATE_COV.2).150
12.9.3 Evaluation of Depth (ATE_DPT.1).152
12.9.4 Evaluation of Functional tests (ATE_FUN.1) .154
12.9.5 Evaluation of Independent testing (ATE_IND.2).159
12.10 Vulnerability assessment activity.164
12.10.1 Evaluation of Misuse (AVA_MSU.1).164
12.10.2 Evaluation of Strength of TOE security functions (AVA_SOF.1) .167
12.10.3 Evaluation of Vulnerability analysis (AVA_VLA.1).169
13 EAL4 evaluation.174
13.1 Introduction.174
13.2 Objectives.175
13.3 EAL4 evaluation relationships.175
13.4 Configuration management activity.175
13.4.1 Evaluation of CM automation (ACM_AUT.1).175
13.4.2 Evaluation of CM capabilities (ACM_CAP.4) .177
13.4.3 Evaluation of CM scope (ACM_SCP.2).182
13.5 Delivery and operation activity .183
13.5.1 Evaluation of Delivery (ADO_DEL.2) .183
13.5.2 Evaluation of Installation, generation and start-up (ADO_IGS.1).185
13.6 Development activity.186
13.6.1 Application notes.186
13.6.2 Evaluation of Functional specification (ADV_FSP.2) .187
13.6.3 Evaluation of High-level design (ADV_HLD.2) .191
13.6.4 Evaluation of Implementation representation (ADV_IMP.1).195
13.6.5 Evaluation of Low-level design (ADV_LLD.1).197
13.6.6 Evaluation of Representation correspondence (ADV_RCR.1).200
13.6.7 Evaluation of Security policy modeling (ADV_SPM.1) .203
13.7 Guidance documents activity .206
13.7.1 Application notes.206
13.7.2 Evaluation of Administrator guidance (AGD_ADM.1).206
13.7.3 Evaluation of User guidance (AGD_USR.1).209
13.8 Life cycle support activity.211
13.8.1 Evaluation of Development security (ALC_DVS.1) .212
13.8.2 Evaluation of Life cycle definition (ALC_LCD.1).214
13.8.3 Evaluation of Tools and techniques (ALC_TAT.1).215
13.9 Tests activity.217
13.9.1 Application notes.217
13.9.2 Evaluation of Coverage (ATE_COV.2).218
13.9.3 Evaluation of Depth (ATE_DPT.1).220
13.9.4 Evaluation of Functional tests (ATE_FUN.1) .222
13.9.5 Evaluation of Independent testing (ATE_IND.2).227
13.10 Vulnerability assessment activity.232
13.10.1 Evaluation of Misuse (AVA_MSU.2).232
13.10.2 Evaluation of Strength of TOE security functions (AVA_SOF.1) .236
13.10.3 Evaluation of Vulnerability analysis (AVA_VLA.2).238
14 Flaw remediation sub-activities.250
14.1 Evaluation of flaw remediation (ALC_FLR.1).250
14.1.1 Objectives.250
© ISO/IEC 2005 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC 18045:2005(E)
14.1.2 Input. 250

14.1.3 Action ALC_FLR.1.1E. 250
14.2 Evaluation of flaw remediation (ALC_FLR.2). 252
14.2.1 Objectives. 252
14.2.2 Input. 252
14.2.3 Action ALC_FLR.2.1E. 252
14.3 Evaluation of flaw remediation (ALC_FLR.3). 255
14.3.1 Objectives. 255
14.3.2 Input. 255
14.3.3 Action ALC_FLR.3.1E. 255
Annex A (normative) General evaluation guidance. 260
A.1 Objectives. 260
A.2 Sampling. 260
A.3 Consistency analysis. 262
A.4 Dependencies. 264
A.4.1 Dependencies between activities. 264
A.4.2 Dependencies between sub-activities. 264
A.4.3 Dependencies between actions. 264
A.5 Site Visits. 264
A.6 TOE Boundary. 265
A.6.1 Product and system. 265
A.6.2 TOE. 266
A.6.3 TSF. 266
A.6.4 Evaluation. 266
A.6.5 Certification. 267
A.7 Threats and FPT Requirements. 267
A.7.1 TOEs not necessarily requiring the FPT class . 268
A.7.2 Impact upon Assurance Families. 268
A.8 St
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

This May Also Interest You

ISO
ISO/IEC 18032:2020(Main)
Information security — Prime number generation

This document specifies methods for generating and testing prime numbers as required in cryptographic protocols and algorithms. Firstly, this document specifies methods for testing whether a given number is prime. The testing methods included in this document are divided into two groups: — probabilistic primality tests, which have a small error probability. All probabilistic tests described here can declare a composite to be a prime; — deterministic methods, which are guaranteed to give the right verdict. These methods use so-called primality certificates. Secondly, this document specifies methods to generate prime numbers. Again, both probabilistic and deterministic methods are presented. NOTE It is possible that readers with a background in algorithm theory have already had previous encounters with probabilistic and deterministic algorithms. The deterministic methods in this document internally still make use of random bits (to be generated via methods described in ISO/IEC 18031), and "deterministic" only refers to the fact that the output is correct with probability one. Annex A provides error probabilities that are utilized by the Miller-Rabin primality test. Annex B describes variants of the methods for generating primes so that particular cryptographic requirements can be met. Annex C defines primitives utilized by the prime generation and verification methods.

  • Standard
    33 pages
    English language
    sale 15% off
  • Draft
    33 pages
    English language
    sale 15% off
ISO
ISO/IEC 24761:2019(Main)
Information technology — Security techniques — Authentication context for biometrics

This document defines the structure and the data elements of Authentication Context for Biometrics (ACBio), which is used for checking the validity of the result of a biometric enrolment and verification process executed at a remote site. This document allows any ACBio instance to accompany any biometric processes related to enrolment and verification. The specification of ACBio is applicable not only to single modal biometric enrolment and verification but also to multimodal fusion. The real-time information of presentation attack detection is not provided in this document. Only the assurance information of presentation attack detection (PAD) mechanism can be contained in the BPU report. Biometric identification is out of the scope of this document. This document specifies the cryptographic syntax of an ACBio instance. The cryptographic syntax of an ACBio instance is defined in this document applying a data structure specified in Cryptographic Message Syntax (CMS) schema whose concrete values can be represented using a compact binary encoding. This document does not define protocols to be used between entities such as BPUs, claimant, and validator. Its concern is entirely with the content and encoding of the ACBio instances for the various processing activities.

  • Standard
    75 pages
    English language
    sale 15% off
ISO
ISO/IEC 30111:2019(Main)
Information technology — Security techniques — Vulnerability handling processes

This document provides requirements and recommendations for how to process and remediate reported potential vulnerabilities in a product or service. This document is applicable to vendors involved in handling vulnerabilities.

  • Standard
    13 pages
    English language
    sale 15% off
  • Standard
    15 pages
    French language
    sale 15% off
ISO
ISO/IEC 9798-2:2019(Main)
IT Security techniques — Entity authentication — Part 2: Mechanisms using authenticated encryption

This document specifies entity authentication mechanisms using authenticated encryption algorithms. Four of the mechanisms provide entity authentication between two entities where no trusted third party is involved; two of these are mechanisms to unilaterally authenticate one entity to another, while the other two are mechanisms for mutual authentication of two entities. The remaining mechanisms require an on-line trusted third party for the establishment of a common secret key. They also realize mutual or unilateral entity authentication. Annex A defines Object Identifiers for the mechanisms specified in this document.

  • Standard
    15 pages
    English language
    sale 15% off
ISO
ISO/IEC 9798-3:2019(Main)
IT Security techniques — Entity authentication — Part 3: Mechanisms using digital signature techniques

This document specifies entity authentication mechanisms using digital signatures based on asymmetric techniques. A digital signature is used to verify the identity of an entity. Ten mechanisms are specified in this document. The first five mechanisms do not involve an on-line trusted third party and the last five make use of on-line trusted third parties. In both of these two categories, two mechanisms achieve unilateral authentication and the remaining three achieve mutual authentication. Annex A defines the object identifiers assigned to the entity authentication mechanisms specified in this document.

  • Standard
    25 pages
    English language
    sale 15% off
ISO
ISO/IEC TS 27008:2019(Main)
Information technology — Security techniques — Guidelines for the assessment of information security controls

This document provides guidance on reviewing and assessing the implementation and operation of information security controls, including the technical assessment of information system controls, in compliance with an organization's established information security requirements including technical compliance against assessment criteria based on the information security requirements established by the organization. This document offers guidance on how to review and assess information security controls being managed through an Information Security Management System specified by ISO/IEC 27001. It is applicable to all types and sizes of organizations, including public and private companies, government entities, and not-for-profit organizations conducting information security reviews and technical compliance checks.

  • Technical specification
    91 pages
    English language
    sale 15% off
ISO
ISO/IEC 10118-3:2018(Main)
IT Security techniques — Hash-functions — Part 3: Dedicated hash-functions

This document specifies dedicated hash-functions, i.e. specially designed hash-functions. The hash-functions in this document are based on the iterative use of a round-function. Distinct round-functions are specified, giving rise to distinct dedicated hash-functions. The use of Dedicated Hash-Functions 1, 2 and 3 in new digital signature implementations is deprecated. NOTE As a result of their short hash-code length and/or cryptanalytic results, Dedicated Hash-Functions 1, 2 and 3 do not provide a sufficient level of collision resistance for future digital signature applications and they are therefore, only usable for legacy applications. However, for applications where collision resistance is not required, such as in hash-functions as specified in ISO/IEC 9797‑2, or in key derivation functions specified in ISO/IEC 11770‑6, their use is not deprecated. Numerical examples for dedicated hash-functions specified in this document are given in Annex B as additional information. For information purposes, SHA-3 extendable-output functions are specified in Annex C.

  • Standard
    398 pages
    English language
    sale 15% off
ISO
ISO/IEC 29147:2018(Main)
Information technology — Security techniques — Vulnerability disclosure

This document provides requirements and recommendations to vendors on the disclosure of vulnerabilities in products and services. Vulnerability disclosure enables users to perform technical vulnerability management as specified in ISO/IEC 27002:2013, 12.6.1[1]. Vulnerability disclosure helps users protect their systems and data, prioritize defensive investments, and better assess risk. The goal of vulnerability disclosure is to reduce the risk associated with exploiting vulnerabilities. Coordinated vulnerability disclosure is especially important when multiple vendors are affected. This document provides: — guidelines on receiving reports about potential vulnerabilities; — guidelines on disclosing vulnerability remediation information; — terms and definitions that are specific to vulnerability disclosure; — an overview of vulnerability disclosure concepts; — techniques and policy considerations for vulnerability disclosure; — examples of techniques, policies (Annex A), and communications (Annex B). Other related activities that take place between receiving and disclosing vulnerability reports are described in ISO/IEC 30111. This document is applicable to vendors who choose to practice vulnerability disclosure to reduce risk to users of vendors' products and services.

  • Standard
    32 pages
    English language
    sale 15% off
  • Standard
    34 pages
    French language
    sale 15% off
ISO
ISO/IEC TS 19608:2018(Main)
Guidance for developing security and privacy functional requirements based on ISO/IEC 15408

This document provides guidance for: — selecting and specifying security functional requirements (SFRs) from ISO/IEC 15408-2 to protect Personally Identifiable Information (PII); — the procedure to define both privacy and security functional requirements in a coordinated manner; and — developing privacy functional requirements as extended components based on the privacy principles defined in ISO/IEC 29100 through the paradigm described in ISO/IEC 15408-2. The intended audience for this document are: — developers who implement products or systems that deal with PII and want to undergo a security evaluation of those products using ISO/IEC 15408. They will get guidance how to select security functional requirements for the Security Target of their product or system that map to the privacy principles defined in ISO/IEC 29100; — authors of Protection Profiles that address the protection of PII; and — evaluators that use ISO/IEC 15408 and ISO/IEC 18045 for a security evaluation. This document is intended to be fully consistent with ISO/IEC 15408; however, in the event of any inconsistency between this document and ISO/IEC 15408, the latter, as a normative standard, takes precedence.

  • Technical specification
    48 pages
    English language
    sale 15% off
ISO
ISO/IEC 27050-2:2018(Main)
Information technology — Electronic discovery — Part 2: Guidance for governance and management of electronic discovery

This document provides guidance for technical and non-technical personnel at senior management levels within an organization, including those with responsibility for compliance with statuary and regulatory requirements, and industry standards. It describes how such personnel can identify and take ownership of risks related to electronic discovery, set policy and achieve compliance with corresponding external and internal requirements. It also suggests how to produce such policies in a form which can inform process control. Furthermore, it provides guidance on how to implement and control electronic discovery in accordance with the policies.

  • Standard
    9 pages
    English language
    sale 15% off