GEISA Specification 0.8.2-69bc3f7

Contents:

• 1. Abstract
• 2. Contributors
• 3. License
  • 3.1. Community Specification License 1.0
• 4. Introduction
• 5. References
• 6. Glossary
• 7. Design Principles
  • 7.1. Interoperability
  • 7.2. Constrained Environment
  • 7.3. Minimal Implementation
  • 7.4. Core Specification with Extensions
  • 7.5. Security
• 8. Operations
  • 8.1. Purpose and Scope
  • 8.2. Roles and Authorities
  • 8.3. End-to-End Operational Context
  • 8.4. Operational Capability
  • 8.5. Device Onboarding and Management Overview
  • 8.6. Application Approval and Deployment Overview
  • 8.7. Off-Device Communication Approval
  • 8.8. Application Activation and Runtime Visibility
  • 8.9. Operational Reporting and Visibility
  • 8.10. Utility and Enterprise Interaction Points
  • 8.11. Application Certification
  • 8.12. Future Considerations
• 9. System Architecture
  • 9.1. General Architecture
  • 9.2. Application Isolation
    • 9.2.1. Application Manifest
    • 9.2.2. Networking Control
    • 9.2.3. API Control
    • 9.2.4. Container Resource Management
• 10. Conformance
• 11. Hardware Expectations
  • 11.1. Metrology
  • 11.2. Sensors
  • 11.3. Actuators
• 12. Application & Device Management
  • 12.1. OMA Lightweight M2M
  • 12.2. Bootstrapping
  • 12.3. Registration
  • 12.4. Application Manifests
  • 12.5. Device Management
  • 12.6. Firmware Management
  • 12.7. Application Management
    • 12.7.1. Software Management
  • 12.8. Application Messaging and Configuration
• 13. Linux Execution Environment
  • 13.1. Operating System
  • 13.2. Application Isolation
    • 13.2.1. Isolation Requirements
    • 13.2.2. Container Image Requirements
  • 13.3. Linux Base Libraries
  • 13.4. Core Services
  • 13.5. Base Filesystem
    • 13.5.1. Filesystem Mounts
    • 13.5.2. Utilities and Environment
    • 13.5.3. GEISA Components
    • 13.5.4. Base Libraries
    • 13.5.5. Construction of the Filesystem
    • 13.5.6. Example Filesystem Construction
• 14. Virtual Execution Environment
  • 14.1. Virtual Execution Runtime
    • 14.1.1. Processing Unit
    • 14.1.2. Scheduler
    • 14.1.3. Java Language Support
    • 14.1.4. C/C++ Language Support
    • 14.1.5. Multi-Sandbox Execution Control
    • 14.1.6. Security Manager
  • 14.2. Virtual Base Libraries
• 15. Application Programming Interface (API)
  • 15.1. API Architecture
    • 15.1.1. Message bus communication
    • 15.1.2. Message bus connection and credentials
    • 15.1.3. Message bus topics and reliability
    • 15.1.4. Non-message bus communication
  • 15.2. API Catalog Reference
    • 15.2.1. API Topic and Permission Catalog
  • 15.3. Platform Discovery
    • 15.3.1. Hardware, Firmware, and Platform Software
    • 15.3.2. Application Information
    • 15.3.3. Metrology Hardware
    • 15.3.4. Sensor Hardware
    • 15.3.5. Network Hardware
    • 15.3.6. Waveform Discovery
    • 15.3.7. Application Deployment Manifest
  • 15.4. Platform and App Status
    • 15.4.1. Runtime Mode
    • 15.4.2. Urgent Platform Updates
    • 15.4.3. Application Updates
    • 15.4.4. Timestamps
    • 15.4.5. Application Status
    • 15.4.6. Connectivity Updates
  • 15.5. Instantaneous Data
    • 15.5.1. Summary
    • 15.5.2. MQTT Details
    • 15.5.3. API Permissions
    • 15.5.4. Transaction Data
  • 15.6. Waveform Data
    • 15.6.1. Baseline Stream Requirement
    • 15.6.2. Device Capabilities
    • 15.6.3. API Request Response
    • 15.6.4. Data Format
    • 15.6.5. MQTT Details
    • 15.6.6. API Permissions
    • 15.6.7. Transaction Data
    • 15.6.8. Examples
  • 15.7. References
  • 15.8. Actuator Status & Control
    • 15.8.1. Summary
    • 15.8.2. Permission and safety model
    • 15.8.3. Actuator targets
    • 15.8.4. Getting actuator status
    • 15.8.5. Setting actuator state
    • 15.8.6. MQTT Details
    • 15.8.7. API Permissions
    • 15.8.8. Transaction Data
    • 15.8.9. Notes
  • 15.9. Sensors
    • 15.9.1. Scope
    • 15.9.2. Sensor Discovery Model
    • 15.9.3. Geolocation Metadata
    • 15.9.4. Sensor Type Enumeration
    • 15.9.5. Runtime Data Model
    • 15.9.6. Sensor Value Model
    • 15.9.7. Read Request and Response
    • 15.9.8. MQTT Details
    • 15.9.9. API Permissions
    • 15.9.10. Transaction Data
    • 15.9.11. Notes
    • 15.9.12. References
  • 15.10. Off-Device Communication
    • 15.10.1. Message-based via LwM2M
    • 15.10.2. IP socket based to local devices, private clouds, or public clouds
    • 15.10.3. Interface Types
    • 15.10.4. Destination Classes
    • 15.10.5. Network State
    • 15.10.6. Volume Limits
    • 15.10.7. Security considerations
    • 15.10.8. Connectivity
    • 15.10.9. Policy Rules
    • 15.10.10. DNS
    • 15.10.11. Local Endpoint Considerations
• 16. Security
  • 16.1. Responsibilities
    • 16.1.1. Shared Responsibility Model
    • 16.1.2. GEISA Responsibilities
    • 16.1.3. Implementer Responsibilities
  • 16.2. Threat Model
    • 16.2.1. Software Provenance and Deployment Authorization
    • 16.2.2. Lifecycle Trust Enforcement
    • 16.2.3. Trust Revocation and Credential Lifecycle
    • 16.2.4. Assets Requiring Protection
    • 16.2.5. Trust Boundaries and External Interfaces
    • 16.2.6. Threat Actors Considered
    • 16.2.7. Representative Threat Scenarios
    • 16.2.8. Unauthorized Use of Local Service Interfaces
    • 16.2.9. Compromise of a Customer-Network Connected Device
    • 16.2.10. Malicious or Altered Software Introduced During Update
    • 16.2.11. Remote Exploitation of Exposed Services
    • 16.2.12. Insider Abuse of Authorized Privileges
    • 16.2.13. Coordinated Manipulation Across Multiple Devices
  • 16.3. Interpretation of Conformance
  • 16.4. Security Capability Expectations
    • 16.4.1. Identity and Authentication
    • 16.4.2. Authorization and Policy Enforcement
    • 16.4.3. Integrity Protection
    • 16.4.4. Isolation of Workloads
    • 16.4.5. Secure Lifecycle Management
    • 16.4.6. Protection of Data
    • 16.4.7. Auditability and Visibility
    • 16.4.8. Resilience and Availability
• 17. Revision History