ISO/IEC 21827

ISO/IEC 21827:2002(E)
acceptable level of confidence that the system security measures are adequate to manage the security risk. Effective
management of the assurance related activities is achieved through the development and enactment of a security
assurance strategy. Early identification and definition of assurance related requirements is essential to producing the
necessary supporting evidence. Understanding and monitoring the satisfaction of customer assurance needs through
continuous external coordination ensures a high quality assurance package.
7.6.3.2 Example Work Products
• security assurance strategy - describes the plan for meeting the customer's security assurance objectives and
identifies the responsible parties.
7.6.3.3 Notes
The security assurance strategy is coordinated with all affected internal engineering groups and external groups (e.g.,
customer, systems security certifier, or user) as defined in PA09 Coordinate Security.
7.6.4 BP.06.03 - Control Assurance Evidence
Identify and control security assurance evidence.
7.6.4.1 Description
Security assurance evidence is gathered as defined in the security assurance strategy through interaction with all
security engineering process areas to identify evidence at various levels of abstraction. This evidence is controlled to
ensure currency with existing work products and relevancy with security assurance objectives.
7.6.4.2 Example Work Products
• security assurance evidence repository (e.g., database, engineering notebook, test results, evidence log) -
stores all evidence generated during development, testing, and use. Could take the form of a database,
engineering notebook, test results, or evidence log.
7.6.4.3 Notes
Assurance work products can be developed from the system, architecture, design, implementation, engineering
process, physical development environment, and physical operational environment.
7.6.5 BP.06.04 - Analyse Evidence
Perform analysis of security assurance evidence.
7.6.5.1 Description
Assurance evidence analysis is conducted to provide confidence that the evidence that is collected meets the security
objectives, thus satisfying the customer's security needs. An analysis of the assurance evidence determines if system
security engineering and security verification processes are adequate and complete enough to conclude that the
security features and mechanisms are satisfactorily implemented. Additionally, the evidence is analysed to ensure that
the engineering artifacts are complete and correct with respect to the baseline system. In the event of insufficient or
inadequate assurance evidence, this analysis may necessitate revisions to the system, security work products and
processes that support the security objectives.
7.6.5.2 Example Work Products
• assurance evidence analysis results - identifies and summarizes the strengths and weaknesses of evidence in
the repository.
7.6.5.3 Notes
Some assurance evidence can only be generated from a consolidation of other system engineering artifacts or inferred
© ISO/IEC 2002 – All rights reserved 39