Direct answer
Device Identity, in this operator guide, is limited to the following inspected scope. Logical and physical identification of an IoT device for cybersecurity management. Current Maha client-credential identity and authorization behavior. The answer carries the source boundaries forward and does not infer authority from a neighboring topic.
Operator checklist, failure states, and rollback
Tell the operator what to check before acting, when to refuse, and how to preserve evidence of the outcome.
The guide cannot infer that a device, service, source, or credential is healthy when observation is unavailable.
Applied scope: Logical and physical identification of an IoT device for cybersecurity management. Current Maha client-credential identity and authorization behavior.
Definition and operating context
The canonical concept owner is maha-os. This route may apply consent; it cannot redefine or inherit the authority of its canonical owner.
This property may publish private-system architecture, consent controls, operator guidance. It must not publish medical diagnosis or cloud-first defaults presented as private.
Evidence and exact locators
IoT Device Cybersecurity Capability Core Baseline — Section 2 and Table 1, Device Identification. Establishes: Logical and physical identification of an IoT device for cybersecurity management.
Agent client credential authorization — credential fingerprint, client binding, status, and authorization checks. Establishes: Current Maha client-credential identity and authorization behavior.
What the evidence does not establish
The baseline is a manufacturer-oriented IoT starting point, not universal device identity or proof that a device has not been substituted.
Repository behavior is implementation evidence, not an independent security certification.
This route must not claim medical diagnosis.
This route must not claim cloud-first defaults presented as private.
Related definitions and applications
same-topic-application: https://www.maha-os.com/knowledge/private-machine-systems/device-identity/definition
canonical-family-owner-definition-first: https://www.maha-os.com/knowledge/private-machine-systems/health-data-consent/definition
same-topic-application: https://www.maha-os.com/knowledge/private-machine-systems/device-identity/failure-mode
same-topic-application: https://www.maha-os.com/knowledge/private-machine-systems/device-identity/controls
property-home: https://www.maha-os.com/
same-topic-application: https://www.maha-os.com/knowledge/private-machine-systems/device-identity/architecture
Questions this page can answer
What does Device Identity mean in this bounded context?
Device Identity, in this operator guide, is limited to the following inspected scope. Logical and physical identification of an IoT device for cybersecurity management. Current Maha client-credential identity and authorization behavior. The answer carries the source boundaries forward and does not infer authority from a neighboring topic.
Which inspected sources support this operator-guide answer?
IoT Device Cybersecurity Capability Core Baseline (NISTIR 8259A, May 2020), at Section 2 and Table 1, Device Identification, supports logical and physical identification of an IoT device for cybersecurity management. Agent client credential authorization (repository source inspected 2026-09-05), at credential fingerprint, client binding, status, and authorization checks, supports current Maha client-credential identity and authorization behavior.
What does the evidence not establish?
The baseline is a manufacturer-oriented IoT starting point, not universal device identity or proof that a device has not been substituted. Repository behavior is implementation evidence, not an independent security certification. Property boundary: This route may apply consent; it cannot redefine or inherit the authority of its canonical owner.
Which definition or canonical owner must be read first?
Read the maha-os definition at https://www.maha-os.com/knowledge/private-machine-systems/health-data-consent/definition first. The present page applies that definition through its narrower route role.
What source, policy, implementation, or release change would require revision?
Re-evaluate this page when a cited source, locator, governing instrument, local implementation, or canonical definition changes. Publication also requires a matching exact-revision review and active canonical release.