CN115333919B - Side-hanging type information safety monitoring method - Google Patents
Side-hanging type information safety monitoring method Download PDFInfo
- Publication number
- CN115333919B CN115333919B CN202210951715.XA CN202210951715A CN115333919B CN 115333919 B CN115333919 B CN 115333919B CN 202210951715 A CN202210951715 A CN 202210951715A CN 115333919 B CN115333919 B CN 115333919B
- Authority
- CN
- China
- Prior art keywords
- request
- expected
- accord
- fusing
- response
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 21
- 238000012544 monitoring process Methods 0.000 title claims abstract description 21
- 230000002159 abnormal effect Effects 0.000 claims abstract description 66
- 238000001514 detection method Methods 0.000 claims abstract description 12
- 230000001960 triggered effect Effects 0.000 claims description 10
- 230000005856 abnormality Effects 0.000 claims description 9
- 238000007689 inspection Methods 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0823—Errors, e.g. transmission errors
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Maintenance And Management Of Digital Transmission (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a side-hanging type information security monitoring method, which comprises the steps of creating a system interface according to different interfaces of different monitored service systems, and setting an abnormal early warning rule and a fusing rule for the created system interface; and installing a Luajit plug-in and a Confd plug-in for Nginx of different monitored service systems, acquiring request data and return data, classifying the request data and the return data according to a system interface path, acquiring classified system interfaces, and carrying out safety detection on the classified system interfaces. On the premise of not modifying the original service system code, the invention analyzes various parameters requested by the system interface by acquiring the request data record of the Nginx interface of the service system and referring to the preset abnormal early warning rule, fusing rule and IPTV supervision system interface specification, and calculates unstable, non-compliant and unsafe system interfaces, and reflects whether the service system is safe or not by the abnormal constant of the service system interface.
Description
Technical Field
The invention relates to a side-hanging type information safety monitoring method.
Background
With the development of IPTV services, in order to meet the increasing service demands, a plurality of service systems are accessed. The system comprises a large number of interfaces, the stability and compliance of the interfaces can directly influence a service system, so whether the interfaces are available or not and whether the interfaces are compliant or not are necessary conditions for safe broadcasting.
In view of the importance of interface quality monitoring, a method which does not affect a service system and has controllable and early-warning interfaces is urgently needed to ensure the safe broadcasting of the existing network.
Disclosure of Invention
In order to solve the technical problems, the invention provides a side-hanging type information security monitoring method, which realizes side-hanging type access to a service system on the premise of not affecting the existing architecture of the service system, and monitors, controls, pre-warns and fuses the stability and compliance of interfaces of the service system.
The invention is realized by the following technical scheme.
The invention provides a side-hanging type information safety monitoring method, which comprises the following steps:
(1) creating a system interface according to different interfaces of different monitored service systems, and setting an abnormal early warning rule and a fusing rule for the created system interface; installing a Luajit plug-in and a Confd plug-in for Nginx of different monitored service systems, acquiring request data and return data, classifying the request data and the return data according to a system interface path, and acquiring a classified system interface;
(2) performing security detection on the classified system interfaces;
(3) in the safety detection, if an abnormal early warning rule is triggered, a corresponding abnormal early warning message is sent to a system interface responsible person; if the fusing rule is triggered, a corresponding fusing message is sent to a system interface responsible person; if the abnormal early warning rule and the fusing rule are not triggered, the safety compliance inspection is carried out on the system interface according to the IPTV supervision system interface specification, and the inspection is finished and the fusing treatment is not carried out.
The step (1) is divided into the following steps:
inputting system interface information, corresponding expected values and system interface responsible persons according to different interfaces of different monitored service systems, and creating a system interface;
(1.2) setting an abnormal early warning rule and a fusing rule for the created system interface, and sending an abnormal early warning message to a responsible person of the system interface when the expected value meets the abnormal early warning rule; when the expected value meets the fusing rule, directly fusing the system interface and sending fusing information to a system interface responsible person;
(1.3) installing a Luajit plug-in and a Confd plug-in for Nginx of different monitored service systems, outputting complete request data and return data of a system interface, and monitoring Nacos configuration;
(1.4) continuously collecting the request data and the return data output by the Nginx through a filecoat component, delivering the request data and the return data to a Kafka message queue after the collection, and storing the request data and the return data of the Kafka queue into a cache;
and (1.5) acquiring corresponding request data and return data from the cache according to the unit time configured in the Nacos, and performing system interface security check after classifying according to the paths of the system interfaces.
The expected values include expected request parameters, expected response times, expected response states, sensitive word matches, expected visitor IPs, expected request types, expected request headers, expected request protocols, expected response headers;
the request data comprises a request header, a request path, a request type, a visitor IP, a request protocol and request parameters; the return data includes a response host IP, a response header, response parameters, a response status, and a response time.
When the expected value satisfies the fusing rules, all subsequent requests are denied.
The abnormal early warning rule and the fusing rule are as follows:
the request parameters in unit time do not accord with the expected request parameters, the N triggering abnormal early warning is carried out, and the M triggering fusing is not carried out;
the response parameters in unit time do not accord with the expected response parameters, the abnormal triggering early warning is carried out for N times, and the abnormal triggering early warning does not accord with M times;
triggering abnormal early warning for N times when the response time exceeds the expected response time in unit time, and triggering fusing for more than M times;
the response state in unit time does not accord with the expected response state, namely N triggering abnormal early warning and M triggering fusing;
the response parameters in unit time comprise sensitive words and N triggering abnormality early warning, including M triggering fusing;
the IP of the visitor does not accord with the IP of the expected visitor for N triggering abnormal early warning and does not accord with M triggering fusing in unit time;
the request type in unit time does not accord with the expected request type N times of triggering abnormal early warning and does not accord with M times of triggering fusing;
the request head does not accord with the expected request head for N triggering abnormal early warning and does not accord with M triggering fusing in unit time;
the request protocol does not accord with the expected request protocol, namely N triggering abnormal early warning and M triggering fusing in unit time;
the response head does not accord with the expected response head N times of triggering abnormality early warning in unit time, and does not accord with M times of triggering fusing.
The unit time is configured in the Nacos.
The N must be less than M and N cannot be equal to M.
The abnormal early warning and fusing message sending modes are configurable, and can be configured into nailing messages, mails, telephones and short messages.
The safety detection in the step (2) is performed in the following sequence:
a. judging whether the request parameters do not accord with the expected request parameters for N times or not in the unit time period, and judging whether the request parameters do not accord with the expected request parameters for M times or not;
b. judging whether the response parameters in the unit time period do not accord with the expected response parameters for N times or not and whether the response parameters do not accord with the expected response parameters for M times or not;
c. judging whether the response time exceeds the expected response time for N times or M times in the unit time period;
d. judging whether the response state does not accord with the expected response state for N times or not in the unit time period, and judging whether the response state does not accord with the expected response state for M times or not;
e. judging whether the response parameters contain sensitive words N times or M times in a unit time period;
f. judging whether the IP of the visitor does not accord with the IP of the expected visitor for N times or not and whether the IP of the visitor does not accord with the IP of the expected visitor for M times or not in a unit time period;
g. judging whether the request type does not accord with the expected request type for N times or not in the unit time period, and judging whether the request type does not accord with the expected request type for M times or not;
h. judging whether the request head does not accord with the expected request head for N times or not in the unit time period, and judging whether the request head does not accord with the expected request head for M times or not;
i. judging whether the request protocol does not accord with the expected request protocol for N times or not in a unit time period, and judging whether the request protocol does not accord with the expected request protocol for M times or not;
j. judging whether the response head does not accord with the expected response head for N times or not in the unit time period, and judging whether the response head does not accord with the expected response head for M times or not;
the above unit time is the unit time configured in Nacos, and the above N and M are the times set in claim 5.
In the step (3), the processing step of triggering the fusing rule is as follows:
A. calling a Nacos updating method, and automatically modifying Nacos configuration of a monitored system;
B. after the Confd plug-in of the monitored system monitors the Nacos configuration change, immediately backing up the current Nginx configuration file;
C. and modifying Nginx configuration according to a preset Nginx configuration template, enabling the configuration to be effective, realizing the fusing of the system interface, and simultaneously, sending a corresponding fusing message to a responsible person of the system interface according to a notification mode of the fusing rule configuration.
The invention has the beneficial effects that:
1. the stability and compliance of an IPTV service system interface are ensured to the greatest extent, and the side-hanging access service is realized on the premise of not affecting the existing architecture of the service system;
2. the original service system codes are not modified, the system interfaces are analyzed to request various parameters according to preset abnormal early warning rules, fusing rules and IPTV supervision system interface specifications by collecting request data records of the Nginx interfaces of the service system, unstable, non-compliant and unsafe system interfaces are counted, and whether the service system is safe or not is reflected by the side surfaces through abnormal constants of the service system interfaces;
3. for the system interface reaching the preset abnormal early warning rule threshold, abnormal early warning is sent to corresponding staff, and for the system interface reaching the preset fusing rule threshold and not meeting the IPTV supervision system interface specification, the corresponding staff is automatically fused and notified, so that the abnormal system interface is prevented, IPTV service is influenced, and IPTV broadcasting safety is guaranteed to the greatest extent.
Drawings
Fig. 1 is a flow chart of the present invention.
Detailed Description
The technical solution of the present invention is further described below, but the scope of the claimed invention is not limited to the above.
Example 1
The side-hanging type information security monitoring method shown in fig. 1 comprises the following steps:
(1) creating a system interface according to different interfaces of different monitored service systems, and setting an abnormal early warning rule and a fusing rule for the created system interface; installing a Luajit plug-in and a Confd plug-in for Nginx of different monitored service systems, acquiring request data and return data, classifying the request data and the return data according to a system interface path, and acquiring a classified system interface;
(2) performing security detection on the classified system interfaces;
(3) in the safety detection, if an abnormal early warning rule is triggered, a corresponding abnormal early warning message is sent to a system interface responsible person; if the fusing rule is triggered, a corresponding fusing message is sent to a system interface responsible person; if the abnormal early warning rule and the fusing rule are not triggered, the system interface is subjected to safety compliance inspection according to IPTV supervision system interface specifications (technical files of broadcasting television and network audiovisual industry of the people's republic of China-GD/J122-2021), and the inspection is finished, and the fusing treatment is not carried out.
The step (1) is divided into the following steps:
inputting system interface information, corresponding expected values and system interface responsible persons according to different interfaces of different monitored service systems, and creating a system interface;
(1.2) setting an abnormal early warning rule and a fusing rule for the created system interface, and sending an abnormal early warning message to a responsible person of the system interface when the expected value meets the abnormal early warning rule; when the expected value meets the fusing rule, directly fusing the system interface and sending fusing information to a system interface responsible person;
(1.3) installing a Luajit plug-in and a Confd plug-in for Nginx of different monitored service systems, outputting complete request data and return data of a system interface, and monitoring Nacos configuration;
(1.4) continuously collecting the request data and the return data output by the Nginx through a filecoat component, delivering the request data and the return data to a Kafka message queue after the collection, and storing the request data and the return data of the Kafka queue into a cache;
and (1.5) acquiring corresponding request data and return data from the cache according to the unit time configured in the Nacos, and performing system interface security check after classifying according to the paths of the system interfaces.
The expected values include expected request parameters, expected response times, expected response states, sensitive word matches, expected visitor IPs, expected request types, expected request headers, expected request protocols, expected response headers;
the request data comprises a request header, a request path, a request type, a visitor IP, a request protocol and request parameters; the return data includes a response host IP, a response header, response parameters, a response status, and a response time.
When the expected value satisfies the fusing rules, all subsequent requests are denied.
The abnormal early warning rule and the fusing rule are as follows:
the request parameters in unit time do not accord with the expected request parameters, the N triggering abnormal early warning is carried out, and the M triggering fusing is not carried out;
the response parameters in unit time do not accord with the expected response parameters, the abnormal triggering early warning is carried out for N times, and the abnormal triggering early warning does not accord with M times;
triggering abnormal early warning for N times when the response time exceeds the expected response time in unit time, and triggering fusing for more than M times;
the response state in unit time does not accord with the expected response state, namely N triggering abnormal early warning and M triggering fusing;
the response parameters in unit time comprise sensitive words and N triggering abnormality early warning, including M triggering fusing;
the IP of the visitor does not accord with the IP of the expected visitor for N triggering abnormal early warning and does not accord with M triggering fusing in unit time;
the request type in unit time does not accord with the expected request type N times of triggering abnormal early warning and does not accord with M times of triggering fusing;
the request head does not accord with the expected request head for N triggering abnormal early warning and does not accord with M triggering fusing in unit time;
the request protocol does not accord with the expected request protocol, namely N triggering abnormal early warning and M triggering fusing in unit time;
the response head does not accord with the expected response head N times of triggering abnormality early warning in unit time, and does not accord with M times of triggering fusing.
The unit time is configured in the Nacos.
The N must be less than M and N cannot be equal to M.
The abnormal early warning and fusing message sending modes are configurable, and can be configured into nailing messages, mails, telephones and short messages.
The safety detection in the step (2) is performed in the following sequence:
a. judging whether the request parameters do not accord with the expected request parameters for N times or not in the unit time period, and judging whether the request parameters do not accord with the expected request parameters for M times or not;
b. judging whether the response parameters in the unit time period do not accord with the expected response parameters for N times or not and whether the response parameters do not accord with the expected response parameters for M times or not;
c. judging whether the response time exceeds the expected response time for N times or M times in the unit time period;
d. judging whether the response state does not accord with the expected response state for N times or not in the unit time period, and judging whether the response state does not accord with the expected response state for M times or not;
e. judging whether the response parameters contain sensitive words N times or M times in a unit time period;
f. judging whether the IP of the visitor does not accord with the IP of the expected visitor for N times or not and whether the IP of the visitor does not accord with the IP of the expected visitor for M times or not in a unit time period;
g. judging whether the request type does not accord with the expected request type for N times or not in the unit time period, and judging whether the request type does not accord with the expected request type for M times or not;
h. judging whether the request head does not accord with the expected request head for N times or not in the unit time period, and judging whether the request head does not accord with the expected request head for M times or not;
i. judging whether the request protocol does not accord with the expected request protocol for N times or not in a unit time period, and judging whether the request protocol does not accord with the expected request protocol for M times or not;
j. judging whether the response head does not accord with the expected response head for N times or not in the unit time period, and judging whether the response head does not accord with the expected response head for M times or not;
the above unit time is the unit time configured in Nacos, and the above N and M are the times set in claim 5.
In the step (3), the processing step of triggering the fusing rule is as follows:
A. calling a Nacos updating method, and automatically modifying Nacos configuration of a monitored system;
B. after the Confd plug-in of the monitored system monitors the Nacos configuration change, immediately backing up the current Nginx configuration file;
C. and modifying Nginx configuration according to a preset Nginx configuration template, enabling the configuration to be effective, realizing the fusing of the system interface, and simultaneously, sending a corresponding fusing message to a responsible person of the system interface according to a notification mode of the fusing rule configuration.
Example 2
The technical scheme of example 1 is adopted, and:
when the system interface is in a dangerous state, a fusing rule is triggered, and all subsequent requests are refused.
Example 3
The technical scheme of example 1 is adopted, and:
the request parameter does not meet the expected request parameter for N triggering abnormal early warning in unit time, and does not meet M triggering fusing, for example: and the request parameters do not accord with the expected request parameters of abnormality for 3 times within 10 seconds, trigger abnormality early warning and do not accord with 10 times of trigger fusing.
Example 4
The technical scheme of example 1 is adopted, and:
the response parameter in unit time does not accord with the expected response parameter, namely N triggering abnormal early warning and M triggering fusing, for example: and the response parameters do not accord with the expected response parameters for 5 times, triggering abnormality early warning is not accord with 50 times, triggering fusing is not carried out within 30 seconds.
Example 5
The technical scheme of example 1 is adopted, and:
the response time exceeds the expected response time by N times in unit time to trigger abnormal early warning, and exceeds M times to trigger fusing, for example: the response time exceeds the expected response time by 10 times within 1 minute to trigger abnormal early warning and exceeds 30 times to trigger fusing.
Example 6
The technical scheme of example 1 is adopted, and:
the method comprises the steps of installing a Luajit plug-in for Nginx of a monitored service system, realizing Nginx reverse proxy, outputting complete request content (comprising a request header, a request path, a request type, a visitor IP, a request protocol and a request parameter) and return content (comprising a response host IP, a response header, a response parameter, a response state and response time) of a system interface, installing a Confd plug-in for the monitored service system, and monitoring Nacos configuration, thereby realizing side-hanging monitoring.
Wherein, the request content and the return content are both in JSON format.
Claims (8)
1. A side-hanging type information safety monitoring method is characterized in that: the method comprises the following steps:
(1) creating a system interface according to different interfaces of different monitored service systems, and setting an abnormal early warning rule and a fusing rule for the created system interface; installing a Luajit plug-in and a Confd plug-in for Nginx of different monitored service systems, acquiring request data and return data, classifying the request data and the return data according to a system interface path, and acquiring a classified system interface;
(2) performing security detection on the classified system interfaces;
(3) in the safety detection, if an abnormal early warning rule is triggered, a corresponding abnormal early warning message is sent to a system interface responsible person; if the fusing rule is triggered, a corresponding fusing message is sent to a system interface responsible person; if the abnormal early warning rule and the fusing rule are not triggered, carrying out safety compliance detection on the system interface according to the IPTV supervision system interface specification, and ending the detection and not carrying out fusing treatment;
the step (1) is divided into the following steps:
inputting system interface information, corresponding expected values and system interface responsible persons according to different interfaces of different monitored service systems, and creating a system interface;
(1.2) setting an abnormal early warning rule and a fusing rule for the created system interface, and sending an abnormal early warning message to a responsible person of the system interface when the expected value meets the abnormal early warning rule; when the expected value meets the fusing rule, directly fusing the system interface and sending fusing information to a system interface responsible person;
(1.3) installing a Luajit plug-in and a Confd plug-in for Nginx of different monitored service systems, outputting complete request data and return data of a system interface, and monitoring Nacos configuration;
(1.4) continuously collecting the request data and the return data output by the Nginx through a filecoat component, delivering the request data and the return data to a Kafka message queue after the collection, and storing the request data and the return data of the Kafka queue into a cache;
(1.5) acquiring corresponding request data and return data from the cache according to the unit time configured in the Nacos, and performing system interface security check after classifying according to the paths of the system interfaces;
in the step (3), the processing step of triggering the fusing rule is as follows:
A. calling a Nacos updating method, and automatically modifying Nacos configuration of a monitored system;
B. after the Confd plug-in of the monitored system monitors the Nacos configuration change, immediately backing up the current Nginx configuration file;
C. and modifying Nginx configuration according to a preset Nginx configuration template, enabling the configuration to be effective, realizing the fusing of the system interface, and simultaneously, sending a corresponding fusing message to a responsible person of the system interface according to a notification mode of the fusing rule configuration.
2. The side-hung information security monitoring method of claim 1, wherein: the expected values include expected request parameters, expected response times, expected response states, sensitive word matches, expected visitor IPs, expected request types, expected request headers, expected request protocols, expected response headers;
the request data comprises a request header, a request path, a request type, a visitor IP, a request protocol and request parameters; the return data includes a response host IP, a response header, response parameters, a response status, and a response time.
3. The side-hung information security monitoring method of claim 1, wherein: when the expected value satisfies the fusing rules, all subsequent requests are denied.
4. The side-hung information security monitoring method of claim 1, wherein: the abnormal early warning rule and the fusing rule are as follows:
the request parameters in unit time do not accord with the expected request parameters, the N triggering abnormal early warning is carried out, and the M triggering fusing is not carried out;
the response parameters in unit time do not accord with the expected response parameters, the abnormal triggering early warning is carried out for N times, and the abnormal triggering early warning does not accord with M times;
triggering abnormal early warning for N times when the response time exceeds the expected response time in unit time, and triggering fusing for more than M times;
the response state in unit time does not accord with the expected response state, namely N triggering abnormal early warning and M triggering fusing;
the response parameters in unit time comprise sensitive words and N triggering abnormality early warning, including M triggering fusing;
the IP of the visitor does not accord with the IP of the expected visitor for N triggering abnormal early warning and does not accord with M triggering fusing in unit time;
the request type in unit time does not accord with the expected request type N times of triggering abnormal early warning and does not accord with M times of triggering fusing;
the request head does not accord with the expected request head for N triggering abnormal early warning and does not accord with M triggering fusing in unit time;
the request protocol does not accord with the expected request protocol, namely N triggering abnormal early warning and M triggering fusing in unit time;
the response head does not accord with the expected response head N times of triggering abnormality early warning in unit time, and does not accord with M times of triggering fusing.
5. The side-hung information security monitoring method of claim 4, wherein: the unit time is configured in the Nacos.
6. The side-hung information security monitoring method of claim 4, wherein: the N must be less than M and N cannot be equal to M.
7. The side-hung information security monitoring method of claim 1, wherein: the abnormal early warning and fusing message sending modes are configurable, and can be configured into nailing messages, mails, telephones and short messages.
8. The side-hung information security monitoring method of claim 4, wherein: the safety detection in the step (2) is performed in the following sequence:
a. judging whether the request parameters do not accord with the expected request parameters for N times or not in the unit time period, and judging whether the request parameters do not accord with the expected request parameters for M times or not;
b. judging whether the response parameters in the unit time period do not accord with the expected response parameters for N times or not and whether the response parameters do not accord with the expected response parameters for M times or not;
c. judging whether the response time exceeds the expected response time for N times or M times in the unit time period;
d. judging whether the response state does not accord with the expected response state for N times or not in the unit time period, and judging whether the response state does not accord with the expected response state for M times or not;
e. judging whether the response parameters contain sensitive words N times or M times in a unit time period;
f. judging whether the IP of the visitor does not accord with the IP of the expected visitor for N times or not and whether the IP of the visitor does not accord with the IP of the expected visitor for M times or not in a unit time period;
g. judging whether the request type does not accord with the expected request type for N times or not in the unit time period, and judging whether the request type does not accord with the expected request type for M times or not;
h. judging whether the request head does not accord with the expected request head for N times or not in the unit time period, and judging whether the request head does not accord with the expected request head for M times or not;
i. judging whether the request protocol does not accord with the expected request protocol for N times or not in a unit time period, and judging whether the request protocol does not accord with the expected request protocol for M times or not;
j. and judging whether the response head does not accord with the expected response head for N times or not in the unit time period, and judging whether the response head does not accord with the expected response head for M times or not.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210951715.XA CN115333919B (en) | 2022-08-09 | 2022-08-09 | Side-hanging type information safety monitoring method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210951715.XA CN115333919B (en) | 2022-08-09 | 2022-08-09 | Side-hanging type information safety monitoring method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115333919A CN115333919A (en) | 2022-11-11 |
| CN115333919B true CN115333919B (en) | 2023-11-07 |
Family
ID=83921189
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210951715.XA Active CN115333919B (en) | 2022-08-09 | 2022-08-09 | Side-hanging type information safety monitoring method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115333919B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH05146038A (en) * | 1991-11-19 | 1993-06-11 | Toshiba Corp | Interface power supply monitoring device |
| JPH05176370A (en) * | 1991-12-24 | 1993-07-13 | Matsushita Electric Works Ltd | Multiplex transmission interface circuit |
| JP2001258145A (en) * | 2000-03-10 | 2001-09-21 | Toshiba Corp | Protective relay system |
| JP2003044324A (en) * | 2001-07-30 | 2003-02-14 | Fujitsu Access Ltd | Method, device and program for confirming abnormality detection |
| CN108345527A (en) * | 2017-12-29 | 2018-07-31 | 广州品唯软件有限公司 | A kind of interface enters the analysis monitoring method and system of ginseng |
| CN110445688A (en) * | 2019-08-12 | 2019-11-12 | 珠海格力电器股份有限公司 | Interface service function monitoring method and system based on data collection |
| CN110569178A (en) * | 2019-09-12 | 2019-12-13 | 成都中科大旗软件股份有限公司 | interface early warning method and system based on big data platform |
| CN111104213A (en) * | 2019-12-25 | 2020-05-05 | 上海众源网络有限公司 | Method and device for adjusting fusing |
| CN111274094A (en) * | 2020-02-04 | 2020-06-12 | 上海携程商务有限公司 | Interface early warning method, system, equipment and storage medium |
| CN111787073A (en) * | 2020-06-18 | 2020-10-16 | 多加网络科技(北京)有限公司 | Current-limiting fusing platform and method for unified service |
| CN112783730A (en) * | 2021-01-29 | 2021-05-11 | 好活（昆山）网络科技有限公司 | Interface monitoring method, device, medium and electronic equipment |
-
2022
- 2022-08-09 CN CN202210951715.XA patent/CN115333919B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH05146038A (en) * | 1991-11-19 | 1993-06-11 | Toshiba Corp | Interface power supply monitoring device |
| JPH05176370A (en) * | 1991-12-24 | 1993-07-13 | Matsushita Electric Works Ltd | Multiplex transmission interface circuit |
| JP2001258145A (en) * | 2000-03-10 | 2001-09-21 | Toshiba Corp | Protective relay system |
| JP2003044324A (en) * | 2001-07-30 | 2003-02-14 | Fujitsu Access Ltd | Method, device and program for confirming abnormality detection |
| CN108345527A (en) * | 2017-12-29 | 2018-07-31 | 广州品唯软件有限公司 | A kind of interface enters the analysis monitoring method and system of ginseng |
| CN110445688A (en) * | 2019-08-12 | 2019-11-12 | 珠海格力电器股份有限公司 | Interface service function monitoring method and system based on data collection |
| CN110569178A (en) * | 2019-09-12 | 2019-12-13 | 成都中科大旗软件股份有限公司 | interface early warning method and system based on big data platform |
| CN111104213A (en) * | 2019-12-25 | 2020-05-05 | 上海众源网络有限公司 | Method and device for adjusting fusing |
| CN111274094A (en) * | 2020-02-04 | 2020-06-12 | 上海携程商务有限公司 | Interface early warning method, system, equipment and storage medium |
| CN111787073A (en) * | 2020-06-18 | 2020-10-16 | 多加网络科技(北京)有限公司 | Current-limiting fusing platform and method for unified service |
| CN112783730A (en) * | 2021-01-29 | 2021-05-11 | 好活（昆山）网络科技有限公司 | Interface monitoring method, device, medium and electronic equipment |
Non-Patent Citations (3)
| Title |
|---|
| 一种多方式融合的载人设备运行参数监测方法;刘辉1;《中国特种设备安全》;全文 * |
| 供电企业信息安全集中监测预警体系探索与实践;佘世洲;;计算机安全(12);全文 * |
| 制药企业复杂信息系统信息集成服务接口管理设计;赵琦;王丽花;樊丽娟;;中国医药工业杂志(02);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115333919A (en) | 2022-11-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210152287A1 (en) | In-vehicle information processing for unauthorized data | |
| CN109684179B (en) | Early warning method, device, equipment and storage medium for system fault | |
| CN110705834B (en) | Industrial and mining enterprise dangerous state identification method | |
| CN106657387A (en) | Intelligent centralized air-traffic-control automation monitoring system | |
| CN107332715B (en) | Network application system with active performance test and passive shunt control and implementation method thereof | |
| CN107171834B (en) | Short message gateway service platform monitoring and early warning system and method based on gateway early warning pool | |
| CN108923972B (en) | Weight-reducing flow prompting method, device, server and storage medium | |
| CN112953971A (en) | Network security traffic intrusion detection method and system | |
| CN110598423B (en) | Database account management method | |
| CN110224865A (en) | A kind of log warning system based on Stream Processing | |
| CN110730087A (en) | Method and device for processing alarm storm | |
| CN115333919B (en) | Side-hanging type information safety monitoring method | |
| CN111949421B (en) | SDK calling method, device, electronic equipment and computer readable storage medium | |
| CN109617795B (en) | Method and system for sending message | |
| CN111741007B (en) | Financial business real-time monitoring system and method based on network layer message analysis | |
| CN112910733A (en) | Full link monitoring system and method based on big data | |
| CN114285633B (en) | Computer network security monitoring method and system | |
| CN113852984A (en) | Wireless terminal access monitoring system and method, electronic equipment and readable storage device | |
| CN112583817B (en) | Network oscillation monitoring and early warning method, device and medium | |
| CN113473243B (en) | Data processing method and apparatus thereof | |
| CN117424797B (en) | Real-time large concurrent alarm receiving and processing method | |
| CN107786673A (en) | A kind of Internet of things system | |
| US11601353B2 (en) | Device identification apparatus and method based on network behavior | |
| CN110896426B (en) | Intelligent authentication telephone system for safe communication | |
| CN115941428A (en) | Exception handling method and device, electronic equipment and computer readable storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |