A managed device is one whose security state and configuration an organization administers and can verify. In access decisions, management becomes a condition alongside identity, clearance, time, and on-call status. section 6.2.1 section 13.3.3
Deployment access after hours
An engineer may deploy from a managed device during business hours when sufficiently cleared. At 10 p.m., the request also requires on-call status; an unmanaged device fails the baseline requirement regardless of the engineer’s other attributes. section 6.2.1
Managed-device requirements support zero-trust authorization when policy engines evaluate them at request time. For employees, a policy enforcement point can verify an identity token together with a signed posture token; customer-managed devices may instead rely on the customer’s identity provider and tenant-scoped authorization. section 9.0 section 13.3.3
Table 6.3 Attribute evaluation matrix for ABAC-based deployment access at ACME Corp
| Scenario |
clearance_level |
device_managed |
hour_of_day |
on_call |
Decision |
|---|---|---|---|---|---|
| Engineer deploying at |
High |
true |
22 |
true |
|
| Engineer deploying at |
High |
true |
22 |
false |
|
| Engineer deploying at |
Medium |
true |
14 |
false |
|
| Engineer deploying at |
High |
true |
14 |
false |
|
| Engineer deploying at 10 a.m. on a managed device |
High |
true |
10 |
false |
|
Compare clearance, device management, time, and on-call status across deployment requests to see how layered policy produces allow or deny decisions. section 6.2.1



