How Businesses Choose Encryption Software

1: Common encryption mode on the market

Transparent encryption: The design idea of ​​transparent encryption is based on the Windows file system (filtering) driver (IFS) technology, which works at the Windows kernel layer. When we install computer hardware, we often need to install its drivers, such as drivers for printers and U disks. A file system driver is a virtual driver that treats files as a device. When an application program operates on a certain suffix file, the file driver will monitor the operation of the program and change its operation mode to achieve the effect of encryption.



Environment encryption: The design idea of ​​environment encryption is that the client starts an encrypted sandbox in the case of secrets. The sandbox is a container, and the secret software and files are thrown into the container for encryption. And this container is transparent, the user can't feel its existence. Using the most advanced disk filter driver, file filter driver, network filter driver and other kernel-level in-depth encryption and anti-leak technology, each module only does what it is best at, so it is very stable. Those who do not enter the sandbox mode and those who enter the sandbox mode are separated into two spaces, which are isolated from each other, so there is no need to worry about leaks.



2: Product stability

There is no stability to talk about the application. After seeing the encryption software of various domestic brands, many people are attracted by the peripheral functions of the encryption software and ignore the functionality of the encryption software itself. When selecting a model, first ask whether it is a BS architecture, whether there is desktop control, whether it can be pushed remotely, and whether it can be compatible with LINUX, MAC and other functions. I think these fancy functions can really make the application icing on the cake, but ignoring the core stability of encryption software and talking about functionality is a misunderstanding of encryption software selection.

　　Without contact with encryption software, relying on the experience of selection management software, it is easy to ignore the stability of encryption software. I feel that a mature software development can ensure stability. Encryption software is different from management software. It involves the underlying driver of WINDOWS, which can not only achieve encryption protection, but also ensure system stability. It is a very difficult work in development. Most of the management software are relatively stable, but there are not many products that can truly achieve stable encryption software.

Encryption software is unstable several manifestations

1: destroy files

Destruction of drawing documents is the first enemy of encryption software, which often occurs in transparent encryption software. During the operation of the transparent encryption software, the files are accidentally damaged, which makes the files unreadable. This is the last thing customers want to happen, but it happens. In the early development stage of the encryption software industry, many softwares have this problem. Even now, it is not uncommon for the so-called famous encryption software to destroy files. Transparent encryption software will never destroy the file, it is almost impossible. What is the probability that the drawings will be destroyed under what circumstances. However, once a file is destroyed, it is a very headache for enterprises. Maybe that file is the result of a department or a project team that spent a week or more, and this problem is encrypted in the environment. will not appear in .

For companies in the design industry and companies that need drawings and documents, this issue needs to be carefully considered when selecting models. If a good product is not selected, it will not only be of no help for future use, but also create a lot of problems, affecting the normal work of employees.



2: Frequent conflicts

with , blue screen of death and other phenomena, which is also a typical problem in the use of the company. This kind of frequent system conflict makes users very crazy, and will directly lead to customers giving up the idea of ​​using encryption software. If the encryption kernel is developed by yourself, the solution is relatively simple, which is the process of constantly patching bugs. The more customers the software is applied to, the more bugs are solved, and the system will gradually stabilize. If a few simple bugs of an encryption software cannot be solved for a long time, it is necessary to suspect that it is not independently developed. Some manufacturers have bought other people's kernels or OEM other people's things, and they do not have the ability to control the encryption kernel at all. Some small problems, It is very laborious to solve.

　　Customers use encryption software and have a series of problems such as crashes and slow speeds. Is it a problem with their own software? uncertain! On the one hand, there are employees who are emotionally disgusted with encryption software, and the computer maintenance of small and medium-sized enterprises is not standardized. A little problem is attributed to encryption software without analysis. Therefore, our implementers spend a lot of time investigating the source of the conflict, or proving their innocence, or finding out the cause of the problem for investigation.

　　How to find a stable encryption software? This is really difficult. First of all, you have to test and try it yourself. The test is just to use the functions of the software, but it cannot reflect the overall stability of the software. If conditions permit, it is best to install it on your own computer for normal use for a period of time, so as to test the basic stability of an encryption software. If you can't go ahead with your own trial, is it necessary to sell such a product? However, to prove whether a product is truly stable, it still depends on whether it has a large-scale application. This is at least when the number of customers is more than a few hundred and the number of sites is more than a few thousand. Only then can a product be truly stable.

Three: Product

　　compatibility The stability of the product is inseparable from the compatibility itself. For example, the stability under the system is actually the compatibility with various software and operating system compatibility. We classify it as the basic stability of the software, which actually counts as compatibility. The compatibility we are talking about here is more about the application with other management software or hardware. This is very important. If an encryption software with very good stability cannot be well integrated with other systems, the project may eventually be stuck.

1: Compatible integration of ERP, PDM, OA and other management software.

Transparent encryption software: To ensure that it is used in an encrypted environment, the files exported by ERP are automatically encrypted, and the ERP can read the encrypted files and ensure that the system is normal. The integration of PDM is relatively complicated, and there are many customer requirements. Some customers require the entire ciphertext, encrypted in and out, and can be previewed by the built-in browser and read by the PDM system normally. And some customers require that the files be automatically decrypted when entering the PDM; The PDM of the CS architecture is relatively easy to integrate, but the PDM of the BS architecture is much more difficult and may encounter more problems. Like BS-based PDM, OA also encounters many problems, especially WebOFFICE. At present, there are still very few products that can integrate well with WEBOFFICE. Due to the limitations of transparent encryption, the integration of management software is still poorer than that of environment encryption.

Environment encryption software: The integration of environment encryption software and management software is better, because the encryption mode is different, it will be easier to be recognized by customers in the integration with management software, and environment encryption software can be integrated with management software. to seamless integration. ERP, PDM, including OA and other management software, are compatible with both CS architecture and BS architecture. It can be achieved that only the client PC or the trusted PC can access the management software, without affecting the normal browsing of the built-in browser, and the outgoing files can be encrypted or not. In terms of compatible management software, environmental encryption software is still doing relatively well.



2: Encryption protection of technical drawings, documents, etc.

Since the drawings are to be encrypted, design customers and manufacturing processing center customers must be involved. At present, the most common customers are CNC design, design institutes, research institutes, and advertising companies. Wait. The more tedious part of the drawing design class is that the numerical control class needs to import the drawings into the relevant equipment, and then the equipment is processed.

Transparent encryption software: A better solution is to transmit encrypted files to the machine through software, and automatically decrypt them during the transmission process. Since the integration with the machining center is very frequent, and the software of the machining center is varied, the workload is still relatively large, and the settings can be customized by the user. If this cannot be customized, it will be a headache. pain.

Environmental encryption software: The solution to environmental encryption is generally to send the drawings to the machining center. Because the environmental encryption is not for process control, there will be no problems that cannot be customized due to the variety of software. Decrypt and send the drawings in a direction. When sending to the machining center, you can also make a monitoring backup, because the sending to the monitoring center itself needs to be in plaintext. In the process of sending, for more security, you can make a monitoring backup and perform the files sent to the machining center in the future. An audit to prevent indiscriminate sending of other critical data.

3: Encryption protection for source code

For source code encryption, this category is generally composed of software development companies, hardware product R&D manufacturers, website development, and APP development. Customers need to automatically decrypt when writing chips, and most electronic companies need to program and debug embedded boards or other hardware peripherals. The customer requires that the program source code be encrypted. And it is automatically decrypted when writing to the chip. This requires both the encryption software to support source code encryption, and the encryption software to be able to automatically decrypt the output (similar to a drawing processing center).

Transparent encryption software: In the process of encrypting the source code, many processes need to call the source code. Like the machining center, custom tools are required. For some encryption software, you need to use the task manager to check what process has been called, and copy it down by yourself. , and then do integration, which is very backward, and some software cannot be customized. This will encounter the same problem as the machining center. Once there is such a customer, or the demand in this area, it will inevitably become a headache. There are also some website development customers who need to perform local debugging. If the local debugging is encrypted, the content cannot be seen.

Environment encryption software: During the development process, environment encryption can be handy in the protection of source code according to its own design advantages. When the user is debugging, the trusted settings can be made for the hardware, and the source code is sent to a specific device in plaintext, so that the user can normally make debugging calls. If the user is concerned about the security of the decentralized information, he can set a whitelist and record the hardware debugging files for later review and trace the source.

The above are some key points when selecting encryption software products, and these points are also the criteria for judging the performance of an encryption software. You can refer to the above points to measure the various capabilities of the software and help companies find an encryption software that suits them.

Transfer: http://blog.csdn.net/shenxinda_lu/article/details/47420997