ISO/IEC 15408-2: 安全技术 - IT安全评估标准 - 第2部分：安全功能要求

需积分: 10 185 浏览量更新于2024-07-08 收藏 2.65MB PDF 举报

"ISO/IEC 15408-2是信息技术安全技术领域的一个重要标准，主要关注信息安全的评估准则，特别是第二部分——安全功能要求。这份国际标准首次发布于1999年12月1日，规定了信息技术产品的安全功能需求，旨在为IT安全的评估提供一套全面的标准。" ISO/IEC 15408-2，通常被称为“信息技术安全评估通用标准”(Common Criteria for Information Technology Security Evaluation)，是全球公认的信息安全产品评估的基础。标准分为多个部分，其中第二部分详细阐述了安全功能要求，是评估IT产品安全性的重要依据。 1. 范围：该标准的范围涵盖了信息安全技术的评估准则，其目的是确保IT产品和服务的安全性符合特定的要求。它不仅定义了安全功能的最低标准，还提供了扩展和维护这些要求的方法，以适应不断发展的技术环境和安全威胁。 1.1 扩展和维护功能要求：标准允许随着技术进步和安全需求变化进行功能要求的扩展和更新。这确保了标准能够保持与时俱进，满足新的安全挑战和用户需求。 1.2 ISO/IEC 15408-2的组织结构：标准采用了一种分层结构，便于理解和应用。组织结构包括类、家族和组件等层次，以清晰地表达各种安全功能要求。 1.3 功能要求范式：功能要求范式是一种框架，用于描述和分类安全功能。这一范式将复杂的安全功能拆分为可管理和可度量的部分，有助于评估和验证产品是否达到设定的安全标准。 2. 安全功能组件：这部分详细介绍了构成安全功能要求的基本元素。这些组件包括： 2.1 概览：提供了对安全功能组件的整体理解，包括类（Class）、家族（Family）和组件（Component）三个层次的结构。 2.1.1 类结构：类是高级别的分类，将相关功能分组在一起，例如数据完整性保护或访问控制。 2.1.2 家族结构：家族是类下的次级分类，更具体地定义了安全功能的子类别，比如密码学家族可能包括加密、解密和数字签名等功能。 2.1.3 组件结构：组件是最小的可度量单元，具体描述了一个具体的、可实现的安全功能，如数据源认证组件或传输数据加密组件。 ISO/IEC 15408-2为IT安全评估提供了全面且严谨的框架，通过明确的功能要求，帮助制造商、供应商以及安全评测机构确保产品和服务达到预定的安全水平。这一标准对于保障用户的数据安全和隐私，以及促进全球信息技术市场的互信和标准化具有重要意义。

ISO/IEC 15408-2:1999(E) ©ISO/IEC

TOEs contain resources that may be used for the processing and storing of information. The

primary goal of the TSF is the complete and correct enforcement of the TSP over the resources and

information that the TOE controls.

TOE resources can be structured and utilised in many different ways. However, ISO/IEC 15408-2

makes a specific distinction that allows for the specification of desired security properties. All

entities that can be created from resources can be characterised in one of two ways. The entities

may be active, meaning that they are the cause of actions that occur internal to the TOE and cause

operations to be performed on information. Alternatively, the entities may be passive, meaning that

they are either the container from which information originates or to which information is stored.

Active entities are referred to as

subjects

. Several types of subjects may exist within a TOE:

a) those acting on behalf of an authorised user and which are subject to all the rules of the

TSP (e.g. UNIX processes);

b)those acting as a specific functional process that may in turn act on behalf of multiple

users (e.g. functions as might be found in client/server architectures); or

c) those acting as part of the TOE itself (e.g. trusted processes).

ISO/IEC 15408-2 addresses the enforcement of the TSP over types of subjects as those listed

above.

Passive entities (i.e. information containers) are referred to in the ISO/IEC 15408-2 security

functional requirements as

objects

. Objects are the targets of operations that may be performed by

subjects. In the case where a subject (an active entity) is the target of an operation (e.g. interprocess

communication), a subject may also be acted on as an object.

Objects can contain

information

. This concept is required to specify information flow control

policies as addressed in the FDP class.

Users, subjects, information and objects possess certain

attributes

that contain information that

allows the TOE to behave correctly. Some attributes, such as file names, may be intended to be

informational (i.e. to increase the user-friendliness of the TOE) while others, such as access control

information, may exist specifically for the enforcement of the TSP. These latter attributes are

generally referred to as

‘security attributes’

. The word attribute will be used as a shorthand in this

part of ISO/IEC 15408 for the word ‘security attribute’, unless otherwise indicated. However, no

matter what the intended purpose of the attribute information, it may be necessary to have controls

on attributes as dictated by the TSP.

Data in a TOE is categorised as either user data or TSF data. Figure 1.3 depicts this relationship.

User Data

is information stored in TOE resources that can be operated upon by users in accordance

with the TSP and upon which the TSF places no special meaning. For example, the contents of an

electronic mail message is user data.

TSF Data

is information used by the TSF in making TSP

decisions. TSF Data may be influenced by users if allowed by the TSP. Security attributes,

authentication data and access control list entries are examples of TSF data.

There are several SFPs that apply to data protection such as

access control SFPs

and

information

flow control SFPs

. The mechanisms that implement access control SFPs base their policy

decisions on attributes of the subjects, objects and operations within the scope of control. These

attributes are used in the set of rules that govern operations that subjects may perform on objects.

©ISO/IEC ISO/IEC 15408-2:1999(E)

The mechanisms that implement information flow control SFPs base their policy decisions on the

attributes of the subjects and information within the scope of control and the set of rules that govern

the operations by subjects on information. The attributes of the information, which may be

associated with the attributes of the container (or may not, as in the case of a multi-level database)

stay with the information as it moves.

Figure 1.3 - Relationship between user data and TSF data

Two specific types of TSF data addressed by ISO/IEC 15408-2 can be, but are not necessarily, the

same. These are

authentication data

and

secrets

Authentication data is used to verify the claimed identity of a user requesting services from a TOE.

The most common form of authentication data is the password, which depends on being kept secret

in order to be an effective security mechanism. However, not all forms of authentication data need

to be kept secret. Biometric authentication devices (e.g. fingerprint readers, retinal scanners) do not

rely on the fact that the data is kept secret, but rather that the data is something that only one user

possesses and that cannot be forged.

The term secrets, as used in ISO/IEC 15408-2 functional requirements, while applicable to

authentication data, is intended to also be applicable to other types of data that must be kept secret

in order to enforce a specific SFP. For example, a trusted channel mechanism that relies on

cryptography to preserve the confidentiality of information being transmitted via the channel can

only be as strong as the method used to keep the cryptographic keys secret from unauthorised

disclosure.

Therefore, some, but not all, authentication data needs to be kept secret and some, but not all,

secrets are used as authentication data. Figure 1.4 shows this relationship between secrets and

authentication data. In the Figure the types of data typically encountered in the authentication data

and the secrets sections are indicated.

USER DATA

TSF DATA

Authentication

Security Attributes

User Attributes

Object Attributes

TOE DATA

Data

Subject Attributes

Information Attributes

剩余353页未读，继续阅读

omibao.zheng

粉丝: 0
资源: 3

ISO/IEC 15408-2: 安全技术 - IT安全评估标准 - 第2部分：安全功能要求

ISO/IEC 15408-2

ISO_IEC_15408-1

ISO-IEC-15408

iso_iec_14496-10-avc-2012.pdf

iso iec 27017-2015.pdf

ISO/IEC 7498

ISO/IEC 24759

iso/iec 9899:1999 - programming languages -- c下载

IEC 61010-2-201 下载

isoiec25010-2011.pdf

最新资源