Zum Inhalt springen
Prototyp pruefen

Policy Engine

This specification defines the Policy Engine: evaluation model, priority hierarchy, action catalog, conflict resolution, and fail-closed semantics.

Audience: Security engineers, platform engineers.


In-ScopeOut-of-Scope
Policy evaluation order and conflict resolutionDetection and scoring logic
Action catalog (warn/block/approve/notify)Event persistence and delivery
Profile types and inheritanceCloud Enrichment processing
Safety constraints (lockout prevention)GUI/UX for policy configuration

The Policy Engine evaluates threat candidates against configured policies in a strict priority hierarchy. The first matching policy determines the action.

  1. Blocklists/Allowlists — Highest priority. Known numbers, domains, apps. Immediate decision without further evaluation.
  2. Profile Rules — Family profiles (child, teen, senior, custom) define profile-specific thresholds and restrictions.
  3. Organization Policies — MDM-managed environments. Admin-defined minimum protection levels.
  4. User-Defined Thresholds — Within permitted bounds, users can adjust sensitivity.
  5. Default Policy — System baseline if no other policy matches.

Constraint: Admin policies (levels 1–3) cannot be overridden by users (level 4). This prevents an attacker from socially engineering a victim into disabling their own protection.


ActionTriggerUser ExperienceReversible?
AllowRisk score below thresholdNo visible interventionN/A
WarnRisk score in warning range (0.3–0.7 confidence)User sees context explanation + recommendation. User can proceed or abort.User can dismiss
BlockRisk score above threshold (≥ 0.7 confidence)Automatic intervention: app install stopped, permission denied, connection blockedRequires admin/guardian override (for restricted profiles)
Require ApprovalGuardian-managed profileAction paused until guardian approves or deniesTime-limited (auto-deny after timeout)
Notify GuardianAny warn/block on protected memberPush notification to all registered guardiansN/A
ContextBlock Behavior
App installationInstallation prevented. User shown explanation.
Permission grantPermission request intercepted. Explanation shown.
URL accessConnection blocked. Warning page displayed.
Remote access sessionSession prevented. Alert shown.
Active call + dangerous actionAction blocked. “Verdacht auf Betrug — legen Sie auf” alert.

ProfileProtection LevelApp Approval RequiredSideload PolicyChange Lock
ChildMaximumYes (guardian approval)BlockedYes (guardian-only changes)
TeenElevatedConfigurableWarn + guardian notificationConfigurable
SeniorElevatedConfigurableBlocked or warnYes (guardian-only changes)
Adult (default)StandardNoWarnNo
ExpertMinimalNoAllowNo
CustomUser-definedConfigurableConfigurableConfigurable
CapabilityChildTeenSeniorAdultExpert
Override warnNoConfigurableNoYesYes
Override blockNoNoNoConfigurableYes
Disable protection modulesNoNoNoNoYes
View threat detailsNoConfigurableYesYesYes
Modify policiesNoNoNoLimitedFull

Entry TypeExampleScope
Phone numbers+49 30 123456Call protection
Contact groups”Family”, “Work”Call + message protection
Appscom.teamviewer.hostRemote control protection
Domainssupport.example.comNetwork protection
Number ranges+49 30 *Call protection

FieldTypeRequiredDescription
policy_idstringYesFormat: pol_...
namestringYesHuman-readable display name
threat_categoriesarray[enum]YesApplicable threat types
actionenumYesallow, warn, block
confidence_thresholdfloatNoMinimum confidence to trigger (default: profile-based)
enabledbooleanYesActive/inactive
priorityintegerYesEvaluation order within tier
profile_idstringNoLinked profile (if profile-scoped)

Workspace note: the current workspace does not yet expose the full policy-management surface described here, so this schema should be treated as target-state documentation rather than a stable runtime contract.


PropertyDescription
DeterministicSame inputs → same outputs. No randomness in policy evaluation.
AuditableEvery decision logged with policy reference, inputs, and outputs.
Fail-closedUnparseable policy → Block (default action). Never fails to Allow.
Policy integrityPolicy files checksummed at load. Manipulated files rejected.
Privilege hierarchyAdmin policies cannot be overridden by users. Prevents attacker from disabling victim’s protection via social engineering.
No lockoutSystem prevents configurations that would lock the user out of their device entirely. Essential device functions always accessible.

ScenarioResolution
Blocklist says Block + Allowlist says AllowBlocklist wins (evaluated first)
Profile says Block + User says AllowProfile wins (higher priority)
Organization says Warn + Profile says BlockMost restrictive action wins (Block)
Two policies at same priority matchMost restrictive action wins
No policy matchesDefault policy applies

FailureImpactMitigation
Policy file corruptedCannot evaluate policiesFail-closed: default to Block for all threats. Agent logs error.
Policy file missingNo policy configurationSystem defaults applied. User notified.
CRE unavailableNo compound risk scoresIndividual signal scores evaluated directly against policies.
Profile misconfiguredOver-blocking or under-blockingConfiguration validation at save time. Invalid configurations rejected.
Conflicting policiesAmbiguous actionMost restrictive action wins. Conflict logged for admin review.