Center --> Personnel Device:
personnel device software install/upgrade
Definitions
personnel device software install/upgrade (Information Flow): This flow supports installation and update of software residing in Personnel Devices. It supports download of the software installation files, including executable code and associated support files.
Center (Source Physical Object): This general physical object is used to model core capabilities that are common to any center.
Personnel Device (Destination Physical Object): 'Personnel Device' represents devices used by emergency personnel or maintenance and construction personnel in the field. In the case of emergency personnel, the devices would include body cameras or smartphones (and their peripherals) that can be used by emergency personnel to provide images or video as well as send or receive data regarding the incident. The devices could also be used for incident scene safety messages to the personnel. In the case of maintenance and construction field personnel, the devices could be cellular phones or specialized safety devices that would be used for work zone safety messages to the personnel.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
- TUF - Secure Wireless Internet (ITS) (4)
- Proprietary Data - Proprietary Comm (16)
- (None-Data) - Secure Wireless Internet (EU) (32)
Selected Solution
Solution Description
ITS Application Entity
Proprietary |
Click gap icons for more info.
|
||
Mgmt
Proprietary |
Facilities
Proprietary |
Security
Proprietary |
|
TransNet
Proprietary |
|||
Access
Proprietary |
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Destination |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | High | High | Moderate | |
Basis | PID control, configuration and software/firmware update should all be protected from view. A hostile third party could use this information to reverse engineer control/configuration/update processes, and use that information in an attack across a broad swatch of similar devices, which would have severe effects to the installed base. | PID control, configuration and update need to be correct or the PID may be misconfigured, which for some applications could have severe safety impacts. | PID control, configuration and update needs to be available; however the availability requirement is probably less than Integrity, as without this flow the PID can continue to operate. The exception would be post-cyber attack, when this flow becomes critical. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |