Method and device for preventing enterprise product authorization file from being leaked

Abstract

The invention discloses a method and a device for preventing enterprise product authorization files from being leaked, and the method comprises the following steps: S1, carrying out the deployment of a system through a system deployment module, and forming a deployment environment; S2, binding the authorization file with the deployment environment; S3, after the system obtains the authorization file, verifying the authorization file with the deployment environment; and S4, if the verification is passed, determining that the authorization file can be used; if verification fails, determining that the authorization file cannot be used. Through the method and the device, the authorization file and the deployment environment are bound, the authorization file has no leakage risk, and the use limitation of the authorization file can also be realized under the condition of no networking.

Description

technical field [0001] The invention relates to the fields of computer and information technology and industrial control security, in particular to a method and device for preventing enterprise product authorization documents from leaking out. Background technique [0002] For enterprise-oriented software, the issue of reuse and leakage of authorized files needs to be considered. Leakage or abuse of authorization files is a great loss to the enterprise. Java-based software products are generally release packages composed of compiled files. class, and the source code is easily decompiled by tools such as JAD, and part of the code is re-implemented accordingly to skip license verification. In view of this, in the prior art, the difficulty of being cracked is generally increased in the process of compiling or class loading, or restricted through network verification. [0003] At present, when the enterprise authorization document is verified, it can be restricted through onli...

AI Technical Summary

Problems solved by technology

[0004] However, for many financial companies, the company's internal network restrictions cannot be connected to the Internet, so the authorization file itself may not be able to be verified online

If it is not verified online, it is difficult to control the authorization file from being used multiple times

There are also situations where the authorization file is bound to the hardware address, but this cannot support the situation of system migration; and now many systems are deployed in containers, and there is no stable hardware address for binding

Images