Request Demo
ZENQIX Control
Preview

Remote actions

Dispatch structured administrative actions through capability, authorization, maintenance and verification controls.

AvailabilityPreview
WorkflowDiscover → Act → Verify → Prove
Evidence model6 evidence elements
EvaluationAcceptance checklist
Operational need

What the administrator needs to solve.

A remote command that returns exit code zero does not prove that the intended endpoint state changed. Raw shell access also creates unnecessary injection and governance risk.

Current approach

How ZENQIX handles it.

ZENQIX models administrative work as typed actions and jobs, with capability checks, policy controls, bounded execution and a separate verification result.

Workflow

Requested action and verified outcome stay separate.

01Define the requested state
02Check authorization and endpoint capability
03Dispatch a structured action
04Execute through the platform provider
05Verify observed state
06Record evidence
Capability

What is currently in scope.

Structured job model

Capability-aware dispatch

Timeout and cancellation foundations

Duplicate execution protection

Verification-aware result model

Platform status

Availability by operating system.

WindowsPreview

Isolated provider/action tests; physical destructive-action QA pending.

macOSPreview

Isolated provider/action tests; physical destructive-action QA pending.

LinuxPreview

Isolated provider/action tests; physical destructive-action QA pending.

Synthetic product model

Inspect the state the UI needs to expose.

This panel uses synthetic data. A genuine ZENQIX Endpoint screen can replace it only after sanitization and publication approval.

Open Product Proof
ZENQIX Endpoint · Remote actionsPreview
Requested / observed stateCapability-specific endpoint state
EvidenceTimestamped, bounded and tenant scoped
VerificationShown separately from execution

Security

  • No shell evaluation for structured actions
  • Tenant isolation
  • RBAC
  • Idempotency/duplicate suppression
  • Bounded output

Evidence

  • Requested action
  • Authorization context
  • Dispatch attempt
  • Provider result
  • Verification result
  • Timestamps

Technical detail

  • At-least-once transport is handled with idempotency rather than assuming exactly-once networking
  • Physical destructive actions remain outside automated website claims until QA is complete
FAQ

Technical questions for this capability.

Can ZENQIX execute arbitrary shell strings as structured actions?

Structured operations use typed parameters rather than concatenated shell commands. Scripts remain a separate explicit action type.

Does dispatch success mean the action succeeded?

No. Dispatch, execution and verification are separate states.

Evaluate remote actions in your environment.

Use the capability matrix and the written acceptance checklist to confirm whether the current status matches your pilot needs.