Certification Report Page 1
KECS-CR-19-62
Document Security V5.0
Certification Report
Certification No.: KECS-CISS-0969-2019
2019. 11. 5.
IT Security Certification Center
Certification Report Page 2
History of Creation and Revision
No. Date
Revised
Pages
Description
00 2019.11.5. -
Certification report for Document Security V5.0
- First documentation
Certification Report Page 3
This document is the certification report for Document Security V5.0 of SoftCamp Co., Ltd.
The Certification Body
IT Security Certification Center
The Evaluation Facility
Korea System Assurance (KOSYAS)
Certification Report Page 4
Table of Contents
1. Executive Summary ............................................................................................ 5
2. Identification........................................................................................................ 8
3. Security Policy..................................................................................................... 9
4. Assumptions and Clarification of Scope ........................................................... 9
5. Architectural Information...................................................................................11
6. Documentation ...................................................................................................11
7. TOE Testing........................................................................................................ 12
8. Evaluated Configuration ................................................................................... 12
9. Results of the Evaluation.................................................................................. 13
9.1 Security Target Evaluation (ASE) .................................................................. 13
9.2 Life Cycle Support Evaluation (ALC)............................................................. 13
9.3 Guidance Documents Evaluation (AGD) ....................................................... 14
9.4 Development Evaluation (ADV)..................................................................... 14
9.5 Test Evaluation (ATE).................................................................................... 14
9.6 Vulnerability Assessment (AVA) .................................................................... 15
9.7 Evaluation Result Summary.......................................................................... 15
10. Recommendations ............................................................................................ 16
11. Security Target................................................................................................... 16
12. Acronyms and Glossary ................................................................................... 17
13. Bibliography ...................................................................................................... 18
Certification Report Page 5
1. Executive Summary
This report describes the certification result drawn by the certification body on the results
of the Document Security V5.0 developed by SoftCamp Co., Ltd. with reference to the
Common Criteria for Information Technology Security Evaluation (“CC” hereinafter)[1]. It
describes the evaluation result and its soundness and conformity.
The Target of Evaluation (“TOE” hereinafter) is Electronic Document Encryption designed
to protect important documents managed by the organization based on the
encryption/decryption. Also, the TOE provide a variety of security features: security audit,
the user identification and authentication including mutual authentication between TOE
components, security management, the TOE access session management, and the TSF
protection function, etc.
The evaluation of the TOE has been carried out by Korea System Assurance (KOSYAS)
and completed on October 24, 2019. This report grounds on the Evaluation Technical
Report (ETR) [4] KOSYAS had submitted and the Security Target (ST) [5].
The ST claims strict conformance to the Korean National PP for Electronic Document
Encryption V1.0 [3]. All Security Assurance Requirements (SARs) in the ST are based
only upon assurance component in CC Part 3. The ST and the resulting TOE is CC Part 3
conformant. The Security Functional Requirements (SFRs) are based upon both functional
components in CC Part 2 and a newly defined component in the Extended Component
Definition chapter of the PP, therefor the ST, and the TOE satisfies the SFRs in the ST.
Therefore the ST and the resulting TOE is CC Part 2 extended.
[Figure 1] shows the operational environment of the TOE. TOE is composed of the
Document Security Server V5.0 (hereinafter ‘Server’) which manage security policy and
cryptographic key, Document Security Client V5.0 (hereinafter ‘Client’) which
encrypt/decrypt Electronic Document, and Document Security Console V5.0 (hereinafter
‘Console’) which provide security management interface. TOE should be installed and
operated inside the internal network of the protected organization
Certification Report Page 6
[Figure 1] Operational Environment of the TOE
The minimum requirements for hardware, software to install and operate the TOE are shown
in [Table 1] below:
Type Requirements
Server
H/W
CPU Intel(R) Xeon(R) CPU E5-2630L @ 2.00 GHz or higher
HDD Space required for TOE installation is 20 GB or higher
RAM 8 GB or higher
NIC 10/100/1000 Mbps Ethernet Card 1 Port or higher
OS CentOS Linux release 6.10 (Linux Kernel 2.6, 64bit)
S/W
JRE 1.7
MariaDB 10.3
Client
H/W
CPU Intel(R) Pentium(R) Dual CPU E2200 @ 2.20 GHz or higher
HDD Space required for TOE installation is 20 GB or higher
RAM 4 GB or higher
NIC 10/100/1000 Mbps Ethernet Card 1 Port or higher
OS Windows 7 Professional SP1 32 bit, 64 bit
Certification Report Page 7
Type Requirements
Windows 8 32 bit, 64 bit
Windows 10 Pro 32 bit, 64 bit
Windows 10 Enterprise 32 bit, 64 bit
S/W
Microsoft Visual C++ 2008 Redistributable package (x86, x64)
MS Notepad, MS Wordpad, MS Paint
Microsoft Office 2010, 2013, 2016, 365
Hancom Office 2010, 2014(VP), NEO, 2018
Acrobat Reader DC, Acrobat Pro 2017, DC
Console
H/W
CPU Intel(R) Pentium(R) Dual CPU E2140 @ 1.60 GHz or higher
HDD Space required for TOE installation is 10 GB or higher
RAM 4 GB or higher
NIC 10/100/1000 Mbps Ethernet Card 1 Port or higher
OS
Windows 7 Professional SP1 32 bit, 64 bit
Windows 8 32 bit, 64 bit
Windows 10 Pro 32 bit, 64 bit
Windows 10 Enterprise 32 bit, 64 bit
S/W Microsoft Visual C++ 2008 Redistributable package (x86, x64)
[Table 1] Hardware/Software Requirements for TOE
External IT entity linked to the TOE operation is Mail server.
Certification Validity: The certificate is not an endorsement of the IT product by the
government of Republic of Korea or by any other organization that recognizes or gives
effect to this certificate, and no warranty of the IT product by the government of
Republic of Korea or by any other organization recognizes or gives effect to the
certificate, is either expressed or implied.
Certification Report Page 8
2. Identification
The TOE reference is identified as follows.
TOE Document Security V5.0
Version V5.0.0.6
TOE
Components
Document Security Server V5.0 (V5.0.0.3)
- SCDS_Server_5.0.0.3.bin
Document Security Client V5.0 (V5.0.0.6)
- SCDS_Client_5.0.0.6.exe
- SCDS_Client_5.0.0.6_x64.exe
Document Security Console V5.0 (V5.0.0.4)
- SCDS_Console_5.0.0.4.exe
- SCDS_Console_5.0.0.4_x64.exe
Guidance
Documents
Document Security V5.0 Preparative Procedures (PRE) V1.2
- Document Security V5.0_Preparative Procedures (PRE)_V1.2.pdf
Document Security V5.0 Manager Guidance (OPE_A) V1.2
- Document Security V5.0_Manager Guidance (OPE_A)_V1.2.pdf
Document Security V5.0 User Guidance (OPE_U) V1.3
- (Document Security V5.0_User Guidance (OPE_U)_V1.3.pdf)
[Table 2] TOE identification
[Table 6] summarizes additional information for scheme, developer, sponsor, evaluation
facility, certification body, etc.
Scheme
Korea Evaluation and Certification Guidelines for IT Security
(August 24, 2017)
Korea Evaluation and Certification Regulation for IT Security
(September 12, 2017)
TOE Document Security V5.0
Common Criteria
Common Criteria for Information Technology Security
Evaluation, Version 3.1 Revision 5, CCMB-2017-04-001 ~
CCMB-2017-04-003, April 2017
Protection Profile
Korean National Protection Profile for Electronic Document
Encryption V1.0, KECS-PP-0821-2017
Developer SoftCamp Co., Ltd.
Sponsor SoftCamp Co., Ltd.
Evaluation Facility Korea System Assurance (KOSYAS)
Certification Report Page 9
Completion Date of
Evaluation
October 24, 2019
Certification Body IT Security Certification Center
[Table 3] Additional identification information
3. Security Policy
The TOE complies security policies defined in the ST [5] by security requirements.
Thus the TOE provides following security features. For more details refer to the ST [5].
TSF Explanation
Security Audit
The TOE generates audit records of security relevant events such
as the start-up/shutdown of the audit functions, integrity violation,
self-test failures, and stores them in the DBMS.
Cryptographic
Support
The TOE performs cryptographic operation such as
encryption/decryption, and cryptographic key management such as
key generation/distribution/destruction using XecureCrypto v2.0.1.1
and SCCrypto v1.0.
User Data
Protection
The TOE protects user’s documents by making them Secured
Documents by means of encrypting them and controlling access to
them in accordance to the access control policy per user set by the
administrator.
Identification and
Authentication
The TOE identifies and authenticates the administrators and
document users based on ID/PW.
Security
Management
Server(TOE) provides functions such as TOE security function
management, security attribute management and TSF data
management to the authorized administrator.
Protection of the
TSF
The TOE provides secure communications amongst TOE
components to protect confidentiality and integrity of the transmitted
data between them. The TOE also protects TSF data against
unauthorized exposure and modification through encryption and
proprietary encoding.
TOE Access
The TOE manages the authorized administrator’s access to itself by
terminating interactive sessions after defined time interval of their
inactivity.
[Table 4] The TOE Security Functions
4. Assumptions and Clarification of Scope
There are no explicit Assumptions in the Security Problem Definition in the Low
Assurance ST. The followings are procedural method supported from operational
environment in order to provide the TOE security functionality accurately.
Certification Report Page 10
 The place where the Server(TOE) among the TOE components are installed and
operated shall be equipped with access control and protection facilities so that
only authorized administrator can access.
 The authorized administrator of the TOE shall be non-malicious users, have
appropriately trained for the TOE management functions and accurately fulfill
the duties in accordance with administrator guidance.
 The authorized administrator shall periodically checks a spare space of audit
data storage in case of the audit data loss, and carries out the audit data backup
(external log server or separate storage device, etc.) to prevent audit data loss.
 The authorized administrator of the TOE shall ensure the reliability and security
of the operating system by removing all unnecessary services or means and
performing the reinforcement on the latest vulnerabilities of the operating system
in which the TOE is installed and operated.
 The audit record where the audit trail, such as the DBMS interacting with the
TOE, is saved should be protected against unauthorized deletion or
modification.
 The TOE shall accurately record the security related events using the reliable
time stamp from the TOE operational environment.
Certification Report Page 11
5. Architectural Information
The following security functions are provided by the TOE Logical scope and boundary
of TOE is shown in [Figure 2]
[Figure 2] TOE Logical scope and boundary
6. Documentation
The following documentation is evaluated and provided with the TOE by the developer
to the customer.
Identifier Version Date
Document Security V5.0 Preparative Procedures (PRE) 1.2 September 20, 2019
Document Security V5.0 Manager Guidance (OPE_A) 1.2 September 20, 2019
Document Security V5.0 User Guidance (OPE_U) 1.3 September 20, 2019
[Table 5] Documentation
Certification Report Page 12
7. TOE Testing
The developer took a testing approach based on the security services provided by
each TOE component based on the operational environment of the TOE. Each test
case includes the following information:
 Test no. and conductor: Identifier of each test case and its conductor
 Test Purpose: Includes the security functions and modules to be tested
 Test Configuration: Details about the test configuration
 Test Procedure detail: Detailed procedures for testing each security function
 Expected result: Result expected from testing
 Actual result: Result obtained by performing testing
 Test result compared to the expected result: Comparison between the expected
and actual result
The developer correctly performed and documented the tests according to the
assurance component ATE_FUN.1.
The evaluator has installed the product using the same evaluation configuration and
tools as the developer’s test and performed all tests provided by the developer. The
evaluator has confirmed that, for all tests, the expected results had been consistent with
the actual results. In addition, the evaluator conducted penetration testing based upon
test cases devised by the evaluator resulting from the independent search for potential
vulnerabilities. The evaluator testing effort, the testing approach, configuration, depth,
and results are summarized in the ETR [4].
8. Evaluated Configuration
The TOE is software consisting of the following components:
TOE: Document Security V5.0
Version: V5.0.0.6
- Document Security Server V5.0 (V5.0.0.3)
- Document Security Client V5.0 (V5.0.0.6)
- Document Security Console V5.0 (V5.0.0.4)
The Administrator can identify the complete TOE reference after installation using the
product’s Info check menu. And the guidance documents listed in this report chapter 6,
Certification Report Page 13
[Table 6] were evaluated with the TOE
9. Results of the Evaluation
The evaluation facility provided the evaluation result in the ETR [4] which references
Single Evaluation Reports for each assurance requirement and Observation Reports.
The evaluation result was based on the CC [1] and CEM [2].
As a result of the evaluation, the verdict PASS is assigned to all assurance components
9.1 Security Target Evaluation (ASE)
The ST Introduction correctly identifies the ST and the TOE, and describes the TOE in a
narrative way at three levels of abstraction (TOE reference, TOE overview and TOE
description), and these three descriptions are consistent with each other. Therefore the
verdict PASS is assigned to ASE_INT.1.
The Conformance Claim properly describes how the ST and the TOE conform to the CC
and how the ST conforms to PPs and packages. Therefore the verdict PASS is assigned
to ASE_CCL.1.
The Security Objectives for the operational environment are clearly defined. Therefore
the verdict PASS is assigned to ASE_OBJ.1.
The Extended Components Definition has been clearly and unambiguously defined, and
it is necessary. Therefore the verdict PASS is assigned to ASE_ECD.1.
The Security Requirements is defined clearly and unambiguously, and they are internally
consistent. Therefore the verdict PASS is assigned to ASE_REQ.1.
The TOE Summary Specification addresses all SFRs, and it is consistent with other
narrative descriptions of the TOE. Therefore the verdict PASS is assigned to
ASE_TSS.1.
Thus, the ST is sound and internally consistent, and suitable to be used as the basis for
the TOE evaluation.
The verdict PASS is assigned to the assurance class ASE.
9.2 Life Cycle Support Evaluation (ALC)
The developer has clearly identified the TOE. Therefore the verdict PASS is assigned
to ALC_CMC.1.
The configuration management document verifies that the configuration list includes the
Certification Report Page 14
TOE and the evaluation evidence. Therefore the verdict PASS is assigned to
ALC_CMS.1.
Also the evaluator confirmed that the correct version of the software is installed in
device.
The verdict PASS is assigned to the assurance class ALC.
9.3 Guidance Documents Evaluation (AGD)
The procedures and steps for the secure preparation of the TOE have been
documented and result in a secure configuration. Therefore the verdict PASS is
assigned to AGD_PRE.1.
The operational user guidance describes for each user role the security functionality
and interfaces provided by the TSF, provides instructions and guidelines for the secure
use of the TOE, addresses secure procedures for all modes of operation, facilitates
prevention and detection of insecure TOE states, or it is misleading or unreasonable.
Therefore the verdict PASS is assigned to AGD_OPE.1.
Thus, the guidance documents are adequately describing the user can handle the TOE
in a secure manner. The guidance documents take into account the various types of
users (e.g. those who accept, install, administrate or operate the TOE) whose incorrect
actions could adversely affect the security of the TOE or of their own data.
The verdict PASS is assigned to the assurance class AGD.
9.4 Development Evaluation (ADV)
The functional specifications specifies a high-level description of the SFR-enforcing
and SFR-supporting TSFIs, in terms of descriptions of their parameters. Therefore the
verdict PASS is assigned to ADV_FSP.1.
The verdict PASS is assigned to the assurance class ADV.
9.5 Test Evaluation (ATE)
The developer correctly performed and documented the tests in the test documentation.
Therefore the verdict PASS is assigned to ATE_FUN.1.
By independently testing a subset of the TSFI, the evaluator confirmed that the TOE
behaves as specified in the functional specification and guidance documentation.
Therefore the verdict PASS is assigned to ATE_IND.1.
Certification Report Page 15
Thus, the TOE behaves as described in the ST and as specified in the evaluation
evidence (described in the ADV class).
The verdict PASS is assigned to the assurance class ATE.
9.6 Vulnerability Assessment (AVA)
By penetrating testing, the evaluator confirmed that there are no exploitable
vulnerabilities by attackers possessing basic attack potential in the operational
environment of the TOE. Therefore the verdict PASS is assigned to AVA_VAN.1.
Thus, potential vulnerabilities identified, during the evaluation of the development and
anticipated operation of the TOE or by other methods (e.g. by flaw hypotheses), don’t
allow attackers possessing basic attack potential to violate the SFRs.
The verdict PASS is assigned to the assurance class AVA.
9.7 Evaluation Result Summary
Assurance
Class
Assurance
Component
Evaluator Action
Elements
Verdict
Evaluator
Action
Elements
Assurance
Component
Assurance
Class
ASE
ASE_INT.1
ASE_INT.1.1E PASS
PASS
PASS
ASE_INT.1.2E PASS
ASE_CCL.1 ASE_CCL.1.1E PASS PASS
ASE_OBJ.1 ASE_OBJ.1.1E PASS PASS
ASE_ECD.1
ASE_ECD.1.1E PASS
PASS
ASE_ECD.1.2E PASS
ASE_REQ.1 ASE_REQ.1.1E PASS PASS
ASE_TSS.1
ASE_TSS.1.1E PASS
PASS
ASE_TSS.1.2E PASS
ALC
ALC_CMS.1 ALC_CMS.1.1E PASS PASS
PASS
ALC_CMC.1 ALC_CMC.1.1E PASS PASS
AGD
AGD_PRE.1
AGD_PRE.1.1E PASS PASS
PASS
AGD_PRE.1.2E PASS PASS
AGD_OPE.1 AGD_OPE.1.1E PASS PASS
ADV ADV_FSP.1
ADV_FSP.1.1E PASS PASS
PASS
ADV_FSP.1.2E PASS PASS
ATE
ATE_FUN.1 ATE_FUN.1.1E PASS PASS
PASS
ATE_IND.1
ATE_IND.1.1E PASS
PASS
ATE_IND.1.2E PASS
Certification Report Page 16
AVA AVA_VAN.1
AVA_VAN.1.1E PASS
PASS PASS
AVA_VAN.1.2E PASS
AVA_VAN.1.3E PASS
[Table 6] Evaluation Result Summary
10. Recommendations
The TOE security functionality can be ensured only in the evaluated TOE operational
environment with the evaluated TOE configuration, thus the TOE shall be operated by
complying with the followings:
 The administrator should periodically check the free space of the audit data
storage in preparation for the loss of the audit records, and perform backups of
the audit records so that the audit storage is not exhausted.
 The Server(TOE) must be installed and operated in a physically secure
environment that is accessible only to authorized administrators and should not
allow remote administration from outside.
 The administrator shall maintain a safe state such as application of the latest
security patches, eliminating unnecessary service, change of the default
ID/password, etc., of the operating system and DBMS in the TOE operation.
 If a cryptographic key is lost due to administrator's neglectful cryptographic key
management, document users may not be able to decrypt the encrypted file
stored on the user's PC, so administrator has to be careful with cryptographic
key management
11. Security Target
Document Security V5.0 Security Target V1.4 is included in this report for reference
Certification Report Page 17
12. Acronyms and Glossary
CC Common Criteria
EAL Evaluation Assurance Level
PP Protection Profile
SAR Security Assurance Requirement
SFR Security Functional Requirement
ST Security Target
TOE Target of Evaluation
TSF TOE Security Functionality
TSFI TSF Interface
Authorized Document
User
The TOE user who may, in accordance with the
SFRs, perform an operation
Authorized Administrator Authorized user to securely operate and manage the
TOE
Data Encryption Key
(DEK)
Key that encrypts the data
Decryption The act that restoring the ciphertext into the plaintext
using the decryption key
Encryption The act that converting the plaintext into the
ciphertext using the encryption key
External Entity An entity (person or IT object) that interact (or can
interact) with the TOE from outside the TOE
Key Encryption Key
(KEK)
Key that encrypts another cryptographic key
Certification Report Page 18
13. Bibliography
The certification body has used following documents to produce this report.
[1] Common Criteria for Information Technology Security Evaluation, Version 3.1
Revision 5, CCMB-2017-04-001 ~ CCMB-2017-04-003, April, 2017
[2] Common Methodology for Information Technology Security Evaluation, Version
3.1 Revision 5, CCMB-2017-04-004, April, 2017
[3] Korean National Protection Profile for Electronic Document Encryption V1.0, August
18, 2017
[4] Document Security V5.0 Evaluation Technical Report Lite V3.00, October 24, 2019
[5] Document Security V5.0 Security Target V1.4, October 23, 2019