The System page is administrator-only tooling for tenant-wide operational settings and visibility into platform-driven scan timing. Open it from the account menu (user avatar, top-right) → System Configurations.
Page layout
- Emergency Stop -- Red control in the header area to halt active system scanning operations immediately when required (use only when you understand the impact).
- Tabs:
- Configurations -- Key/value settings stored for your organization (below).
- Metrics -- May appear only in certain environments (for example on-prem or staging); not shown in all SaaS builds.
- Scan Timeline -- Read-only overview of automated scan schedules across the shared S4E execution layer (below).
- Accessibility Checker -- Accessibility-related checks for the product experience.
Administrator access
If you do not see System Configurations in the account menu, your user does not have administrative privileges.
Configurations
On the Configurations tab you maintain organization-level secrets and runtime tuning. Typical elements:
| Element | Purpose |
|---|---|
| Search | Narrow the configuration list by key name. |
| Available Keys | Opens documented keys you are allowed to set. Today this includes Web vulnerability scanning and Slow Mode (scan throttling) (see below). Additional documented keys appear here as they are exposed in the product. |
| + Add Config | Create a custom entry: supply a key and value. Use this for AI-based scan runtime settings and other keys documented by S4E, in addition to the keys listed under Available Keys. |
Configurations are listed in a table with Key, Value (often masked after save), Added at, and row Actions (for example edit or delete).
Web vulnerability scanning keys
Under Available Keys, the Web vulnerability scanning section explains how the recurring web vulnerability task behaves per tenant. Supported keys:
| Key | Type | Default | Description |
|---|---|---|---|
WEB_VULN_MAX_PARALLEL_ASSET |
int | Unlimited | Maximum number of assets scanned per run. |
WEB_VULN_MAX_PARALLEL_SCAN_PER_ASSET |
int | Unlimited | Maximum number of scans per asset per run. |
Notes:
- URL selection happens per (asset, port). Up to 10 URLs can be chosen per pair, and URLs must not have been scanned in the last 20 days.
Slow Mode (scan throttling) keys
Under Available Keys, the Slow Mode (scan throttling) section limits how many scans a single user can run at the same time. Use this for noisy neighbors, fragile targets, or customers that must stay under a hard concurrency cap — without slowing down everyone else on the shared scan queues.
| Key | Type | Default | Description |
|---|---|---|---|
SLOW_MODE |
bool | Off | Turn slow mode on for this user (accepts 1 / true / yes / on). |
SLOW_MODE_WORKERS |
int | 2 | How many of this user's scans may run in parallel (minimum 1). |
SLOW_MODE_INFRA |
string | (auto) | Optional cluster pin; must be one of the user's infra clusters when set. |
Notes:
- Purpose: Isolate and throttle one user's
first_scanand continuous scans on a private queue so they cannot flood shared workers. - Jobs are routed to
slow_{cluster}_u_{user_id}; first and regular scans share the same worker cap. Global, stress, and manual group scans are unchanged. - If Redis/pool setup fails, routing fails open to the normal priority queues so jobs are not dropped.
AI scans and other configurations
Runtime parameters for AI-generated or AI-related scans use the same Configurations table. Add the key/value pair supplied in S4E documentation or by support via + Add Config. When those keys are published in-product, they also surface under Available Keys alongside web vulnerability scanning and Slow Mode.
Warning
Misconfigured keys can affect scanning coverage or performance. Prefer copying keys exactly from Available Keys or from official guidance.
Scan Timeline
Open the Scan Timeline tab for a cross-tenant view of automated scanner cadence: which scan definitions are queued on the shared S4E scheduler, how often they run, when they last ran, and when the next run is expected.
Typical behaviours:
- A yellow banner may appear when Skip Configuration rules are active, for example: Scheduler skip configuration is active. Your scans will be skipped based on this configuration.
- Filters help narrow the list: Search, Asset Type, Scan Tools, AI Scans (similar in spirit to other results screens that separate AI-created workload).
- Columns often include Scan name, Last Run Time, Scheduled Time, Scan Interval, Status (for example Scheduled), Severity, and Asset Type (targets such as domain, IPv4, subdomain, or URL).
This view answers “when does the platform plan to fire this recurring scan globally,” not manual one-off scans you start yourself. Use it for planning and correlating outages or skip windows with expected activity.
What's Next?
- Skip Configuration -- Define cron-based windows when automated scans must not run.
- Users & Roles -- Confirm who qualifies as an administrator.