KR20180074967A - Software security method based on virtualization technologies to ensure the security level equivalent to hardware and system using the same - Google Patents

Abstract

Disclosed are a software security method based on virtualization technologies to ensure the security level equivalent to hardware and a system using the same. The virtualization-based software security system includes a security module engine for encryption and security protocol execution, a security module interface transmitting a command and data to a software security module in an application program, and a security module storage capable of storing information used in the security module engine. A hardware level security can be provided on a security software basis by means of the software security module engine operating every function provided by a hardware security chip in a high-performance central processing unit.

Description

TECHNICAL FIELD [0001] The present invention relates to a virtualization-based software security method for securing hardware level security, and a device using the security method. [0002]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software security technique using virtualization technology, and more particularly, to a virtualization-based software security method and device that can guarantee hardware level security.

Recently, users have used various devices such as personal computers (PCs) as well as portable devices such as smart phones and tablet PCs, and wearable devices such as smart watches. In each device, the user generates and uses a lot of data. The user wants to be able to freely share and use data, such as photographs, videos, documents, or application programs,

These devices are shared through network services such as the cloud. Data stored for sharing in the cloud that can be accessed by a large number of users and administrators as well as the user must be confidential for security purposes.

To ensure the confidentiality of such data, a hardware security chip such as a Trusted Platform Module is used. The hardware security chip can protect the symmetric key used to guarantee the confidentiality of the data by using the asymmetric key which can be used only within the security hardware. In addition, by defining the state or policy of a computing environment in which an asymmetric key can be used, if the environment requested by the data owner is not configured, the function of limiting the use of the asymmetric key is supported by the hardware chip, .

However, hardware security chips have problems in performance and scalability. The hardware security chip is equipped with a low-performance cryptographic computation device according to the power and cost constraints. Therefore, even if the user equipment has high performance, if hardware security chip is frequently used for data security, high performance overhead due to low performance of hardware security chip is shown.

In addition, due to the characteristics of the hardware, it is impossible to add a new technology such as a security protocol update according to newly discovered security threat, and to change the technology already mounted on the hardware security chip. Thus, the scalability issues of such hardware security chips make it difficult to actively cope with ever-increasing security threats.

It is an object of the present invention to solve the above problems and to provide a virtualization-based software security system capable of solving performance and scalability problems of a hardware security chip while ensuring the same level of security as a hardware security chip by utilizing virtualization technology. And a device for performing the same.

According to an aspect of the present invention, there is provided an apparatus for performing a virtualization-based software security method, including: a security module engine for performing encryption and security protocols; a security module for transmitting commands and data to a software security module in an application program; A module-based software security device is provided that includes a module interface, and a security module store that can hold information used by the security module engine.

Here, a software security module including a security module engine and a security module interface is a software security module that protects a central processing unit which is guaranteed to be independent from an operating system and an application program operating in the same apparatus or whose unauthorized access of an operating system and an application program is restricted Lt; / RTI > area.

Here, the software security module operates in a protection area of an operating system or a central processing unit in which the application program is executed, and the protection area can be created using virtualization technology.

Here, the security module interface can detect a command event generated by a general program.

Here, the security module interface transmits commands of the external operating system and the application program to the security module engine according to a protocol defined in the software security module located in the protection area, and receives the result of the command from the security module engine .

Here, the security module engine may include an execution engine for processing the external data transmitted through the security module interface according to a protocol.

Here, the security module engine may further include a security function engine. The security function engine may include a cryptographic engine, a hash engine, an authenticator, a variable generator, and a symmetric key / asymmetric key generator required by the execution engine in executing the command.

Here, the security module engine may further include an engine interface that can receive commands from the security module interface and display the status of the security module engine.

Here, the security module engine can perform hardware security chip level security by controlling the execution engine and the engine interface interlockingly. To this end, the security module engine may further include a volatile information storage space for storing information on a usage policy set on the key and the software security apparatus used in the software security process. The security module engine may further include a nonvolatile security module engine information space for temporarily storing nonvolatile security module engine information managed by the software security module.

Here, the nonvolatile security module engine information may include a root key required for the configuration of the key hierarchy by the software security module, and a certificate or secret key information used by the software security module.

Here, the security module engine may store the non-volatile security module engine information in the security module storage when the non-volatile security module engine information stored in the non-volatile security module engine information space is changed according to the definition.

Here, the security module engine may encrypt the non-volatile security module engine information and store the information in the security module storage for securing confidentiality.

Here, when the non-volatile security module engine information is registered in the security module storage, or when the non-volatile security module engine information is registered in the security module storage in the security module engine, the security module engine stores the integrity information of the software security module Can be obtained.

Here, the security module engine may generate an engine information encrypted symmetric key that is used to encrypt or decrypt the non-volatile security module engine information based on the integrity information.

Here, the security module engine can encrypt or decrypt the non-volatile security module engine information only from a secure device or a predetermined device using the engine information encryption symmetric key.

Here, the security module repository is implemented to restrict access to the generic program that is connected to the security module interface.

According to another aspect of the present invention, there is provided a virtualization-based software security method performed in a computer, the virtualization-based software security method comprising: creating a protection area that operates independently of a general program using a virtualization technology of a computer; Loading a software security module including a security module interface and a security module engine connecting the security module engine and the general program; Driving a security module engine and registering a security module interface; Collecting uncertain information of the software security module; Generating an engine information encrypted symmetric key based on the integrity information; Obtaining encrypted security module engine information from a security module storage connected to the software security module; Decrypting the encrypted security module engine information using an engine information encrypted symmetric key; And registering the decrypted security module engine information.

Here, the virtualization-based software security method includes: detecting a command event in the security module interface after registering the security module engine information; Checking the status of the security module engine; Transmitting an instruction to an engine interface of a security module engine; Updating the status of the security module engine; Transmitting an instruction to an execution engine of the security module engine; Determining whether execution of the command by the execution engine is successful; Updating the state of the security module engine upon successful execution of the command; And delivering the result of the instruction execution to the generic program via the security module interface in the security module engine.

When a virtualization-based software security method that ensures hardware level security according to an embodiment of the present invention as described above or an apparatus that performs the virtualization-based software security method is used, all the functions provided by the hardware security chip are executed in a high- The software security module engine can be used to provide hardware level security as security software. Also, the general program can acquire the security result generated in the same manner as the hardware security chip through the security module interface.

In addition, according to the present embodiment, access to an existing operating system and an application program is restricted by operating in an independent protection area through a virtualization technology, commands can be transmitted to the software security module through the same interface and protocol as the hardware security chip, The software security module engine information stored in the security module storage can be used only in a securely configured environment of the software security module, thereby solving the scalability problem of the hardware security chip while maintaining the same level of confidentiality as the hardware security chip.

1 is a block diagram schematically illustrating a virtualization-based software security apparatus according to an embodiment of the present invention.
FIG. 2 is a flowchart illustrating an operation process of the virtualization-based software security apparatus of FIG. 1. FIG.
3 is a flowchart illustrating a security command and a result transmission operation of the virtualization-based software security apparatus of FIG.
4 is a block diagram illustrating a method for managing a symmetric key in a hardware-based trusted platform module, which is one of hardware security chips according to a comparative example.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It is to be understood, however, that the invention is not to be limited to the specific embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention. Like reference numerals are used for like elements in describing each drawing.

The terms first, second, A, B, etc. may be used to describe various elements, but the elements should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, the terms "comprises", "having" and the like are used to specify that there is a stated feature, number, step, operation, element, part or combination thereof, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless otherwise defined herein, all terms used herein, including technical or scientific terms, shall be understood to have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs . And terms as defined in commonly used dictionaries are to be interpreted as representing a meaning consistent with the meaning in the context of the relevant art and, unless expressly defined herein, are interpreted in an ideal or overly formal sense It does not.

Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram schematically illustrating a virtualization-based software security apparatus according to an embodiment of the present invention.

Referring to FIG. 1, a virtualization-based software security apparatus 100 according to an embodiment of the present invention performs a software security method that assures hardware level security and utilizes virtualization technology. The software security module 101 includes a software security module 101, (104).

The software security module 101 includes a security module interface 102 and a security module engine 103 and is connected to the security module storage 104. The software security module 101 operates in a separate protection area from the general program 200 using virtualization technology. Unlike the software security module 101, the general program 200 operates in the general area. The general program 200 may include a boot loader, an operating system, an application program, and the like. The application may include a virtual machine, a Trusted Computing Gourp (TCG) software stack, a Trusted Computing Module (TPM) driver, and the like.

Each component of the virtualization-based software security device 100 will be described in more detail as follows.

The security module interface 102 transmits a command received and received in accordance with the protocol defined by the software security module 101 in the general program 200 to the security module engine 103, And transmits the result to the general program 200 according to a predetermined protocol.

The security module interface 102 can receive an instruction from the general program 200 by detecting an interrupt generated from the general program 200, a memory mapped input / output (MMIO), or other predefined event.

The aforementioned security module interface 102 may include a first means for a virtual interrupt and a second means for detecting an event. The first means may comprise a Virtual Trusted Computing Group Interrupt Handler and the second means may comprise a Trust Computing Group MMIO Handler.

As an example of the trust platform module of the personal computer (PC) in detecting the command of the general program 200, a command generated through the interrupt 1AH which is a specific interrupt vector and an instruction generated through the MMIO from 0xFED40000 to 0xFED44FFF memory address Can be detected and processed. For other hardware security chips, a trust platform can be configured according to the standard protocol of each hardware security chip.

The security module engine 103 includes an engine interface 105, an execution engine 106, a security function engine 107, a volatile information storage space 108, and a nonvolatile security module engine information space 109.

Engine interface 105 is responsible for receiving commands from security module interface 102 or for communicating results, e.g., command execution results, to security module interface 102. The engine interface 105 may also include a function to indicate the state of the security module engine 103 to allow the generic program 200 to issue an instruction or receive a result. This engine interface 105 may include a Trust Computing Group Function Interface (TCG BIOS Function Interface).

Execution engine 106 performs the function of interpreting the transmitted instructions in accordance with a predefined protocol and generating the results in accordance with the interpreted instructions.

The security function engine 107 includes an encryption engine, a hash engine, an authenticator, a key generator, and the like that are required in the process of executing the instruction by the execution engine 106.

The volatile information storage space 108 stores volatile information managed by the software security module 101. The volatile information may include information such as a key used in the security performance process, a usage policy set in the current software security module, and the like.

The non-volatile security module engine information space 109 is a space (for example, temporary storage space) for temporarily storing non-volatile information that needs to be continuously managed and updated when the software security module 101 operates, a root key required for constructing the hierarchy, a certificate used by the software security module 101, and a secret key.

The volatile information storage space 108 and / or the non-volatile security module engine information space 109 may be stored in a virtualization-based software trusted computing module register (VS-TCM Registers) Information.

The security module storage 104 stores the nonvolatile security module engine information required when the software security module 101 operates. The security module storage 104 may be set or designed such that access of the general program 200 is blocked when the software security module 101 is in operation. When the non-volatile security module engine information is changed, the information updated by the security module engine 103 can be stored in the security module storage 104. [ In this case, the operating system of the system reads from one of the TCM memory areas of the security module storage and the information stored in a specific area of the TCM register, Write operation can be performed.

Also, in the security module repository 104, when the non-volatile security module engine information is stored in the security module repository 104, the security module engine 103 may determine whether the non- The engine information encryption symmetric key can be generated. For example, the virtualization-based software security device 10 generates a Permanent Information Key (PIK) using hardware information and a VS-TCM integrity measurement value, encrypts and / Or decryption. In this manner, the security module engine 103 can ensure confidentiality in the virtualization-based software security device 100 by performing encryption and / or decryption using the engine information encryption symmetric key. The decrypted security module engine information may be registered with the security module engine as non-volatile security module engine information.

2 is a flowchart illustrating an operation process of a virtualization-based software security apparatus according to an embodiment of the present invention.

Referring to FIG. 2, the virtualization-based software security apparatus according to the present embodiment includes a protection area that can operate independently of a general program using a virtualization technology before a software security module is activated according to a software security setting on an operating system of the computer (S100).

After the protection area is created, the software security module is loaded into the protection area (S101). The software security module includes a security module engine and a security module interface. According to the above two steps S100 and S101, the virtualization-based software security device may include at least a part of the operating system of the computer in a broad sense.

The software security module operating in the protection zone drives the security module engine (S102). The software security module registers the security module interface in the system (S103).

Using the registered security module interface, the general program can issue a command to the software security module and receive the result. In this regard, as an example of a trust platform module of a personal computer (PC), the trusted platform module may be configured to detect an event occurring up to the memory area of interrupt 1AH and one of the interrupt vectors 0xFED40000 to 0xFED44FFF And the security module interface can similarly be registered in the system.

The software security module or the security module engine drives all the components necessary for the security operation of the software security module and then collects the integrity information of the driven components (S104).

Then, an engine information encrypted symmetric key is generated based on the collected integrity information (S105). The engine information encryption symmetric key may include, but is not limited to, PIK. If the integrity information has not been compromised, a symmetric key that is the same as the encrypted symmetric key used to encrypt the non-volatile engine information is generated.

Next, the encrypted non-volatile security module engine information is obtained from the security module storage (S106). The security module repository is accessible only through the protection domain. The term "nonvolatile" refers to the ability to retain stored information even when the system is powered down, and such terms exclude volatile storage means that retain information stored upon power down, or components that perform a function corresponding to such means I do not want to.

The encrypted non-volatile security module engine information is decrypted using the generated engine information encrypted symmetric key based on the integrity information (S107).

If the software security module operates normally and integrity information is not damaged, the same symmetric key is generated, so that the decryption can be normally performed. In this case, the software security module or the security module engine transmits the decrypted nonvolatile security module engine information to the security module And registers it in the engine (S108).

When the nonvolatile security module engine information is registered, since the security command is received from the general program and the preparation for generating the result is completed, the software security module completes the preparation operation (S109).

On the other hand, if the decryption is unsuccessful in step S107, that is, if the software security module is abnormally operated or damaged for a malicious purpose, the integrity information is corrupted. Therefore, another symmetric key is generated in step S105 , So decoding can not be performed normally. In this case, since the non-volatile security module engine information can not be registered in the security module engine, the operation of the current software security module is terminated (S110).

3 is a flowchart illustrating a process of transmitting a security command and a result of a virtualization-based software security apparatus according to an exemplary embodiment of the present invention.

Referring to FIG. 3, the virtualization-based software security apparatus according to the present embodiment detects when a security command event occurs in a general program of a computer (S200). That is, the security module interface detects the security command event generated in the general program and collects the command content (S201).

Next, the security module interface confirms the state of the current security module engine through the engine interface (S202).

If it is determined that the security module engine is able to execute the command (normal engine status), the security module interface transmits the collected security command to the engine interface (S203).

Next, the engine interface updates the current state before delivering the security command to the execution engine, and notifies the security module interface or the like that the command is currently being performed (S204).

After completing the status update, the engine interface transmits the received security command to the execution engine (S205).

The execution engine carries out a security command according to a predetermined protocol (S206). If the execution engine has normally performed the security command, the security module engine updates the engine status to inform the security module interface that the result is generated (S207).

Next, the security module engine transmits the generated result to the security module interface (S208). The generic program can receive the results generated through the security module interface.

On the other hand, if it is determined that the current security module engine is executing another command (corresponding to an abnormal state of the engine) or fails to execute the command or the command of the step S206 as a result of the checking, (S210). The general program can recognize that the execution of the security command has failed through the security module interface.

The software security module of the above-described virtualization-based software security device may be mounted on a microprocessor or a processor which is a central processing unit of the computer.

A processor may include one or more cores, a cache memory, a memory interface, and a peripheral interface. When a processor has a multi-core structure, a multi-core refers to integrating two or more independent cores into a single package of a single integrated circuit. A single core may refer to a central processing unit. The central processing unit (CPU) may be implemented as a system on chip (SOC) in which a micro control unit (MCU) and a peripheral device (integrated circuit for external expansion device) are disposed together, but the present invention is not limited thereto. The core consists of a register for storing instructions to be processed, an arithmetic logical unit (ALU) for comparisons, judgments, and arithmetic operations, a control unit for controlling the CPU internally for interpreting and executing instructions unit, a bus interface, and the like.

A processor may also include, but is not limited to, one or more data processors, image processors, or codecs (CODECs). The data processor, image processor, or codec may be configured separately. The processor may also have a peripheral interface and a memory interface, wherein the peripheral interface connects the processor with the input / output system and various other peripherals, and the memory interface can couple the processor to the memory.

The processor of the above-described configuration may execute data input, data processing, and data output in order to execute various software programs to perform a virtualization-based software security method. In addition, the processor may execute a specific software module (instruction set) stored in the memory to perform various specific functions corresponding to the module. A module is a set of instructions that can be represented as an instruction set or program.

The memory may include a high-speed random access memory such as one or more magnetic disk storage devices and / or a non-volatile memory, one or more optical storage devices, and / or a flash memory.

The memory may store software, programs, a set of instructions, or a combination thereof. In this embodiment, the memory may store encrypted virtualization-based software trust platform module persistent information, encrypted virtualization-based software trust computing group information, security module engine information, software security module information, virtualization-based security device information, and the like.

The operating system includes built-in operating systems such as MS WINDOWS, LINUX, Darwin, RTXC, UNIX, OS X, iOS, Mac OS, VxWorks, Google OS, Android, And may include various components for controlling the system operation of a user terminal including a mobile device and the like. The above-described operating system may also include, but is not limited to, a function of performing communication between various hardware devices and software components (modules).

For the control of general system operations or functions, except for the control of the functions implementing the virtualization-based softway security method, a software security device or a computer may be used, for example, for one of memory management, storage hardware control, power control, And may include the above-mentioned means or a component performing a function corresponding to this means.

The network may be, for example, a Global System for Mobile Communications (GSM) network, an Enhanced Data GSM Environment (EDGE) network, a Code Division Multiple Access (CDMA) network, a W- But are not limited to, a long term evolution (OFDM) network, an orthogonal frequency division multiple access (OFDMA) network, a WiMax network, a wireless fidelity (Wi-Fi) network,

Meanwhile, in the present embodiment, the components of the virtualization-based software security method may be, but are not limited to, functional blocks or modules mounted on a computer device. The above-described components may be stored in a computer-readable medium (recording medium) in the form of software for implementing a series of functions that they perform, or may be transmitted to a remote location in the form of a carrier to be implemented to operate in various computer devices. The computer readable medium may include a plurality of computer devices or a cloud system connected via a network and at least one of the plurality of computer devices or the cloud system may perform the virtualization- You can save programs and source code for

That is, the computer-readable medium may be embodied in the form of a program command, a data file, a data structure, or the like, alone or in combination. Programs recorded on a computer-readable medium may include those specifically designed and constructed for the present invention or those known and available to those skilled in the computer software arts.

The computer-readable medium can also include a hardware device specifically configured to store and execute program instructions, such as a ROM, a RAM, a flash memory, and the like. Program instructions may include machine language code such as those produced by a compiler, as well as high-level language code that may be executed by a computer using an interpreter or the like. The hardware device may be configured to operate with at least one software module to perform the noise reduction method of the present embodiment, and vice versa.

4 is a block diagram illustrating a method for managing a symmetric key used in data encryption in a trusted platform module, which is one of hardware security chips according to a comparative example.

Referring to FIG. 4, the trusted platform module 10 according to the comparative example has an asymmetric secret key 11 and an asymmetric public key 12 therein. The asymmetric secret key 11 exists only in the trusted platform module 10 and is used according to the secret key usage policy 13 defined beforehand when the secret key is generated. The asymmetric public key 12 is then passed outside the trusted platform module 10 and used to encrypt the predetermined symmetric key to generate the encrypted symmetric key 14.

To use the encrypted symmetric key 14, the encrypted symmetric key must be delivered to the trusted platform module 10, which has the asymmetric secret key 11 necessary for decryption.

When the encrypted symmetric key is delivered, the trust platform module 10 determines whether the usage policy 15 currently set in the trusted platform module 10 is valid before the asymmetric secret key 11 is used, Check whether it meets the usage policy.

If it meets the usage policy, the trusted platform module 10 generates and decrypts the decrypted symmetric key 16 using the asymmetric secret key 11. If not, the trusted platform module 10 prohibits the use of the secret key and does not decrypt the symmetric key.

As described above, the hardware-based trusted platform module according to the comparative example and the hardware-based security chip including the hardware-based trusted platform module have problems such as problems in performance and scalability, scalability of the hardware security chip, and the like.

Meanwhile, the software security method or the virtualization-based software security device of the embodiment described above with reference to FIG. 1 to FIG. 3 includes a software-based trusted platform module, and the user's device has high performance, Data security of hardware security level can be performed in a software manner quickly and quickly. In addition, due to the characteristics of the hardware, the update of the security protocol according to the newly discovered security threat can be performed substantially in real time. That is, it is possible to easily perform addition of a new security technology and change of a pre-installed security technology, thereby actively coping with a continuously increasing security threat while eliminating disadvantages such as a scalability problem of a hardware security chip have.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the present invention as defined by the following claims It can be understood that

Claims (20)

An apparatus for performing a virtualization-based software security method,
A security module engine for performing encryption and security protocols;
A security module interface for transferring commands and data from the application to the software security module; And
And a security module store that can store information used by the security module engine. The method according to claim 1,
The software security module including the security module engine and the security module interface may be provided with a function of protecting the central processing unit which is ensured of independence from the operating system and the application program operating in the same device or whose unauthorized access of the operating system and the application program is restricted A virtualization-based software security appliance located in a zone. The method of claim 2,
Wherein the software security module operates in the central processing unit in which the operating system or the application program is executed, and the protection area is created using virtualization technology. The method of claim 2,
Wherein the security module interface detects a command event generated by a general program. The method of claim 2,
Wherein the security module interface transmits a command of an external operating system and an application program to the security module engine according to a protocol defined in advance in the software security module located in the protection area and transmits a result of the command from the security module engine Receiving, virtualization-based software security devices. The method of claim 5,
Wherein the security module engine comprises an execution engine for processing external data passed through the security module interface according to a protocol. The method of claim 6,
Wherein the security module engine further comprises a security function engine, wherein the security function engine includes an encryption engine, a hash engine, an authenticator, a variable generator, a symmetric key / A virtualization-based software security device comprising an asymmetric key generator. The method of claim 7,
Wherein the security module engine further comprises an engine interface capable of receiving commands from the security module interface and displaying the status of the security module engine. The method of claim 8,
Wherein the security module engine cooperates with the execution engine and the engine interface to perform hardware security chip level security. The method of claim 9,
Wherein the security module engine further comprises a volatile information storage space for storing information on a usage policy set in a key and a software security device used in a software security process. The method of claim 10,
Wherein the security module engine further comprises a non-volatile security module engine information space for temporarily storing non-volatile security module engine information managed by the software security module. The method of claim 11,
Wherein the non-volatile security module engine information includes a root key required for the configuration of the key hierarchy by the software security module and a certificate or secret key information used by the software security module, . The method of claim 11,
Wherein the security module engine stores the nonvolatile security module engine information in the security module repository upon changing the nonvolatile security module engine information stored in the nonvolatile security module engine information space according to a predefined definition, . 14. The method of claim 13,
Wherein the security module engine encrypts the non-volatile security module engine information and stores the information in the security module repository to ensure confidentiality. The method according to any one of claims 11 to 14,
When the non-volatile security module engine information is stored in the security module storage, or when the non-volatile security module engine information is registered in the security module storage to the security module engine, Based software security device. 16. The method of claim 15,
Wherein the security module engine generates an engine information encrypted symmetric key for use in encrypting or decrypting the non-volatile security module engine information based on the integrity information. 18. The method of claim 16,
Wherein the security module engine encrypts or decrypts the non-volatile security module engine information only with a secure device using the engine information encrypted symmetric key. The method according to claim 1,
Wherein the security module store restricts access of a generic program coupled to the security module interface. A virtualization-based software security method performed on a computer,
Creating a protection area that operates independently of a general program using the virtualization technology of the computer;
Loading a security module interface connecting the security module engine and the general program and a software security module including the security module engine;
Activating the security module engine and registering the security module interface;
Collecting uncertain information of the software security module;
Generating an engine information encrypted symmetric key based on the integrity information;
Obtaining encrypted security module engine information from a security module repository coupled to the software security module;
Decrypting the encrypted security module engine information using the engine information encrypted symmetric key; And
And registering the decrypted security module engine information.
Virtualization - based software security methods. The method of claim 19,
After registering the security module engine information,
Detecting a command event in the security module interface;
Checking the status of the security module engine;
Transmitting an instruction to an engine interface of the security module engine;
Updating the state of the security module engine;
Transmitting an instruction to an execution engine of the security module engine;
Determining whether command execution by the execution engine is successful;
Updating the state of the security module engine if the command execution is successful; And
And transmitting the result of the command execution from the security module engine to the generic program via the security module interface.
Virtualization - based software security methods.

Images