Workflows · Device compliance

Push disk encryption to every managed laptop and read each one back.

Close CC6.8: push the disk-encryption profile through device management such as Kandji or Jamf Pro, read each device's state back, and send unmanaged laptops to the company as a decision.

Request early access

Example workflow. Execution requires a configured tool with provider permissions for this action; see the connection’s operation reference or bring your company tool to the demo.

Agent request

Push the disk-encryption profile to every managed laptop

A profile that restarts devices reaches laptops in use; an unmanaged laptop cannot be fixed without its owner.

Identity
device-agent · IT operations
Target
Managed laptop fleet
Cost
Recorded agent cost
Evidence
Device inventory, current encryption status, and key escrow setting

SOC 2 CC6.8

Low-risk: runs within written policy.

CC6.8: Endpoint protection

Read-back

Per device: encryption status as installed on the device, not as sent.

Receipt

The device inventory with each state before and after, the profile pushed, key escrow status, and the re-run of the CC6.8 test.

Policy decision

Disk-encryption profiles run within written policy. A profile that restarts devices requires the IT owner.

Approver

IT owner

Dex, raising a card that asks for approval

The action waits until this owner approves or denies it.

Approved

Tool call resumes

Device management installs the profile, Deixic reads each device's state back, and the receipt attaches to the CC6.8 test.

Denied

Tool call stays blocked

Dex, holding up a stop after an action was denied

No profile is pushed and the affected laptops go to the IT owner as a decision.

Execution order

The agent request stops before the connected tool runs.

  1. 01Device agent requests the profile push
  2. 02Deixic checks the inventory, the profile, and policy
  3. 03The profile runs within policy, or the IT owner decides
  4. 04Connected device management returns the install result
  5. 05Deixic reads each device back and attaches the receipt to CC6.8

Activity history keeps the request, decision, cost, and result.

Keep the procedure for the next request.

Keep the policy and decision history, save the steps and evidence as a skill, and test changes on real sessions; an approval stays specific to its request.

Reusable skills · Tests and replay

Put this action under policy.

Request early access.