GB/T 20274.4-2008Information security technology Evaluation framework for information systems security assurance Part 4: Engineering assurance (English PDF)

3.1.1 Validation

The solution that meets the user's operation security requirements.

5.1 Overview of Information Systems Security Engineering Assurance

Part 1 of this Standard puts forward the information security assurance model (refer to Figure 3 in Part 1 of this Standard) and describes the relationship among assurance elements (technology, engineering, management and personnel), security features and life cycle of information system security therein.

5.2 Information Systems Security Engineering Assurance Control

5.2.1 Information systems security engineering assurance control class

This Part divides information system security engineering into three basic process domains (i.e. information system security engineering assurance control class). risk, engineering and assurance. Although these domains are interdependent, they may be considered separately. In the simplest level, risk process identifies and ranks in the order of priority the inherent risk of the developed product or system. Security engineering process determines and implements the solution to the problems caused by risks by acting together with other engineering disciplines. Finally, assurance process establishes confidence for security solution and transfers such confidence to the users.

5.2.3 Corresponding relationship between security engineering life cycle and process domain

The relationship between security engineering life cycle and process domain is shown in Table 1.

5.3 Information System Security Engineering Capability Maturity Level

In the engineering process modules, the process domain involved in information security engineering process is specified and it is the optimal reflection of the practice abstracted from information security engineering process. Engineering process capability, which is the measurable range achievable by complying with an engineering process, reflects the planned cost, function and quality target measurement reached by the organization in implementing information security project through the organization's capability in implementing each process domain of the security engineering.

6.1 General

This chapter defines the structure of information security engineering assurance control class used in this Part. The information security engineering assurance control class is expressed by security engineering assurance control class, security engineering assurance control subclass and security engineering assurance control module.

6.2 Structure of Security Engineering Assurance Control Class

Each security engineering assurance control class includes one name of the security engineering assurance control class, the introduction of a security engineering assurance control class and one or more security engineering assurance control subclass(es). Figure 2 shows the structure of security engineering assurance control classes used in this Part.

6.3 Structure of Security Engineering Assurance Control Subclass

One security engineering assurance control class includes one or multiple security engineering assurance control subclasses. Each security engineering assurance control subclass includes one name of the security engineering assurance control subclass, one purpose of the security assurance project and one or multiple security engineering assurance control module(s) (control measure(s)) for realizing this security engineering assurance purpose.

6.4 Structure of Security Engineering Assurance control module

Security engineering assurance control module is the engineering control measure of information security assurance to realize security engineering assurance purpose.

Each security engineering assurance control module includes one name, one control and one optional explanation of the security engineering assurance control module.

7.2 System Definition (PRM_SDF)

7.2.1 Purpose of security engineering assurance

The system definition of security engineering assurance control subclass aims at identifying the system task and mission, i.e.

7.3.3 PRM_ATT.2 Identify man-made threat

7.3.3.1 Control of security engineering assurance control module

PRM. Process of risk

7.3.4 PRM_ATT.3 Identify the measuring block of threat

7.3.4.1 Control of security engineering assurance control module

Identify the suitable measuring blocks and application scope in specific environment.

Most natural threats and many man-made threats have relevant measuring blocks. In most cases, the whole measuring block is not applicable to particular case.

7.4 Assess Vulnerability (PRM_AVL)

7.4.1 Purpose of security engineering assurance

Identify and characterize the security vulnerability of the system.

The purpose of assessing security vulnerability is to obtain the understanding to the system security vulnerability in one given environment.

7.4.5 PRM_AVL.4 Compose system vulnerability

Assess the system vulnerability and make comprehensive collection of the result of specific vulnerability and the combination of all kinds of specific vulnerabilities.

7.4.6 PRM_AVL.5 Monitor vulnerability and its characteristics

Monitor the frequent changes of vulnerability and its characteristic changes.

7.5 Assess Impact (PRM_AIM)

7.5.1 Purpose of security engineering assurance

The purpose of assessing influence is to identify the influence on system and assess the occurrence possibility of influences. Influences may be tangible, e.g. income loss or economic punishment, and may also be intangible, e.g. reputation and credit loss.

The target of this security engineering assurance control subclass is to identify and characterize the risk's security influence on the system.

8.1 Introduction of Engineering Process of Engineering Process Security

Control Class Security engineering, like other engineering disciplines, is a process running through concept, design, implementation, testing, acceptance, operation, maintenance and abandonment. During the whole process, security engineer must work closely with other parts of the system engineering group.

8.2 Identify Security Requirements (PEN_ISR)

8.2.1 Purpose of security engineering assurance

The purpose of identifying security requirements is to mark the security need of the system clearly. The security basis of the definition system related to security Identify security requirements

8.2.3 PEN_ISR.2 Identify available laws, policies and restrictions

8.2.3.1 Control of security engineering assurance control module

The laws, policies, standards, external effects and restrictions of the management system shall be identified.

8.2.4 PEN_ISR.3 Identify system security relevance

8.2.4.1 Control of security engineering assurance control module

Identify the system applications to determine the contextual environment of security.

The purpose of this security engineering assurance control module is to identify whether the system context affects the security.

8.2.7 PEN_ISR.6 Define security-related need

8.2.7.1 Control of security engineering assurance control module

Define a series of consistent illustrations that define the executive protection of the system.

8.3 High-level Security Design (PEN_HSD)

8.3.1 Purpose of security engineering assurance

The high-level security design of information system includes system architecture, design and achieved needs; corresponding design principle and suggestion, security architecture suggestion and protective principle shall be established to obtain security model and security architecture for reliability analysis; all the security mechanisms shall be ensured to be corresponding to the high-level security designs, and the latter shall be of specific security mechanism to ensure.

9.2 Verify and Validate Security (PAS_VVS)

9.2.1 Purpose of security engineering assurance

The purpose of security verification and validation is to ensure that the solution has verified and validated security. Verify the solution by observation, demonstration, analysis and testing, based on security requirements, architecture and design. Validate the solution according to the operation security need of the customer.

9.2.2 PAS_VVS.1 Identify the targets of verification and validation

9.2.2.1 Control of security engineering assurance control module

Identify the solutions for verification and validation.

9.2.2.2 Explanation of security engineering assurance control module

1.Identify the targets of verification and validation.

9.2.5 PAS_VVS.4 Execute validation

9.2.5.1 Control of security engineering assurance control module

Validate the solution and demonstrate that the solution has fulfilled the previous abstract requirements, and finally satisfied the customer's operation security need.

The purpose of this security engineering assurance control module is to validate that the solution has effectively fulfilled the previous abstract requirements. There are multiple methods for such validation, including testing the solution in operation or typical test setting environment. The method applied is identified in PAS_VVS.2 "define the methods of verification and validation".

9.2.5.2 Explanation of security engineering assurance control module

This practice involves traceability. […]