InformationTimezones are a source of contention in larger corporations. On one hand, if infrastructure is configured with time consistent with the local timezone, then it is simpler to co-relate end-user symptoms and logs on end-user equipment with logs from network equipment. On the other hand, in organizations that span multiple time zones, configuring local time can make it easy to mis-match log entries from gear in different time zones.
In some organizations, the solution is to post both local and UTC time in all log entries. In other organizations, all gear is configured for one timezone (either UTC or 'head office time').
The important thing is to have a standard for time zone, and to configure it consistently across all hosts and infrastructure equipment.
Not having a consistent time zone policy across all hosts and infrastructure means that when dealing with a security incident or technical issue, it becomes very easy to mis-match logs as affected hosts span multiple time zones.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
SolutionTo set the timezone, define the timezone name, the offset in hours, then the offset in seconds. The example below shows EST (Offset of -5 hours, zero seconds).
switch(config)# clock timezone EST -5 0
By default no time zone is configured.