RC-Scanner FAQ

FAQ

Q: Can RC-Scanner scan IPv6 targets?

A: Yes, provided the appliance itself has working IPv6 connectivity. The scanner connects to targets over their IPv6 address, so the appliance needs a usable IPv6 path to the target network.

What happens if the appliance has no IPv6 interface?

The connection cannot be established and scans against IPv6 targets will fail.

How do I confirm the appliance can scan a given IPv6 target?

Verify IPv6 reachability from the appliance to the target network before scanning. A successful scan of a known-good IPv6 host is the most reliable check.

Q: How does the RC-Scanner get updated?

A: Updates are fully automatic via GitOps

Software updates:

• ArgoCD continuously monitors GitOps repository

• Detects new versions of components

• Automatically applies updates to scanner

• No manual intervention required

Rule updates:

• rule-synchroniser periodically check for updates and download the changes

• Applies updates to local rules-db

• Runs automatically on a fixed schedule

Workflow templates updates:

• Cronjob to sync the workflows with Outscan

• Runs automatically on a fixed schedule

Q: How do I know if my scanner is up to date?

A: Check ArgoCD sync status. All applications should show "Synced" status.

kubectl get applications -n argocd

Q: How do I troubleshoot issues with scans and deployments?

A: Go to ArgoCD UI or Argo Workflows UI

After you complete the installation. Now you can use these 2 commands to get access to RC-Scanner ArgoWF and ArgoCD

// Get ArgoCD password, the username is admin
kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d
// Get ArgoWF token
kubectl -n vm-scans get secret argo-admin-token -o=jsonpath='{.data.token}' | base64 -d

• Now you can access RC-Scanner ArgoCD via https://<your-vm-ip>:30080

  • With username: admin

  • Password: is in the upper script

• And ArgoWF via http://<your-vm-ip>:32746

  • Enter this to the token section

    • Bearer <the-token-you-get-from-the-upper-script>

Q: Should I troubleshoot or replace a broken scanner?

A: Replace, not repair. RC-Scanner is designed for replacement rather than repair.

• All critical data stored in Outscan (scan configurations, scan data, scan logs)

• Replacement only takes about 15-30 minutes

• Fresh installation guarantees known-good state

Q: Where do RC-Scanner's detection rules come from?

A: RC-Scanner does not maintain its own rule set. Rules are synchronized from Outscan, which acts as the source of truth. The appliance uses these rules to evaluate scan data and generate findings against discovered assets.

Q: Does the appliance need to sync before it can produce findings?

A: Yes. Without a synchronized rule set, the appliance can still discover and identify assets, but it cannot generate findings from them.

Q: How long does synchronization take?

A: On a stable connection, the appliance completes rule synchronization in approximately 10–15 minutes. Allow for this before expecting a newly deployed or newly resynced appliance to generate findings. On a slow or intermittent connection, synchronization takes longer.

Q: How do I replace a scanner?

A:

• Hit the Re-link button on the scanner config on Portal, save the newly generated token

• Remove the existing cluster entirely by removing k3s

k3s-uninstall.sh

• Run rc-scanner-bootstrap with the --token flag, using the generated token

• Deploy RC-Scanner from fresh state