Tenable SC study plan

Diagram the SecurityCenter/Tenable SC component model (user interface tier, scan tier, data tier) and explain what each tier stores and processes

Install or walk through an installation workflow and record every prerequisite, port, and default credential decision point

Configure the initial organization/zone/repository scaffolding needed before any scan can be launched

List the order-of-operations dependencies between licensing, scanners, zones, and repositories, and justify the sequence

Define scan zones and assign scanner IP ranges so that no two zones overlap, verifying the mapping against a sample address plan

Tune global and organizational settings that affect scan behavior, such as scan timeouts, purge settings, and default thresholds

Differentiate between host discovery, port scanning, and vulnerability plugin evaluation in the scan pipeline and describe where each is configured

Document a rollback path for a misconfigured scanner or zone, including how to re-register or re-zone a scanner safely

Build at least two scan policies from scratch: one broad discovery policy and one targeted policy limited by plugin family and port range

Configure credentialed checks for at least two operating-system families and explain what evidence confirms credentials succeeded

Identify the common causes of failed credentialed scans and write a triage sequence for each

Set scan performance options (host concurrency, plugin timeouts, throttling) and predict their effect on scan duration and accuracy

Compare scheduled, on-demand, and recurring scan configurations and select the right one for a given operational requirement

Create static and dynamic asset lists and confirm which hosts each one resolves to under given filters

Choose between repository types for a stated data-retention requirement and justify the choice in writing

Configure asset import and asset tagging so that ownership metadata survives into reporting

Explain how assets, repositories, and asset lists relate, including what happens to asset records when a repository is purged

Map organizational structure (organizations, groups, users) onto a multi-tenant or business-unit model

Assign roles at each level and trace how a lower-privilege role sees a narrower set of assets and results

Test permission boundaries by logging in as at least two restricted roles and recording what each can and cannot do

Reconcile asset ownership data with the organizational model so reports can be scoped to the right audience

Configure authentication integration options and describe the failure modes when group mapping is wrong

Design a least-privilege role assignment for a scanning team, a remediation team, and an audit team

Audit an existing configuration for over-privileged accounts and propose specific remediations

Document the approval and change-control path for creating a new organization or elevating a user's role

Build dashboards that answer distinct questions for an executive, a remediation owner, and an auditor, using different widgets and time windows

Create scheduled reports in more than one output format and verify delivery to a test recipient

Apply risk recasting, acceptance, and mitigation rules to a sample data set and confirm the effect propagates into dashboards and reports

Rank a set of findings using severity, exploitability, and asset criticality and defend the ordering in writing

Re-run one scenario from each earlier week without notes to confirm retention

Rewrite every personal weak-area note into a corrected one-line rule

Take timed practice sets covering all five domains and categorize every miss by domain and root cause

Finalize a one-page reference sheet of configuration decisions, role names, and report types