Yes, signatures 3327 and 3328 in signature update S49 will catch the buffer overflow attack used by the worm. Due to false positives, signature 3327 should be tuned to just inspect traffic on port 135, not ports 139 or 445. In addtion, you can add a custom signature to catch a host infected by the atempting to request a copy of worm payload file using TFTP. Here are the necessary parameters:
Whether or not your sensor will see this worm on your network depends on the positioning of your sensor due to the nature of the way the worm spreads. It limits most of it's scanning activity to the local network segment of the infected host. If your sensor is positioned such that only inter-network communication is seen and it can not see intra-network communication you will probably not see many if any alarms.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...