2. NMAP
3. Nessus
4. You can create different policies to scan different things to see what risks you have in different departments.
5. Yes, because they can be exploited and an attacker can create a backdoor into the computer.
6. In the Nessus after scan report and it will give you recommendations on what to do to mitigate the risk.
7. The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft Internet Information Services (IIS) 7.0, mod_ssl in the Apache HTTP Server 2.2.14 and earlier, OpenSSL before 0.9.8l, GnuTLS 2.8.5 and earlier, Mozilla Network Security Services (NSS) 3.12.4 and earlier, multiple Cisco products, and other products, does not properly associate renegotiation handshakes with an existing connection, which allows man-in-the-middle attackers to insert data into HTTPS sessions, and possibly other types of sessions protected by TLS or SSL, by sending an unauthenticated request that is processed retroactively by a server in a post-renegotiation context, related to a "plaintext injection" attack, aka the "Project Mogul" issue.
8. It’s a tool for practitioners because they can see what vulnerability they need to correct and patch,and it’s a hacker’s tool because it lists the vulnerability they can exploit.
9. They can set up a WSUS server that runs at certain times and holds the updates that can bring down the computer because the update hasn’t been tested yet.
10. I would define the tools needed as both give excellent information that will help safeguard the network and tell you what is needed as eliminating a lot of the risk.