How to package signatures back to *.pkg file after they are customized
I have an unusual task to reduce the number of signatures to deploy them to IOS router. The point is it is 871 router with only 128MB of RAM much of it is utilized and the router actually runs low on memory. I would like to minimize the number of active signatures from the basic set to only critical ones. So, the idea is deploy a basic set to a reference router, retire those signatures I don't need and then package everything back to a pkg file that will be pushed to about 80 production routers at the remote locations.
Re: How to package signatures back to *.pkg file after they are
Router memory and resource constraints prevent a router from loading all Cisco IOS IPS signatures. Thus, it is recommended that you load only a selected set of signatures that are defined by the categories. Because the categories are applied in a "top-down" order, you should first retire all signatures, followed by "unretiring" specific categories. Retiring signatures enables the router to load information for all signatures, but the router will not build the parallel scanning data structure.
Retired signatures are not scanned by Cisco IOS IPS, so they will not fire alarms. If a signature is irrelevant to your network or if you want to save router memory, you should retire signatures, as appropriate.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...