Probably the first step in securing snmp access is to create good community strings (and control who has the community strings). Also you can configure access lists to work in conjunction with the community strings to limit who has snmp access to the router.
I would suggest the usage of SNMP v3 otherwise it wont matter how strong you create your community strings because they will be sent as clear text, and someone with a sniffer can eassily decode them. Here is a link on how to configure SNMP v3
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...