Perkon IPT-360 Pico New Generation FCR Fiscalapp Security Target-Lite Document Attributes File name: Perkon IPT-360 Pico ST-Lite.docx Status: Released Release Date: 15.06.2017 Version: 1.0 Sensitivity: Public Author: Orçun ERTUĞRUL Approved by Altan GEZEROĞLU Perkon New Generation FCR Application Security Target Page 2 / 67 Revision Table Revision No Revision Date Explanation Made by 1.0 15.06.2017 Initial Release Orçun Ertuğrul Perkon New Generation FCR Application Security Target Page 3 / 67 Table of Contents Revision Table ....................................................................................................................................................2 Table of Contents...............................................................................................................................................3 1. INTRODUCTION..........................................................................................................................................5 1.1. ST Reference ......................................................................................................................................5 1.2. TOE Reference....................................................................................................................................5 1.3. TOE Overview.....................................................................................................................................5 1.3.1. General overview of the TOE and related components ............................................................5 1.3.2. Required Non-TOE Hardware/Software ....................................................................................6 1.3.3. Major security and functional features .....................................................................................8 1.3.4. TOE Type ....................................................................................................................................9 1.3.5. Non-TOE hardware/software/firmware ....................................................................................9 1.4. TOE Description..................................................................................................................................9 1.4.1. TOE Boundaries..........................................................................................................................9 1.4.2. TOE Guidance Documents .......................................................................................................10 2. CONFORMANCE CLAIMS..........................................................................................................................10 2.1. CC Conformance Claims...................................................................................................................10 2.2. PP Conformance Claims...................................................................................................................10 2.3. Package Claim ..................................................................................................................................11 2.4. Conformance Rationale ...................................................................................................................11 3. 3. SECURITY PROBLEM DEFINITION .........................................................................................................11 3.1. Introduction .....................................................................................................................................11 3.1.1. External Entities .......................................................................................................................11 3.1.2. Roles.........................................................................................................................................12 3.1.3. Modes of FCR...........................................................................................................................12 3.1.4. Assets .......................................................................................................................................13 3.2. Threats .............................................................................................................................................14 3.3. Organizational Security Policies.......................................................................................................16 3.4. Assumptions.....................................................................................................................................18 4. SECURITY OBJECTIVES..............................................................................................................................19 4.1. Security Objectives for the TOE .......................................................................................................19 4.2. Security Objectives for the Operational Environment.....................................................................20 4.3. Security Objective Rationale............................................................................................................21 5. EXTENDED COMPONENTS DEFINITION....................................................................................................25 Perkon New Generation FCR Application Security Target Page 4 / 67 6. SECURITY REQUIREMENTS.......................................................................................................................25 6.1. Security Functional Requirements for the TOE................................................................................25 6.1.1. Class FAU Security Audit ..........................................................................................................26 6.1.2. Class FCO Communication .......................................................................................................26 6.1.3. Class FCS Cryptographic Support .............................................................................................27 6.1.4. Class FDP User Data Protection ...............................................................................................32 6.1.5. Class FIA Identification and Authentication.............................................................................36 6.1.6. Class FMT Security Management.............................................................................................37 6.1.7. Class FPT Protection of the TS..................................................................................................40 6.1.8. Class FTP Trusted Patch/Channels ...........................................................................................42 6.2. Security Assurance Requirements for the TOE................................................................................43 6.3. Security Requirements Rationale.....................................................................................................43 6.3.1. Security Functional Requirements Rationale...........................................................................43 6.3.2. Rationale for SFR’s Dependencies ...........................................................................................52 6.3.3. Security Assurance Requirements Rationale...........................................................................57 6.3.4. Security Requirements – Internal Consistency........................................................................57 7. 7. TOE SUMMARY SPECIFICATION ...........................................................................................................57 7.1. TOE Security Functions ....................................................................................................................57 7.1.1. Access Control..........................................................................................................................57 7.1.2. Accuracy and event recording .................................................................................................58 7.1.3. Authentication .........................................................................................................................59 7.1.4. Integrity Control.......................................................................................................................59 7.1.5. Secure Communication............................................................................................................60 7.2. Assurance Measure..........................................................................................................................61 7.3. TOE Summary Specification Rational...............................................................................................62 7.3.1. Security Functions Rational......................................................................................................62 7.3.2. Assurance Measures Rational..................................................................................................64 8. ACRONYMS ..............................................................................................................................................65 9. BIBLIOGRAPHY .........................................................................................................................................67 Perkon New Generation FCR Application Security Target Page 5 / 67 1. INTRODUCTION 1.1. ST Reference ST Title Perkon IPT-360 Pico New Generation FCR Fiscalapp Security Target-Lite CC Version Common Criteria for Information Technology Security Evaluation, Version 3.1 (revision 4) Version Number 1.0 Status Released 1.2. TOE Reference TOE Identification IPT-360 Pico Fiscalapp 3.152-1256 CC Conformance Common Criteria for Information Technology Security Evaluation, Version 3.1 (revision 4) PP Conformance COMMON CRITERIA PROTECTION PROFILE for NEW GENERATION CASH REGISTER FISCAL APPLICATION SOFTWARE (NGCRFAS PP), TSE- CCCS/PP-007, version 2.0, 06.May 2015 Assurance Level Evaluation Assurance Level 2 1.3. TOE Overview The TOE addressed by this Security Target (ST) is an application software and crypto library which defines the main items of a Fiscal Cash Register (FCR). TOE is used to process transaction amount of purchases to be viewed by both seller and buyer. This transaction amount is used to determine tax revenues. Therefore, secure processing, storing and transmitting of this data is very important. The FCR is mandatory for first-and second-class traders. FCR is not mandatory for sellers who sell the goods back to its previous seller completely the same as the purchased good. In addition to TOE, which is the main item of FCR, FCR may consist of several other hardware and software components as described in Section 1.3.1 and Section 1.3.2. TOEs related components are given in Figure 1. Usage and major security features of TOE are described in section 1.3.3. 1.3.1. General overview of the TOE and related components Figure 1 shows the general overview of the TOE and related components as regarded in this ST. The green part of Figure 1 is the TOE. Yellow parts; that are given as input/output interface, fiscal memory, daily memory, database, ERU, fiscal certificate memory; are TOE’s environmental components which are crucial for functionality and security. Connections between the TOE and its environment are also subject to evaluation since these connections are made over the interfaces of the TOE. Perkon New Generation FCR Application Security Target Page 6 / 67 Figure 1 TOE and related components 1.3.2. Required Non-TOE Hardware/Software Software and hardware environment of the TOE are described below. Software environment of TOE TOE runs at the top of an operating system’s kernel, its file-system as in a typical software environment. This structure is shown in Table-1 Table 1 Typical software environment of TOE File System Operating System Kernel In addition to TOE, following software components are necessary for security and functionality of the FCR:  Application runs on an operating system which supports following features o at least 32-bit data processing capacity o multi-processing o IPv4 and IPv6 Perkon New Generation FCR Application Security Target Page 7 / 67 o NTP (Network Time Protocol)  Database which is used to store sales data, has the following features; I. Database has data recording, organizing, querying, reporting features II. Database stores sales records for main product groups (food, clothing, electronics, glassware etc.) and sub-product groups (milk, cigarette, fruit, trousers etc.) in order to track detailed statistics III. Database has indexing mechanism Hardware Environment of TOE In addition to TOE, following hardware components are necessary for security and functionality of the FCR:  Fiscal memory i. Fiscal memory has following features; a. Fiscal memory has the capacity to store at least 10 years (3650 days) of data, b. Fiscal memory keeps data at least 5 years after the capacity specified in (a) has been reached, c. Fiscal memory is fixed in FCR in a way that it cannot be removed without damaging the chassis. d. Fiscal memory is protected with mesh cover, e. Fiscal memory has the ability to protect against magnetic and electronic threats, When the Fiscal memory and main processor interconnection is interrupted, FCR will begin to run in maintenance mode, f. The data stored in the fiscal memory doesn’t lost in case of power off, g. Fiscal Memory accepts only positive amounts from the application and the peripherals, h. Fiscal memory checks "Z" reports integrity during device start-up. i. In case there are days for which Z report was not generated, FCR automatically generates Z- Report for the interval that is not generated. ii. Fiscal Memory includes following data; a. Fiscal symbol, company code, identification number of the device, b. Cumulative sum of the total sales amount and Value Added Tax (VAT) amounts of all sales receipts, starting from the device activation (i.e. first use), c. Date and number of daily "Z" reports with total sales and VAT per day, d. The number of receipts per day.  Daily memory has following features; i. Receipt total and total VAT amount for each receipt are to be stored in the daily memory instantly. This data can be transmitted to PRA - IS, instantly or daily depending on demand. ii. Data in the daily memory which is not already transmitted to fiscal memory, cannot be modified in an uncontrolled way. iii. Data transmitted from daily memory to fiscal memory is kept in daily memory for at least 10 days. iv. Z reports, taken at the end of the day; and X reports, taken within the current day are produced by using the data in the daily memory. v. Following values are stored in the daily memory a. total VAT amount per day, b. total daily sales values per day grouped by payment type Perkon New Generation FCR Application Security Target Page 8 / 67 c. payment type (Cash, credit card etc.) d. number of receipts.  FCR supports X.509 formatted digital certificate generated by Authorized Certificate Authority. This Public Key Infrastructure (PKI) compatible digital certificate is called fiscal certificate and is used for authentication and secure communication between PRA-IS and FCR through Trusted Service Manager (TSM). For physical security, FCR is protected by electronic and mechanic systems called electronic seal. FCR uses cryptographic library for secure communication with PRA-IS and TSM  Electronic Record Unit(ERU) is used to keep second copy of the receipt and has following features; i. ERU stores information about receipts and FCR reports (except ERU reports) in a retrievable form. ii. ERU has at least 1.2 million row capacity. ERU can be accessible from outside and it can be changeable by any user. iii. Data stored in ERU cannot be modified iv. ERU also has features specified in “Fiscal Cash Register General Communique Serial Number: 67” part A which is about Law No: 3100 except item (ii) above.  FCR device has ETHERNET interface for communication with PRA-IS (for data transfer) and TSM system (for parameter management and software update).  Incoming and outgoing data traffic for FCR passes over a firewall.  FCR has a printer to print sales receipt.  FCR supports the use of EFTPOS.  FCR needs some input/output devices for functionalities listed below; i. FCR has separate displays for cashier and buyer ii. FCR has a keyboard unit iii. FCR has internal battery to keep time information, to protect event data and fiscal memory. 1.3.3. Major security and functional features The functional and major security features of the TOE are described below. TOE functional features The TOE is used as part of a FCR which is an electronic device for calculating and recording sales transactions and for printing receipts. TOE provides the following services; i. TOE supports storing sales data in fiscal memory. ii. TOE supports storing for each receipt the total receipt amount and total VAT amount in daily memory. iii. TOE supports generating reports (X report, Z report etc.). iv. TOE supports transmitting Z reports, receipt information, sale statistics and other information determined by PRA to PRA-IS in PRA Messaging Protocol format. v. TOE stores records of important events as stated in PRA Messaging Protocol document and transmits to PRA-IS in PRA Messaging Protocol [6] format in a secure way. Perkon New Generation FCR Application Security Target Page 9 / 67 vi. TOE supports using by authorized user or authorized manufacturer user and using in secure state mode or maintenance mode. Roles and modes of operation are described in 3.1.2 and 3.1.3 respectively. TOE major security features The TOE provides following security features; i. TOE supports access control. ii. TOE has the ability to detect disconnection between main processor and fiscal memory and it enters into the maintenance mode. iii. TOE supports usage of ITU X509 v3 formatted certificate and its protected private key for authenticating against PRA-IS and TSM and establishing a secure communication with PRA-IS and TSM. iv. TOE supports secure communication between FCR, PRA-IS and FCR TSM. v. TOE supports secure communication with EFT-POS vi. TOE ensures the integrity of event data, sales data, authentication data, characterization data and FCR parameters. vii. TOE records important events given in PRA Messaging Protocol document and send urgent event data immediately to PRA-IS in a secure way. viii. TOE detects physical attacks to FCR and enters into the maintenance mode in such cases. 1.3.4. TOE Type TOE consists of an embedded software application, openssl crypto library v1.0.1e, secure IC firmware and hardware crypto engine. 1.3.5. Non-TOE hardware/software/firmware TOE is implemented in a microprocessor in FCR. FCR includes printer keyboard, Fiscal Memory, Daily Memory, Operating System, Electronic Recording Unit, Database, communication interfaces. Although all parts of FCR are necessary for a fiscal cash register, they are not parts of TOE. 1.4. TOE Description The target of evaluation (TOE) is the NGFCRA as developed by PERKON Personel Barkod Sistemleri Bil. Yaz. Elek. Tic. Ltd. Şti. 1.4.1. TOE Boundaries TOE Physical Boundaries FCR is containing several parts necessary information is given in chapter 1.3.5. TOE is application running on microprocessor in FCR hardware. This application uses a smart card and a software library for cryptographic processes such as RSA and AES operations, cryptographic key generation. A smart card is used for digital Perkon New Generation FCR Application Security Target Page 10 / 67 signing and AES operations. The cryptographic library is compiled and used for key generation and AES operations. TOE Logical Boundaries The logical boundaries of the TOE include those security functions implemented exclusively by the TOE. These security functions includes accurate fiscal operation, generation security related and fiscal log information and storing in dedicated memories (daily memory, fiscal memory and Electronic Recording Unit), access control for sales data, event data, time information, authentication for FCR Authorised User, Authorised Manufacturer User, communication security function with TSM, PRA-IS and EFT-POS Device. A more detailed description of the implementation of these security functions is provided in Section 7 “TOE SUMMARY SPECIFICATION” 1.4.2. TOE Guidance Documents The TOE guidance documentation delivered is listed in the section 7.2 Assurance Measure. 2. CONFORMANCE CLAIMS 2.1. CC Conformance Claims This security target and TOE claim conformance to:  Common Criteria for Information Technology Security Evaluation, Part 1: Introduction and General Model; CCMB-2012-09-001, Version 3.1, Revision 4, September 2012 [1]  Common Criteria for Information Technology Security Evaluation, Part 2: Security Functional Components; CCMB-2012-09-002, Version 3.1, Revision 4, September 2012 [2]  Common Criteria for Information Technology Security Evaluation, Part 3: Security Assurance Requirements; CCMB-2012-09-003, Version 3.1, Revision 4, September 2012 [3] As follows  Part 2 conformant,  Part 3 conformant. The  Common Methodology for Information Technology Security Evaluation, Evaluation Methodology; CCMB-2012-09-004, Version 3.1, Revision 4, September 2012 [4] has to be taken into account. 2.2. PP Conformance Claims Perkon New Generation FCR Application Security Target Page 11 / 67 This security target claims conformance to the protection profile Common criteria protection profile for new generation cash register fiscal application software (NGCRFAS PP), TSE- CCCS/PP-007, version 2.0, 06 May 2015 2.3. Package Claim The current Security Target is conformant to the following security requirements package:  Assurance package EAL2 conformant to CC, part 3. 2.4. Conformance Rationale Since this security target (ST) claims demonstrable conformance with the protection profile (PP) Common criteria protection profile for new generation cash register fiscal application software (NGCRFAS PP), TSE- CCCS/PP-007, version 2.0, 06 May 2015. “PP Claim”. The statement of security problem definition of this ST is equivalent to the statement of security problem definition in the PP to which conformance is being claimed. The statement of security objectives of this ST is equivalent to the statement of security objectives in the PP to which conformance is being claimed. The statement of security requirements of this ST is equivalent to the statement of security requirements in the PP to which conformance is being claimed. 3. SECURITY PROBLEM DEFINITION 3.1. Introduction 3.1.1. External Entities PRA-IS PRA-IS takes sales data and event data from FCR by sending query with parameters to FCR through TSM. Trusted Service Manager TSM is the system which is used to load parameters, update software and manage FCR. Attacker Attacker tries to manipulate the TOE in order to change its expected behaviour and functionality. Attacker tries to breach confidentiality, integrity and availability on the FCR. PRA On-site Auditor PRA On-site Auditor is an employee of PRA who performs audits onsite to control the existence of expected FCR functionalities by using the rights of FCR Authorised User. Certificate storage The certificate storage holds certificates and private key used for authentication and secure communication. Certificate storage is protected inside physical and logical tampering system. Time Information Perkon New Generation FCR Application Security Target Page 12 / 67 FCR gets time information from trusted server. Time information is used during receipt, event, fiscal memory record, daily memory record and ERU record creation and is also used to send information to PRA-IS according to FCR Parameters. Audit storage Audit storage can be any appropriate memory unit in FCR. Audit storage stores important events according to their critical level (urgent, high, warning, information). List of events can be found in PRA messaging protocol document [6]. Storage unit Storage units of FCR are database, fiscal memory, daily memory and ERU. Input interface Input interfaces provide necessary input data from input devices to the TOE. Input devices for FCR may be keyboard, barcode reader, QR code (matrix barcode) reader, order tracking device or global positioning devices. External Device External device is the device which is used to communicate with FCR by using secure channel according to External Device Communication Protocol Document [7] Output interface Output interfaces deliver outputs of the TOE to the output devices. Output devices for FCR may be printer, display etc. 3.1.2. Roles FCR Authorised User FCR authorised user is the user who uses the functions of FCR and operates FCR by accessing the device over an authentication mechanism. Authorised Manufacturer User Authorised Manufacturer User works for FCR manufacturer and conducts maintenance works on FCR. 3.1.3. Modes of FCR Maintenance Mode Maintenance Mode is the mode that allow only Authorised Manufacturer User;  to fiscalize FCR  to fix FCR in case of any technical problem,  to change time information,  to change IP/Port information of TSM, Perkon New Generation FCR Application Security Target Page 13 / 67  to review event data,  to start update operation of TOE, FCR does not allow any fiscal transaction in maintenance mode. FCR enters this mode when the following occur;  Fiscal Memory is full or corrupted,  Fiscal Memory module belongs to another FCR,  Root Certificate check fails,  TOE signature checks fails,  FCR Certificate check fails,  Mesh cover monitoring check fails,  A disconnection between fiscal memory and main processor occurs,  Electronic seal is opened, or forced by unauthorised persons  EJ Media disconnection  NVRAM low battery voltage, while service mode is not active  Z-Report Message not sent to Revenue Administration during maximum number of days defined in Parameter Loading Message Secure State Mode: Secure State Mode is the mode that allows;  FCR Authorised User; o to configure FCR, o to take fiscal reports Secure State Mode is also allowing;  Unauthenticated Users; o to do fiscal sales, o to get FCR reports (except fiscal reports). 3.1.4. Assets Sensitive data Sensitive data is used for secure communication with PRA-IS and TSM. Confidentiality and integrity of this asset needs to be protected. Sensitive data consists of symmetric keys (TREK, TRAK, TRMK and SSL session keys).  TREK is used for provide confidentiality of data transfer to PRA-IS,  TRAK is used for integrity control of data transferred to the PRA-IS,  TRMK is used for key transportation from PRA-IS to TOE,  SSL session keys are used for secure communication with the TSM. Perkon New Generation FCR Application Security Target Page 14 / 67 Event data Event data is used to obtain information about important events contained in audit storage. The integrity of this asset is crucial while stored in FCR and both integrity and confidentiality of this asset are important while it is transferred from TOE to PRA-IS. Event data is categorized in PRA Messaging Protocol Document [6]. Sales data Sales data is stored in storage unit. Sales data is required for PRA-IS to calculate tax amount and to provide detailed statistics about sales. The integrity of this asset has to be protected while stored in FCR; and both integrity and confidentiality have to be protected while it is transferred from TOE to PRA-IS. Characterization data (Identification data for devices) Characterization data is a unique number assigned to each FCR given by the manufacturer. PRA-IS uses characterization data for system calls to acquire sales data or event data of an FCR. Integrity of this asset has to be protected. Authentication data Authentication data contains authentication information which is required for FCR Authorised Users and Authorised Manufacturer User to gain access to FCR functionalities. Both integrity and confidentiality of this asset has to be protected. Application Note 1: TOE does not use Authentication Data (password) to authenticate Authorised Manufacturer User. A challenge-response application is implemented in TOE and a secondary system which is run in manufacturer premises is used to create a response to authenticate authorised manufacturer user. Time Information Time information is stored in FCR and synchronized with trusted server. Time information is important when logging important events and sending reports to the PRA-IS. The integrity of this asset has to be protected. Server Certificates Server certificates contain PRA-IS certificates (PPRA and PPRA-SIGN) PPRA and PPRA-SIGN certificates are used for signing and encryption process during key transport between TOE and PRA-IS. FCR Parameters FCR parameters stored in FCR are updated by TSM after Z report is printed. FCR parameters set;  Sales and event data transferring time  Critical level of event data sent to the PRA-IS  Maximum number of days that FCR will work without communicating with PRA-IS 3.2. Threats Perkon New Generation FCR Application Security Target Page 15 / 67 Threats averted by TOE and its environment are described in this section. Threats described below results from assets which are protected or stored by TOE or from usage of TOE with its environment. T.AccessControl Adverse action: Authenticated users could try to use functions which are not allowed. (e.g. FCR Users gaining access to FCR Authorised User management functions) Threat agent: An attacker who has basic attack potential and has logical access to FCR. Asset: Event data, sales data, time information. T. Authentication Adverse action: Unauthorized users could try to use FCR functions. Threat agent: An attacker who has basic attack potential, has logical and physical access to the FCR. Asset: Sales data, event data, time information. T.MDData - Manipulation and disclosure of data Adverse action: This threat deals with five types of data: event data, sales data, characterization data, authentication data and FCR parameters.  An attacker could try to manipulate the event data to hide its actions and unauthorised access to the FCR, failure reports, and deletion of logs. An attacker also could try to disclose important events while transmitted between PRA-IS and FCR.  An attacker could try to manipulate or delete the sales data generated by TOE which may result in tax fraud. In addition, an attacker also could try to disclose sales data while transmitted between PRA-IS and FCR. Manipulation and deletion of sales data may be caused by magnetic and electronic reasons.  An attacker could try to manipulate the characterization data to cover information about tax fraud; to masquerade the user identity.  An attacker could try to manipulate the FCR parameters to use FCR in undesired condition.  An attacker also could try to disclose and modify authentication data in FCR Threat agent: An attacker who has basic attack potential, has physical and logical access to the FCR. Asset: Event data, sales data, characterization data, FCR parameters and authentication data. T.Eavesdrop - Eavesdropping on event data, sales data and characterization data Adverse action: An attacker could try to eavesdrop event data, sales data and characterization data transmitted between the TOE and the PRA-IS and also between the TOE and the distributed memory units (Fiscal Memory, Database, Daily Memory and ERU). Perkon New Generation FCR Application Security Target Page 16 / 67 Threat agent: An attacker who has basic attack potential, has physical access to the FCR and physical access to the FCR communication channel. Asset: Characterization data, sales data, and event data. T.Skimming - Skimming the event data, sales data and characterization data Adverse action: An attacker could try to imitate TSM to set parameters to FCR via the communication channel. Threat agent: An attacker who has basic attack potential and logical access to the FCR. Asset: FCR parameters. T.Counterfeit - FCR counterfeiting Adverse action: An attacker could try to imitate FCR by using sensitive data while communicating with PRA- IS and TSM to cover information about tax fraud. Threat agent: An attacker who has basic attack potential and has physical and logical access to the FCR. Asset: Sensitive data. T. Server counterfeiting Adverse action: An attacker could try to imitate PRA-IS by changing server certificates (PPRA and PPRA-SIGN) in FCR. In this way, the attacker could try to receive information from FCR while communicating with PRA-IS. Threat agent: An attacker who has basic attack potential, has physical and logical access to the FCR. Asset: Server Certificates T.Malfunction - Cause malfunction in FCR Adverse action: An attacker may try to use FCR out of its normal operational conditions to cause malfunction without the knowledge of TOE. Threat agent: An attacker who has basic attack potential, has physical access to the FCR. Asset: Sales data, event data. T.ChangingTime Adverse action: An attacker may try to change time to invalidate the information about logged events and reports in FCR. Threat agent: An attacker who has basic attack potential, has physical and logical access to the FCR. Asset: Time Information. 3.3. Organizational Security Policies This section describes organizational security policies that must be satisfied. Perkon New Generation FCR Application Security Target Page 17 / 67 P.Certificate It has to be assured that certificate which is installed at initialization step is compatible with ITU X.509 v3 format. FCR contains;  FCR certificate,  Certification Authority root and sub-root (subordinate) certificates that are used for verification of all certificates that are produced by Certification Authority,  PPRA certificate that is used for key transport process between FCR and PRA-IS,  PPRA-SIGN certificate that is used by TOE for signature verification  UpdateControl certificate that is used to verify the signature of the TOE. P.Certificates Installation It has to be assured that environment of TOE provides secure installation of certificates (PPRA and PPRA-SIGN) into the FCR at initialization phase. Before the installation of certificates, it has to be assured that asymmetric key pair is generated in a manner which maintains security posture. P.Comm_EXT - Communication between TOE and External Device It has to be assured that communication between TOE and External Devices is used to encrypt using AES algorithm with 256 bits according to External Device Communication Protocol Document [7] P.InformationLeakage - Information leakage from FCR It has to be assured that TOE’s environment provides a secure mechanism which prevents attacker to obtain sensitive information (private key) when FCR performs signature operation; i.e by side channel attacks like SPA (Simple power analysis), SEMA (Simple Electromagnetic Analysis), DPA (Differential power analysis), DEMA (Differential electromagnetic analysis). P.SecureEnvironment It has to be assured that environment of TOE senses disconnection between fiscal memory and main processor. Then TOE enters into the maintenance mode and logs urgent event. It has to be assured that fiscal memory doesn't accept transactions with negative amounts which results in a decrease of total tax value. It has to be assured that environment of TOE provides a mechanism that sales data in daily memory which is not reflected to the fiscal memory cannot be deleted and modified in an uncontrolled way. It has to be assured that sales data in ERU cannot be deleted and modified. P.PhysicalTamper It has to be assured that TOE environment and TOE provide a tamper respondent system which is formed by electromechanical seals. Perkon New Generation FCR Application Security Target Page 18 / 67 It has to be assured that physical tampering protection system protects the keys (asymmetric key, symmetric key), the certificates, event data, characterization data, FCR parameters and sales data in FCR. It has to be assured that TOE logs this type of events and enters into the maintenance mode when physical tampering protection system detect unauthorised access. It has to be assured that authorised access such as maintenance work or service works are logged. It has to be assured that physical tampering protection system (mesh cover) protects fiscal memory. P.PKI - Public key infrastructure It has to be assured that IT environment for the TOE provides public key infrastructure for encryption, signing and key agreement. P.UpdateControl TOE is allowed to be updated by TSM or Authorised Manufacturer User to avoid possible threats during this operation, FCR shall verify the signature of the new version of TOE to ensure that the TOE to be updated is signed by the correct organisation. Thus, the TOE to be updated is ensured to be the correct certified version because only the certified versions will be signed. In addition, FCR shall check version of TOE to ensure that it is in latest version. 3.4. Assumptions This section describes assumptions that must be satisfied by the TOE's operational environment. A.TrustedManufacturer It is assumed that manufacturing is done by trusted manufacturers. They process manufacturing step in a manner which maintains IT security. A.Control It is assumed that PRA-IS personnel performs random controls on FCR. During control PRA-IS should check if tax amount, total amount printed on receipt and sent to PRA-IS is the same. In addition to this, a similar check should be processed for events as well. A.Initialisation It is assumed that environment of TOE provides secure initialization steps. Initialization step consists of secure boot of operating systems, and integrity check for TSF data. Moreover, it is assumed that environment of TOE provides secure installation of certificate to the FCR in initialization phase. Before certificate installation it is assumed that asymmetric key pair generated in a manner which maintains security posture. A.TrustedUser User is assumed to be trusted. It is assumed that for each sale a sales receipt is provided to the buyer. A.Activation Perkon New Generation FCR Application Security Target Page 19 / 67 It is assumed that environment of TOE provides secure activation steps at the beginning of the TOE operation phase and after each maintenance process. A.AuthorisedService It is assumed that repairing is done by trusted authorised services. The repairing step is processed in a manner which maintains legal limits. A.Ext_Key It is assumed that External Device (EFT-POS/SMART PINPAD) generates strong key for communicating with TOE and stores it in a secure way. A.Ext_Device Pairing It is assumed that External Device and TOE are paired by Authorised Service. 4. SECURITY OBJECTIVES This chapter describes security objectives for the TOE and its operational environment. 4.1. Security Objectives for the TOE This part describes security objectives provided by the TOE. O.AccessControl TOE must control authenticated user’s access to functions and data by using authorization mechanism. O.Event TOE must record important events stated as in PRA Messaging Protocol Document [6]. O.Integrity TOE must provide integrity for sales data, event data, characterization data, authentication data, sensitive data, server certificates and FCR parameters located in the FCR and between the distributed memory units. O.Authentication TOE must run authentication mechanism for users and systems. O.Function TOE must ensure that processing of inputs to derive sales data and event data is accurate. TOE must ensure that time information is accurate by doing anomaly detection. TOE must enter a maintenance mode when maintenance mode events occur in section 3.1.3 O.Transfer Perkon New Generation FCR Application Security Target Page 20 / 67 TOE must provide confidentiality, integrity and authenticity for sales data, event data, characterization data transferred to the PRA-IS and FCR parameters transferred from TSM. TOE must provide confidentiality, integrity and authenticity for information send/received during external device communication. 4.2. Security Objectives for the Operational Environment This part describes security objectives provided by the operational environment. OE.Manufacturing Manufacturer should ensure that FCR is protected against physical attacks during manufacturing. OE.Delivery Authorised Manufacturer User must ensure that delivery and activation of the TOE done by a secure way. OE.KeyGeneration Asymmetric key and certificate generation mechanism shall be compatible with ITU X.509 format and accessible only by trusted persons. OE.SecureStorage Asymmetric private key shall be stored within smartcard. Sensitive data, certificates, event data, characterization data and sales data shall be stored within secure environment protected by electronic seal. OE.KeyTransportation Transportation and installation of asymmetric private key to the FCR must be done by protecting their confidentiality and integrity. In addition to this, transportation and installation of server certificates, Certification Authority root and sub-root certificates, FCR certificates and update control certificates must be done by protecting their integrity. OE.TestEnvironment Before FCR activation; test interfaces (functions, parameters) inserted in TOE should be disabled or removed. OE.StrongAlgorithm Environment of TOE shall use asymmetric private keys for signature operation by using libraries of smartcard. These libraries used in FCR shall be strong. Also they should have protection against side channel analysis (SPA, DPA, SEMA, DEMA). OE.UpgradeSoftware FCR software Updates should be get pass verdict from Common Criteria maintenance or reevaluation procedures (according to update type) before installed to the FCR. This will be validated by the FCR, using the cryptographic signature control methods. OE.TrustedUser Perkon New Generation FCR Application Security Target Page 21 / 67 Users shall act responsibly. OE.Control PRA Onsite Auditor must check FCR functionality by controlling tax amount on the receipt and tax amount sent to the PRA-IS. OE.External Device External Device should generate strong key for communicating with TOE and should store it in a secure way. OE.Ext_Pairing External Device should be paired with TOE by only Authorised Service. OE.SecureEnvironment Fiscal memory shall not accept transactions with negative amounts which results in a decrease of total tax value. Tampering protection system shall protect fiscal memory with mesh cover. Environment of TOE provides secure initialization steps. Initialization step is consist of secure boot of operating system, and integrity check for TSF data. 4.3. Security Objective Rationale Table 2 provides security problem definition covered by security objectives. Threats and OSPs are addressed by security objectives for the TOE and its operational environment. Assumptions are addressed by only security objectives for the operational environment. Perkon New Generation FCR Application Security Target Page 22 / 67 Table 2 Security Objective Rationale Threats OSPs Assumptions T.AccessControl T. Authentication T.MDData T.Eavesdropping T.Server Counterfeiting T.Skimming T.Counterfeit T.Malfunction T.ChangingTime P.Certificate P.Certificates Installation P.SecureEnvironment P.PhysicalTamper P.PKI P.InformationLeakage P.Comm_EXT P.UpdateControl A.Ext_Key A.TrustedManufacturer A.Control A. AuthorisedService A.Initialisation A.Activation A.Ext_Device Pairing A.TrustedUser O.AccessControl X X X X O.Event X X X X X X X X X X O.Integrity X X X X X X O.Authentication X X O.Function X X X O.Transfer X X X OE.External Device X OE.Manufacturing X OE.Delivery X X OE.KeyGeneration X X OE.SecureStorage X X X X X X OE.KeyTransportation X X X OE.TestEnvironment X OE.StrongAlgorithm X Perkon New Generation FCR Application Security Target Page 23 / 67 OE.UpgradeSoftware X OE.TrustedUser X X OE.Control X OE.SecureEnvironment X X X OE.Ext_Pairing X Perkon New Generation FCR Application Security Target Page 24 / 67 Justification about Table 2 is given below; T.AccessControl is addressed by O.AccessControl to control user access to functions and data; O.Event to log all access attempts. T.Authentication is addressed by O.Authentication to ensure that if user is authenticated to the FCR; O.Event to log successful/unsuccessful authentication attempts. T.MDData is addressed by O.Integrity to ensure integrity of sales data, event data, characterization data, authentication data and FCR parameters in FCR with logical and physical security features; O.Transfer to ensure integrity, confidentiality and authenticity of sales data, event data and characterization data during transferring to PRA-IS and parameters during transferring from TSM to FCR ; O.Event to log unexpected behavior of these memories and unexpected behavior in transferring data; OE.SecureStorage to provide secure environment for Sensitive Data, all certificates, event data, characterization data and sales data. T.Eavesdropping is addressed by O.Transfer to ensure confidentiality of sales data, event data and characterization data during communication with PRA-IS; O.Integrity to ensure the integrity of event data, sales data and characterization data; O.Event to log physical tamper; by OE.SecureStorage to provide secure environment for event data, characterization data and sales data T.Server Counterfeiting is addressed by O.Integritytoensure the integrity of server certificates (PPRA, PPRA-SIGN); O.Event to log physical tamper; OE.SecureStorage to provide secure environment for server certificates. T.Skimming is addressed by O.Authentication to establish communication only with permitted systems. T.Counterfeit is addressed by O.Integrity to ensure the integrity of sensitive data; O.Event to log physical tamper; OE.SecureStorage to provide secure environment for sensitive data. T.Malfunction is addressed by O.Function to ensure functions processing accurately; O.Event to log unexpected behavior of functions. T.ChangingTime is addressed by O.Event to log unexpected changes in time information; by O.Access Control to control user access to time information; by O.Function to ensure accuracy of time information. P.Certificate is fulfilled by OE.KeyGeneration. P.CertificateInstallation is fulfilled OE.KeyTransportation and OE.SecureStorage P.SecureEnvironment is fulfilled by OE.SecureEnvironment, O.Event, O.Integrity and O.Function. P.PhysicalTamper is fulfilled by OE.SecureEnvironment, O.AccessControl, O.Event, O.Integrity and OE.SecureStorage. P.PKI is fulfilled by OE.KeyTransportation Perkon New Generation FCR Application Security Target Page 25 / 67 P.InformationLeakage is fulfilled by OE.StrongAlgorithm to ensure that cryptographic algorithms used by FCR have side channel protection. P.Comm_EXT is fulfilled by O.Transfer. P. UpdateControl is upheld by OE.UpgradeSoftware and O.AccessControl. A.Ext_Key is upheld OE.External Device. A.TrustedManufacturer is upheld by OE.Manufacturing and OE.TestEnvironment. A.Control is upheld by OE.Control. A. AuthorisedService is upheld by OE.TrustedUser. A.Initialisation is upheld by OE.KeyGeneration, OE.SecureEnvironment and OE.KeyTransportation. A.Activation is upheld by OE.Delivery. A.TrustedUser is upheld by OE.TrustedUser. A.Ext_Device Pairing is upheld by OE.Ext_Pairing 5. EXTENDED COMPONENTS DEFINITION This security target does not use any components defined as extensions to CC part 2. 6. SECURITY REQUIREMENTS This chapter describes the security functional and the assurance requirements which have to be fulfilled by the TOE. Those requirements comprise functional components from CC part 2 and the assurance components as defined for the Evaluation Assurance Level 2 from CC part 3. The following notations are used: Refinement operation (denoted in such a way that added words are in bold text and changed words are crossed out): is used to add details to a requirement, and thus further restricts a requirement. Selection operation (denoted by italicised bold text and placed in square bracket): is used to select one or more options provided by the [CC] in stating a requirement. Assignment operation (denoted by underlined text and placed in square bracket): is used to assign a specific value to an unspecified parameter, such as the length of a password. Showing the value in square brackets indicates assignment. Iteration operation are identified with a slash (e.g. “(/)”) 6.1. Security Functional Requirements for the TOE This chapter defines the security functional requirements for the TOE according to the functional requirements components drawn from the CC part 2 version 3.1 revision 4. Perkon New Generation FCR Application Security Target Page 26 / 67 6.1.1. Class FAU Security Audit FAU_GEN Security audit data generation FAU_GEN.1 Audit data generation Hierarchical to: - Dependencies: FPT_STM.1 Reliable time stamps. FAU_GEN.1.1 The TSF shall be able to generate an audit record of the following auditable events: a) Start-up and shutdown of the audit functions; b) All auditable events for the [not specified] level of audit; and c) [the auditable security events specified in PRA messaging protocol document [6] ] FAU_GEN.1.2 The TSF shall record within each audit record at least the following information: a) Date and time of the event, type of event, subject identity, and the outcome (success or failure) of the event; and b) For each audit event type, based on the auditable event definitions of the functional components included in the PP/ST, [none] FAU_SAR Security audit review FAU_SAR.1 Audit review Hierarchical to: - Dependencies: FAU_GEN.1 Audit data generation. FAU_SAR.1.1 The TSF shall provide [Authorized Manufacturer User] with the capability to read [all event data] from the audit records. FAU_SAR.1.2 The TSF shall provide the audit records in a manner suitable for the user to interpret the information. FAU_STG Security audit event storage FAU_STG.1 Protected audit trail storage Hierarchical to: - Dependencies: FAU_GEN.1 Audit data generation FAU_STG.1.1 The TSF shall protect the stored audit records in the audit trail from unauthorised deletion. FAU_STG.1.2 The TSF shall be able to [prevent] unauthorised modifications to the stored audit records in the audit trail. FAU_STG.4 Prevention of audit data loss Hierarchical to: FAU_STG.3 Action in case of possible audit data loss Dependencies: FAU_STG.1 Protected audit trail storage FAU_STG.4.1 The TSF shall [overwrite the oldest stored audit records] and [none] if the audit trail is full. Perkon New Generation FCR Application Security Target Page 27 / 67 6.1.2. Class FCO Communication FCO_NRO Non-repudiation of origin FCO_NRO.2 Enforced proof of origin Hierarchical to: FCO_NRO.1 Selective proof of origin Dependencies: FIA_UID.1 Timing of identification FCO_NRO.2.1 The TSF shall enforce the generation of evidence of origin for transmitted [sales data and event data] at all times. FCO_NRO.2.2 The TSF shall be able to relate the [originator identity, time of origin] of the originator of the information, and the [body of the message] of the information to which the evidence applies. FCO_NRO.2.3 The TSF shall provide a capability to verify the evidence of origin of information to [recipient] given [immediately]. 6.1.3. Class FCS Cryptographic Support FCS_CKM Cryptographic key management FCS_CKM.1/ TRMK Cryptographic key generation Hierarchical to: - Dependencies: [FCS_CKM.2 Cryptographic key distribution, or FCS_COP.1 Cryptographic operation] FCS_CKM.4 Cryptographic key destruction FCS_CKM.1.1 The TSF shall generate cryptographic keys in accordance with a specified cryptographic key generation algorithm [RNG] and specified cryptographic key sizes [256 bits] that meet the following: [NIST SP800-90A]. FCS_CKM.1/TLS_AES Cryptographic key generation Hierarchical to: - Dependencies: [FCS_CKM.2 Cryptographic key distribution, or FCS_COP.1 Cryptographic operation] FCS_CKM.4 Cryptographic key destruction FCS_CKM.1.1 The TSF shall generate cryptographic keys in accordance with a specified cryptographic key generation algorithm [PRF] and specified cryptographic key sizes [AES:128 bits and/or AES:256 bits] that meet the following: [RFC 5246]. FCS_CKM.1/TLS_HMAC Cryptographic key generation Hierarchical to: - Dependencies: [FCS_CKM.2 Cryptographic key distribution, or FCS_COP.1 Cryptographic operation] Perkon New Generation FCR Application Security Target Page 28 / 67 FCS_CKM.4 Cryptographic key destruction FCS_CKM.1.1 The TSF shall generate cryptographic keys in accordance with a specified cryptographic key generation algorithm [PRF] and specified cryptographic key sizes [256 bit] that meet the following: [RFC 5246]. FCS_CKM.1/ DHE-KEY Cryptographic key generation Hierarchical to: - Dependencies: [FCS_CKM.2 Cryptographic key distribution, or FCS_COP.1 Cryptographic operation] FCS_CKM.4 Cryptographic key destruction FCS_CKM.1.1 The TSF shall generate cryptographic keys in accordance with a specified cryptographic key generation algorithm [RNG] and specified cryptographic key sizes [2048 bits] that meet the following: [NIST SP800-90A]. FCS_CKM.1/ EXT-DEV KHMAC Cryptographic key generation Hierarchical to: - Dependencies: [FCS_CKM.2 Cryptographic key distribution, or FCS_COP.1 Cryptographic operation] FCS_CKM.4 Cryptographic key destruction FCS_CKM.1.1 The TSF shall generate cryptographic keys in accordance with a specified cryptographic key generation algorithm [PRF] and specified cryptographic key sizes [256 bits] that meet the following: [RFC 5246]. FCS_CKM.1/ EXT-DEV KENC Cryptographic key generation Hierarchical to: - Dependencies: [FCS_CKM.2 Cryptographic key distribution, or FCS_COP.1 Cryptographic operation] FCS_CKM.4 Cryptographic key destruction FCS_CKM.1.1 The TSF shall generate cryptographic keys in accordance with a specified cryptographic key generation algorithm [PRF] and specified cryptographic key sizes [AES:256 bits] that meet the following: [RFC 5246]. FCS_CKM.2 Cryptographic key distribution Hierarchical to: - Dependencies: [[FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4 Cryptographic key destruction FCS_CKM.2.1 The TSF shall distribute cryptographic keys in accordance with a specified cryptographic key distribution method [according to PRA Messaging Protocol Document [6]] that meets the following: [none]. Perkon New Generation FCR Application Security Target Page 29 / 67 FCS_CKM.4 Cryptographic key destruction Hierarchical to: - Dependencies: [FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4.1 The TSF shall destroy cryptographic keys in accordance with a specified cryptographic key destruction method [as specified below] that meets the following: [none]. FCS_COP Cryptographic operation FCS_COP.1/TREK Cryptographic operation Hierarchical to: - Dependencies: [FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4 Cryptographic key destruction FCS_COP.1.1 The TSF shall perform [encryption] in accordance with a specified cryptographic algorithm [AES in CBC mode] and cryptographic key sizes [AES:256 bits] that meet the following: [NIST SP800-38A (CBC.AES256)]. FCS_COP.1/TRAK Cryptographic operation Hierarchical to: - Dependencies: [FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4 Cryptographic key destruction FCS_COP.1.1 The TSF shall perform [encryption and decryption for integrity protection] in accordance with a specified cryptographic algorithm [AES in CBC mode] and cryptographic key sizes [AES:256 bits] that meet the following: [NIST SP800-38A (CBC.AES256)]. FCS_COP.1/ TRMK-DEC Cryptographic operation Hierarchical to: - Dependencies: [FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4 Cryptographic key destruction FCS_COP.1.1 The TSF shall perform [decryption] in accordance with a specified cryptographic algorithm [AES in CBC mode] and cryptographic key sizes [AES:256 bits] that meet the following: [NIST SP800-38A (CBC.AES256)]. Perkon New Generation FCR Application Security Target Page 30 / 67 FCS_COP.1/PUB-ENC Cryptographic operation Hierarchical to: - Dependencies: [FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4 Cryptographic key destruction FCS_COP.1.1 The TSF shall perform [encryption] in accordance with a specified cryptographic algorithm [RSA] and cryptographic key sizes [2048 bits] that meet the following: [PKCS#1 v2.1 (RSAES-PKCS1-v1_5)]. FCS_COP.1/SIGN-VER Cryptographic operation Hierarchical to: - Dependencies: [FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4 Cryptographic key destruction FCS_COP.1.1 The TSF shall perform [signature verification] in accordance with a specified cryptographic algorithm [RSA] and cryptographic key sizes [2048 bits] that meet the following: [PKCS#1 v1.5, SHA256 Type 2 (random padding)]. FCS_COP.1/ENC-DEC Cryptographic operation Hierarchical to: - Dependencies: [FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4 Cryptographic key destruction FCS_COP.1.1 The TSF shall perform [encryption, decryption] in accordance with a specified cryptographic algorithm [AES] and cryptographic key sizes [AES:128 bits and AES:256 bits] that meet the following: [NIST SP800-38A]. FCS_COP.1/INT-AUTH Cryptographic operation Hierarchical to: - Dependencies: [FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4 Cryptographic key destruction FCS_COP.1.1 The TSF shall perform [authentication and integrity protection] in accordance with a specified cryptographic algorithm [HMAC-SHA256] and cryptographic key sizes [256 bits] that meet the following: [FIPS 198-1 and NIST FIPS PUB 180-2]. Perkon New Generation FCR Application Security Target Page 31 / 67 FCS_COP.1/HASHING Cryptographic operation Hierarchical to: - Dependencies: [FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4 Cryptographic key destruction FCS_COP.1.1 The TSF shall perform [hashing] in accordance with a specified cryptographic algorithm [SHA2] and cryptographic key sizes [none] that meet the following: [NIST FIPS PUB 180-2]. FCS_COP.1/EXT-DEV KEYEXCHANGE Cryptographic operation Hierarchical to: - Dependencies: [FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4 Cryptographic key destruction FCS_COP.1.1 The TSF shall perform [key exchange] in accordance with a specified cryptographic algorithm [DHE] and cryptographic key sizes [2048 bits] that meet the following: [NIST SP 800-56A]. FCS_COP.1/ EXT-DEV KENC Cryptographic operation Hierarchical to: - Dependencies: [FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4 Cryptographic key destruction FCS_COP.1.1 The TSF shall perform [encryption and decryption] in accordance with a specified cryptographic algorithm [AES with CBC] and cryptographic key sizes [256 bits] that meet the following: [NIST SP800-38A (CBC.AES256)]. FCS_COP.1/ EXT-DEV KHMAC Cryptographic operation Hierarchical to: - Dependencies: [FDP_ITC.1 Import of user data without security attributes, or FDP_ITC.2 Import of user data with security attributes, or FCS_CKM.1 Cryptographic key generation] FCS_CKM.4 Cryptographic key destruction FCS_COP.1.1 The TSF shall perform [encryption and decryption for integrity protection] in accordance with a specified cryptographic algorithm [HMAC-SHA256] and cryptographic key sizes [256 bits] that meet the following: [FIPS 198-1 and NIST FIPS PUB 180-2]. Perkon New Generation FCR Application Security Target Page 32 / 67 6.1.4. Class FDP User Data Protection FDP_ACC Access control policy FDP_ACC.1 Subset access control Hierarchical to: - Dependencies: FDP_ACF.1 Security attribute based access control FDP_ACC.1.1 The TSF shall enforce the [Administrative Access Control SFP ] on [Subjects: FCR Authorised User and Authorised Manufacturer User Objects: Sales and event data, exchange rates, time information. Operations: Secure state mode and maintenance mode actions], [none] FDP_ACF Access control functions FDP_ACF.1 Security attribute based access control Hierarchical to: - Dependencies: FDP_ACC.1 Subset access control FMT_MSA.3 Static attribute initialisation FDP_ACF.1.1 The TSF shall enforce the [Administrative Access Control SFP] to objects based on the following: [Subjects: FCR Authorised User and Authorised Manufacturer User Subject Attributes: Privileges Objects: Sales and event data, exchange rates, time information. Object Attributes: Access Control List (Secure State Mode and Maintenance Mode access rights). Operations: Secure state mode and maintenance mode actions describe in Section 3.1.3], [none]. FDP_ACF.1.2 The TSF shall enforce the following rules to determine if an operation among controlled subjects and controlled objects is allowed: [verify the operator’s privileges]. FDP_ACF.1.3 The TSF shall explicitly authorise access of subjects to objects based on the following additional rules: [none]. FDP_ACF.1.4 The TSF shall explicitly deny access of subjects to objects based on the following additional rules: [none]. FDP_ETC Export from the TOE FDP_ETC.2/TSM Export of user data with security attributes Hierarchical to: - Dependencies: [FDP_ACC.1 Subset access control, or FDP_IFC.1 Subset information flow control] FDP_ETC.2.1 The TSF shall enforce the [Information Flow Control SFP with TSM and PRA-IS] when exporting user data, controlled under the SFP(s), outside of the TOE. FDP_ETC.2.2 The TSF shall export the user data with the user data's associated security attributes. Perkon New Generation FCR Application Security Target Page 33 / 67 FDP_ETC.2.3 The TSF shall ensure that the security attributes, when exported outside the TOE, are unambiguously associated with the exported user data. FDP_ETC.2.4 The TSF shall enforce the following rules when user data is exported from the TOE: [Communication with secure messaging according to PRA Messaging Protocol Document[6]]. Application Note 2: User data (sales data, event data and TRMK) are exported from FCR to the PRA-IS via TSM. FDP_ETC.2/EFT-POS/SMART PINPAD Export of user data with security attributes Hierarchical to: - Dependencies: [FDP_ACC.1 Subset access control, or FDP_IFC.1 Subset information flow control] FDP_ETC.2.1 The TSF shall enforce the [Information Flow Control SFP with EFT-POS/SMART PINPAD Device] when exporting user data, controlled under the SFP(s), outside of the TOE. FDP_ETC.2.2 The TSF shall export the user data with the user data's associated security attributes. FDP_ETC.2.3 The TSF shall ensure that the security attributes, when exported outside the TOE, are unambiguously associated with the exported user data. FDP_ETC.2.4 The TSF shall enforce the following rules when user data is exported from the TOE: [Communication with secure messaging according to External Device Communication Protocol Document [7]]. FDP_IFC Information flow control policy FDP_IFC.1/TSMCOMMUNICATION Subset information flow control Hierarchical to: - Dependencies: FDP_IFF.1 Simple security attributes FDP_IFC.1.1 The TSF shall enforce the [Information Flow Control SFP with TSM and PRA- IS] on [subjects (TSM and PRA-IS) and objects (sales data ,event data reports, FCR parameters), TREK, TRAK and TRMK as specified in PRA Messaging Protocol Document [6]] FDP_IFC.1/EFTPOS/SMART PINPADCOMMUNICATION Subset information flow control Hierarchical to: - Dependencies: FDP_IFF.1 Simple security attributes FDP_IFC.1.1 The TSF shall enforce the [Information Flow Control SFP with EFT-POS/SMART PINPAD Device] on [subjects (EFT-POS/SMART PINPAD) and objects (amount information in sales data, and outcome of the operation, slip data request, EOD requests, loyalty card operation commands, bank selection command, other Perkon New Generation FCR Application Security Target Page 34 / 67 banking operational commands, EFT-POS/SMART PINPAD status commands, etc) as specified in External Device Communication Protocol Document [7] ] FDP_IFF Information flow control functions FDP_IFF.1/TSMCOMMUNICATION Simple security attributes Hierarchical to: - Dependencies: FDP_IFC.1 Subset information flow control FMT_MSA.3 Static attribute initialisation FDP_IFF.1.1 The TSF shall enforce the [Information Flow Control SFP with TSM and PRA-IS] based on the following types of subject and information security attributes: [TOE has ability to send reports related to sales data and event data reports and TRMK to PRA-IS by using subject identifier(IP/Port information) and object identifier (file name);TOE has ability to receive TREK and TRAK from PRA-IS by using subject identifier (IP/Port information) and object identifier (information label) according to PRA Messaging Protocol Document [6]; TOE has ability to receive FCR parameters from TSM by using subject identifier (IP/Port information) and object identifier (information label) according to PRA Messaging Protocol Document [6]]. FDP_IFF.1.2 The TSF shall permit an information flow between a controlled subject and controlled information via a controlled operation if the following rules hold: [Communication with secure messaging according to PRA Messaging Protocol Document [6]]. FDP_IFF.1.3 The TSF shall enforce the [none]. FDP_IFF.1.4 The TSF shall explicitly authorise an information flow based on the following rules: [none]. FDP_IFF.1.5 The TSF shall explicitly deny an information flow based on the following rules: [none]. FDP_IFF.1/ EFT-POS/SMART PINPADCOMMUNICATION Simple security attributes Hierarchical to: - Dependencies: FDP_IFC.1 Subset information flow control FMT_MSA.3 Static attribute initialisation FDP_IFF.1.1 The TSF shall enforce the [Information Flow Control SFP with EFT-POS/SMART PINPAD Device] based on the following types of subject and information security attributes: [TOE has ability to send amount information to EFT-POS/SMART PINPAD Device by using subject identifier (EFT-POS/SMART PINPAD label and source port).TOE has ability to receive outcome of the operation conducted by the EFT-POS/SMART PINPAD Device by using subject identifier (source port)]. FDP_IFF.1.2 The TSF shall permit an information flow between a controlled subject and controlled information via a controlled operation if the following rules hold: [Communication with secure messaging according to External Device Communication Protocol Document [7]]. FDP_IFF.1.3 The TSF shall enforce the [none]. FDP_IFF.1.4 The TSF shall explicitly authorise an information flow based on the following rules: [none]. FDP_IFF.1.5 The TSF shall explicitly deny an information flow based on the following rules: [none]. Perkon New Generation FCR Application Security Target Page 35 / 67 FDP_ITC Import from the outside of the TOE FDP_ITC.2/TSM Import of user data with security attributes Hierarchical to: - Dependencies: [FDP_ACC.1 Subset access control, or FDP_IFC.1 Subset information flow control] [FTP_ITC.1 Inter-TSF trusted channel, or FTP_TRP.1 Trusted path] FPT_TDC.1 Inter-TSF basic TSF data consistency FDP_ITC.2.1 The TSF shall enforce the [Information Flow Control SFP with TSM and PRA-IS] when importing user data, controlled under the SFP, from outside of the TOE. FDP_ITC.2.2 The TSF shall use the security attributes associated with the imported user data. FDP_ITC.2.3 The TSF shall ensure that the protocol used provides for the unambiguous association between the security attributes and the user data received. FDP_ITC.2.4 The TSF shall ensure that interpretation of the security attributes of the imported user data is as intended by the source of the user data. FDP_ITC.2.5 The TSF shall enforce the following rules when importing user data controlled under the SFP from outside the TOE: [Communication with secure messaging according to PRA Messaging Protocol Document [6]]. Application Note 3: FCR parameters are imported from TSM to TOE. TREK and TRAK are imported from PRA-IS to TOE FDP_ITC.2/ EFT-POS/SMART PINPAD Import of user data with security attributes Hierarchical to: - Dependencies: [FDP_ACC.1 Subset access control, or FDP_IFC.1 Subset information flow control] [FTP_ITC.1 Inter-TSF trusted channel, or FTP_TRP.1 Trusted path] FPT_TDC.1 Inter-TSF basic TSF data consistency FDP_ITC.2.1 The TSF shall enforce the [Information Flow Control SFP with EFT-POS/SMART PINPAD Device] when importing user data, controlled under the SFP, from outside of the TOE. FDP_ITC.2.2 The TSF shall use the security attributes associated with the imported user data. FDP_ITC.2.3 The TSF shall ensure that the protocol used provides for the unambiguous association between the security attributes and the user data received. FDP_ITC.2.4 The TSF shall ensure that interpretation of the security attributes of the imported user data is as intended by the source of the user data. FDP_ITC.2.5 The TSF shall enforce the following rules when importing user data controlled under the SFP from outside the TOE: [Communication with secure messaging according to External Device Communication Protocol Document [7]]. FDP_SDI Stored data integrity FDP_SDI.2/MEMORY Stored data integrity monitoring and action Hierarchical to: FDP_SDI.1 Stored data integrity monitoring Dependencies: - FDP_SDI.2.1 The TSF shall monitor user data sales data stored in fiscal memory and ERU, event data and characterization data stored in containers controlled by the TSF for Perkon New Generation FCR Application Security Target Page 36 / 67 [integrity errors] on all objects, based on the following attributes: [assignment: user data attributes]. FDP_SDI.2.2 Upon detection of a data integrity error, the TSF shall [Generate an audit event and then enter into the maintenance mode] FDP_SDI.2/ DAILY and PRMTR Stored data integrity monitoring and action Hierarchical to: FDP_SDI.1 Stored data integrity monitoring Dependencies: - FDP_SDI.2.1 The TSF shall monitor user data sales data stored in daily memory and FCR Parameters stored in containers controlled by the TSF for [integrity errors] on all objects, based on the following attributes: [assignment: user data attributes]. FDP_SDI.2.2 Upon detection of a data integrity error, the TSF shall [generate an audit event and print Z report automatically] 6.1.5. Class FIA Identification and Authentication FIA_AFL Authentication failures FIA_AFL.1/MANUFACTURER Authentication failure handling Hierarchical to: - Dependencies: FIA_UAU.1 Timing of authentication FIA_AFL.1.1 The TSF shall detect when [three] unsuccessful authentication attempts occur related to [Authorised Manufacturer User authentication]. FIA_AFL.1.2 When the defined number of unsuccessful authentication attempts has been [met], the TSF shall [warn the user and make user wait for a new authentication attempt for 15 minutes]. FIA_AFL.1/AUTHORISED Authentication failure handling Hierarchical to: - Dependencies: FIA_UAU.1 Timing of authentication FIA_AFL.1.1 The TSF shall detect when [three] unsuccessful authentication attempts occur related to [FCR Authorised User]. FIA_AFL.1.2 When the defined number of unsuccessful authentication attempts has been [met], the TSF shall [warn the user and make user wait for a new authentication attempt for 15 minutes]. FIA_UAU User authentication FIA_UAU.1 Timing of authentication Hierarchical to: - Perkon New Generation FCR Application Security Target Page 37 / 67 Dependencies: FIA_UID.1 Timing of identification FIA_UAU.1.1 The TSF shall allow [to do fiscal sales and to get FCR reports (except fiscal reports)] on behalf of the user to be performed before the user is authenticated. FIA_UAU.1.2 The TSF shall require each user to be successfully authenticated before allowing any other TSF-mediated actions on behalf of that user FIA_UAU.4 Single-use authentication mechanisms Hierarchical to: - Dependencies: - FIA_UAU.4.1 The TSF shall prevent reuse of authentication data related to [the authentication mechanism employed to authenticate Authorised Manufacturer User]. FIA_UID User Identification FIA_UID.1 Timing of identification Hierarchical to: - Dependencies: - FIA_UID.1.1 The TSF shall allow [to do fiscal sales and to get FCR report (except fiscal reports)] on behalf of the user to be performed before the user is identified. FIA_UID.1.2 The TSF shall require each user to be successfully identified before allowing any other TSF-mediated actions on behalf of that user. 6.1.6. Class FMT Security Management FMT_MOF Management of security functions behaviour FMT_MOF.1 Management of security functions behaviour Hierarchical to: - Dependencies: FMT_SMR.1 Security roles FMT_SMF.1 Specification of Management Functions FMT_MOF.1.1 The TSF shall restrict the ability to [modify the behaviour of] the functions [New Generation Cash Register Application Software normal operation functions] to [assignment: the authorised identified roles]nobody. Application Note 4: No authorised user makes the changes on the behaviour of the functions. The TSF itself makes the behavioral changes according to the FCR parameters received from TSM. Application Note 5: Ability to Modification of behaviour shall be used according to PRA directives. Normal operation functions include all FCR parameters that are sent to FCR by TSM. FMT_MSA Management of security attributes FMT_MSA.1/PRIVILEGES Management of security attributes Hierarchical to: - Perkon New Generation FCR Application Security Target Page 38 / 67 Dependencies: [FDP_ACC.1 Subset access control, or FDP_IFC.1 Subset information flow control] FMT_SMR.1 Security roles FMT_SMF.1 Specification of Management Functions FMT_MSA.1.1 The TSF shall enforce the [Administrative Access Control SFP] to restrict the ability to [modify] the security attributes [Privileges and Access Control List] to [none]. FMT_MSA.1/IP:PORT INFO Management of security attributes Hierarchical to: - Dependencies: [FDP_ACC.1 Subset access control, or FDP_IFC.1 Subset information flow control] FMT_SMR.1 Security roles FMT_SMF.1 Specification of Management Functions FMT_MSA.1.1 The TSF shall enforce the [Information Flow Control SFP with TSM and PRA-IS] to restrict the ability to [modify] the security attributes [IP:Port Information] to [Authorised Manufacturer User]. FMT_MSA.1/FILE NAME and INFO-LABEL Management of security attributes Hierarchical to: - Dependencies: [FDP_ACC.1 Subset access control, or FDP_IFC.1 Subset information flow control] FMT_SMR.1 Security roles FMT_SMF.1 Specification of Management Functions FMT_MSA.1.1 The TSF shall enforce the [Information Flow Control SFP with TSM and PRA-IS] to restrict the ability to [modify] the security attributes [file name and information label] to [none]. FMT_MSA.1/ EFT-POS/SMART PINPADSOURCE PORT INFO Management of security attributes Hierarchical to: - Dependencies: [FDP_ACC.1 Subset access control, or FDP_IFC.1 Subset information flow control] FMT_SMR.1 Security roles FMT_SMF.1 Specification of Management Functions FMT_MSA.1.1 The TSF shall enforce the [Information Flow Control SFP with EFT- POS/SMART PINPAD Devices] to restrict the ability to [modify] the security attributes [Source Port] to [none]. FMT_MSA.1/ EFT-POS/SMART PINPAD LABEL INFO Management of security attributes Hierarchical to: - Dependencies: [FDP_ACC.1 Subset access control, or FDP_IFC.1 Subset information flow control] FMT_SMR.1 Security roles FMT_SMF.1 Specification of Management Functions Perkon New Generation FCR Application Security Target Page 39 / 67 FMT_MSA.1.1 The TSF shall enforce the [Information Flow Control SFP with EFT- POS/SMART PINPAD Device] to restrict the ability to [modify] the security attributes [EFT-POS/SMART PINPAD Label] to [none]. FMT_MSA.3/USERS and SYSTEMS Static attribute initialisation Hierarchical to: - Dependencies: FMT_MSA.1 Management of security attributes FMT_SMR.1 Security roles FMT_MSA.3.1 The TSF shall enforce the [Administrative Access Control SFP, Information Flow Control SFP with TSM and PRA-IS] to provide [restrictive] default values for security attributes that are used to enforce the SFP. FMT_MSA.3.2 The TSF shall allow the [none] to specify alternative initial values to override the default values when an object or information is created. FMT_MSA.3/ EFT-POS/SMART PINPAD Static attribute initialisation Hierarchical to: - Dependencies: FMT_MSA.1 Management of security attributes FMT_SMR.1 Security roles FMT_MSA.3.1 The TSF shall enforce the [Information Flow Control SFP with EFT-POS/SMART PINPAD Device] to provide [permissive] default values for security attributes that are used to enforce the SFP. FMT_MSA.3.2 The TSF shall allow the [none] to specify alternative initial values to override the default values when an object or information is created. FMT_MTD Management of TSF data FMT_MTD.1/FCR AUTHORISED USER Management of TSF data Hierarchical to: - Dependencies: FMT_SMR.1 Security roles FMT_SMF.1 Specification of Management Functions FMT_MTD.1.1 The TSF shall restrict the ability to [modify] the [FCR Authorised User’s authentication data] to [FCR Authorised User and FCR Authorised Manufacturer User] FMT_MTD.1/AUTHORISED MANUFACTURER USER Management of TSF data Hierarchical to: - Dependencies: FMT_SMR.1 Security roles FMT_SMF.1 Specification of Management Functions FMT_MTD.1.1 The TSF shall restrict the ability to [create] the [Authorised Manufacturer User’s authentication data] to [assignment: the authorised identified roles] [nobody]. Application Note 6: No authorised identified roles make the changes on Authorized Manufacturer User’s authentication data but TSM creates it. Perkon New Generation FCR Application Security Target Page 40 / 67 FMT_SMF Specification of Management Functions FMT_SMF.1 Specification of Management Functions Hierarchical to: - Dependencies: - FMT_SMF.1.1 The TSF shall be capable of performing the following management functions: [Authorised Manufacturer User modifies IP: Port Information, FCR Authorised User modifies FCR Authorised User’s authentication data, Authorised Manufacturer User modifies FCR Authorised User’s authentication data] FMT_SMR Security management roles FMT_SMR.2 Restrictions on security roles Hierarchical to: FMT_SMR.1 Security roles Dependencies: FIA_UID.1 Timing of identification FMT_SMR.2.1 The TSF shall maintain the roles: [FCR Authorised User and Authorised Manufacturer User]. FMT_SMR.2.2 The TSF shall be able to associate users with roles. FMT_SMR.2.3 The TSF shall ensure that the conditions [Authorised Manufacturer User shall take action in maintenance works, FCR authorised user takes action in secure state works] are satisfied. 6.1.7. Class FPT Protection of the TSF FPT_FLS Fail secure FPT_FLS.1 Failure with preservation of secure state Hierarchical to: - Dependencies: - FPT_FLS.1.1 The TSF shall preserve a secure state when the following types of failures occur:[except maintenance mode events that specified in section 3.1.3] FPT_PHP TSF physical protection FPT_PHP.2 Notification of physical attack Hierarchical to: FPT_PHP.1 Passive detection of physical attack Dependencies: FMT_MOF.1 Management of security functions behaviour FPT_PHP.2.1 The TSF shall provide unambiguous detection of physical tampering that might compromise the TSF. FPT_PHP.2.2 The TSF shall provide the capability to determine whether physical tampering with the TSF's devices or TSF's elements has occurred. FPT_PHP.2.3 For [the devices/elements for which active detection is required in Technical Guidance Document [5]], and elements and notify [all user] when physical tampering with the TSF's devices or TSF's elements has occurred. Perkon New Generation FCR Application Security Target Page 41 / 67 FPT_RCV Trusted recovery FPT_RCV.1 Manual recovery Hierarchical to: - Dependencies: AGD_OPE.1 Operational user guidance FPT_RCV.1.1 After [maintenance mode events which expressed in section 3.1.3 occur] the TSF shall enter a maintenance mode where the ability to return to a secure state is provided. FPT_RCV.4 Function recovery Hierarchical to: - Dependencies: - FPT_RCV.4.1 The TSF shall ensure that [except maintenance mode events that specified in section 3.1.3] have the property that the function either completes successfully, or for the indicated failure scenarios, recovers to a consistent and secure state. FPT_STM Time stamps FPT_STM.1 Reliable time stamps Hierarchical to: - Dependencies: - FPT_STM.1.1 The TSF shall be able to provide reliable time stamps. FPT_TDC Inter-TSF TSF data consistency FPT_TDC.1/TSM Inter-TSF basic TSF data consistency Hierarchical to: - Dependencies: - FPT_TDC.1.1 The TSF shall provide the capability to consistently interpret [CheckSum] when shared between the TSF and another trusted IT product. FPT_TDC.1.2 The TSF shall use [Communication with secure messaging according to PRA Messaging Protocol Document [6]] when interpreting the TSF data from another trusted IT product. FPT_TDC.1/EFT-POS/SMART PINPAD Inter-TSF basic TSF data consistency Hierarchical to: - Dependencies: - FPT_TDC.1.1 The TSF shall provide the capability to consistently interpret [CheckSum] when shared between the TSF and another trusted IT product. FPT_TDC.1.2 The TSF shall use [Communication with secure messaging according to External Device Communication Protocol Document [7]] when interpreting the TSF data from another trusted IT product. Perkon New Generation FCR Application Security Target Page 42 / 67 FPT_TEE Testing of external entities FPT_TEE.1/EXT Testing of external entities Hierarchical to: - Dependencies: - FPT_TEE.1.1 The TSF shall run a suite of tests [during initial start-up and during fiscal transactions] to check the fulfilment of [proper working of external entities]. FPT_TEE.1.2 If the test fails, the TSF shall [generate an audit event according to PRA Messaging Protocol Document [6] ] Application Note 7: External entities are ERU, Fiscal Memory, Daily Memory, Mesh Cover and Electronic Seal. FPT_TEE.1/TIME Testing of external entities Hierarchical to: - Dependencies: - FPT_TEE.1.1 The TSF shall run a suite of tests [during time synchronization with NTP] to check the fulfilment of [accuracy of time information]. FPT_TEE.1.2 If the test fails, the TSF shall [overwrite time information received from trusted server, generate an audit event according to Technical Guidance Document [5] ] 6.1.8. Class FTP Trusted Patch/Channels FTP_ITC Inter-TSF trusted channel FTP_ITC.1/TSM Inter-TSF trusted channel Hierarchical to: - Dependencies: - FTP_ITC.1.1 The TSF shall provide a communication channel between itself and another trusted IT product that is logically distinct from other communication channels and provides assured identification of its end points and protection of the channel data from modification or disclosure. FTP_ITC.1.2 The TSF shall permit [the TSF] to initiate communication via the trusted channel. FTP_ITC.1.3 The TSF shall initiate communication via the trusted channel for [sending user data (sales, event data and TRMK) to PRA-IS; receiving user data (TREK and TRAK) from PRA-IS and receiving user data (FCR parameters and exchange rates) from TSM]. FTP_ITC.1/EFT-POS/SMART PINPAD Inter-TSF trusted channel Hierarchical to: - Dependencies: - FTP_ITC.1.1 The TSF shall provide a communication channel between itself and another trusted IT product that is logically distinct from other communication channels and provides assured identification of its end points and protection of the channel data from modification or disclosure. FTP_ITC.1.2 The TSF shall permit [the TSF] to initiate communication via the trusted channel. Perkon New Generation FCR Application Security Target Page 43 / 67 FTP_ITC.1.3 The TSF shall initiate communication via the trusted channel for [sending amount information to EFT-POS/SMART PINPAD and receiving outcome of the operation from EFT-POS/SMART PINPAD]. 6.2. Security Assurance Requirements for the TOE The assurance requirements for the evaluation of the TOE and for its development and operating environment are chosen as the predefined assurance package EAL2. 6.3. Security Requirements Rationale 6.3.1. Security Functional Requirements Rationale Table 3 provides an overview for security functional requirements coverage and also giving an evidence for sufficiency and necessity of the SFRs chosen. Table 3 Coverage of security objectives by SFRs for TOE O.AccessControl O.Event O.Integrity O.Authentication O.Function O.Transfer FAU_GEN.1 Audit data generation X FAU_SAR.1 Audit review X FAU_STG.1 Protected audit trail storage X FAU_STG.4 Prevention of audit data loss X FCO_NRO.2 Enforced proof of origin X FCS_CKM.1/TRMK Cryptographic key generation X FCS_CKM.2 Cryptographic key distribution X FCS_CKM.1/TLS_AES Cryptographic key generation X FCS_CKM.1/TLS_HMAC Cryptographic key generation X FCS_CKM.1/ DHE-KEY Cryptographic key generation X FCS_CKM.1/ EXT-DEV KENC Cryptographic key generation X FCS_CKM.1/ EXT-DEV Khmac Cryptographic key generation X FCS_CKM.4 Cryptographic key destruction X Perkon New Generation FCR Application Security Target Page 44 / 67 O.AccessControl O.Event O.Integrity O.Authentication O.Function O.Transfer FCS_COP.1/TREK Cryptographic operation X FCS_COP.1/TRAK Cryptographic operation X FCS_COP.1/ ENC-DEC Cryptographic operation X FCS_COP.1/INT-AUTH Cryptographic operation X FCS_COP.1/HASHING Cryptographic operation X FCS_COP.1/TRMK-DEC Cryptographic operation X FCS_COP.1/PUB-ENC Cryptographic operation X FCS_COP.1/SIGN-VER Cryptographic operation X FCS_COP.1/EXT-DEV KENC Cryptographic operation X FCS_COP.1/EXT-DEV KHMAC Cryptographic operation X FCS_COP.1/EXT-DEV KEYEXCHANGE Cryptographic operation X FDP_ACC.1 Subset access control X FDP_ACF.1 Security attribute based access control X FDP_ETC.2/TSM Export of user data with security attributes X FDP_ETC.2/EFTPOS/SMART PINPAD Export of user data with security attributes X FDP_IFC.1/TSMCOMMUNICA TION Subset information flow control X FDP_IFC.1/EFTPOS/SMART PINPADCOMMUNICATI ON Subset information flow control X FDP_IFF.1/TSMCOMMUNICA TION Simple security attributes X Perkon New Generation FCR Application Security Target Page 45 / 67 O.AccessControl O.Event O.Integrity O.Authentication O.Function O.Transfer FDP_IFF.1/EFTPOS/SMART PINPADCOMMUNICATI ON Simple security attributes X FDP_ITC.2/TSM Import of user data with security attributes X FDP_ITC.2/EFTPOS/SMART PINPAD Import of user data with security attributes X FDP_SDI.2/MEMORY Stored data integrity monitoring and action X FDP_SDI.2/DAILY and PRMTR Stored data integrity monitoring and action X FIA_AFL.1/MANUFACTURER Authentication failure handling X FIA_AFL.1/AUTHORISED Authentication failure handling X FIA_UAU.1 Timing of authentication X FIA_UAU.4 Single-use authentication mechanisms X FIA_UID.1 Timing of identification X FMT_MOF.1 Management of security functions behaviour X FMT_MSA.1/PRIVILEGES Management of security attributes X FMT_MSA.1/IP:PORT INFO Management of security attributes X FMT_MSA.1/FILE NAME and INFO-LABEL Management of security attributes X FMT_MSA.1/EFTPOS/SMART PINPAD SOURCE PORT INFO Management of security attributes X FMT_MSA.1/EFTPOS/SMART PINPAD LABEL INFO Management of security attributes X FMT_MSA.3/USERS and SYSTEMS Static attribute initialisation X X Perkon New Generation FCR Application Security Target Page 46 / 67 O.AccessControl O.Event O.Integrity O.Authentication O.Function O.Transfer FMT_MSA.3/EFTPOS/SMART PINPAD Static attribute initialisation X FMT_MTD.1/FCR AUTHORISED USER Management of TSF data X X FMT_MTD.1/AUTHORISED MANUFACTURER USER Management of TSF data X FMT_SMF.1 Specification of Management Functions X FMT_SMR.2 Restrictions on security roles X FPT_FLS.1 Failure with preservation of secure state X FPT_PHP.2 Notification of physical attack X X FPT_RCV.1 Manual recovery X FPT_RCV.4 Function recovery X FPT_STM.1 Reliable time stamps X FPT_TDC.1/TSM Inter-TSF basic TSF data consistency X FPT_TDC.1/EFTPOS/SMART PINPAD Inter-TSF basic TSF data consistency X FPT_TEE.1/EXT Testing of external entities X FPT_TEE.1/TIME Testing of external entities X FTP_ITC.1/TSM Inter-TSF trusted channel X FTP_ITC.1/EFTPOS/SMART PINPAD Inter-TSF trusted channel X A detailed justification of required for suitability of the security functional requirements to achieve the security objectives is given in Table 4. Perkon New Generation FCR Application Security Target Page 47 / 67 Table 4 Suitability of the SFRs Security Objective Security Functional Requirement O.AccessControl FDP_ACC.1 Provides security functional policy for functions and data FDP_ACF.1 Defines security attributes for functions and data FAU_SAR.1 Allows users to read audit records FMT_MSA.1/PRIVILEG ES Provides the functions to restrict the ability to modify the security attributes (privileges) to nobody. FMT_MSA.3/USERS and SYSTEMS Provides the functions to provide restrictive default values for security attributes that are used to enforce the SFP and allows nobody to specify alternative initial values to override the default values when an object or information is created. FMT_SMF.1 Describe the specification of management functions being allowed to use in maintenance mode and secure state mode. FMT_SMR.2 Maintains the roles with restrictions FMT_MTD.1/AUTHO RISED MANUFACTURER USER Provides authorised processing of FCR Manufacturer User’s authentication data FMT_MTD.1/FCR AUTHORISED USER Provides authorised modification of FCR Authorised User’s authentication data O.Event FAU_GEN.1 Generates correct audit events FPT_STM.1 Provides accurate time for logging events O.Integrity FAU_STG.1 Protects stored audit data integrity from unauthorised deletion FAU_STG.4 Prevents loss of audit data loss FPT_PHP.2 Generation of audit event detection of physical tampering FDP_SDI.2/MEMORY Monitors user data stored for integrity errors Perkon New Generation FCR Application Security Target Page 48 / 67 FDP_SDI.2/DAILY and PRMTR Monitors user data stored for integrity errors FPT_TDC.1/TSM Provides the capability to consistently interpret TSF data (checksum) FPT_TDC.1/EFT- POS/SMART PINPAD Provides the capability to consistently interpret TSF data (checksum) O.Authentication FIA_AFL.1/MANUFAC TURER Detects and records authentication failure events for Authorised Manufacturer User FIA_AFL.1/ AUTHORISED Detects and records authentication failure events for FCR Authorised User FIA_UAU.1 Defines timing of user authentication FIA_UAU.4 Provides single use authentication mechanism for Authorised Manufacturer User FIA_UID.1 Defines timing of user identification FMT_MTD.1/ FCR AUTHORISED USER Provides authorised processing of FCR Authorised User’s authentication data FMT_MTD.1/ AUTHORISED MANUFACTURER USER Provides authorised processing of Authorised Manufacturer User’s authentication data FCS_COP.1/HASHING Provides authentication operation for PRA-IS and TSM O.Function FMT_MOF.1 Restricts the ability to enable the functions to nobody and, thus, prevents an unintended access to data in the operational phase. FPT_FLS.1 Failure types which makes new generation cash register fiscal application software continue working in secure state FPT_RCV.1 Provides new generation cash register fiscal application software start working in maintenance mode in failure. (has ability to switch to the secure state manually) FPT_RCV.4 Provides new generation cash register fiscal application software start working in maintenance Perkon New Generation FCR Application Security Target Page 49 / 67 mode in failure. (has ability to switch to the secure state automatically with functions) FPT_TEE.1/EXT Provides test for IT environment for functioning accurately FPT_TEE.1/TIME Provides test for time information for accuracy O.Transfer FCS_CKM.1/TLS_AES Generates session keys for communication between FCR-PRA-IS and FCR–TSM FCS_CKM.1/TRMK Generates session keys for communication between FCR-PRA-IS and FCR–TSM FCS_CKM.2 Provides cryptographic key distribution to generate keys FCS_CKM.1/TLS_HMA C Generates session keys for communication between FCR-PRA-IS and FCR–TSM FMT_MSA.1/EFT- POS/SMART PINPAD LABEL INFO Provides the functions to restrict the ability to modify the security attribute(EFT-POS label) to nobody FMT_MSA.1/FILE NAME and INFO- LABEL Provides the functions to restrict the ability to modify the security attribute (file name) to nobody FMT_MSA.1/ IP:PORT INFO Provides the functions to restrict the ability to modify the security attribute(IP/Port)to Authorised Manufacturer User FMT_MSA.1/EFT- POS/SMART PINPAD SOURCE PORT INFO Provides the functions to restrict the ability to modify the security attribute (EFT-POS source port) to nobody Perkon New Generation FCR Application Security Target Page 50 / 67 FMT_MSA.3/USERS and SYSTEMS Provides the functions to provide restrictive default values for security attributes that are used to enforce the SFP and allows nobody to specify alternative initial values to override the default values when an object or information is created FMT_MSA.3/EFT- POS/SMART PINPAD Provides the functions to provide permissive default values for security attributes that are used to enforce the SFP and allows nobody to specify alternative initial values to override the default values when an object or information is created FCS_CKM.4 Destroys cryptographic keys in the TOE FCS_COP.1/ENC-DEC Provides the cryptographic operation for secure communication between PRA-IS and new generation cash register fiscal application software, and between TSM and new generation cash register fiscal application software FCS_COP.1/INT-AUTH Provides authentication and integrity protection for communication between FCR-PRA-IS and FCR–TSM FCS_COP.1/TREK Provides the cryptographic operation for secure communication between PRA-IS and TOE FCS_COP.1/TRAK Provides authentication and integrity protection for communication between PRA-IS and TOE FCS_COP.1/TRMK- DEC Provides the cryptographic operation for secure communication between PRA-IS and TOE FCS_COP.1/PUB-ENC Provides the cryptographic operation for secure communication between PRA-IS-TOE FCS_COP.1/SIGN-VER Provides non-repudiation for TREK and TRAK sharing between PRA-IS and TOE. FCS_COP.1/HASHING Provides the cryptographic operation for secure communication between PRA-IS-TOE and TOE-TSM FPT_PHP.2 Generation of audit event detection of physical tampering FCO_NRO.2 Generates evidence of origin of the data to be transferred to the PRA-IS FCS_CKM.1/DHE-KEY Generates private key for DHE key agreement Perkon New Generation FCR Application Security Target Page 51 / 67 FCS_COP.1/EXT-DEV KENC Provides symmetric encryption in order to establish secure communication with External Devices. FCS_COP.1/EXT-DEV KHMAC Provides authentication and integrity protection for communication with External Devices. FCS_CKM.1/EXT-DEV KENC Generates keys for communication between TOE and External Devices FCS_CKM.1/EXT-DEV KHMAC Generates keys for communication between TOE and External Devices FCS_COP.1/EXT-DEV KEYEXCHANGE Provides asymmetric agreement operation with External Devices decryption for secure exchange of the symmetric key with EFT-POS/SMART PINPAD FDP_ETC.2/TSM Provides export of sales data and event data from the TOE to the PRA-IS using the information flow control SFP with TSM and PRA-IS FDP_ETC.2/EFT- POS/SMART PINPAD Provides export of amount information in sales data from the TOE to the EFT-POS using the information flow control SFP with EFT-POS/SMART PINPAD Devices FDP_IFC.1/TSMCOM MUNICATION Provides information flow control policy for TSM and PRA-IS communication FDP_IFC.1/EFT- POS/SMART PINPAD COMMUNICATION Provides information flow control policy for EFT- POS/SMART PINPAD communication FDP_IFF.1/TSMCOM MUNICATION Provides information flow control policy rules for TSM and PRA-IS communication FDP_IFF.1/EFT- POS/SMART PINPAD COMMUNICATION Provides information flow control policy rules for EFT-POS communication FDT_ITC.2/TSM Provides protection of FCR Parameters confidentiality and integrity during import from TSM FDT_ITC.2/EFT- POS/SMART PINPAD Provides protection of confidentiality and integrity of outcome of the operation conducted by the EFT- POS/SMART PINPAD device and AES keys (KENC and KHMAC)during import from EFT-POS/SMART PINPAD device. Perkon New Generation FCR Application Security Target Page 52 / 67 FTP_ITC.1/EFT- POS/SMART PINPAD Provides protection of data (confidentiality+integrity) during communication with EFT-POS by the help of secure channel FTP_ITC.1/TSM Provides protection of sales data and event data (confidentiality+integrity) during communication with PRA-IS by the help of secure channel 6.3.2. Rationale for SFR’s Dependencies Selected security functional requirements include related dependencies. Table 5 below provides a summary of the security functional requirements dependency analysis. Table 5 Security Functional Requirements dependencies Component Dependencies Included / not included FAU_GEN.1 FPT_STM.1 included FAU_SAR.1 FAU_GEN.1 included FAU_STG.1 FAU_GEN.1 included FAU_STG.4 FAU_STG.1 included FCO_NRO.2 FIA_UID.1 Non-repudiation of the origin satisfied for the event and sales data send from FCR not on behalf of each user but FCR itself. Requirement satisfied but the dependency is not fulfilled because of the operational requirement. FCS_CKM.1/TRMK FCS_CKM.2 or FCS_COP.1; FCS_CKM.4 FCS_CKM.2; FCS_COP.1 TRMK-DEC; FCS_CKM.4 included FCS_CKM.2 [FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1]; FCS_CKM.4 FCS_CKM.1/TRMK; FCS_CKM.4 FCS_CKM.1/TLS_AES FCS_CKM.2 or FCS_COP.1; FCS_CKM.4 FCS_COP.1/ENC-DEC and FCS_CKM.4 included FCS_CKM.1/TLS_HMAC FCS_CKM.2 or FCS_COP.1; FCS_CKM.4 FCS_COP.1/INT-AUTH and FCS_CKM.4 included Perkon New Generation FCR Application Security Target Page 53 / 67 Component Dependencies Included / not included FCS_CKM.1/EXT-DEV KENC FCS_CKM.2 or FCS_COP.1; FCS_CKM.4 FCS_COP.1/EXT-DEV KENC FCS_CKM.4 included FCS_CKM.1/EXT-DEV KHMAC FCS_CKM.2 or FCS_COP.1; FCS_CKM.4 FCS_COP.1/EXT-DEV KHMAC FCS_CKM.4 included FCS_CKM.4 FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1 FCS_CKM.1(FCS_CKM.1/ EXT-DEV KENC, FCS_CKM.1/ EXT-DEV KHMAC, FCS_CKM.1/TLS_HMAC, FCS_CKM.1/TLS_AES, FCS_CKM.1/TRMK, FCS_CKM.1/DHE-KEY ) included FCS_COP.1/TRAK FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1 ;FCS_CKM.4 FDP_ITC.2/TSM and FCS_CKM.4 included FCS_COP.1/TREK FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1 ;FCS_CKM.4 FDP_ITC.2/TSM and FCS_CKM.4 included FCS_COP.1/TRMK-DEC FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1 ;FCS_CKM.4 FCS_CKM.1/TRMK; FCS_CKM.4 FCS_COP.1/PUB-ENC FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1 ;FCS_CKM.4 According to PRA messaging protocol, there is no need to import key for this SFR. Key is imported during initialization. According to PRA messaging protocol, PPRA and PTSM public key should not be deleted. Tamper system of the TOE protects keys from misuse, disclosure or modification. FCS_COP.1/SIGN-VER FDP_ITC.1 or According to PRA messaging protocol, there is no need to import key for this Perkon New Generation FCR Application Security Target Page 54 / 67 Component Dependencies Included / not included FDP_ITC.2 or FCS_CKM.1 ;FCS_CKM.4 SFR. Key is imported during initialization. According to PRA messaging protocol, PPRA-SIGN public key should not be deleted. Tamper system of the TOE protects keys from misuse, disclosure or modification FCS_COP.1/ENC-DEC FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1; FCS_CKM.4 FCS_CKM.1/TLS_AES and FCS_CKM.4 included FCS_COP.1/INT-AUTH FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1; FCS_CKM.4 FCS_CKM.1/TLS_HMAC and FCS_CKM.4 included FCS_COP.1/HASHING FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1; FCS_CKM.4 No need to include any dependencies because there is no need to use any key for HASHING FCS_COP.1/DHE-KEY FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1; FCS_CKM.4 FCS_COP.1/ EXT-DEV KEYEXCHANGE and FCS_CKM.4 included. FCS_COP.1/EXT-DEV KENC FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1; FCS_CKM.4 FCS_CKM.1/ EXT-DEV KENC, FCS_CKM.4 included FCS_COP.1/EXT-DEV KHMAC FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1; FCS_CKM.4 FCS_CKM.1/ EXT-DEV KHMAC, FCS_CKM.4 included FCS_COP.1/ EXT-DEV KEYEXCHANGE FDP_ITC.1 or FDP_ITC.2 or FCS_CKM.1; FCS_CKM.4 FCS_CKM.1/ DHE-KEY and FCS_CKM.4 included FDP_ACC.1 FDP_ACF.1 included FDP_ACF.1 FDP_ACC.1; FMT_MSA.3 FDP_ACC.1; FMT_MSA.3/USERS and SYSTEMS included FDP_ETC.2/TSM FDP_ACC.1 or FDP_IFC.1 FDP_ACC.1; FDP_IFC.1/TSMCOMMUNICATION included FDP_ETC.2/EFT-POS/SMART PINPAD FDP_ACC.1 or FDP_IFC.1 FDP_ACC.1; FDP_IFC.1/EFTPOSCOMMUNICATION included FDP_IFC.1/TSMCOMMUNICATI ON FDP_IFF.1 FDP_IFF.1/TSMCOMMUNICATION included Perkon New Generation FCR Application Security Target Page 55 / 67 Component Dependencies Included / not included FDP_IFC.1/EFT-POS/SMART PINPADCOMMUNICATION FDP_IFF.1 FDP_IFF.1/EFT-POS/SMART PINPADCOMMUNICATION included FDP_IFF.1/TSMCOMMUNICATIO N FDP_IFC.1; FMT_MSA.3 FDP_IFC.1/TSMCOMMUNICATION; FMT_MSA.3/USERS and SYSTEMS included FDP_IFF.1/EFT-POS/SMART PINPADCOMMUNICATION FDP_IFC.1; FMT_MSA.3 FDP_IFC.1/EFT-POS/SMART PINPADCOMMUNICATION; FMT_MSA.3/EFT-POS/SMART PINPAD included FDP_ITC.2/TSM FDP_ACC.1 or FDP_IFC.1 ; FTP_ITC.1 or FTP_TRP.1 ; FPT_TDC.1 FDP_IFC.1/TSMCOMMUNICATION; FTP_ITC.1; FPT_TDC.1 included FDP_ITC.2/EFT-POS/SMART PINPAD FDP_ACC.1 or FDP_IFC.1 ; FTP_ITC.1 or FTP_TRP.1 ; FPT_TDC.1 FDP_IFC.1/EFT-POS/SMART PINPADCOMMUNICATION; FTP_ITC.1/EFT-POS/SMART PINPAD ; FPT_TDC.1/EFT-POS/SMART PINPAD included FDP_SDI.2/MEMORY No dependencies. - FDP_SDI.2/DAILY and PRMTR No dependencies. - FIA_AFL.1/MANUFACTURER FIA_UAU.1 included FIA_AFL.1/AUTHORISED FIA_UAU.1 included FIA_UAU.1 FIA_UID.1 included FIA_UAU.4 No dependencies - FIA_UID.1 No dependencies - FMT_MOF.1 FMT_SMR.1; FMT_SMF.1 FMT_SMR.2 is hierarchical to FMT_SMR.1; FMT_SMF.1 FMT_MSA.1/PRIVILEGES FDP_ACC.1 or FDP_IFC.1 FDP_ACC.1 included Perkon New Generation FCR Application Security Target Page 56 / 67 Component Dependencies Included / not included FMT_MSA.1/ IP:PORT INFO FDP_ACC.1 or FDP_IFC.1 FDP_IFC.1/TSMCOMMUNICATION included FMT_MSA.1/FILE NAME and INFO-LABEL FDP_ACC.1 or FDP_IFC.1 FDP_IFC.1/TSMCOMMUNICATION included FMT_MSA.1/EFT-POS/SMART PINPAD SOURCE PORT INFO FDP_ACC.1 or FDP_IFC.1 FDP_IFC.1/EFT-POS/SMART PINPADCOMMUNICATION included FMT_MSA.1/EFT-POS/SMART PINPAD LABEL INFO FDP_ACC.1 or FDP_IFC.1 FDP_IFC.1/EFT-POS/SMART PINPADCOMMUNICATION included FMT_MSA.3/USERS and SYSTEMS FMT_MSA.1; FMT_SMR.1 FMT_MSA.1 (FMT_MSA.1/PRIVILEGES, FMT_MSA.1/IP:PORT INFO, FMT_MSA.1/FILE NAME and INFO- LABEL) ; FMT_SMR.2 is hierarchical to FMT_SMR.1 included FMT_MSA.3/EFT-POS/SMART PINPAD FMT_MSA.1 ; FMT_SMR.1 FMT_MSA.1(FMT_MSA.1/EFT-POS LABEL INFO ) ; FMT_SMR.2 is hierarchical to FMT_SMR.1 included FMT_MTD.1/FCR AUTHORISED USER FMT_SMR.1 ; FMT_SMF.1 FMT_SMR.2 is hierarchical to FMT_SMR.1 ; FMT_SMF.1 included FMT_MTD.1/AUTHORISED MANUFACTURER USER FMT_SMR.1 ; FMT_SMF.1 FMT_SMR.2 is hierarchical to FMT_SMR.1 ; FMT_SMF.1 included FMT_SMF.1 No dependencies. - FMT_SMR.2 FIA_UID.1 included FPT_FLS.1 No dependencies - FPT_PHP.2 FMT_MOF.1 included FPT_RCV.1 AGD_OPE.1 included (assurance component) FPT_RCV.4 No dependencies - FPT_STM.1 No dependencies - Perkon New Generation FCR Application Security Target Page 57 / 67 Component Dependencies Included / not included FPT_TDC.1 No dependencies - FPT_TEE.1/EXT No dependencies - FPT_TEE.1/TIME No dependencies - FTP_ITC.1/TSM No dependencies - FTP_ITC.1/EFT-POS/SMART PINPAD No dependencies - 6.3.3. Security Assurance Requirements Rationale The current assurance package was chosen based on the pre-defined assurance packet EAL2. EAL2 is chosen because the threats that were chosen are consistent with an attacker of basic attack potential. 6.3.4. Security Requirements – Internal Consistency Set of security requirements for the TOE consisting of the security functional requirements (SFRs) and the security assurance requirements (SARs) together forms an internally consistent whole. The dependency analysis in section 6.3.2 Rationale for SFR’s Dependencies for the security functional requirements shows that the basis for internal consistency between all defined functional requirements is satisfied. All dependencies between the chosen functional components are analysed and non-satisfied dependencies are appropriately explained. The assurance package EAL2 is a pre-defined set of internally consistent assurance requirements. The dependency analysis for the sensitive assurance components in section 6.3.3 Security Assurance Requirements Rationale shows that the assurance requirements are internally consistent, because all (additional) dependencies are satisfied and no inconsistency appears. Inconsistency between functional and assurance requirements could only arise, if there are functional- assurance dependencies being not met – an opportunity having been shown not to arise in sections 6.3.2 Rationale for SFR’s Dependencies and 6.3.3 Security Assurance Requirements Rationale. Furthermore, as also discussed in section 6.3.3 Security Assurance Requirements Rationale, the chosen assurance components are adequate for the functionality of the TOE. So, there are no inconsistencies between the goals of these two groups of security requirements 7. 7. TOE SUMMARY SPECIFICATION 7.1. TOE Security Functions 7.1.1. Access Control Perkon New Generation FCR Application Security Target Page 58 / 67 TOE controls user ( FCR Authorised User, Authorised Manufacturer User) access to functions and data. Following security function policies is applied by TOE. Access Rules for assets:  Authorised Manufacturer User can change FCR Authorised User Identity password values to default.  Any user or TSM or PRA-IS cannot modify Privileges, secure state and maintenance mode access rights.  TSM or PRA–IS cannot modify Privileges, secure state and maintenance mode access rights.  Authorised Manufacturer User can modify IP: Port Information,  Authorised Manufacturer users are allowed to do their actions in only maintenance mode, FCR Authorised Users are allowed to their actions in only secure state mode.  FCR Authorised User’s password can be modified by FCR Authorised Users and Authorised Manufacturer Users.  No authorised identified roles make the changes on Authorised Manufacturer User’s authentication data (challenge-response code) but manufacturer trusted server creates it.  TOE allows only authorised users and systems to read relevant records. 7.1.2. Accuracy and event recording TOE ensures that processing of inputs to derive sales data and event data is accurate. TOE security functionality cannot be changed by any user. Only parameters are sent from TSM by acceptance of PRA is used for functionality change. Sales can be made and FCR reports(except fiscal reports) can be taken by unauthorised user. Fiscal reports can be taken by Authorised user. Event data is reviewed only if FCR is used by Authorised Manufacturer user. Authentication attempts are restricted to 3 try. If TOE enters in maintenance mode, it can be switched to the secure state manually by FCR manufacturer authorised user. If any situation except followings, it can be switched to the secure state automatically.  FCR Certificate check fails,  Mesh cover monitoring check fails,  A disconnection between fiscal memory and main processor occurs,  Electronic seal is opened, or forced by unauthorised persons  EJ Media disconnection  NVRAM low battery voltage, while service mode is not active  Z-Report Message not sent to Revenue Administration during maximum number of days defined in Parameter Loading Message  Events that block FCR which are defined in New generation FCR Detail guidance[8] TOE has the testing capability of external entities during the initial start-up and fiscal transaction. TOE has the capability of time synchronisation with trusted server. During Z report delivery or parameter download, TOE synchronizes its time information by using NTP with trusted server. If any test fails, the TOE generates an audit event according to PRA Messaging Protocol Document [6]. Perkon New Generation FCR Application Security Target Page 59 / 67 TOE records important events stated as in PRA Messaging Protocol document [6] and start-up shutdown actions with reliable time stamps. All events contains following information date and time of the event, type of event, subject identity, and the outcome (success or failure) of the event. For reliable time information TOE uses Trusted Server to synchronise its time with TSM meanwhile every Z report sending actions. 7.1.3. Authentication TOE authenticates FCR Authorised User and FCR Authorised Manufacturer. FCR Authorised User authentication is based on Password control. Authorised Manufacturer User authentication is based on Challenge Response Authentication. FCR Authorised User’s password can be modified by only FCR Authorised User. FCR Authorised User’s password can be set to default value by only Authorised Manufacturer User. FCR Authorised User enters wrong password three times. TOE does not accept its authentication attempt and it warns the user make user wait for a new authentication attempt for 15 minutes TOE authenticates Authorised Manufacturer User by challenge response authentication mechanism. TOE generates a randomized challenge code to Authorised Manufacturer user for authentication. Authorised Manufacturer User uses this code information to generate the response code by using a web site of manufacturer. If user enters the required response code then TOE authenticates authorised manufacturer user. If Authorised Manufacturer User enters wrong response code three times, TOE does not accept its authentication attempt and it warns the user and make user wait for a new authentication attempt for 15 minutes. FCR authenticates PRA-IS by using Digital certificates by TLS 1.2. TOE has capability of authenticate TSM by using TSM certificate provided the same certification authority with its environment while communication with TSM and PRA-IS. 7.1.4. Integrity Control TOE provides integrity for sales data and event data while storing these data by using CRC and for the daily memory stored data integrity is controlled by using CRC. TOE protects stored audit records from unauthorised deletion and modification. For that purpose TOE does not give any deletion and modification capability to any user role. FCR has hardware and software tampering detection measures. When unauthorised case opening attempt occurs, hardware and software measures can detect this kind of attack even the FCR powered off. If physical tampering occurs TOE notifies the user. TOE has limited capacity for audit records. When limit is reached TOE overwrite the oldest stored audit records. Perkon New Generation FCR Application Security Target Page 60 / 67 TOE monitors integrity of sales data, event data, authentication data, characterization data and FCR parameters. TOE uses CRC check and Hash controls for detection of integrity errors even if it is erroneous or misuse of TOE. TOE controls all records from unauthorised modification by using integrity checking mechanisms. If any integrity error occurs in sales data stored in fiscal memory and ERU, event data and characterization data, TOE generates an audit event and then TOE enters maintenance mode. If any integrity error occurs in sales data stored in daily memory and FCR Parameters TOE generates an audit event and prints Z report automatically. During the communication of TSM and PRA-IS, TOE uses checksum for checking integrity of messages. 7.1.5. Secure Communication TOE communicates external systems TSM, PRA-IS and external EFT-POS Device securely. FOR secure communication with these entities TOE uses well known cryptographic algorithms such as TLS, AES and RSA. TOE uses TLS and AES algorithms for communication with TSM and PRA-IS and TOE uses DHE for AES key agreement with EFT-POS and also it uses AES to communicate securely with EFT-POS Device. TOE generates AES, DHE keys by using True Random Number Generator. When a physical tampering attack occurs FCR hardware controls detects unauthorised case openings and TOE generates an audit log for that kind of physical tampering by using environment hardware measures/controls. TSM Communication: TOE initiates traffic to TSM and uses SSL authentication to authenticate TSM. TOE generates AES session key and HMAC key by using cryptographic library for encryption and integrity control. After usage of keys they are deleted by library new keys are created for the next session during the next communication with TSM. FCR private key is stored in smartcard. The asymmetric keys used in communication with TSM cannot be changed by any user types for an identified FCR and default security attribute (keys) values cannot be changed. Information Flow Control Security Function Policy for TSM and PRA-IS Rules:  TOE uses IP/Port information TSM.  TSM has ability to send parameters of new generation cash register fiscal application software functions to FCR according to PRA messaging protocol document [6]. TOE uses IP/Port information and information label to communicate TSM.  Information flow is granted only if secure communication with SSL CA is established. After secure communication settlement communication can be started with TSM and FCR parameters and exchange rates can be received from TSM.  Only Authorised Manufacturer User can change TSM IP and port information any other security related functionality cannot be changed by any user. PRA-IS Communication: Perkon New Generation FCR Application Security Target Page 61 / 67 TOE communicates to PRA-IS over TSM. TOE does not communicate PRA-IS directly. While sending sales and event data to PRA-IS TOE will provide its identity and time information. TOE provides confidentiality and integrity for transferring sales data, event data to the PRA-IS by using GMP protocol. All data transfer uses encryption and integrity controls. TOE provides integrity for characterization data transferred to the PRA-IS. TOE initiates traffic to TSM for sending to and receiving from related information PRA-IS. TOE generates TRMK by using random number generator. TOE encrypts TRMK by using PRA-IS public key then sends encrypted TRMK to PRA-IS. PRA-IS generates TREK and TRAK keys and encrypt both keys then sends back to TOE. After receiving and controlling integrity of keys, if there is no error. TOE uses these keys for secure communication with PRA-IS and deletes TRMK. TOE deletes the TREK and TRAK keys when an attack is detected on device power on. TOE uses AES cryptosystem for encryption of packets to send to PRA-IS. Information Flow Control Security Function Policy for PRA-IS Rules:  PRA-IS has ability to receive reports related to sales data, event data reports. TOE uses IP/Port information of TSM and file name to communicate PRA-IS  After secure communication settlement sales and event data can be sent to PRA-IS and FCR parameters and exchange rates can be downloaded from TSM. EFT-POS Device Communication: EFT-POS Device communication is done by using AES encrypted messages. All fiscal data is encrypted between EFT-POS Device and TOE. For AES key exchange, TOE uses DHE key exchange methods detailed in GMP3 document [7]. Generated keys (KENC,KHMAC and DHE-KEY) by TOE for external device communication are deleted according to conditions specified in External Device Communication Protocol Document [7] occur. The EFT-POS pairing process can only be done under supervision of Authorised Manufacturer user and default security attribute (source port, label) values cannot be changed by any user. Information Flow Control SFP with EFT_POS Device Rules:  Amount information in sales data can be sent to EFT-POS Device.  Outcome of EFT-POS operation can be received from EFT-POS.  EFT-POS Label, EFT-POS source port info cannot be modified by any user.  Initial configuration can only be done by Authorised Manufacturer User. 7.2. Assurance Measure To satisfy the security assurance requirements, suitable assurance measures are employed by the developer of the TOE. The documents describe the measures and include further information supporting the verification of the conformance of these measures against the claimed assurance requirements. Perkon New Generation FCR Application Security Target Page 62 / 67 7.3. TOE Summary Specification Rational 7.3.1. Security Functions Rational Table 9 Security Functions Specification List Access Control Accuracy and event recording Authentication Integrity Control Secure Communication FAU_GEN.1 Audit data generation X FAU_SAR.1 Audit review X FAU_STG.1 Protected audit trail storage X FAU_STG.4 Prevention of audit data loss X FCO_NRO.2 Enforced proof of origin X FCS_CKM.1/TRMK Cryptographic key generation X FCS_CKM.2 Cryptographic key distribution X FCS_CKM.1/TLS_AES Cryptographic key generation X FCS_CKM.1/TLS_HMAC Cryptographic key generation X FCS_CKM.1/ DHE-KEY Cryptographic key generation X FCS_CKM.1/ EXT-DEV KENC Cryptographic key generation X FCS_CKM.1/ EXT-DEV KHMAC Cryptographic key generation X FCS_CKM.4 Cryptographic key destruction X FCS_COP.1/TREK Cryptographic operation X FCS_COP.1/TRAK Cryptographic operation X FCS_COP.1/ ENC-DEC Cryptographic operation X FCS_COP.1/INT-AUTH Cryptographic operation X FCS_COP.1/EXT-DEV KENC Cryptographic operation X FCS_COP.1/EXT-DEV KHMAC Cryptographic operation X FCS_COP.1/HASHING Cryptographic operation X X FCS_COP.1/TRMK-DEC Cryptographic operation X FCS_COP.1/PUB-ENC Cryptographic operation X FCS_COP.1/SIGN-VER Cryptographic operation X FCS_COP.1/EXT-DEV KEYEXCHANGE Cryptographic operation X FDP_ACC.1 Subset access control X Perkon New Generation FCR Application Security Target Page 63 / 67 Access Control Accuracy and event recording Authentication Integrity Control Secure Communication FDP_ACF.1 Security attribute based access control X FDP_ETC.2/TSM Export of user data with security attributes X FDP_ETC.2/EFT-POS/SMART PINPAD Export of user data with security attributes X FDP_IFC.1/TSMCOMMUNICA TION Subset information flow control X FDP_IFC.1/EFT-POS/SMART PINPADCOMMUNICATION Subset information flow control X FDP_IFF.1/TSMCOMMUNICA TION Simple security attributes X FDP_IFF.1/EFT-POS/SMART PINPADCOMMUNICATION Simple security attributes X FDP_ITC.2/TSM Import of user data with security attributes X FDP_ITC.2/EFT-POS/SMART PINPAD Import of user data with security attributes X FDP_SDI.2 /MEMORY Stored data integrity monitoring and action X FDP_SDI.2/DAILY and PRMTR Stored data integrity monitoring and action X FIA_AFL.1/MANUFACTURER Authentication failure handling X FIA_AFL.1/AUTHORISED Authentication failure handling X FIA_UAU.1 Timing of authentication X X FIA_UAU.4 Single-use authentication mechanisms X FIA_UID.1 Timing of identification X X FMT_MOF.1 Management of security functions behaviour X FMT_MSA.1/PRIVILEGES Management of security attributes X FMT_MSA.1/IP:PORT INFO Management of security attributes X FMT_MSA.1/FILE NAME and INFO-LABEL Management of security attributes X FMT_MSA.1/EFT- POS/SMART PINPADSOURCE PORT INFO Management of security attributes X FMT_MSA.1/EFT- POS/SMART PINPAD LABEL INFO Management of security attributes X Perkon New Generation FCR Application Security Target Page 64 / 67 Access Control Accuracy and event recording Authentication Integrity Control Secure Communication FMT_MSA.3/USERS and SYSTEMS Static attribute initialisation X X FMT_MSA.3/ EFT- POS/SMART PINPAD Static attribute initialisation X FMT_MTD.1/FCR AUTHORISED USER Management of TSF data X X FMT_MTD.1/AUTHORISED MANUFACTURER USER Management of TSF data X FMT_SMF.1 Specification of Management Functions X FMT_SMR.2 Restrictions on security roles X FPT_FLS.1 Failure with preservation of secure state X FPT_PHP.2 Notification of physical attack X X FPT_RCV.1 Manual recovery X FPT_RCV.4 Function recovery X FPT_STM.1 Reliable time stamps X FPT_TDC.1/TSM Inter-TSF basic TSF data consistency X FPT_TDC.1/EFT-POS/SMART PINPAD Inter-TSF basic TSF data consistency X FPT_TEE.1/EXT Testing of external entities X FPT_TEE.1/TIME Testing of external entities X FTP_ITC.1/TSM Inter-TSF trusted channel X FTP_ITC.1/EFT-POS/SMART PINPAD Inter-TSF trusted channel X 7.3.2. Assurance Measures Rational The assurance measures of the developer as referred in section 7.2 are suitable and sufficient to meet the CC assurance level EAL2 as claimed in section 6.2. In particular, the deliverables listed in chapter 7.2 are suitable and sufficient to document that the assurance requirements are met. Perkon New Generation FCR Application Security Target Page 65 / 67 8. ACRONYMS AES : Advanced Encryption Standard CC : Common Criteria CCMB : Common Criteria Management Board DEMA : Differential Electromagnetic Analysis DES : Data Encryption Standard DFA : Differential Fault Analysis DPA : Differential Power Analysis EAL : Evaluation Assurance Level (defined in CC) EFTPOS : Electronic Funds Transfer at Point of Sale EMV : Europay, MasterCard and Visa ERU : Electronic Recording Unit FCR : Fiscal Cash Register GPRS : General Packet Radio Service GPS : Global Positioning System IT : Information Technology ITU : International Telecommunication Union OSP : Organisational Security Policy PP : Protection Profile PKI : Public Key Infrastructure PRA : Presidency of Revenue Administration PRA-IS : Presidency of Revenue Administration Information Systems SAR : Security Assurance Requirements SEMA : Simple Electromagnetic Analysis SFR : Security Functional Requirements SHA : Secure Hash Algorithm SPA : Simple Power Analysis Perkon New Generation FCR Application Security Target Page 66 / 67 SSL - CA : Secure Sockets Layer - Client Authentication TOE : Target of Evaluation TLS 1.2 : Transport Layer Security version 1.2 TSF : TOE Security Functionality (defined in CC) TSE : Turkish Standards Institute TSM : Trusted Service Manager VAT : Value Added Tax Perkon New Generation FCR Application Security Target Page 67 / 67 9. BIBLIOGRAPHY Common Criteria [1] Common Criteria for Information Technology Security Evaluation, Part 1: Introduction and General Model; CCMB-2012-09-001, Version 3.1, Revision 4, September 2012 [2] Common Criteria for Information Technology Security Evaluation, Part 2: Security Functional Components; CCMB-2012-09-002, Version 3.1, Revision 4, September 2012 [3] Common Criteria for Information Technology Security Evaluation, Part 3: Security Assurance Requirements; CCMB-2012-09-003, Version 3.1, Revision 4, September 2012 [4] Common Methodology for Information Technology Security Evaluation, Evaluation Methodology; CCMB-2012-09-004, Version 3.1, Revision 4, September 2012 New Generation Cash Register Directives [5] Technical Guidance (TK1) Document, version 3.0, 6 January 2015 [6] PRA Messaging Protocol (for TK1) Document, version 4.0, 18 May 2015 [7] External Device Communication Protocol Document, version 2.0, 20 March 2015 [8] FCR Detailed Guidance, version 1.6, 14 May 2015