EN ISO/IEC 18045:2026

• Abstract:

  This document specifies requirements and the minimum actions performed by an evaluator in order to conduct an evaluation using the criteria and evaluation evidence defined in the ISO/IEC 15408 series evaluation.

• Status: Published
• Publication Date: 26-May-2026
• ICS: 35.030 - IT Security
• Technical Committee: CEN/CLC/TC 13 - Cybersecurity and Data Protection
• Current Stage: 6060 - Definitive text made available (DAV) - Publishing
• Start Date: 27-May-2026
• Completion Date: 27-May-2026
• Ref Project: SIST EN ISO/IEC 18045:2026 - Information security, cybersecurity and privacy protection - Evaluation criteria for IT security - Requirements and methodology for IT security evaluation (ISO/IEC 18045:2026)

• Replaces: EN ISO/IEC 18045:2023 - Information security, cybersecurity and privacy protection - Evaluation criteria for IT security - Methodology for IT security evaluation (ISO/IEC 18045:2022)
• Effective Date: 17-Apr-2024
• Consolidated By: ISO/IEC 18045:2026 - Information security, cybersecurity and privacy protection — Evaluation criteria for IT security — Requirements and methodology for IT security evaluation
• Effective Date: 12-Feb-2026

EN ISO/IEC 18045:2026 is a CEN European Standard that adopts ISO/IEC 18045:2026 without modification. It specifies the requirements and minimum actions an evaluator performs when conducting information security evaluations using the criteria and evaluation evidence defined in the ISO/IEC 15408 series. It is used for Protection Profile (PP), PP-Configuration, Security Target (ST), and related TOE evaluations in information security, cybersecurity and privacy protection.

What does EN ISO/IEC 18045:2026 specify?

EN ISO/IEC 18045:2026 specifies the evaluator methodology for IT security evaluation. Its scope is the work an evaluator must perform, not the security functionality of the product itself.

The standard is organized around a common evaluation process and then separate clauses for PP evaluation, PP-Configuration evaluation, ST evaluation, development, testing, vulnerability assessment, and composition-related evaluation work. Clause 7 maps the evaluation methodology structure to the assurance structures in the ISO/IEC 15408 series, and Clause 8 introduces the shared process and evaluator tasks.

General guidance that applies across many activities is collected in Annex A. The document also refers the reader to Annexes B, C and D of ISO/IEC 15408-1:2026 for concepts and examples used alongside PP and ST evaluation.

What are the key requirements of EN ISO/IEC 18045:2026?

Common evaluation process, evidence, and reporting

EN ISO/IEC 18045:2026 requires every evaluation to follow the same core process: an input task, an output task, the evaluation sub-activities, and demonstration of technical competence for the evaluation authority task. In practice, this means an evaluator does not just inspect documents - the evaluator must manage evidence, produce traceable outputs, and support a defensible verdict.

Clause 8 states that the input and output tasks are about management of evaluation evidence and report generation, and that they do not have verdicts attached to them. The evaluator must record and handle evaluation evidence with configuration control, disposal, and confidentiality in mind. That matters because the evaluation result depends on the evidence trail, not only on the final report.

The output task includes writing an observation report (OR) and an evaluation technical report (ETR). The ETR is the technical justification of the verdicts, so it is the main record a certification or validation body can review.

The standard also says that evaluation activities from ISO/IEC 15408-4:2026 may be used instead of the work units defined here, provided that this is made clear in the output reports. That gives schemes some flexibility, but it also means the report must show exactly what method was used.

PP and PP-Configuration evaluation

Clause 9 covers Protection Profile (PP) evaluation. A PP evaluation uses the same requirements and methodology regardless of the assurance level claimed in the PP. The evaluator checks the PP introduction, conformance claims, security problem definition, security objectives, extended components definition, and security requirements. In practice, this is the review that shows whether the PP is coherent and usable as a basis for later evaluation work.

Clause 10 covers PP-Configuration evaluation. This part depends on already evaluated PPs and on the PP-Modules built on them. The methodology requires the evaluator to follow the dependency structure from PPs to PP-Modules, and to check that each PP-Module Base is a closed set and includes at least one PP.

When a PP-Module allows alternative PP-Module Bases, the evaluator checks that the base identification describes the dependency structure correctly and that the PP-Module introduction contains as many TOE overviews as there are alternative bases. The TOE overview must summarize the usage and major security features, identify the TOE type, identify non-TOE hardware, software or firmware, and describe differences from the PP-Module Base(s). In practice, this keeps a modular PP from becoming ambiguous when it is reused in different configurations.

ST evaluation and later TOE-related work

Clause 11 covers Security Target (ST) evaluation. The ST evaluation should start before TOE evaluation sub-activities, because the ST gives the context for the rest of the evaluation. The evaluator reviews the ST introduction, conformance claims, security problem definition, security objectives, extended components definition, security requirements, TOE summary specification, and the consistency of a composite product Security Target.

This matters because the ST is the central statement of what the TOE claims to do and how it is supposed to be evaluated. If the ST is not internally consistent, later TOE evaluation work cannot rest on a stable basis.

Clause 12 covers development evaluation. It requires assessment of the design documentation to see whether it is adequate to understand how the TSF meets the SFRs and how those SFRs cannot be tampered with or bypassed. The document lists several kinds of design documentation, including the functional specification, TOE design description, implementation description, security architecture description, internal description, and security policy model. That helps evaluators trace security claims down to the design evidence they are based on.

Later clauses cover testing, vulnerability assessment, and composition-related activities, including ATE_* work units, AVA_* work units, and ACO_* work units. These sections guide the evaluator through checking expected behaviour, testing coverage, analysing vulnerabilities, and handling composite products.

What terms does EN ISO/IEC 18045:2026 define?

• Evaluation authority - the entity that runs and maintains a scheme, monitors the evaluator, and issues certification or validation reports and certificates based on the evaluation results.
• Evaluation evidence - the item or items used as the basis for an evaluation verdict; in practice, this is the documentation and other material the evaluator relies on.
• Evaluation technical report (ETR) - the report that presents the technical justification for the evaluation verdicts.
• Observation report (OR) - a report written by the evaluator to request clarification or to identify a problem during evaluation.
• Sub-activity - the application of an assurance component from ISO/IEC 15408-3:2026; it is the unit of work the methodology breaks assurance into.
• Task - methodology-specific evaluation work that is required but not derived directly from an ISO/IEC 15408 series requirement.
• Verdict - the evaluator’s statement about an evaluator action element, assurance component, or class.
• Work unit - the most granular level of evaluation work in the document.

Who uses EN ISO/IEC 18045:2026?

EN ISO/IEC 18045:2026 is used by security evaluation laboratories, evaluators, evaluation authorities, certification and validation bodies, and scheme operators. It is also used by developers and suppliers of PPs, PP-Configurations, STs, and TOEs who need their evaluation evidence organized in the form the evaluator expects.

In practice, the standard supports tasks such as reviewing security claims, checking dependency structures, assessing design documentation, managing evidence, writing ORs and ETRs, and judging whether a product, profile, or configuration is ready for a verdict. It is relevant across information technology products and systems where formal security evaluation is part of procurement, assurance, or certification.

What changed in EN ISO/IEC 18045:2026 from the previous edition?

EN ISO/IEC 18045:2026 supersedes EN ISO/IEC 18045:2023. The Slovene adoption notice also identifies SIST EN ISO/IEC 18045:2024 as replaced.

Which standards are used with EN ISO/IEC 18045:2026?

• ISO/IEC 15408-1:2026 - provides the introduction and general model, and the annexes used with PP and ST evaluation concepts.
• ISO/IEC 15408-2:2026 - provides the security functional components used in security requirement evaluation.
• ISO/IEC 15408-3:2026 - provides the security assurance components that this methodology applies to through sub-activities and work units.
• ISO/IEC 15408-4:2026 - provides the framework for specifying evaluation methods and activities; EN ISO/IEC 18045:2026 allows those activities to be used when clearly identified in reports.
• ISO/IEC 15408-5:2026 - provides pre-defined packages of security requirements that may be relevant to evaluation claims.
• ISO/IEC/IEEE 24765:2017 - provides general systems and software engineering vocabulary used for terms and definitions.

What does the EN ISO/IEC 18045:2026 document contain?

The document contains a common evaluation process, role and responsibility notes, evidence-handling guidance, and the rules for evaluator verdicts and reporting. It then gives class-by-class evaluation work for PP, PP-Configuration, ST, development, testing, vulnerability assessment, and composition.

It includes structured work units and tasks, with objectives, inputs, actions, and application notes where needed. Figure 1 maps the assurance constructs to the methodology structure, and Figure 7 shows the dependency structure between PPs and PP-Modules in a PP-Configuration.

The document also contains the material needed to write an OR and an ETR, plus guidance on re-using results of certified PPs and on composition. Annex A collects guidance that applies widely across activities, while the clause references to ISO/IEC 15408-1 annexes provide supporting concepts and examples for PP and ST evaluations.

SLOVENSKI STANDARD
01-oktober-2026
Nadomešča:
SIST EN ISO/IEC 18045:2024
Informacijska varnost, kibernetska varnost in varstvo zasebnosti - Merila za
ocenjevanje varnosti IT - Zahteve in metodologija za ocenjevanje varnosti IT
(ISO/IEC 18045:2026)
Information security, cybersecurity and privacy protection - Evaluation criteria for IT
security - Requirements and methodology for IT security evaluation (ISO/IEC
18045:2026)
Informationssicherheit, Cybersicherheit und Schutz der Privatsphäre -
Evaluationskriterien für IT-Sicherheit - Methodik für die Bewertung der IT-Sicherheit
(ISO/IEC 18045:2026)
Sécurité de l'information, cybersécurité et protection de la vie privée - Critères
d'évaluation pour la sécurité des technologies de l'information - Exigences et
méthodologie pour l'évaluation de sécurité (ISO/IEC 18045:2026)
Ta slovenski standard je istoveten z: EN ISO/IEC 18045:2026
ICS:
35.030 Informacijska varnost IT Security
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN ISO/IEC 18045

NORME EUROPÉENNE
EUROPÄISCHE NORM
May 2026
ICS 35.030
Supersedes EN ISO/IEC 18045:2023
English version
Information security, cybersecurity and privacy protection
- Evaluation criteria for IT security - Requirements and
methodology for IT security evaluation (ISO/IEC
18045:2026)
Sécurité de l'information, cybersécurité et protection Informationssicherheit, Cybersicherheit und Schutz
de la vie privée - Critères d'évaluation pour la sécurité der Privatsphäre - Evaluationskriterien für IT-
des technologies de l'information - Exigences et Sicherheit - Methodik für die Bewertung der IT-
méthodologie pour l'évaluation de sécurité (ISO/IEC Sicherheit (ISO/IEC 18045:2026)
18045:2026)
This European Standard was approved by CEN on 3 March 2026.

CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for
giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical
references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to
any CEN and CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN and CENELEC member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.

CEN and CENELEC members are the national standards bodies and national electrotechnical committees of Austria, Belgium,
Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy,
Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia,
Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and United Kingdom.

CEN-CENELEC Management Centre:
Rue de la Science 23, B-1040 Brussels
© 2026 CEN/CENELEC All rights of exploitation in any form and by any means Ref. No. EN ISO/IEC 18045:2026 E
reserved worldwide for CEN national Members and for
CENELEC Members.
Contents Page
European foreword . 3

European foreword
This document (EN ISO/IEC 18045:2026) has been prepared by Technical Committee ISO/IEC JTC 1
"Information technology" in collaboration with Technical Committee CEN-CENELEC/ JTC 13
“Cybersecurity and Data Protection” the secretariat of which is held by DIN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by November 2026, and conflicting national standards
shall be withdrawn at the latest by November 2026.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN-CENELEC shall not be held responsible for identifying any or all such patent rights.
This document supersedes EN ISO/IEC 18045:2023.
Any feedback and questions on this document should be directed to the users’ national standards
body/national committee. A complete listing of these bodies can be found on the CEN and CENELEC
websites.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and the
United Kingdom.
Endorsement notice
The text of ISO/IEC 18045:2026 has been approved by CEN-CENELEC as EN ISO/IEC 18045:2026
without any modification.
International
Standard
ISO/IEC 18045
Fourth edition
Information security, cybersecurity
2026-05
and privacy protection —
Evaluation criteria for IT security —
Requirements and methodology for
IT security evaluation
Sécurité de l'information, cybersécurité et protection de la vie
privée — Critères d'évaluation pour la sécurité des technologies
de l'information — Exigences et méthodologie pour l'évaluation
de sécurité
Reference number
ISO/IEC 18045:2026(en) © ISO/IEC 2026

ISO/IEC 18045:2026(en)
© ISO/IEC 2026
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2026 – All rights reserved
ii
ISO/IEC 18045:2026(en)
Contents Page
Foreword .viii
Introduction .ix
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Terminology . . 4
5 Verb usage . 5
6 General evaluation guidance . 5
7 Relationship between structures within the CC and the structure of this document . 5
8 Evaluation process and related tasks . 6
8.1 General .6
8.2 Evaluation process overview . .6
8.2.1 Objectives .6
8.2.2 Responsibilities of the roles .6
8.2.3 Relationship of roles .7
8.2.4 General evaluation model .7
8.2.5 Evaluator verdicts .8
8.3 Evaluation input task .9
8.3.1 Objectives .9
8.3.2 Application notes .9
8.3.3 Management of evaluation evidence task .10
8.4 Evaluation sub-activities .11
8.5 Evaluation output task .11
8.5.1 Objectives .11
8.5.2 Management of evaluation outputs .11
8.5.3 Application notes .11
8.5.4 Write OR task .11
8.5.5 Write ETR task . 12
9 Protection Profile (PP) evaluation . 19
9.1 Introduction .19
9.2 Application notes .19
9.2.1 Re-using the evaluation results of certified PPs .19
9.3 PP introduction (APE_INT) . 20
9.3.1 Evaluation of sub-activity (APE_INT.1) . 20
9.4 Conformance claims (APE_CCL) .21
9.4.1 Evaluation of sub-activity (APE_CCL.1) .21
9.5 Security problem definition (APE_SPD) .32
9.5.1 Evaluation of sub-activity (APE_SPD.1) .32
9.6 Security objectives (APE_OBJ) . 33
9.6.1 Evaluation of sub-activity (APE_OBJ.1) . 33
9.6.2 Evaluation of sub-activity (APE_OBJ.2) . 35
9.7 Extended components definition (APE_ECD) .37
9.7.1 Evaluation of sub-activity (APE_ECD.1) .37
9.8 Security requirements (APE_REQ) .41
9.8.1 Evaluation of sub-activity (APE_REQ.1) .41
9.8.2 Evaluation of sub-activity (APE_REQ.2).47
10 Protection Profile Configuration evaluation . 51
10.1 Introduction .51
10.2 PP-Module introduction (ACE_INT) .52
10.2.1 Evaluation of sub-activity (ACE_INT.1) .52
10.3 PP-Module conformance claims (ACE_CCL) . 55

© ISO/IEC 2026 – All rights reserved
iii
ISO/IEC 18045:2026(en)
10.3.1 Evaluation of sub-activity (ACE_CCL.1) . 55
10.4 PP-Module security problem definition (ACE_SPD) .61
10.4.1 Evaluation of sub-activity (ACE_SPD.1) .61
10.5 PP-Module security objectives (ACE_OBJ) .62
10.5.1 Evaluation of sub-activity (ACE_OBJ.1) .62
10.5.2 Evaluation of sub-activity (ACE_OBJ.2) . 64
10.6 PP-Module extended components definition (ACE_ECD). 66
10.6.1 Evaluation of sub-activity (ACE_ECD.1) . 66
10.7 PP-Module security requirements (ACE_REQ) .70
10.7.1 Evaluation of sub-activity (ACE_REQ.1) .70
10.7.2 Evaluation of sub-activity (ACE_REQ.2) .76
10.8 PP-Module consistency (ACE_MCO) . 81
10.8.1 Evaluation of sub-activity (ACE_MCO.1) . 81
10.9 PP-Configuration consistency (ACE_CCO) . 84
10.9.1 Evaluation of sub-activity (ACE_CCO.1) . 84
11 Security Target (ST) evaluation .93
11.1 Introduction . 93
11.2 Application notes . 93
11.2.1 Re-using the evaluation results of certified PPs . 93
11.2.2 Composition . 94
11.3 ST introduction (ASE_INT) . 94
11.3.1 Evaluation of sub-activity (ASE_INT.1) . 94
11.4 Conformance claims (ASE_CCL) . 98
11.4.1 Evaluation of sub-activity (ASE_CCL.1) . 98
11.5 Security problem definition (ASE_SPD) . 112
11.5.1 Evaluation of sub-activity (ASE_SPD.1) . 112
11.6 Security objectives (ASE_OBJ) . 113
11.6.1 Evaluation of sub-activity (ASE_OBJ.1) . 113
11.6.2 Evaluation of sub-activity (ASE_OBJ.2) . 115
11.7 Extended components definition (ASE_ECD) .117
11.7.1 Evaluation of sub-activity (ASE_ECD.1) .117
11.8 Security requirements (ASE_REQ). 121
11.8.1 Evaluation of sub-activity (ASE_REQ.1) . 121
11.8.2 Evaluation of sub-activity (ASE_REQ.2) .128
11.9 TOE summary specification (ASE_TSS) .134
11.9.1 Evaluation of sub-activity (ASE_TSS.1) .134
11.9.2 Evaluation of sub-activity (ASE_TSS.2) . 135
11.10 Consistency of composite product Security Target (ASE_COMP) . 136
11.10.1 Evaluation of sub-activity (ASE_COMP.1) . 136
12 Development .141
12.1 Introduction .141
12.2 Application notes .141
12.2.1 General .141
12.2.2 Composition .142
12.3 Security architecture (ADV_ARC) .142
12.3.1 Evaluation of sub-activity (ADV_ARC.1) .142
12.4 Functional specification (ADV_FSP) .147
12.4.1 Evaluation of sub-activity (ADV_FSP.1) .147
12.4.2 Evaluation of sub-activity (ADV_FSP.2) . 150
12.4.3 Evaluation of sub-activity (ADV_FSP.3) . 155
12.4.4 Evaluation of sub-activity (ADV_FSP.4) . 160
12.4.5 Evaluation of sub-activity (ADV_FSP.5) . 166
12.5 Implementation representation (ADV_IMP) . 172
12.5.1 Evaluation of sub-activity (ADV_IMP.1) . 172
12.5.2 Evaluation of sub-activity (ADV_IMP.2) .174
12.6 TSF internals (ADV_INT) . 177
12.6.1 Evaluation of sub-activity (ADV_INT.1) . 177
12.6.2 Evaluation of sub-activity (ADV_INT.2) . 180

© ISO/IEC 2026 – All rights reserved
iv
ISO/IEC 18045:2026(en)
12.6.3 Evaluation of sub-activity (ADV_INT.3) . 182
12.7 Formal TSF model (ADV_SPM). 185
12.7.1 Evaluation of sub-activity (ADV_SPM.1) . 185
12.8 TOE design (ADV_TDS) .191
12.8.1 Evaluation of sub-activity (ADV_TDS.1) .191
12.8.2 Evaluation of sub-activity (ADV_TDS.2) . 195
12.8.3 Evaluation of sub-activity (ADV_TDS.3) .200
12.8.4 Evaluation of sub-activity (ADV_TDS.4).209
12.8.5 Evaluation of sub-activity (ADV_TDS.5) .219
12.9 Composite design compliance (ADV_COMP) . 227
12.9.1 Evaluation of sub-activity (ADV_COMP.1) . 227
13 Guidance documents .229
13.1 Introduction . 229
13.2 Application notes . 229
13.3 Operational user guidance (AGD_OPE) . 230
13.3.1 Evaluation of sub-activity (AGD_OPE.1) . 230
13.4 Preparative procedures (AGD_PRE) . 233
13.4.1 Evaluation of sub-activity (AGD_PRE.1) . 233
14 life cycle support .235
14.1 Introduction . 235
14.2 Application notes . 235
14.2.1 Composition . 235
14.3 CM capabilities (ALC_CMC) . 236
14.3.1 Evaluation of sub-activity (ALC_CMC.1). 236
14.3.2 Evaluation of sub-activity (ALC_CMC.2) . 237
14.3.3 Evaluation of sub-activity (ALC_CMC.3) . 239
14.3.4 Evaluation of sub-activity (ALC_CMC.4) . 243
14.3.5 Evaluation of sub-activity (ALC_CMC.5) .248
14.4 CM scope (ALC_CMS) . 256
14.4.1 Evaluation of sub-activity (ALC_CMS.1) . 256
14.4.2 Evaluation of sub-activity (ALC_CMS.2) . 257
14.4.3 Evaluation of sub-activity (ALC_CMS.3) . 258
14.4.4 Evaluation of sub-activity (ALC_CMS.4) . 259
14.4.5 Evaluation of sub-activity (ALC_CMS.5) .260
14.5 Delivery (ALC_DEL) . 262
14.5.1 Evaluation of sub-activity (ALC_DEL.1) . 262
14.6 Developer environment security (ALC_DVS) . 263
14.6.1 Evaluation of sub-activity (ALC_DVS.1) .263
14.6.2 Evaluation of sub-activity (ALC_DVS.2) . 265
14.7 Flaw remediation (ALC_FLR) .268
14.7.1 Evaluation of sub-activity (ALC_FLR.1) .268
14.7.2 Evaluation of sub-activity (ALC_FLR.2) . 271
14.7.3 Evaluation of sub-activity (ALC_FLR.3) .274
14.8 Development life cycle definition (ALC_LCD) .280
14.8.1 Evaluation of sub-activity (ALC_LCD.1) .280
14.8.2 Evaluation of sub-activity (ALC_LCD.2) . 281
14.9 TOE development artefacts (ALC_TDA) .284
14.9.1 Evaluation of sub-activity (ALC_TDA.1) .284
14.9.2 Evaluation of sub-activity (ALC_TDA.2) .287
14.9.3 Evaluation of sub-activity (ALC_TDA.3) . 291
14.10 Tools and techniques (ALC_TAT) . 296
14.10.1 Evaluation of sub-activity (ALC_TAT.1).296
14.10.2 Evaluation of sub-activity (ALC_TAT.2) .298
14.10.3 Evaluation of sub-activity (ALC_TAT.3) . 301
14.11 Integration of composition parts and consistency check of delivery procedures (ALC_
COMP) .304
14.11.1 Evaluation of sub-activity (ALC_COMP.1) .304

© ISO/IEC 2026 – All rights reserved
v
ISO/IEC 18045:2026(en)
15 Tests . 306
15.1 Introduction . 306
15.2 Application notes . 307
15.2.1 General . 307
15.2.2 Understanding the expected behaviour of the TOE . 307
15.2.3 Testing vs. alternate approaches to verify the expected behaviour of
functionality . 307
15.2.4 Verifying the adequacy of tests .308
15.2.5 Composition .308
15.3 Coverage (ATE_COV) .309
15.3.1 Evaluation of sub-activity (ATE_COV.1) .309
15.3.2 Evaluation of sub-activity (ATE_COV.2) .309
15.3.3 Evaluation of sub-activity (ATE_COV.3) . 311
15.4 Depth (ATE_DPT) . 313
15.4.1 Evaluation of sub-activity (ATE_DPT.1) . . 313
15.4.2 Evaluation of sub-activity (ATE_DPT.2) . 315
15.4.3 Evaluation of sub-activity (ATE_DPT.3) . 318
15.5 Functional tests (ATE_FUN) . 321
15.5.1 Evaluation of sub-activity (ATE_FUN.1) . 321
15.5.2 Evaluation of sub-activity (ATE_FUN.2) . 324
15.6 Independent testing (ATE_IND) . 328
15.6.1 Evaluation of sub-activity (ATE_IND.1) . 328
15.6.2 Evaluation of sub-activity (ATE_IND.2) . 331
15.7 Composite functional testing (ATE_COMP) . 336
15.7.1 Evaluation of sub-activity (ATE_COMP.1) . 336
16 Vulnerability assessment .338
16.1 Introduction . 338
16.2 Application notes . 338
16.2.1 Composition . 338
16.3 Vulnerability analysis (AVA_VAN) .338
16.3.1 Evaluation of sub-activity (AVA_VAN.1). 338
16.3.2 Evaluation of sub-activity (AVA_VAN.2) .344
16.3.3 Evaluation of sub-activity (AVA_VAN.3) . 351
16.3.4 Evaluation of sub-activity (AVA_VAN.4) . 359
16.3.5 Evaluation of sub-activity (AVA_VAN.5) . 367
16.4 Composite vulnerability assessment (AVA_COMP) . 375
16.4.1 Evaluation of sub-activity (AVA_COMP.1). 375
17 Composition .378
17.1 Introduction . 378
17.2 Application notes . 378
17.3 Composition rationale (ACO_COR) . 379
17.3.1 Evaluation of sub-activity (ACO_COR.1) .
...