Admin
Data sources & connectivity
Two settings decide where your data comes from and how ThreatWeaver reaches the outside world: the Data Sources page picks which scanner engines supply your assets and vulnerabilities, and the Proxy page routes outbound traffic through a corporate proxy when your network requires one.
What it's for
- Choose your scanner engine(s) — run a single source, or combine several so your exposure views draw on all of them.
- Reach the internet through your proxy — send ThreatWeaver's outbound connections through a corporate HTTP or SOCKS5 proxy, and verify it works.
Data Sources
The Data Sources page controls which engine(s) feed the Vulnerability Management views. Credentials and sync schedules for those engines live in the API configuration and sync areas of the same Admin menu — this page is only about which engines are switched on.
Selection mode
| Mode | What it does |
|---|---|
| Single | One engine is active at a time; dashboards and lists show only its data. Turning on a different engine replaces the current one. |
| Multiple | Any number of engines can be active at once; exposure views combine the active providers. A note appears when more than one engine is contributing. |
Engine cards
Each supported engine has a card describing what it is and its availability. A card is marked Active when it's switched on, Preview when it's available but not yet generally available, or Coming Soon when it can't be selected yet.
| Control | What it does |
|---|---|
| Engine toggle | In Single mode, switches this engine to be the one active source. In Multiple mode, adds or removes this engine from the active set. |
Each toggle shows an "Applying…" note while the change saves, and coming-soon engines are disabled until they're available.
A Preview card doesn't mean nothing works yet — for Qualys VMDR and Rapid7 InsightVM you can already enter credentials and confirm the connection today; see Scanner connections & scan history import for what's live now versus still on the way for those two engines.
Proxy
If your network only reaches the internet through a proxy, configure it here so ThreatWeaver's outbound connections succeed.
Enable / disable
A status card at the top shows whether the proxy is Enabled or Disabled, and when it was last tested. Use Enable / Disable to switch it on or off.
Configuration
| Control | What it does |
|---|---|
| Proxy Type | Choose HTTP or SOCKS5. The default port updates to match. |
| Proxy Host | The hostname or IP address of your proxy server. |
| Proxy Port | The port your proxy listens on. Common ports are suggested beneath the field. |
| Proxy Authentication | An expandable section for a Username and Password if your proxy requires them. The password field can be revealed with the eye icon and shows a masked marker when a value is already saved. |
Advanced settings
| Control | What it does |
|---|---|
| No-Proxy List | A comma-separated list of hosts that should bypass the proxy and connect directly. |
| DNS over Proxy | Routes DNS lookups through the proxy too. Available only for SOCKS5 proxies. |
Connectivity
| Control | What it does |
|---|---|
| Test Connection | Makes a test request through the proxy and reports success or failure with the round-trip time. |
| Run Diagnostics | Checks reachability to the services ThreatWeaver depends on and lists each result with its status and timing. |
| Save Proxy Settings | Stores the configuration. |
Common workflows
Workflow: switch your active scanner engine
-
On the Data Sources page, set Selection Mode to Single.
-
On the engine you want, flip its toggle to make it the active source. A confirmation appears once it applies.
Step — activating a single engine -
To draw on several engines at once instead, switch to Multiple and turn on each engine you want to include.
Workflow: configure and test a proxy
-
On the Proxy page, click Enable, then choose the Proxy Type and enter the Host and Port.
Step 1 — entering the proxy address -
If your proxy needs credentials, expand Proxy Authentication and enter a Username and Password.
-
Click Test Connection to confirm it works, then Save Proxy Settings.
Step 2 — a successful connection test