Each juniper switch syslog is unique, all having different lengths, different types of entries based on the configuration of the network it is providing switching services for, and on the configuration of the juniper switch syslog itself. One thing that all juniper switch syslog have in common is the difficulty in sorting through the vast amounts of entries contained within the juniper switch syslog. This can be necessary when looking for a specific data transaction, or just general juniper switch syslog inspections with an admin should do on a regular basis. There are times when the traffic across a switch might prove necessary to filter through and identify specifics on what types of communications are taking place.
In the instance of a virus being present on a network, there are reasons you might dip into a juniper switch syslog. When a virus infects a computer, often times it tries to reproduce itself onto other computers by doing ping sweeps of the network that it is connected to. Then, the virus can attempt to access shared resources once it has located a target machine. By accessing the juniper switch syslog, you can see where this suspicious activity is originating from by searching for specific types of log entries. The average computer will not be sending echo requests to all IP addresses on its own subnet, but when that activity is present on a juniper switch syslog, then the computer that is sending the traffic is likely the infected machine.
This is one of many scenarios where the inspection of a juniper switch syslog can take place for a specific reason of tracking down the source of a network security issue. While it may not seem as serious as a hacker, a virus is certainly a security mater and warrants immediate response.