CN113836097A - Local file security protection method and device - Google Patents
Local file security protection method and device Download PDFInfo
- Publication number
- CN113836097A CN113836097A CN202111151459.8A CN202111151459A CN113836097A CN 113836097 A CN113836097 A CN 113836097A CN 202111151459 A CN202111151459 A CN 202111151459A CN 113836097 A CN113836097 A CN 113836097A
- Authority
- CN
- China
- Prior art keywords
- local file
- risk
- browser
- local
- protection
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000004590 computer program Methods 0.000 claims description 10
- 230000004044 response Effects 0.000 claims description 6
- 238000012790 confirmation Methods 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000001514 detection method Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0635—Risk analysis of enterprise or organisation activities
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0639—Performance analysis of employees; Performance analysis of enterprise or organisation operations
- G06Q10/06393—Score-carding, benchmarking or key performance indicator [KPI] analysis
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Marketing (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- General Business, Economics & Management (AREA)
- Operations Research (AREA)
- Game Theory and Decision Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Library & Information Science (AREA)
- Storage Device Security (AREA)
Abstract
The embodiment of the application discloses a method and equipment for protecting the safety of a local file. One embodiment of the method comprises: opening local file library protection when the browser runs; detecting that a current access page of a browser uploads a local file of a local file library; and carrying out risk prompt based on the local file uploaded by the browser. The method and the system enable any page accessed by the browser to be visible to the operation of the local file library, and risk is controllable.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to a method and equipment for protecting the security of a local file.
Background
With the rapid development of the mobile internet, more and more applications are supported by the terminal device of the user. Currently, one of the most installed applications on a terminal device is a browser. The browser can be used for retrieving, displaying and transmitting Web information resources, and is convenient for users to obtain more information.
However, some browsers may silently upload local files stored on their terminal devices when the user accesses the page, which may cause leakage of personal information of the user.
Disclosure of Invention
The embodiment of the application provides a method and equipment for protecting the safety of a local file.
In a first aspect, an embodiment of the present application provides a method for protecting local files, including: opening local file library protection when the browser runs; detecting that a current access page of a browser uploads a local file of a local file library; and carrying out risk prompt based on the local file uploaded by the browser.
In some embodiments, before detecting that the current access page of the browser uploads the local file of the local file library, the method further includes: and detecting that the current access page of the browser traverses the directory of the local file library.
In some embodiments, after detecting that the current access page of the browser traverses the directory of the local file library, the method further includes: and carrying out risk prompt based on the directory position traversed by the browser.
In some embodiments, opening local file library protection while the browser is running includes: and setting different risk levels according to the file types and/or the file contents of the local files in the local file library.
In some embodiments, the risk level of a text-type local file in the local repository is higher than the risk level of a streaming media-type local file in the local repository.
In some embodiments, for a text-type local file in the local repository, the risk level for a local file containing a preset keyword is higher than the risk level for a local file without a preset keyword.
In some embodiments, the risk prompting based on the local file uploaded by the browser includes: and according to the risk levels of the local files uploaded by the browser, carrying out risk prompting in a risk prompting mode of a corresponding level, wherein the local files of different risk levels correspond to the risk prompting modes of different levels.
In some embodiments, the risk cues include at least one of: prompting by characters; color prompting; voice prompt; displaying a risk page close button; the risk page is automatically closed.
In some embodiments, the risk cues made based on uploading the local file are ranked higher than the risk cues made based on traversing the directory.
In some embodiments, opening local file library protection while the browser is running includes: and in response to detecting that the browser starts to run, starting a local file protection plug-in to open the local file library protection.
In some embodiments, opening local file library protection while the browser is running includes: running a browser, wherein a local file library protection button is arranged on a current access page of the browser; and in response to detecting the confirmation operation of the local file library protection button, starting a local file protection plug-in to open the local file library protection.
In a second aspect, an embodiment of the present application provides a security protection apparatus for a local file, including: the opening module is configured to open the local file library protection when the browser runs; the first detection module is configured to detect that a current access page of the browser uploads a local file of the local file library; the first prompt module is configured to prompt risks based on the local files uploaded by the browser.
In some embodiments, the apparatus further comprises: and the second detection module is configured to detect that the current access page of the browser traverses the directory of the local file library.
In some embodiments, the apparatus further comprises: and the second prompt module is configured to prompt risks based on the directory position traversed by the browser.
In some embodiments, the opening module is further configured to: and setting different risk levels according to the file types and/or the file contents of the local files in the local file library.
In some embodiments, the risk level of a text-type local file in the local repository is higher than the risk level of a streaming media-type local file in the local repository.
In some embodiments, for a text-type local file in the local repository, the risk level for a local file containing a preset keyword is higher than the risk level for a local file without a preset keyword.
In some embodiments, the first prompting module is further configured to: and according to the risk levels of the local files uploaded by the browser, carrying out risk prompting in a risk prompting mode of a corresponding level, wherein the local files of different risk levels correspond to the risk prompting modes of different levels.
In some embodiments, the risk cues include at least one of: prompting by characters; color prompting; voice prompt; displaying a risk page close button; the risk page is automatically closed.
In some embodiments, the risk cues made based on uploading the local file are ranked higher than the risk cues made based on traversing the directory.
In some embodiments, the opening module is further configured to: and in response to detecting that the browser starts to run, starting a local file protection plug-in to open the local file library protection.
In some embodiments, the opening module is further configured to: running a browser, wherein a local file library protection button is arranged on a current access page of the browser; and in response to detecting the confirmation operation of the local file library protection button, starting a local file protection plug-in to open the local file library protection.
In a third aspect, an embodiment of the present application provides a computer device, including: one or more processors; a storage device having one or more programs stored thereon; when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method as described in any implementation of the first aspect.
In a fourth aspect, the present application provides a computer-readable medium, on which a computer program is stored, which, when executed by a processor, implements the method as described in any implementation manner of the first aspect.
According to the method and the device for protecting the local file safety, the local file library protection is started when a browser runs; and then under the condition that the local file of the local file library is uploaded on the current access page of the browser, carrying out risk prompt based on the local file uploaded by the browser. Any page accessed by the browser is operated to the local file library in a visual mode, and risks are controllable.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is a flow chart of a first embodiment of a method for securing a local file according to the present application;
FIG. 2 is a flow chart of a second embodiment of a method for securing local files according to the present application;
FIG. 3 is a flow chart of a third embodiment of a method of securing a local file according to the present application;
FIG. 4 is a flow chart of a fourth embodiment of a method of securing local files according to the present application;
FIG. 5 is a schematic block diagram of a computer system suitable for use in implementing the computer device of an embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 shows a flow 100 of a first embodiment of a method for securing a local file according to the present application. The method for protecting the local file comprises the following steps:
In this embodiment, the execution subject of the security protection method for the local file may open the local file library protection when the browser runs.
Generally, a browser may be installed on a terminal device of a user. In addition, various types of local files including, but not limited to, documents, images, videos, and the like may be stored in the local file repository of the user's terminal device. In order to avoid leakage of personal information of a user when the user accesses a page by using a browser, local file library protection can be opened when the browser runs.
In practice, the opening mode of the local file library protection can comprise automatic opening and manual opening. For automatic opening, a local file protection plug-in may be started to open local file library protection upon detecting that the browser starts running. For manual opening, after the browser is run, a local repository protection button may be set on the currently accessed page of the browser. In the case that a confirmation operation on the local repository protection button is detected, the local repository protection plug-in may be started to open the local repository protection. In general, when the user clicks the local repository protection button, it may be considered that a confirmation operation is performed on the local repository protection button.
In this embodiment, during the running of the browser, the execution main body may detect in real time or periodically whether the currently accessed page of the browser uploads the local file of the local file library. In case an upload of a local file is detected, step 103 is performed. Typically, the currently visited page of the browser may be uploaded with the file stream to the local file through a js (javascript) engine.
And 103, carrying out risk prompt based on the local file uploaded by the browser.
In this embodiment, when it is detected that the local file is uploaded, the execution main body may perform risk prompting based on the local file uploaded by the browser, and notify the user that a currently accessed page of the browser is uploading a certain local file and an address of the local file, so that the user can make a corresponding processing measure in time.
Generally, the risk level prompt mode is various, including but not limited to text prompt, color prompt, voice prompt, display risk page close button, automatic closing risk page, and so on. For example, in the event that an upload of a local file is detected, a pop-up prompt may be provided. The text on the popup window can inform the user that the currently accessed page is uploading a certain local file and the address of the local file. At the same time, the red exclamation point on the pop-up window blinks to alert the user to the risk. In addition, a risk page closing button can be displayed on the popup. And under the condition that the user determines that the risk of user information leakage is brought by uploading the local file, the risk page closing button can be clicked to close the current access page and terminate the uploading of the local file. Of course, the local file may be actively selected by the user to be uploaded through the browser. In this case, the user may close the pop-up window and stop the risk prompt for the file upload.
According to the safety protection method for the local file, firstly, local file library protection is started when a browser runs; and then under the condition that the local file of the local file library is uploaded on the current access page of the browser, carrying out risk prompt based on the local file uploaded by the browser. Any page accessed by the browser is operated to the local file library in a visual mode, and risks are controllable.
With continued reference to FIG. 2, a flow 200 is shown that is a second embodiment of a method of securing a local file according to the present application. The method for protecting the local file comprises the following steps:
In this embodiment, the specific operation of step 201 has been described in detail in step 101 in the embodiment shown in fig. 1, and is not described herein again.
In this embodiment, the execution subject of the security protection method for the local file may detect whether the currently accessed page of the browser traverses the directory of the local file library in real time or periodically. In the event that a directory traversing the local repository is detected, step 203 is performed. Typically, the currently accessed page of the browser can traverse the directory of the local repository of files through the JS engine.
Generally, if a user actively selects to upload a local file in a local text library through a browser, the address of the local file is selected in the browser. At this time, the browser can directly search the local file from the address selected by the user for uploading without traversing the directory of the local file library. For the situation that the browser secretly uploads the local file which is not authorized by the user, since the browser does not yet obtain the address of the local file which the browser wants to upload, the address of the local file is usually obtained by traversing the directory of the local file library. Therefore, before detecting whether the browser uploads the local file, whether the browser traverses the directory of the local file library is detected, and the error alarm of the condition that the user actively selects to upload the local text can be avoided.
And step 204, carrying out risk prompt based on the local file uploaded by the browser.
In the present embodiment, the specific operations of steps 203-204 have been described in detail in steps 102-103 in the embodiment shown in fig. 1, and are not described herein again.
As can be seen from fig. 2, compared with the embodiment corresponding to fig. 1, the process 200 of the method for securing a local file in the present embodiment adds a step of detecting that a browser traverses a directory of a local file library. Therefore, the scheme described in this embodiment performs double detection, and detects whether the browser traverses the directory of the local file library, and then detects whether the browser uploads the local file, so as to avoid false alarm for the situation that the user actively selects to upload the local text.
With further reference to fig. 3, a flow 300 is shown which is a third embodiment of a method of securing a local file according to the present application. The method for protecting the local file comprises the following steps:
In the present embodiment, the specific operations of steps 301 and 302 have been described in detail in step 201 and 202 in the embodiment shown in fig. 2, and are not described herein again.
And step 303, performing risk prompt based on the directory position traversed by the browser.
In this embodiment, the execution subject of the security protection method for the local file may perform risk prompting based on the directory location traversed by the browser, and notify the user that the current access page of the browser is traversing a certain location of the directory of the local file repository, so that the user can make a corresponding processing measure in time.
Generally, the risk level prompt mode is various, including but not limited to text prompt, color prompt, voice prompt, display risk page close button, automatic closing risk page, and so on. For example, a pop-up prompt may be provided in the event that a directory is detected that traverses the local repository of files. The text on the pop-up window may inform the user that the currently accessed page is traversing a location of the directory of the local repository. At the same time, the yellow exclamation mark on the pop-up window blinks to alert the user to the risk. In addition, a risk page closing button can be displayed on the popup. And under the condition that the local file corresponding to the traversed directory position is determined by the user to bring the risk of user information leakage, a risk page closing button can be clicked to close the current access page, so that the browser is prevented from uploading the local file. Certainly, under the condition that the local file corresponding to the directory position determined by the user to traverse does not bring the risk of user information leakage, the popup window can be closed, and the risk prompt of the directory traversal at this time is stopped.
And step 304, detecting that the current access page of the browser uploads the local file of the local file library.
And 305, performing risk prompt based on the local file uploaded by the browser.
In the present embodiment, the specific operations of steps 304-305 have been described in detail in steps 203-204 in the embodiment shown in fig. 2, and are not described herein again.
As can be seen from fig. 3, compared with the embodiment corresponding to fig. 2, the process 300 of the method for securing a local file in this embodiment increases the steps of risk prompting of directory traversal. Thus, the scheme described in this embodiment performs dual risk cues. And risk prompt of directory traversal is firstly carried out, and then risk prompt of file uploading is carried out, so that the risk prompt is prevented from being omitted by a user.
With further reference to fig. 4, a flow 400 is shown which is a fourth embodiment of a method of securing a local file according to the present application. The method for protecting the local file comprises the following steps:
In this embodiment, the execution subject of the security protection method for the local file may set different risk levels according to the file type and/or the file content of the local file in the local file library when the browser is running.
In general, the risk levels of the local files in the local file library can be set differently, so that a user can distinguish different damage degrees caused by leakage of different local files. In practice, since the text-type local files mostly have the personal information of the user, while the streaming media-type local files mostly are files browsed by the user, the personal information of the user rarely exists. Thus, the risk level of a local file of text type is typically higher than the risk level of a local file of streaming media type. For example, the risk level for a text type of local file is a and the risk level for a streaming media type of local file is B. The risk level of leakage of the local file with the risk level A is far higher than that of the local file with the risk level B.
In addition, for the local files of the same file type, the risk levels can be further subdivided according to the file contents of the local files. For example, for a local file of a text type in the local file library, the execution subject may analyze the file content thereof to determine whether a preset keyword is included. The preset keywords are keywords related to personal information of the user, including but not limited to a user name, a password, an account number, a phone number, a card number, a verification code, and the like. It can be seen that the local files containing the preset keywords generally have a high probability of including personal information of the user. While local files that do not contain the preset keywords generally have a small probability of including the user's personal information. Therefore, the risk level of the local file containing the preset keyword is generally higher than that of the local file without the preset keyword. For example, the risk level of the local file containing the preset keyword is a1, and the risk level of the local file without the preset keyword is a 2. The risk level of leakage of the local file with a risk level of a1 is much higher than the risk level of the local file with a risk level of a 2.
And step 403, performing risk prompt based on the directory position traversed by the browser.
In the present embodiment, the specific operations of steps 402-404 have been described in detail in steps 302-304 in the embodiment shown in fig. 3, and are not described herein again.
And 405, according to the risk level of the local file uploaded by the browser, performing risk prompt in a risk prompt mode of a corresponding level.
In this embodiment, the execution main body may perform risk prompting in a risk prompting manner of a corresponding level according to a risk level of a local file uploaded by a browser, and notify a user that a local file of a certain risk level and an address of the local file are being uploaded on a current access page of the browser, so that the user can make a corresponding processing measure in time.
Generally, the risk level prompt mode is various, including but not limited to text prompt, color prompt, voice prompt, display risk page close button, automatic closing risk page, and so on. And uploading the local files with different risk levels can perform risk prompts with different levels, so that a user can conveniently make different treatment measures according to the risk prompts with different levels. For example, in the case of detecting uploading a local file with a risk level of a1, the prompt may be popped first. The text on the popup window may inform the user that the currently accessed page is uploading a local file with a risk level of a1 and the address of the local file. At the same time, the red exclamation point on the pop-up window blinks to alert the user to the risk. In addition, after 5 seconds of popup display, the risk page can be automatically closed, and uploading of the local file is terminated. For another example, in the case where a local file with an upload risk level of a2 is detected, a pop-up prompt may be provided. The text on the popup window may inform the user that the currently accessed page is uploading a local file with a risk level of a2 and the address of the local file. At the same time, the red exclamation point on the pop-up window blinks to alert the user to the risk. In addition, a risk page closing button can be displayed on the popup. And under the condition that the user determines that the risk of user information leakage is brought by uploading the local file, the risk page closing button can be clicked to close the current access page and terminate the uploading of the local file. For another example, in the case that the local file with the upload risk level B is detected, the prompt may be popped up. The text on the popup window can inform the user that the currently accessed page is uploading the local file with the risk level B and the address of the local file. At the same time, the yellow exclamation mark on the pop-up window blinks to alert the user to the risk. Under the condition that the user determines that the risk of user information leakage is brought by uploading the local file, the user can click an inherent browser closing button at the upper right corner of the current access page to close the current access page and terminate uploading of the local file. Of course, under the condition that the user determines that the risk of user information leakage is not brought by uploading the local file, the popup window can be closed, and the risk prompt of the file uploading is stopped.
And the double risk prompting scheme is used for prompting the risk of directory traversal firstly and then prompting the risk of file uploading. Since the directory traversal cannot directly cause the leakage of the personal information of the user, and the file uploading can directly cause the leakage of the personal information of the user, the directory traversal and the file uploading can respectively carry out risk prompting in different levels. In general, risk hints based on uploading local files are ranked higher than risk hints based on traversing the directory. For example, a pop-up prompt may be provided in the event that a directory is detected that traverses the local repository of files. The text on the pop-up window may inform the user that the currently accessed page is traversing a location of the directory of the local repository. At the same time, the yellow exclamation mark on the pop-up window blinks to alert the user to the risk. Under the condition that the user determines that the user information leakage risk is brought by traversing the directory, the user can click an inherent browser closing button at the upper right corner of the current access page to close the current access page, so that the browser is prevented from uploading the local file. Certainly, under the condition that the user determines that the directory traversal does not bring the risk of user information leakage, the popup window can be closed, the risk prompt of the directory traversal is stopped, and the browsing of the currently accessed webpage is continued. Subsequently, in the event that uploading of the local file is detected, a pop-up prompt may be presented. The text on the popup can inform the user that the currently accessed page is uploading a local file and the address of the local file. At the same time, the red exclamation point on the pop-up window blinks to alert the user to the risk. In addition, a risk page closing button can be displayed on the popup. And under the condition that the user determines that the risk of user information leakage is brought by uploading the local file, the risk page closing button can be clicked to close the current access page and terminate the uploading of the local file.
As can be seen from fig. 4, compared with the embodiment corresponding to fig. 3, the process 300 of the security protection method for local files in this embodiment highlights the step of differentiating the risk levels. Therefore, the scheme described in the embodiment differentially sets the risk level so as to facilitate the user to distinguish different harm degrees caused by leakage of different local files. Moreover, the local files with different risk levels can be uploaded to carry out risk prompts with different levels, so that a user can conveniently make different treatment measures according to the risk prompts with different levels.
Referring now to FIG. 5, shown is a block diagram of a computer system 500 suitable for use in implementing the computer devices of embodiments of the present application. The computer device shown in fig. 5 is only an example, and should not bring any limitation to the function and the scope of use of the embodiments of the present application.
As shown in fig. 5, the computer system 500 includes a Central Processing Unit (CPU)501 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data necessary for the operation of the system 500 are also stored. The CPU 501, ROM 502, and RAM 503 are connected to each other via a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The following components are connected to the I/O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output portion 507 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The driver 510 is also connected to the I/O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 508 as necessary.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 509, and/or installed from the removable medium 511. The computer program performs the above-described functions defined in the method of the present application when executed by the Central Processing Unit (CPU) 501.
It should be noted that the computer readable medium described herein can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or electronic device. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present application may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprises a starting module, a first detection module and a first prompt module. The names of these modules do not constitute a limitation on the module itself in this case, for example, the opening module may also be described as a "module that opens the local repository protection when the browser is running".
As another aspect, the present application also provides a computer-readable medium, which may be contained in the computer device described in the above embodiments; or may exist separately and not be incorporated into the computer device. The computer readable medium carries one or more programs which, when executed by the computing device, cause the computing device to: opening local file library protection when the browser runs; detecting that a current access page of a browser uploads a local file of a local file library; and carrying out risk prompt based on the local file uploaded by the browser.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (13)
1. A security protection method of a local file comprises the following steps:
opening local file library protection when the browser runs;
detecting that a current access page of the browser uploads a local file of the local file library;
and carrying out risk prompt based on the local file uploaded by the browser.
2. The method of claim 1, wherein prior to the detecting that the current page of the browser uploads the local file of the local repository, further comprising:
and detecting that the current access page of the browser traverses the directory of the local file library.
3. The method of claim 2, wherein after said detecting that a currently visited page of the browser traverses a directory of the local repository, further comprising:
and carrying out risk prompt based on the directory position traversed by the browser.
4. The method of any of claims 1-3, wherein the opening a local repository protection while a browser is running comprises:
and setting different risk levels according to the file types and/or the file contents of the local files in the local file library.
5. The method of claim 4, wherein the risk level of a text-type local file in the local repository is higher than the risk level of a streaming media-type local file in the local repository.
6. The method of claim 5, wherein for a text-type local file in the local file repository, the risk level of a local file containing a preset keyword is higher than the risk level of a local file without a preset keyword.
7. The method of any of claims 4-6, wherein the risk prompting based on the local file uploaded by the browser comprises:
and according to the risk levels of the local files uploaded by the browser, carrying out risk prompt in a risk prompt mode of a corresponding level, wherein the local files of different risk levels correspond to the risk prompt modes of different levels.
8. The method of claim 7, wherein the risk tips include at least one of:
prompting by characters;
color prompting;
voice prompt;
displaying a risk page close button;
the risk page is automatically closed.
9. The method of claim 8, wherein the risk cues made based on uploading the local file are ranked higher than the risk cues made based on traversing the directory.
10. The method of any of claims 1-3, wherein the opening a local repository protection while a browser is running comprises:
and starting a local file protection plug-in to open local file library protection in response to detecting that the browser starts to run.
11. The method of any of claims 1-3, wherein the opening a local repository protection while a browser is running comprises:
the browser is operated, wherein a local file library protection button is arranged on a current access page of the browser;
and in response to detecting the confirmation operation of the local file library protection button, starting a local file protection plug-in to open the local file library protection.
12. A computer device, comprising:
one or more processors;
a storage device on which one or more programs are stored;
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-11.
13. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111151459.8A CN113836097A (en) | 2021-09-29 | 2021-09-29 | Local file security protection method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111151459.8A CN113836097A (en) | 2021-09-29 | 2021-09-29 | Local file security protection method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113836097A true CN113836097A (en) | 2021-12-24 |
Family
ID=78967347
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111151459.8A Pending CN113836097A (en) | 2021-09-29 | 2021-09-29 | Local file security protection method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113836097A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090222925A1 (en) * | 2008-03-02 | 2009-09-03 | Yahoo! Inc. | Secure browser-based applications |
| CN104239752A (en) * | 2013-06-09 | 2014-12-24 | 腾讯科技（深圳）有限公司 | Method and apparatus for protecting private information during using of browser |
| CN105893863A (en) * | 2015-11-30 | 2016-08-24 | 乐视致新电子科技（天津）有限公司 | Privacy information protection method and device |
| CN106878366A (en) * | 2016-06-20 | 2017-06-20 | 阿里巴巴集团控股有限公司 | A kind of file uploading method and device |
| CN109558730A (en) * | 2018-12-29 | 2019-04-02 | 360企业安全技术(珠海)有限公司 | A kind of safety protecting method and device of browser |
| CN109768992A (en) * | 2019-03-04 | 2019-05-17 | 深信服科技股份有限公司 | Webpage malicious scanning processing method and device, terminal device, readable storage medium storing program for executing |
| CN109784073A (en) * | 2018-12-29 | 2019-05-21 | 360企业安全技术(珠海)有限公司 | Data access method and device, storage medium, computer equipment |
-
2021
- 2021-09-29 CN CN202111151459.8A patent/CN113836097A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090222925A1 (en) * | 2008-03-02 | 2009-09-03 | Yahoo! Inc. | Secure browser-based applications |
| CN104239752A (en) * | 2013-06-09 | 2014-12-24 | 腾讯科技（深圳）有限公司 | Method and apparatus for protecting private information during using of browser |
| CN105893863A (en) * | 2015-11-30 | 2016-08-24 | 乐视致新电子科技（天津）有限公司 | Privacy information protection method and device |
| CN106878366A (en) * | 2016-06-20 | 2017-06-20 | 阿里巴巴集团控股有限公司 | A kind of file uploading method and device |
| CN109558730A (en) * | 2018-12-29 | 2019-04-02 | 360企业安全技术(珠海)有限公司 | A kind of safety protecting method and device of browser |
| CN109784073A (en) * | 2018-12-29 | 2019-05-21 | 360企业安全技术(珠海)有限公司 | Data access method and device, storage medium, computer equipment |
| CN109768992A (en) * | 2019-03-04 | 2019-05-17 | 深信服科技股份有限公司 | Webpage malicious scanning processing method and device, terminal device, readable storage medium storing program for executing |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108509533B (en) | Control method, device and equipment for screen shot file sharing and computer storage medium | |
| US8935755B1 (en) | Managing permissions and capabilities of web applications and browser extensions based on install location | |
| US9219719B1 (en) | Automatic dynamic vetting of browser extensions and web applications | |
| KR102071160B1 (en) | Application Information Methods and Devices for Risk Management | |
| US8935798B1 (en) | Automatically enabling private browsing of a web page, and applications thereof | |
| US20160285859A1 (en) | Method and device for accessing webpage | |
| US9443077B1 (en) | Flagging binaries that drop malicious browser extensions and web applications | |
| US11182500B2 (en) | Sensitive data management | |
| CN110855642B (en) | Application vulnerability detection method and device, electronic equipment and storage medium | |
| US11157576B2 (en) | Method, system and terminal for performing search in a browser | |
| EP3176719A1 (en) | Methods and devices for acquiring certification document | |
| CN110764680B (en) | Method and device for generating simulated keyboard, electronic equipment and computer readable medium | |
| CN110336781A (en) | A kind of method and apparatus based on browser identification terminal uniqueness | |
| US8001099B2 (en) | Maintaining and utilizing copy histories | |
| US20150205767A1 (en) | Link appearance formatting based on target content | |
| US20170017803A1 (en) | Determining potential sharing of private data associated with a private network domain to improve data security | |
| CN114036501A (en) | APP detection method, system, device, equipment and storage medium | |
| CN113836097A (en) | Local file security protection method and device | |
| CN111353296A (en) | Article processing method and device, electronic equipment and computer-readable storage medium | |
| US9965744B1 (en) | Automatic dynamic vetting of browser extensions and web applications | |
| US10606621B2 (en) | Assisting users to execute content copied from electronic document in user's computing environment | |
| CN113486401A (en) | Method, device, equipment and medium for verifying access authority | |
| CN113657334B (en) | Picture identification method and device | |
| US10997262B2 (en) | Infinite scrolling search | |
| CN109523591A (en) | Processing method, device, equipment and the storage medium of picture |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |