Skip to main content
A Privilege Elevation rule defines what triggers it (which application, on which endpoints, for which users) and what happens when it does: Auto-elevate, Require approval, or Deny.

The Rules page

1

Open Privilege Elevation

Log in as a user with the Privilege Elevation administrative permission. In the left navigation click Privilege Elevation.
2

Select the Rules tab

The Rules tab shows every configured rule in a grid. It is empty by default until you create one.
Any Management Tool user with the Privilege Elevation administrative permission can create, edit, enable, disable, and delete any rule, regardless of who created it. There are no per-rule permissions and no rule owner.
Privilege Elevation Rules tab with the rules grid

The Privilege Elevation Rules tab.

The rules grid

Click the ⋮ menu next to a rule for Edit, Enable/Disable, or Delete. Filters: Status (multi-select), Elevation Mode (multi-select), Last Update Time (date range). Search matches Name and Description, full or partial text. Sort by Name or Last Update Time.

Bulk actions

Select multiple rules’ checkboxes to Enable, Disable, or Delete them together.
  • Bulk Enable/Disable shows a confirmation: “You are about to change the status of <N> selected rules. Are you sure you want to continue?”
  • Bulk Delete shows: “You are about to permanently delete <N> rules. Are you sure you want to continue?” — deletion is permanent.
Acting on a single rule through the ⋮ menu shows the same confirmations, naming the rule: “You are about to change the status of the <Rule Name> rule. Are you sure you want to continue?” and “You are about to permanently delete the <Rule Name> rule. Are you sure you want to continue?”
If you don’t want a rule to run but aren’t ready to delete it, you can disable it either from the grid’s ⋮ menu, via bulk action, or by clearing the Enabled toggle while editing the rule. A disabled rule stays in the system but is never evaluated.
Deleting a rule does not remove its history. Every elevation it produced stays on the Events tab.

Create a rule

Click Create on the Rules page to open the rule wizard: Details → Elevation Mode → Targeting Criteria → Assign Endpoints → Assigned Users → Summary. The Cancel button discards all changes and returns you to the Rules page.
The next tab stays unavailable until every required field on the tabs before it is complete. Once the rule has all its required settings, you can move freely between tabs.

1. Details

The failure notification names the rule, the assigned user and endpoint, the application, the reason, and the date and time. See when elevation fails for the conditions that trigger it.
Details tab of the Privilege Elevation rule wizard showing rule name, description, and failure notification settings

The Details tab, with the notification settings at the bottom.

2. Elevation Mode

Choose the rule’s core action. Auto-elevate is selected by default.
Launches the application with administrator rights immediately, with no prompt and no approval.Select credentials to use for privilege elevation is required. Choose one or more Secrets (Windows or Active Directory account types) to use as the elevation identity. Only Secrets you have at least PAM User permission on are available; click Add Secret in the drop-down to create one without leaving the wizard. See how the Secret is chosen below.Optionally, enable Auto-elevate during work hours to restrict automatic elevation to a schedule. The schedule fields become available, and mandatory, only while this toggle is on:Choosing Require approval here makes Users who can approve access mandatory. Choosing Always deny reveals a Show warning message to user checkbox, which works the same as on the Deny tab.
If a rule’s configured Allowed dates range expires, the rule doesn’t stop working. It falls back to whatever Action outside of work hours specifies (deny, or require approval).
Elevation Mode tab showing Auto-elevate, Require approval, and Deny options

The Elevation Mode tab, with Auto-elevate scheduling expanded.

Session recording during elevation sits in the Privilege Elevation Recording section and is off by default. It is available for Auto-elevate and Require approval; with Deny selected the section is shown as unavailable, because there is no elevated session to capture. When enabled, it records the screen, keyboard, and command input while a process is elevated, for audit and forensic purposes. See Events and monitoring for how this behaves depending on your license.

How the Secret is chosen

A rule can hold several Secrets. Which one is used is decided on the server, not on the endpoint:
1

The Client reports its state

On start, the Syteca Client sends the server whether the endpoint is domain-joined, along with its hostname and IP address.
2

The server picks one Secret

For a domain-joined endpoint, an Active Directory Secret from the rule is used. If none matches, the server matches the hostname or IP against the rule’s Windows Secrets. For an endpoint that isn’t domain-joined, the server matches hostname or IP against the Windows Secrets directly.
3

Only that Secret reaches the endpoint

The Client receives the single matched Secret. It never receives the rule’s full list of Secrets and never iterates through them locally.
If a rule holds only an Active Directory Secret and the endpoint isn’t domain-joined, elevation fails. See when elevation fails.
A Secret selected for privilege elevation can’t be deleted while it’s in use by a rule. See Delete a secret for the messages shown when deletion is blocked.

3. Targeting Criteria

Define what the rule matches against: manually, by uploading a file to extract its parameters, or both together. Manual and uploaded parameters combine with AND logic, and parameters of the same type combine with OR.
Choose a parameter type, a comparison operator, and a value. A new rule opens with File hash (SHA-256) and Equals already selected.The value field is required, holds up to 5000 characters, and accepts multiple values separated by semicolons. An empty field shows: “This field is required.”Matching is case-insensitive. A wildcard mask (* or *.exe) is supported for Like and Not like only.Click +Or to add another condition of the same logical group, or +And to add a condition that must also be true. Conditions of the same parameter type combine with OR; different parameter types combine with AND. The X button appears once a rule holds two or more conditions, and removes the one next to it.
Once a rule holds five conditions, the tab shows a reminder: “Use simple rules to reduce rule evaluation time.”

Extract parameters offline

For SaaS customers, or anyone who prefers not to upload files to the Management Tool, the Offline Parameters Extractor is a small, standalone Windows utility you run locally.
1

Download and run the tool

Download the Offline Parameters Extractor and run it on any Windows computer. No installation and no server connection are required.
2

Choose a file

Click Browse and select a .exe or .msi file.
3

Copy the extracted values

The tool displays File hash (SHA-256), Executable name(s), Path prefix, and Digital signature, each with its own Copy button. A field that couldn’t be extracted shows Empty.
4

Paste into your rule

Paste the copied values into the corresponding manual-entry fields on the Targeting Criteria tab.
The tool never uploads or executes the file. It only reads it locally to extract metadata, and isn’t included in the standard server installation package.

4. Assign Endpoints

Select at least one endpoint or endpoint group. If none is selected, the tab shows: “At least one Endpoint or Endpoint group must be selected.”
Domain Computer groups combines with Endpoints and Endpoint groups using AND logic, so if you specify a domain group you must also select at least one endpoint or endpoint group. The Domain Computer group field on its own is not mandatory. Endpoints and Endpoint groups combine with each other using OR logic. The PAM Client group can’t be selected here.
Each added item appears with an X to remove it individually. Clear All appears once a section holds at least one item and removes everything in that section at once.

5. Assigned Users

Choose whether the rule applies to everyone, or to specific users. All is selected by default. Add entries to the grid with Add, then fill both columns: Both columns are mandatory. An empty column shows “This field is required.” under the field, and the entry isn’t saved. Use the tick icon to save a row, the pencil icon to edit it, and the X icon to remove it. Remove All appears once the grid holds at least one entry.
Autocomplete queries Active Directory only when a Domain is selected, and returns at most 20 suggestions plus the exact text you typed. Selecting a Computer returns only the typed value, with no directory lookup. Selecting * searches across every available domain.
Exceptions are configured the same way, in their own grid, and always override the main selection. A user listed as an exception is excluded from the rule even if they would otherwise match.
The Exceptions grid is available with both All and Selected, and may be left empty. To apply a rule to everyone except a few people, choose All and list those people as exceptions. Choosing Selected and filling in only the Exceptions grid is not enough: the Users and User Groups grid still needs at least one entry.

6. Summary

Review every section before saving: Elevation Mode, Targeting Criteria, Assigned Endpoints, Assigned Users (with exceptions). Each section has its own Edit link, which jumps to the matching tab. An Impact preview shows the total number of endpoints the rule will affect. Where a section holds more than three values, only the first three are listed, followed by a +N more indicator. Clicking it reveals the rest.
If a required setting is missing (for example, Require approval selected with no approver defined), the Summary tab highlights it in a red error block so you can fix it before saving.
Click Save to activate the rule and return to the Rules page, where it now appears in the grid.

Edit a rule

Opening an existing rule for editing starts on the Summary tab, where you can jump to any section via the left navigation or that section’s Edit link. A tab opened through Edit behaves exactly as it does when you navigate to it manually. Changes are saved as you move between tabs, whether you use the tab navigation or the Next and Back buttons, and Save commits them and closes edit mode. Cancel discards changes made in that session and returns you to the Rules page. Mandatory fields left empty block saving and are highlighted.

How rules are matched

When a user runs something that triggers elevation, Syteca evaluates every enabled rule and works out which ones apply to the current context. A rule is matched only if all of the following hold:
  • The rule is enabled.
  • Its endpoint and user targeting covers the endpoint and the user.
  • Its targeting criteria match the application, whether entered manually or extracted from a file.
  • Its schedule constraints, if configured, are satisfied.

How conflicting rules resolve

If more than one enabled rule matches the same elevation attempt, Syteca doesn’t pick a rule arbitrarily. It applies the most restrictive matching decision, in this order:
  1. Deny (most restrictive)
  2. Require approval
  3. Auto-elevate (least restrictive)
In other words: if even one matched rule says Deny, the result is Deny, regardless of what any other matched rule allows. If none say Deny but at least one says Require approval, the result is Require approval. Only if every matched rule says Auto-elevate does the attempt actually auto-elevate.

What happens when the Client starts enforcing a rule

1

No changes until the first rule is saved

After installing the Syteca Client, nothing changes on the endpoint until you save an enabled Privilege Elevation rule targeting it.
2

UAC is intercepted, not removed

Once a rule is active, the Syteca Client enforces Windows UAC settings so that elevation always triggers a prompt, making silent unmanaged elevation impossible, and intercepts that prompt before it completes to evaluate your rules against it.
3

Group membership is untouched

Privilege Elevation does not remove any user from the local Administrators group. It governs how elevation happens, not who’s technically capable of it.
Upgrading to a version with Privilege Elevation adds the new page and rules to the Management Tool but changes nothing by default. The native Windows UAC continues to work exactly as before until you create and enable your first rule.

Windows UAC policies that Privilege Elevation changes

To guarantee that every elevation attempt produces a prompt it can intercept, the Syteca Client sets four Windows UAC security policies on the endpoint: These policies live under Security Settings → Local Policies → Security Options in Local Security Policy or Group Policy.
A change to “Run all administrators in Admin Approval Mode” takes effect only after the endpoint restarts. Windows enables this policy by default, so endpoints where it has never been changed need no action. On endpoints where it has been disabled, Syteca sets it back to Enabled, and that endpoint must be rebooted before Privilege Elevation rules are enforced on it.
Review these four settings on your target endpoints before you deploy Privilege Elevation. If your organization has changed any of them away from the Windows defaults, include a reboot window in your rollout plan so the rules take effect when you expect them to.

Multi-tenant and high availability

In multi-tenant mode, the Privilege Elevation page is added to every tenant, and rule evaluation works the same way for a non-default tenant as for the default one.

Overview

What Privilege Elevation does and how it’s licensed.

Events and monitoring

Every elevation decision, logged and searchable.

End-user experience

What a user sees when a rule applies to them.

Add a secret

Create the Secret a Require approval or Auto-elevate rule uses.