Before you begin
- Obtain authorization for the systems in scope and the credentials required by the selected collector.
- Select the correct Active client and Active program. Configure one small, known target first.
- A framework profile does not imply every technical collector applies to it. Run only the focus offered for the selected program.
1. Save the assessment scope and credentials
- Open Configuration → Settings & Credentials. Under Organization and server scope, enter the Organization and AD domain if applicable.
- Enter the authorized computers under Explicit server targets, or configure the intended Server IPv4 /24 subnets. For the first test, use a specific authorized host instead of expanding to a broad subnet.
- Click Load / change credential for the audit session credential. Use the account approved for the selected systems; do not assume the MSP Server API key is a target-system credential.
- Under Evidence locations, review Evidence Root and use Browse if you need an approved writable location. The optional external evidence copy root is separate.
- For optional Linux assessment, enable Enable optional Linux Server assessment in Servers / Full assessment, then enter the SSH username and SSH private key path. Leave it disabled when Linux is not in scope.
- Click Save Settings. Reopen the page or inspect the save status to confirm the non-secret scope values were retained.
Check before continuingThe selected workspace has the intended target scope, evidence location and usable session credentials.
2. Configure a network device profile
- In Settings & Credentials → Network & Firewalls, click New device. Enter a Profile label that distinguishes this device or management service.
- Select the actual Vendor and Mode. Enter Devices / scope and Management endpoint according to that connector. An integration/profile label alone does not establish working collector support.
- Enter Username / client ID and Password / API token when that mode needs them. Click Save encrypted device secret rather than placing the secret in the description.
- Select Enabled for assessment, then click Add / update device and Save Settings. Confirm the profile row shows the intended endpoint and scope.
- Open Configuration → Dependencies and click Refresh. Resolve required prerequisites with Repair required prerequisites. Download only the vendor dependencies needed for the selected connector and mode.
Check before continuingThe enabled device row and dependency status match the authorized target and selected collector mode.
3. Run and inspect the result
- Open Run Assessment. Confirm the client and certification/program named above the controls.
- Use Assessment focus (select exactly what this run should execute) to choose the applicable collector/test family. Read its scope description. Full Technical Assessment runs all applicable collectors; it is not required for a first targeted test.
- Click Run Assessment. Watch the progress and status. Use Cancel if you selected the wrong scope; inspect the resulting run state before assuming a cancelled run is complete.
- When the run completes, open Reports (also called Reports & Runs in some views), click Refresh and select the run. Use Open run folder and Open workpapers to inspect the saved evidence and forms.
- Check warnings, No data results and missing observations. Resolve credential, network or prerequisite issues before interpreting a missing result as a pass. Link and review the relevant evidence in the requirement workspace.
Check before continuingA saved run exists for the intended scope, and its results and gaps have been inspected. A completed run is not automatically an approved assessment.
If something goes wrong
Run Assessment is unavailable
Confirm the active client/program, license/write permission and selected assessment focus. Read the displayed status before changing scope.
A collector returns No data
Check the selected target, authentication method and required dependencies. Keep the collector error and rerun the same small scope after correcting it.
A listed vendor has no suitable mode
Do not substitute unrelated credentials or assume a planned integration is implemented. Use supported external/manual evidence and record the coverage gap.