Konferensiyasi

I.
 
INTRODUCTION 
There are rules for recording all events. If the system is performing a very important 
task and any deviation from the assigned task will cause an unpleasant situation, it is 
necessary to record down to the smallest detail, for systems used for everyday purposes to 
record events that do not significantly affect system performance. may be appropriate. A 
number of factors need to be analyzed to determine the level of record detail: the impact of 
protocol on work speed and memory allocation, the speed of analysis requirements, and the 
appropriateness of cost to enterprise capacity, the task at hand. to be able to fully satisfy, 
and so on.
II.
 
METHODS 
Another concept introduced in the Book of Fire is selective recording, which is the 
process of tracking both consumers and events to determine which ones seem more 
suspicious. autocollection. To do this, the observations are made on the basis of pre-
prepared sample standards, which are insignificant analysis of events by specific 
parameters, and only if the result is unsatisfactory, the details of the event are recorded. 
It should be noted that the protocol and audit depend on other security measures. For 
example, if identification and authentication provide the first information about the 
consumer, the logical management of the application protects the completeness and 
confidentiality of the information recorded. Cryptography can also contribute to this 
process. 
Another feature of protocols and audits is that they serve to prevent possible attacks. 
After all, if you know for sure that they can monitor your work, record it somewhere, 
analyze the essence of the work, then it is natural to refrain from inappropriate behavior! 
Especially if the system user knows that every movement - even every press of a key - is 
recorded! In addition, the accounts not only provide information on the security breach, but 
also provide the information necessary to restore it to its original state (because the 

---