![]() ![]() Site Technical Audit Report Template, v1.If you are a Mac user and want to make ringtones, transfer old cassette tapes or albums onto your computer, create a podcast or do just about any common audio editing task, Amadeus Pro is a good option. Management of code disclosure and software IP reuse, v1.2 Minimum site security requirements (MSSR), v3.0Ĭhecklist associated to Minimum site security requirements (MSSR), v3.0ĭocument related to Security Requirements for post-delivery code loading, v1.0 Minimum ITSEF Requirements for Security Evaluations of Smart cards and similar devicesĪpplication of Attack Potential to Smartcards ![]() Security Architecture requirements (ADV_ARC) for smart cards and similar devices, version 2.1 - Appendix 1 Security Architecture requirements (ADV_ARC) for Smart Cards and similar devices extended to Secure Sub-Systems in SoC, version 2.1Īpplication of CC to Integrated Circuits v3.0Ĭomposite product evaluation for Smartcards and similar devices Rationale for Smart cards and similar devices Supporting Documents related to Smart Cards and similar devices Document title Those which are termed 'Guidance Supporting Documents' contain more general advice.įor more information see the CCRA Procedure for Supporting Documents.ĬCRA Supporting Documents Document Numberįull Drive Encryption: Authorization AcquisitionĮvaluation Activities for Stateful TrafficĮvaluation Activities for Network Device cPPĬharacterizing Attacks to Fingerprint Verification MechanismsĮvaluation methodology for product series, v1.0Ĭonducting Voluntary Periodic Assessments of Schemes Participating in the CCRA Product involving the particular technology is certified in order to support mutual recognition. Those which are termed 'Mandatory Supporting Documents' are required to have been applied when a There are two classes of CC Supporting documentation: Their relevance and use for particular technologies is approved through an external approval process in which all CCRA members have input. They replace multiple individual interpretations and hence provide clarity for developers, evaluators, and users. Supporting documents are used within the Common Criteria certification process to define how the criteria and evaluation methods are applied when certifying specific technologies. The following documents are CC Supporting Documents. ![]() Guidelines for Developer Documentation according to Common Criteria Version 3.1įor previous versions of the CC and CEM please click hereįor unofficial versions of the CC and CEM please click here Transition Guide Summary of changes in the CC/CEM from v2.3 to v3.1. Guide for the Transition from CC v2.3 to CC v3.1 Make sure to download and use these files marked as "Final": Make sure to download and use these files:ĬC v3.1 consists of three parts. Make sure to download and use these files:ĬCDB-013-v2.0-2021-Sep-30-Final-CCaddenda-Exact_Conformance.pdfĬC v3.1 Release 4 consists of three parts. Security Targets conformant to CC:2022 based on Protection Profiles certified according to CC v3.1 will be accepted up to the 31st of December 2027.Īfter 30th of June 2024, re-evaluations and re-assessments based on CC v3.1 evaluations can be started for up to 2 years from the initial certification date.ĬC v3.1 Release 5 consists of three parts. Transition Policy to CC:2022 and CEM:2022ĬC v3.1 R5 is the last revision of version 3.1 and may optionally be used for evaluations of Products and Protection Profiles starting no later than the 30th of June 2024. Transition Policy to CC:2022 and CEM: 2022 Part 5: Pre-defined packages of security requirements Part 4: Framework for the specification of evaluation methods and activities Make sure to download and use these files. The member organisations of the CCRA declare that defined assurance levels (EALs) between versions of theĬriteria are equivalent and can therefore be used without restrictions for composition activities.ĬC:2022 Release 1 consists of five parts. ![]()
0 Comments
Leave a Reply. |