ISO/IEC. Third edition. Information technology — Security techniques — Evaluation criteria for IT security —. Part 2: Security functional. ISO/IEC (E). PDF disclaimer. This PDF file may contain embedded typefaces. In accordance with Adobe’s licensing policy, this file. The Common Criteria for Information Technology Security Evaluation is an international standard (ISO/IEC ) for computer security certification.
|Country:||Bosnia & Herzegovina|
|Published (Last):||20 February 2014|
|PDF File Size:||19.60 Mb|
|ePub File Size:||20.44 Mb|
|Price:||Free* [*Free Regsitration Required]|
Webarchive template wayback links Interlanguage link template link number. As well as the Common Criteria standard, there is also a sub-treaty level Common Criteria MRA Mutual Recognition Arrangementwhereby each party thereto recognizes evaluations against the Common Criteria standard done by other parties. Instead, 15048-2 standards, like FIPS give the specifications for cryptographic modules, and various standards specify the cryptographic algorithms in use.
Although some have argued that both paradigms do not align well,  others have attempted to reconcile both paradigms. Failure by the isi to take either of these steps would result in involuntary withdrawal of the product’s certification by the certification body of the country in which the product was evaluated. In other words, products evaluated against a Common Criteria standard exhibit a clear chain of evidence that the process of specification, implementation, and evaluation has been conducted in a rigorous and standard manner.
This is possible because the process of obtaining a Common Criteria certification allows a vendor to restrict the analysis to certain security features and to make certain assumptions about the operating environment and the strength of threats faced by the product in that environment. There is some concern that this may have a negative impact on mutual recognition.
Evaluations activities are therefore only performed to a certain depth, use of time, and resources and offer reasonable assurance for the intended environment. In contrast, much FOSS software is produced using modern agile paradigms. Vendors can then implement or make claims about the security attributes of their products, and testing laboratories can evaluate the products to determine if they actually meet the claims.
Standard ISO/IEC , CC v Release 4
Some national evaluation schemes are phasing out EAL-based evaluations and only accept products for evaluation that claim strict conformance with an approved PP. This will be achieved through technical working groups developing 154082 PPs, and as yet a transition period has not been fully determined.
Views Read Edit View history. CC was produced by unifying these pre-existing standards, predominantly so that companies selling computer products for the government market mainly for Defence or Intelligence use would only need to have them evaluated against one set of standards. Canada is in the process of phasing out EAL-based evaluations.
Further, this vision uso a move away from assurance levels altogether and evaluations will be confined isl conformance with Protection Profiles ido have no stated assurance level. Whether you run Microsoft Windows in the precise evaluated configuration or not, you should apply Microsoft’s security patches for 1548-2 vulnerabilities in Windows as they continue to appear.
Retrieved from ” https: In Sept ofthe Common Criteria published a Vision Statement implementing to a large extent Chris Salter’s thoughts from the previous year. Common Criteria is very generic; it does not directly provide a list of product isl requirements or features for specific classes of products: In this approach, communities of interest form around technology types which in turn develop protection profiles that define the evaluation methodology for the technology type.
Archived from the original PDF on April 17, List of International Electrotechnical Commission standards.
Additionally, the CC recognizes a need to limit the scope of evaluation in order to provide cost-effective and useful security certifications, such that evaluated products are examined to a level of detail specified by the assurance level or PP.
Computer security standards Evaluation ixo computers ISO standards.
The compliance with ISO is typically demonstrated to a National approval authority:. There are no security requirements that address the need to trust external systems or the communications links to such systems. Evaluations at EAL5 and above tend to involve the security requirements of the host ieo government.
The UK has also produced a number iwo alternative schemes when the timescales, costs and overheads of mutual recognition have been found to be impeding the operation of the market:. Major changes to the Arrangement include:. From Wikipedia, the free encyclopedia.
If any of these security vulnerabilities are exploitable in the product’s evaluated configuration, the product’s Common Criteria certification should be voluntarily withdrawn by the vendor.
Common Criteria – Wikipedia
Various Microsoft Windows versions, including Windows Server and Windows XPhave been certifiedbut security patches to address security vulnerabilities are still getting published by Microsoft for these Windows systems. Archived from the original on August 1, Kso is currently in version 3. Common Criteria certification cannot guarantee security, but it can ensure that claims about the security attributes of the evaluated product were independently verified.
Objections outlined in the article include:. Wheeler suggested that the Common Criteria process discriminates against free and open-source software FOSS -centric organizations and development models. Common Criteria certification is sometimes specified for IT procurement. ISO standards by sio number. In Septembera majority of members of the CCRA produced a vision statement whereby mutual recognition of CC evaluated products will be lowered to EAL 2 Including augmentation with flaw remediation.
Alternatively, the vendor should re-evaluate the product to include the application of patches to fix the security vulnerabilities within the evaluated configuration.
Standard ISO/IEC 15408, CC v3.1. Release 4
Based on this and other assumptions, which may not be realistic for the common use of general-purpose operating systems, the claimed security functions of the Windows products are evaluated. More recently, PP authors are including cryptographic requirements for CC evaluations that would typically be covered by FIPS evaluations, broadening the bounds of the CC through scheme-specific interpretations. This shows both the limitation and strength of an evaluated configuration. Other standards containing, e.
In other words, Common Criteria provides assurance that the process of specification, implementation and evaluation of a computer security product has been conducted in a rigorous and standard and repeatable manner at a level that is commensurate with the target environment for use.
The TOE is applicable to networked or distributed environments only if the entire network operates under the same constraints and resides within a single management domain. The evaluation process also tries to establish the level of confidence that may be placed in the product’s security features through quality assurance processes:. Thus they should only be considered secure in the assumed, specified circumstances, also known as the evaluated configuration.