Domains and categories
Block or allow content and choose whether subdomains are included.
Web Control
Clear rules for web access.Flexible for the people who work.
Define allowed or blocked sites and categories, create profiles for users and departments, apply schedules and manage temporary exceptions. Policies become active on endpoints only after publication.
CompanyMarketingAdministration
Black listGaming and streamingcategory
White listsocial.exampledomain
ScheduleMon–Fri · 08:00–19:00calendar
RequestsTemporary access allowed30 min
Profile Marketingapplicable policy
01 Policy02 Profiles03 Schedules04 Analytics
A policy people can understand
General rules. Precise exceptions. No ambiguity.
Guided configuration separates what the company blocks or allows from profile-specific rules. Changes remain in draft until they are published.
Users and departments
Specific rules override general rules and follow accounts, groups or organizational units.
Days and times
Control can follow weekly schedules without confusing blocking with logging.
Requests and temporary access
Authorized operators can grant temporary or permanent, revocable access.
Central governance across multiple levels
The policy starts at company level and adapts to each endpoint.
The general configuration establishes company behavior. Profiles and endpoints can then receive more specific rules while preserving a clear hierarchy and one published version to govern.
Every important decision remains visible
Status, published revision, active endpoints and schedules are presented in one view.
Governed exceptions
When a site is genuinely needed, the exception remains controlled.
Two paths. Both traceable.
User, domain, reason, duration and outcome remain recorded and verifiable by authorized administrators.
Approval-based request
A justified exception reviewed by the company IT administrator.
If a domain has been placed in the wrong category, or correctly belongs to a blocked category but is required for a specific work activity, the user can submit a request. The policy determines whether requests are available and defines selectable reasons, durations and any additional justification.
ReasonsChoices aligned with the company contextDurationTime-limited or persistent accessJustificationAn optional or required note
The IT administrator can:
01Grant access for a defined periodOnly to that user and for the time required.
02Add the domain to the White listFor the affected user or profile, or for every user in the company.
03Reject the requestWhile preserving the request, decision and supplied justification.
This is not an informal bypass. The standard request preserves the request, review and outcome within the Argus control perimeter.
Immediate unblock
Immediate access without losing governance.
When a user needs to reach a blocked site immediately, Argus can authorize access without waiting for prior IT review. The unblock is granted only when the capability is enabled by policy and the user still has an immediate unblock available.
AllowanceNumber of unblocks granted by policyDurationConfigured access windowContextDomain, reason and user are recorded
1
The user provides a reasonThe request identifies the domain and operational need.
2
Argus checks the allowanceIf an unblock remains, access is granted immediately.
3
IT remains in controlWhen the allowance is exhausted, the administrator can renew it.
Immediate does not mean invisible. The unblock, duration and justification are recorded and verifiable by administrators.
Governed deployment
One policy, two deployment modes.
Each endpoint can adopt Web Control through the mode best suited to the infrastructure. The Monitor clearly shows what is included, what can be enabled and which checks are required before changing modes.
01
Individual management
Argus directly governs assignment for each endpoint, useful for standalone workstations or heterogeneous groups.
02
Deployment through GPO
In domain environments, deployment can follow Group Policy while remaining centralized across many systems.
03
Preliminary check
Before changing mode, Argus checks endpoint eligibility and highlights conditions that require attention.
Clear assignments before publication
Technical names, status, eligibility and deployment mode make it possible to verify impact before applying changes.
Operational evidence
Web activity becomes measurable over time.
The Monitor shows allowed connections, distinct domains, identified endpoints and users, as well as received and sent volumes. Colored bands distinguish policy intervals and help interpret peaks and gaps.
Peaks and operating windows
Connections and transferred volume remain separate measures.
Continuous classification
New domains are categorized automatically as well.
Argus maintains and updates the classification catalog, progressively including newly observed domains. Company customizations remain layered over the central catalog so each organization retains control of its exceptions.
Thousands of domains become actionable information
Traffic volume, distinct domains and connections show where web activity is concentrated.
The same evidence, multiple perspectives
From domain to company without losing context.
Statistics can be explored by domain, category, user, program, endpoint and company. Each view answers a different question while using the same time range and the same data received by the Argus proxy.
Systems and users in the same view
The perspective changes without losing the analysis period or scope.
Correct interpretation of the data
Observed connections are not a complete browser history.
Statistics represent traffic received by the Argus proxy. Direct or bypassed traffic and blocked connections do not belong to the same telemetry source.
An empty period does not prove there was no browsing activity.Logging level, synchronization, retention and endpoint availability determine the effective coverage.