Worker

Workers are the execution layer of OASM responsible for processing scan jobs and interacting with external systems. They operate in a distributed, stateless manner and continuously pull jobs from the Core API.

​

Connecting a Worker

A worker connects to the system using a workspace API key. Once authenticated, it starts pulling available jobs from the Core API and executes them. This pull-based model ensures flexibility and fault tolerance. Workers can join or leave the system at any time without impacting overall stability.

​

Horizontal Scalability

Workers are designed to scale horizontally without limitation. You can run multiple worker instances in parallel to increase processing capacity. This allows the system to handle large-scale scanning workloads efficiently. As demand grows, additional workers can be deployed to distribute the load and reduce execution time.

​

Worker Scope

Each worker operates under a defined scope that determines which jobs it can access:

• This workspace: The worker only processes jobs belonging to its associated workspace.
• Global: The worker can process jobs across all workspaces.

Global workers are typically managed by administrators and are intended for shared infrastructure. When running under this scope, a worker has permission to access and execute jobs from any workspace in the system.

​

Integrated Scanning Tools

Workers are responsible for executing scanning tasks by integrating with external scanning tools. Any tools configured and connected within a worker environment will be reflected in the system interface. This provides visibility into the capabilities available for job execution without requiring direct configuration in the Core API or Console.

​

Worker Visibility

All connected workers are displayed in the Workers section of the Console, including their status, scope, and activity state. This enables real-time monitoring and management of the execution layer.