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.
|Published (Last):||17 July 2015|
|PDF File Size:||15.49 Mb|
|ePub File Size:||12.81 Mb|
|Price:||Free* [*Free Regsitration Required]|
More recently, 154408-2 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.
Computer security standards Evaluation of computers ISO standards. 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.
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. Canada is in the process of phasing out EAL-based evaluations. Whether you run Microsoft Windows in the precise evaluated configuration or not, you should apply Microsoft’s security patches for the vulnerabilities in Windows as they continue to appear.
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 isl target environment for 115408-2. From Wikipedia, the free encyclopedia. Although some have argued that both paradigms do not align well,  others have attempted to reconcile both paradigms. 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.
Further, this vision indicates a move away from assurance levels altogether and evaluations will be confined to conformance with Protection Profiles that have no stated assurance level.
Views Read Edit View history. Evaluations at EAL5 and above tend to involve the security requirements of the host nation’s government.
Failure by the vendor 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 Septembera majority of members of the CCRA produced a vision statement whereby mutual recognition of CC evaluated products will be 1540-82 to EAL 2 Including augmentation with flaw remediation.
List of International Electrotechnical Commission standards. This shows both the limitation and strength of an evaluated configuration.
ISO standards by standard number. Evaluations activities are therefore only performed to a certain depth, use 1508-2 time, and resources and offer reasonable assurance for the intended environment. 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. Vendors can then implement or make claims about the security attributes of 1508-2 products, and testing laboratories can evaluate the products to determine if they actually meet the claims.
There is some concern that this may have a negative impact on mutual recognition.
Other standards containing, e. Key elements of the Vision included:. Common Criteria certification cannot guarantee security, but it can ensure that claims about the security attributes of the evaluated product were independently verified.
The United States currently only allows PP-based evaluations. 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.
Standard ISO/IEC 15408, CC v3.1. Release 4
Instead, national standards, like FIPS give the specifications for cryptographic modules, and various standards specify the cryptographic algorithms in use. Major changes to the Arrangement include:. Characteristics of these organizations were examined and presented at ICCC 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.
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:. 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.
The compliance with ISO is typically demonstrated to a National approval authority:. Alternatively, the vendor should re-evaluate the product to include the application of patches to fix the security vulnerabilities within the evaluated configuration.
Common Criteria – Wikipedia
This is iwo 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.
Retrieved from ” https: 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 will 154408-2 achieved through technical working groups developing worldwide PPs, and as yet a transition period has not been fully determined. In contrast, much FOSS software is produced using modern agile paradigms. The UK has also produced a number of alternative 15480-2 when the timescales, costs and overheads 14508-2 mutual recognition have been found to be impeding the operation of the market:.
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. There are no security requirements that address the need to trust external systems or the communications links to such systems.