<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ivan Burmaka</style></author><author><style face="normal" font="default" size="100%">Nicolai Stoianov</style></author><author><style face="normal" font="default" size="100%">Vitalii Lytvynov</style></author><author><style face="normal" font="default" size="100%">Mariia Dorosh</style></author><author><style face="normal" font="default" size="100%">Svitlana Lytvyn</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Proof of Stake for Blockchain Based Distributed Intrusion Detecting System</style></title><secondary-title><style face="normal" font="default" size="100%">Advances in Intelligent Systems and Computing 1265</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2021</style></year></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pub-location><style face="normal" font="default" size="100%">Cham</style></pub-location><pages><style face="normal" font="default" size="100%">237-247</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ihor Skiter</style></author><author><style face="normal" font="default" size="100%">Ivan Burmaka</style></author><author><style face="normal" font="default" size="100%">Andriy Sigayov</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Design of Technical Methods for Analysing Network Security Based on Identification of Network Traffic Anomalies</style></title><secondary-title><style face="normal" font="default" size="100%">Information &amp; Security: An International Journal</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">anomaly</style></keyword><keyword><style  face="normal" font="default" size="100%">database</style></keyword><keyword><style  face="normal" font="default" size="100%">network monitoring</style></keyword><keyword><style  face="normal" font="default" size="100%">network parameters</style></keyword><keyword><style  face="normal" font="default" size="100%">network traffic</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2020</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2020</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">47</style></volume><pages><style face="normal" font="default" size="100%">306-316</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&lt;p&gt;The article presents the design of a system for analysing technical networks with three main components. The attack generator monitors the network, checks its response, stability, and effectiveness to counter external threats. The database contains data about network parameters, their behaviour over time, network status, incidents, anomalies, etc. The network monitoring module uses information from the database for qualitative analysis of the network status.&lt;/p&gt;&lt;p&gt;The technical data analysis system of the distributed information system consists of two subsystems: the &amp;ldquo;Attacker&amp;rdquo; and the &amp;ldquo;Analyzer.&amp;rdquo; The &amp;ldquo;Attacker&amp;rdquo; is a scanning tool for targeted information monitoring. It generates streams of network attacks with the aim to test the network response, stability, and effectiveness of network protection. The subsystem &amp;ldquo;Analyzer&amp;rdquo; collects information in predetermined periods of time, establishes criticality levels of network parameters; determines the time of the last criticality levels&amp;rsquo; change, records criticality levels values, and reports on the status, errors and script execution.&lt;/p&gt;</style></abstract><issue><style face="normal" font="default" size="100%">3</style></issue><section><style face="normal" font="default" size="100%">306</style></section></record></records></xml>