2
Tenable SC Specialist Course Exam with precise detailed || || || || || || || ||
answers
(Technology Overview) ||
List types of Tenable.sc sensors - ✔✔Nessus scanner
|| || || || || || ||
Nessus agent ||
(Technology Overview) ||
Discuss hardware requirements for various components - ✔✔Tenable.sc Hardware
|| || || || || || || ||
8GB of RAM || ||
125GB of Storage || ||
Four(4) 2GHz Cores || ||
Nessus Scanner Hardware || ||
4GB of RAM || ||
30GB of Storage || ||
Four(4) 2GHz cores || ||
(Technology Overview) ||
Explain how Tenable.sc and Nessus can be deployed in virtualized environments - ✔✔It can
|| || || || || || || || || || || || || ||
either be deployed through Tenable Core as a virtual image, or implemented as a traditional
|| || || || || || || || || || || || || || ||
application on supported platforms (i.e. rhel, centos, etc) || || || || || || ||
(Technology Overview) ||
Describe licensing for Tenable.sc - ✔✔- IP in two repositories only counts once
|| || || || || || || || || || || ||
- For multiple network interfaces on single host, each interface actively scanned counts
|| || || || || || || || || || || ||
- Host discovery scans do not count
|| || || || || ||
,2
(Deployment Considerations) ||
Identify Tenable.sc and Nessus scanners placements in an environment - ✔✔Tenable.sc is
|| || || || || || || || || || || ||
typically managed by the NOC or SOC.
|| || || || || ||
(Deployment Considerations) ||
Determine required network connection speed between Tenable.sc and Nessus - ✔✔The network
|| || || || || || || || || || || ||
connection between Tenable.sc and Nessus should be persistent and be at least 1MBps.
|| || || || || || || || || || || ||
(Deployment Considerations) ||
Explain factors that should be considered when determining the number of Nessus scanners for
|| || || || || || || || || || || || || ||
deployment - ✔✔The number of Nessus scanners required for a deployment depends on network
|| || || || || || || || || || || || || ||
partitions, network bandwidth, the number of hosts in a network partition and the types of scans
|| || || || || || || || || || || || || || || ||
being run.
||
(Deployment Considerations) ||
Describe connectivity requirements for Tenable.sc and Nessus scanners - ✔✔For every 500 hosts
|| || || || || || || || || || || || ||
that are being scanned, only one Nessus scanner is needed. However, Nessus scanners can be
|| || || || || || || || || || || || || || ||
configured to scan multiple network partitions. || || || || ||
(Nessus Deployment) ||
List the different types of sensors - ✔✔Tenable Core + Nessus,
|| || || || || || || || || ||
Nessus,
Tenable.io
(Nessus Deployment) ||
Define Tenable Core + Nessus - ✔✔Tenable Core + Nessus is a pre-built virtual image for
|| || || || || || || || || || || || || || || ||
VMware, Hyper-V, dedicated hardware and Microsoft Azure.
|| || || || || ||
(Nessus Deployment) ||
Demonstrate the configuration - ✔✔Demonstrate || || || ||
, 2
(Nessus Deployment) ||
Process for Tenable Core + Nessus - ✔✔Review
|| || || || || || ||
(Nessus Deployment) ||
Demonstrate the installation process for Nessus - ✔✔Demonstrate || || || || || || ||
(Nessus Deployment) ||
Demonstrate the configuration process for Tenable.io - ✔✔Demonstrate
|| || || || || || ||
(Tenable.sc deployment configuration) || ||
List the items needed prior to a Tenable.sc installation - ✔✔Items needed prior to installation are:
|| || || || || || || || || || || || || || ||
- Nessus activation code and license key;
|| || || || || ||
- Software;
||
- Deployed host;
|| ||
- IP address of at least one configured Nessus Scanner;
|| || || || || || || || ||
- Credentials;
||
- Network range to be scanned;
|| || || || ||
- LDAP/Active Directory server information;
|| || || ||
(Tenable.sc deployment configuration) || ||
Recall the five optional pieces of LDAP/Active Directory server information - ✔✔- IP address of
|| || || || || || || || || || || || || || ||
LDAP server ||
- Credentials (must have administrative read rights)
|| || || || || ||
- LDAP schema settings
|| || ||
- User schema settings
|| || ||
- Base search string (optional)
|| || || ||
Tenable SC Specialist Course Exam with precise detailed || || || || || || || ||
answers
(Technology Overview) ||
List types of Tenable.sc sensors - ✔✔Nessus scanner
|| || || || || || ||
Nessus agent ||
(Technology Overview) ||
Discuss hardware requirements for various components - ✔✔Tenable.sc Hardware
|| || || || || || || ||
8GB of RAM || ||
125GB of Storage || ||
Four(4) 2GHz Cores || ||
Nessus Scanner Hardware || ||
4GB of RAM || ||
30GB of Storage || ||
Four(4) 2GHz cores || ||
(Technology Overview) ||
Explain how Tenable.sc and Nessus can be deployed in virtualized environments - ✔✔It can
|| || || || || || || || || || || || || ||
either be deployed through Tenable Core as a virtual image, or implemented as a traditional
|| || || || || || || || || || || || || || ||
application on supported platforms (i.e. rhel, centos, etc) || || || || || || ||
(Technology Overview) ||
Describe licensing for Tenable.sc - ✔✔- IP in two repositories only counts once
|| || || || || || || || || || || ||
- For multiple network interfaces on single host, each interface actively scanned counts
|| || || || || || || || || || || ||
- Host discovery scans do not count
|| || || || || ||
,2
(Deployment Considerations) ||
Identify Tenable.sc and Nessus scanners placements in an environment - ✔✔Tenable.sc is
|| || || || || || || || || || || ||
typically managed by the NOC or SOC.
|| || || || || ||
(Deployment Considerations) ||
Determine required network connection speed between Tenable.sc and Nessus - ✔✔The network
|| || || || || || || || || || || ||
connection between Tenable.sc and Nessus should be persistent and be at least 1MBps.
|| || || || || || || || || || || ||
(Deployment Considerations) ||
Explain factors that should be considered when determining the number of Nessus scanners for
|| || || || || || || || || || || || || ||
deployment - ✔✔The number of Nessus scanners required for a deployment depends on network
|| || || || || || || || || || || || || ||
partitions, network bandwidth, the number of hosts in a network partition and the types of scans
|| || || || || || || || || || || || || || || ||
being run.
||
(Deployment Considerations) ||
Describe connectivity requirements for Tenable.sc and Nessus scanners - ✔✔For every 500 hosts
|| || || || || || || || || || || || ||
that are being scanned, only one Nessus scanner is needed. However, Nessus scanners can be
|| || || || || || || || || || || || || || ||
configured to scan multiple network partitions. || || || || ||
(Nessus Deployment) ||
List the different types of sensors - ✔✔Tenable Core + Nessus,
|| || || || || || || || || ||
Nessus,
Tenable.io
(Nessus Deployment) ||
Define Tenable Core + Nessus - ✔✔Tenable Core + Nessus is a pre-built virtual image for
|| || || || || || || || || || || || || || || ||
VMware, Hyper-V, dedicated hardware and Microsoft Azure.
|| || || || || ||
(Nessus Deployment) ||
Demonstrate the configuration - ✔✔Demonstrate || || || ||
, 2
(Nessus Deployment) ||
Process for Tenable Core + Nessus - ✔✔Review
|| || || || || || ||
(Nessus Deployment) ||
Demonstrate the installation process for Nessus - ✔✔Demonstrate || || || || || || ||
(Nessus Deployment) ||
Demonstrate the configuration process for Tenable.io - ✔✔Demonstrate
|| || || || || || ||
(Tenable.sc deployment configuration) || ||
List the items needed prior to a Tenable.sc installation - ✔✔Items needed prior to installation are:
|| || || || || || || || || || || || || || ||
- Nessus activation code and license key;
|| || || || || ||
- Software;
||
- Deployed host;
|| ||
- IP address of at least one configured Nessus Scanner;
|| || || || || || || || ||
- Credentials;
||
- Network range to be scanned;
|| || || || ||
- LDAP/Active Directory server information;
|| || || ||
(Tenable.sc deployment configuration) || ||
Recall the five optional pieces of LDAP/Active Directory server information - ✔✔- IP address of
|| || || || || || || || || || || || || || ||
LDAP server ||
- Credentials (must have administrative read rights)
|| || || || || ||
- LDAP schema settings
|| || ||
- User schema settings
|| || ||
- Base search string (optional)
|| || || ||
