General Information on Targeted Scans
last modified
2007-07-27 11:28
Brief description of the targeted scanning process.
- The targeted vulnerability scan is a relatively new initiatve. The entire RUNet address space is targeted, but the scan will test for a limited number of critical vulnerabilities-- generally only one at a time.
- Information about the vulnerability and remediation steps will be announced in the security_admins mailing list
- Scanning will stop at the end of business hours (5 PM) each day.
- Announcements will be made in the security_admins mailing list as to the progress of the scan.
- Scan targets: Rutgers University Address Space
- 128.6.0.0/16
- 165.230.0.0/16
- 192.76.178.0/24
- 172.16.0.0/12
- Notification of scan results will be made to the Technical Contact (or Group Contact, if available). See the Network Contact Group Guideline for background information.
- Notifications will be made on a rolling basis. When the vulnerability is detected, a ticket will be entered and the Technical Contact will be notified within one business day of the discovery. One of the following outcomes is expected:
- The report correctly identified a vulnerable system. Take steps to remediate the issue. A follow up scan will be launched three business days after the original notification to confirm that the host is no longer vulnerable.
- The report was sent to an incorrect contact and the host is not yours. Please respond to abuse@rutgers.edu to indicate that the contact information is no longer correct, and work with the Network Operations Center to get the information updated.
- The report is a false positive; that is, the appropriate patches have been applied or the host is not a Windows system. Please respond to abuse@rutgers.edu with this information.
It will be helpful for tracking purposes if the SUBJECT: with the Ticket: number is retained in the email response. Please contact abuse@rutgers.edu with regard to any other issues with the targeted vulnerability scan.
Comments and Feedback
Your comments are needed as we seek to provide a useful service to the community. Contact the author or Information Protection and Security.